Appearance
Supported blockchains
IBEx targets EVM networks for Safe smart-account flows. Use the chain identifiers below when configuring API requests.
Chain reference
| Chain | Mainnet ID | Testnet ID | Status |
|---|---|---|---|
| Ethereum | 1 | 11155111 (Sepolia) | Supported |
| Arbitrum | 42161 | 421614 (Sepolia) | Supported |
| Base | 8453 | 84532 (Sepolia) | Supported |
| Polygon | 137 | 80002 (Amoy) | Supported |
| Gnosis | 100 | 10200 (Chiado) | Supported |
| BNB Chain | 56 | 97 | Work in progress |
| Solana | 900 | 901 | Work in progress |
X-Blockchain-Id header
Most IBEx API calls that touch on-chain state or wallet deployment must target a specific network. Send the numeric chain ID in the X-Blockchain-Id HTTP header so the backend routes the request to the correct chain and RPC configuration.
Example:
http
GET /v1/example HTTP/1.1
Host: api.example.com
Authorization: Bearer <token>
X-Blockchain-Id: 11155111Replace the value with the mainnet or testnet ID from the table above. For work-in-progress chains, confirm availability in your environment before relying on this header.
Further reading
- Per-chain notes: use the links in the table.
- Wallet models: Wallets overview.