Server Wallet: Networks
Per-operation network selection for CDP-managed wallets
Advanced Trade has no network concept. It always talks to the live production Coinbase exchange at
api.coinbase.com — there's nothing to select. Everything on this page is specific to Server Wallet.
Every Server Wallet operation accepts an optional network config key. Unlike Hedera-style nodes, there is no central Networks registry/options class for this node — the default network is a literal fallback coded per operation (info.Network ?? "..."), inferred directly from the executor's feature files rather than a single shared config section.
| Operation | Default network when omitted |
|---|---|
account/getOrCreate | No implicit default — whatever network the created account reports. |
account/listBalances | base (mainnet) |
account/requestFaucet | base-sepolia (testnet) |
balance/listTokens | base (mainnet) |
transfer/sendNative | base-sepolia (testnet) |
transfer/sendErc20 | base-sepolia (testnet) |
swap/execute | base-sepolia (testnet) |
swap/quote | base-sepolia (testnet) |
Read operations default to mainnet (
base); write/fund operations default to testnet (base-sepolia). Always set network explicitly in production workflows rather than relying on these fallbacks — the split exists so a misconfigured write can't accidentally move real mainnet funds, but it also means an omitted network silently changes meaning between resources.
Faucets are testnet-only
account/requestFaucet and solanaAccount/requestFaucet only work against test networks (e.g. base-sepolia) — there is no faucet on mainnet.