Supported Networks

OOLIN groups networks into mainnets for real asset transfers and testnets for integration testing. The following catalog highlights major networks. Confirm the networks, assets, and deposit/withdrawal scope available to your organization during onboarding.

TIP

Network support can be expanded upon customer request. Share the additional network and required assets to discuss the support scope and rollout schedule. See Network expansion requests.

Mainnets

Use mainnets for real asset deposits, withdrawals, and production services.

Major network	EVM Chain ID
Bitcoin	—
Ethereum Mainnet	1
BNB Smart Chain	56
Solana	—
TRON	—
XRP Ledger	—
Sui	—
Aptos	—
Polygon PoS	137
Avalanche C-Chain	43114
Arbitrum One	42161
Base Mainnet	8453
OP Mainnet (Optimism)	10

This catalog introduces major networks; it does not imply immediate deposit/withdrawal availability in every customer environment. Confirm the required network scope during onboarding or through an expansion request. — identifies networks that do not use an EVM Chain ID.

Ecosystem references: Major L1 networks, Ethereum L2 overview.

Testnets

Use testnets with test assets to verify address allocation, deposit tracking, balance queries, and withdrawals. Keep testnet assets separate from mainnet assets.

Network	EVM Chain ID	Native coin	Purpose
Ethereum Sepolia	11155111	Test ETH	Wallet/Digital Payment tutorials and integration testing
Base Sepolia	84532	Test ETH	Base testnet integration testing

The native coins in the testnet table are test assets used for network fees. Check each network's asset list separately for token support, including USDT. Confirm test-token provisioning and available asset/network combinations during onboarding.

Verify availability in your environment

Check this network catalog together with the active state in your integration environment. Availability of a network does not imply support for every asset or the same deposit/withdrawal capabilities.

1. Query active networks with GET /networks?is_active=true&page=1&page_size=100 and retrieve subsequent pages as needed.
2. Use GET /asset-types/{id}/networks to find networks associated with the selected asset type.
3. Query GET /assets/by-type-network with asset_type_id and network_id to verify the combination and its is_active state.
4. Allocate destinations or request withdrawals within the scope agreed during onboarding.

The network API's is_active indicates availability, not whether a network is a mainnet or testnet. Classify networks using the catalog agreed during onboarding and identifiers such as names and chain_id. Obtain network_id from your environment's API response; do not substitute the Chain IDs above.

An API integration environment and a blockchain's mainnet/testnet classification are separate concepts. Do not infer the transfer network from the Base URL's name. See Environments and Base URLs and Networks and Assets.

Display networks in wallet interfaces

After asset selection, group deposit/withdrawal networks under Mainnet / Testnet, labeling each option and the selected destination. For example, display Ethereum Mainnet · Mainnet and Ethereum Sepolia · Testnet. If a production wallet offers mainnets only, exclude testnets from its displayed options.

Deposit instructions should show the selected network classification, full address, and any required tag/memo. Withdrawal confirmation should also show the asset, network, and destination. Matching address strings or the shared coin symbol ETH do not distinguish transfer environments.

See Deposit Addresses for destination information and Issue a Deposit Address for a testnet example.