Supported Networks
DobProtocol operates across Stellar Soroban and multiple EVM-compatible chains. This page lists every supported network, its configuration, and which products are available on each.
Network Reference
Production Networks
| Network | Chain ID | Type | Explorer |
|---|---|---|---|
| Stellar Mainnet | 10 | Soroban | stellar.expert |
| Ethereum Mainnet | 1 | EVM | etherscan.io |
| Base Mainnet | 8453 | EVM (L2) | basescan.org |
| Polygon Mainnet | 137 | EVM | polygonscan.com |
Test Networks
| Network | Chain ID | Type | Explorer |
|---|---|---|---|
| Stellar Testnet | 9 | Soroban | stellar.expert (testnet) |
| Sepolia | 11155111 | EVM | sepolia.etherscan.io |
| Base Sepolia | 84532 | EVM (L2) | sepolia.basescan.org |
| Arbitrum Sepolia | 421614 | EVM (L2) | sepolia.arbiscan.io |
RPC Endpoints
Stellar
| Network | RPC Endpoint | Horizon Endpoint |
|---|---|---|
| Mainnet | https://soroban.stellar.org | https://horizon.stellar.org |
| Testnet | https://soroban-testnet.stellar.org | https://horizon-testnet.stellar.org |
Network Passphrases:
Mainnet: "Public Global Stellar Network ; September 2015"
Testnet: "Test SDF Network ; September 2015"
EVM Chains
EVM RPC endpoints are configured per network in the networks database table. Default public endpoints:
| Network | Chain ID | Public RPC |
|---|---|---|
| Ethereum Mainnet | 1 | Via MetaMask default / Infura / Alchemy |
| Sepolia | 11155111 | https://rpc.sepolia.org |
| Base Mainnet | 8453 | https://mainnet.base.org |
| Base Sepolia | 84532 | https://sepolia.base.org |
| Polygon Mainnet | 137 | https://polygon-rpc.com |
| Arbitrum Sepolia | 421614 | https://sepolia-rollup.arbitrum.io/rpc |
Product Availability by Network
Not every product is available on every network. The following table shows current availability:
| Product | Stellar Mainnet | Stellar Testnet | Ethereum | Base | Polygon | Arbitrum |
|---|---|---|---|---|---|---|
| Token Studio (Pools) | Yes | Yes | Yes | Yes | Yes | -- |
| Marketplace | Yes | Yes | -- | -- | -- | -- |
| Distributions (V1) | Yes | Yes | Yes | Yes | Yes | -- |
| Distributions (V2) | Yes | Yes | -- | -- | -- | -- |
| DobValidator | -- | -- | Yes | Yes | -- | Yes |
| DobDex | -- | -- | Yes | Yes | -- | -- |
| DobLink | Yes | Yes | Yes | Yes | -- | -- |
Stellar Soroban is the primary chain for pool operations, including V2 lazy-claim distributions and the secondary share marketplace. EVM chains support pool creation and V1 distributions, with V2 and marketplace support planned.
Chain ID Usage in the Codebase
The chain_id field appears throughout the database and API to identify which network a pool, event, or transaction belongs to. When querying or creating resources, always include the appropriate chain ID.
Database Examples
-- Find all active pools on Stellar Mainnet
SELECT * FROM pools WHERE chain_id = '10' AND deleted IS NOT TRUE;
-- Find marketplace listings on Stellar Testnet
SELECT * FROM dob_buy_sales WHERE chain_id = '9' AND is_active = true;
-- Find events for a specific pool on Ethereum
SELECT * FROM "eventRecords" WHERE pool_id = '0x...' AND chain_id = '1';
API Examples
# Query pools on Stellar Mainnet
GET /api/pool?network_id=10
# Query marketplace on Stellar Testnet
GET /api/marketplace?network_id=9
# Frontend URL with network parameter
https://home.dobprotocol.com/marketplace/pool/{address}?network_id=10
Network Configuration Table
The networks database table stores per-network configuration:
| Column | Purpose |
|---|---|
id | Chain ID (primary key) |
name | Human-readable network name |
rpc_url | Primary RPC endpoint |
horizon_url | Stellar Horizon endpoint (Stellar networks only) |
explorer_url | Block explorer base URL |
stellar_pool_wasm_hash_v1 | Deployed V1 pool contract WASM hash (Stellar only) |
stellar_pool_wasm_hash_v2 | Deployed V2 pool contract WASM hash (Stellar only) |
contract_addresses | JSON object with deployed contract addresses |
is_testnet | Boolean flag for test networks |
is_active | Whether the network is currently enabled |
Wallet Support
| Network Type | Supported Wallets |
|---|---|
| Stellar | Freighter |
| EVM | MetaMask, WalletConnect-compatible wallets |
Connecting to the Right Network
Token Studio automatically detects the connected wallet's network. For Stellar pools, users must have the Freighter browser extension installed. For EVM pools, MetaMask (or a compatible wallet) must be connected to the correct chain.
If a user's wallet is on the wrong network, the frontend prompts them to switch. For EVM chains, the application can request an automatic network switch through the wallet provider.
Adding a New Network
To add support for a new EVM network:
- Insert a row into the
networkstable with the chain configuration - Deploy the required smart contracts to the new chain
- Update the frontend network switcher to include the new option
- Configure RPC endpoints and explorer URLs
- Test pool creation, distribution, and marketplace on the new chain
For Stellar networks, the process also requires uploading the pool contract WASM and storing the hash in the networks table.