Skip to main content

EVM Blockchains

WalletConnect namespace: eip155.

Chains are offered according to the user’s mainnet/testnet mode. Use CAIP-2 IDs with the eip155: prefix (not eip:).

Mainnet

NetworkCAIP-2 Chain ID
Flareeip155:14
Songbirdeip155:19
Ethereumeip155:1
Arbitrum Oneeip155:42161
Optimismeip155:10
Baseeip155:8453
Polygoneip155:137
BNB Smart Chaineip155:56
XDCeip155:50
HyperEVMeip155:999

Testnet

NetworkCAIP-2 Chain ID
Flare Coston2eip155:114
Songbird Costoneip155:16
Ethereum Sepoliaeip155:11155111
Arbitrum Sepoliaeip155:421614
Optimism Sepoliaeip155:11155420
Base Sepoliaeip155:84532
Polygon Amoyeip155:80002
BNB Smart Chain testneteip155:97
XDC Apothemeip155:51
HyperEVM testneteip155:998

Methods

Supported for WalletConnect session requests:

MethodNotes
eth_accountsApproved accounts for the session
eth_requestAccountsMay prompt if needed
eth_sendTransactionSign and submit
eth_signTypedDataEIP-712
eth_signTypedData_v3EIP-712 v3
eth_signTypedData_v4EIP-712 v4
personal_signMessage signing
wallet_requestPermissionseth_accounts
wallet_watchAssetTrack ERC-20
wallet_scanQRCodeDevice QR scanner

Request chain

Session requests must include a chainId in CAIP-2 form (for example eip155:14). Bifrost does not emit EVM chainChanged / accountsChanged over WalletConnect when the user changes network in the app. Plan UI around explicit chain selection in your session namespaces.

References