Networks
TL;DR
- The app supports
testnetandmainnet. - Factory contracts differ by network.
- Network context determines RPC target, factory ID, token IDs, and explorer links.
Network map
| Network | Factory | RPC upstream | Explorer base |
|---|---|---|---|
| mainnet | sudostake.near | https://rpc.mainnet.fastnear.com | https://explorer.near.org |
Default request token IDs
| Network | Default USDC token ID |
|---|---|
| mainnet | 17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1 |
App behavior
- JSON-RPC requests are proxied through
/api/rpc?network=<network>. - The header shows the active network.
- Request and balance flows use token config for the active network.
Notes
- Current app UX does not expose a dedicated in-app network switch control.
- Default network is
testnetunless configured otherwise.