Overview
Prudra identifies blockchains by a stable string slug (for examplebase, arbitrum, tempo). The same slug is used in REST bodies, SDK Chain constants, and configuration. Each slug maps to a numeric chain id, default RPC URL (typically via Alchemy), and confirmation defaults.
Supported chains (mainnet)
| Slug | Typical chain id | Notes |
|---|---|---|
tempo | 4217 | Tempo network; MPP-oriented flows. |
base | 8453 | Coinbase L2. |
ethereum | 1 | Mainnet. |
optimism | 10 | OP Mainnet. |
arbitrum | 42161 | Arbitrum One. |
polygon | 137 | Polygon PoS. |
base-sepolia, eth-sepolia, and tempo-moderato for integration testing.
How Prudra uses chain slugs
- Provisioning —
POST /wallet-infra/master-walletsvalidateschainagainst the server allowlist. - Transfers —
fromChainandtoChainmust both be supported and have RPC configuration (orPAYMENT_STUB_MODEfor development). - Token contracts — Per-chain token addresses live in server config (
tokens.ts); unsupported pairs return422with a clear validation error.
SDK
@prudra/core exports Chain and type ChainType:
Related
- Tokens — symbols per chain.
- Token transfers — routing across chains.
- Managed wallets — one master per chain per org (subject to plan).