Networks and tokens
Tempo Mainnet and Moderato settings, supported token addresses, Robinhood testnet details and mainnet migration guidance.
Network configuration
| Network | Chain ID | RPC |
|---|---|---|
| Tempo Mainnet | 4217 | https://rpc.tempo.xyz |
| Tempo Moderato | 42431 | https://rpc.moderato.tempo.xyz |
| Robinhood Chain Testnet | 46630 | https://rpc.testnet.chain.robinhood.com |
The dashboard and hosted payment API use Tempo Mainnet. Robinhood testnet is used only for the membership pilot. Public RPC providers can impose rate limits; configure a suitable provider for your application's workload.
Supported mainnet tokens
| SDK symbol | Address | Decimals |
|---|---|---|
| PathUSD | 0x20c0000000000000000000000000000000000000 | 6 |
| USDC.e | 0x20c000000000000000000000b9537d11c60e8b50 | 6 |
The on-chain pathUSD symbol is normalized as PathUSD in SDK examples. USDC.e is bridged USDC. Verify the network and address when funding a wallet; similarly named assets on another network are not interchangeable.
Explicit testnet development
const agent = new TempoKey({
network: "testnet",
privateKey: process.env.TESTNET_AGENT_KEY,
rootAddress: process.env.TESTNET_OWNER_ADDRESS,
});The testnet SDK registry supports PathUSD, AlphaUSD, BetaUSD and ThetaUSD. Testnet authorization does not carry over to mainnet. The hosted API has no per-request network switch; use a separate testnet API instance for integration tests.
Migrating from testnet
- Install the SDK 0.3 build and choose your network explicitly.
- Fund the owner on Tempo Mainnet.
- Create and authorize a fresh mainnet agent key.
- Register that key with the hosted API if you use HTTP execution.
- Update scripts, token addresses and explorer links; check health.chainId before automation.
Mainnet browser storage uses its own namespace. The API stores mainnet records separately from legacy testnet records. Old data is retained but is not automatically imported. An API RPC override is checked against the configured chain during startup.