Supported blockchains
Pick a tab to check blockchain support for each capability or adapter.- Capabilities
- Adapters
Chain identifiers
For most blockchains, the identifier is the blockchain name with any spaces replaced by underscores (for example, Arc Testnet →Arc_Testnet). Identifiers
are case-sensitive and match the BridgeChain enum exported from
@circle-fin/app-kit:
Discover supported blockchains programmatically
You can usegetSupportedChains() instead of hardcoding the preceding tables.
The method returns ChainDefinition[] (name, type, isTestnet, explorer URL,
protocol config, and related fields) for the blockchains your kit currently
supports.
App Kit SDK
Pass an optionaloperationType to narrow by capability:
operationType. Bridge filters are
available on the standalone Bridge Kit. Unified Balance
forwarder filters are available on the namespaced API:
getSupportedChains
in the SDK reference.
Standalone kits
If you import a kit package directly, callgetSupportedChains() on that kit.
Each package accepts different optional filters:
- Bridge Kit:
chainType,isTestnet,forwarderSupported - Swap Kit: none—filter the returned array yourself
- Unified Balance Kit:
forwarderSupportedas"source"or"destination"
Supported tokens
You can specify either a contract address or an alias for any
supported token.
- Send: Any token. Use token aliases for common tokens or the token’s contract address for other tokens.
- Bridge: USDC only.
- Swap:
- Any tokens with enough liquidity to trade with major stablecoins such as USDC, EURC, USDT, USDe, DAI, and PYUSD.
- Native tokens on blockchains where Swap is supported.
- On Arc Testnet, only USDC, EURC, and cirBTC.
- Unified Balance: USDC only.
Token aliases
App Kits works with any supported token when you supply the contract address. For convenience, you can use the following aliases for the most common tokens instead:USDCEURCUSDTUSDeDAIPYUSDcirBTCNATIVE: Uses the blockchain’s native token.