Action required: IBC assets on Sei will become inaccessible If you hold USDC.n (USDC via Noble), USDT.kava (Kava USDT), Wormhole-bridged tokens, or any other IBC asset on Sei, you must swap, migrate, or bridge out before the governance proposal to disable inbound/outbound IBC transfers passes and is activated to avoid permanent loss of access. After this, Sei will no longer support IBC bridging of assets from Cosmos-based chains to and from Sei Network. Consult the SIP-03 Migration Guide for the full list of affected assets, required actions, and supported routes. For USDC.n specifically, see: Holders of USDC.n Need to Swap or Migrate.
Interact with native Sei chain features — staking, governance, native token balances, and more — from EVM applications
Sei exposes native chain functionality through precompiled contracts at deterministic EVM addresses. You can call them from any EVM library (viem, ethers, wagmi) using the ABIs exported from @sei-js/precompiles — no special SDK required.Available precompiles include:
Bank — query native denom balances (usei, factory tokens)
Precompiles are callable like any contract — even with a plain eth_call from the browser. This hits the Bank precompile at 0x0000000000000000000000000000000000001001 on Sei mainnet, calling name("usei"). The response is ABI-encoded; it contains the bytes 53 45 49 — ASCII for SEI.For installation instructions, code examples (viem and ethers), common patterns, and a full working Node.js script, see the precompiles reference:
Precompile Example Usage
Usage examples for all precompiles with viem and ethers — Bank, Staking, Distribution, Governance, JSON, and P256.
For the full ABI reference and every available function on each precompile: