@sei-js/registry exports typed chain IDs, endpoints, token metadata, and wallet information for Sei Mainnet and Sei Testnet. Network and wallet data comes from the official sei-protocol/chain-registry. Token metadata comes from the community-maintained Seitrace asset list.
The package is ESM-only. Sei Mainnet and Sei Testnet are the only supported networks. The package no longer exports
CHAIN_IDS.devnet, GAS_INFO, or IBC_INFO.Installation
CHAIN_IDS
CHAIN_IDS has the canonical chain ID for each Sei network:
NETWORKS
NETWORKS has the RPC, REST, gRPC, EVM RPC, WebSocket, and explorer endpoints for each network:
provider and url fields. To implement fallback logic, you can iterate through the available providers:
@sei-js/registry no longer exports gas metadata. For EVM transactions, use eth_gasPrice and eth_estimateGas. See Gas and fees.TOKEN_LIST
The token metadata for each network includes names, symbols, base denominations, decimal exponents, images, and CoinGecko IDs:RegistryToken type, so type_asset is required. images.png, images.svg, and coingecko_id are optional. NFT entries can have an empty denom_units array. Some assets also include optional pointer_contract metadata (address plus cw20 or erc20). Identify an asset by network and base denomination, not by pointer data alone.
CHAIN_INFO
CHAIN_INFO contains Sei Mainnet metadata such as the seid binary name, Bech32 prefix, fee token, SLIP-44 coin type, and supported native wallets:
supported_wallets reflects the upstream chain registry. It is not an exhaustive list of wallets that can connect to Sei.
WALLETS
Wallet metadata includes icons, URLs, and EVM or native capability flags:evm), Keplr (native and evm), and Coin98 (native). This list is separate from CHAIN_INFO.supported_wallets, which is the upstream native-wallet list (keplr, coin98).