CosmWasm deployments are frozen, and IBC is disabled in both directions. Per Proposal 115, no new CosmWasm contracts can be uploaded or instantiated on Sei. Proposals 116, 120, and 121 disabled inbound and then outbound IBC transfers. No asset can be bridged into or out of Sei over IBC.The interoperability features on this page apply to already-deployed CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed through precompiles. Tokenfactory is not a supported development path. Do not use native-denom pointers or Bank Module interfaces to build tokenfactory integrations. For new smart contract development, build directly on the EVM. See SIP-3, Tokenfactory is not supported, and the SIP-03 Migration Guide.
Dual address support
Sei uses two distinct address types:- EVM (0x) address: Ethereum-style addresses with the “0x” prefix.
- Cosmos address: Bech32 addresses with the “sei1” prefix.
Virtual machine interoperability
EVM and existing CosmWasm smart contracts coexist on Sei, but they run in different execution environments. This is a problem for users, because their wallets typically support only one execution environment. Developers have the same problem. Existing tools and libraries can interact with only EVM or only Wasm (for example, EthersJS for EVM and CosmJS for Wasm). To connect EVM and Wasm, Sei exposes Cosmos-SDK modules and already-deployed CosmWasm contracts to the EVM through precompiled contracts. New smart contracts on Sei should be deployed directly on the EVM.Precompile contracts
Sei precompiles are smart contracts built directly into the Sei EVM environment. Users and developers can use them to access Cosmos-SDK functions through the EVM RPC interface. To learn how to use EVM precompiles, see the Example Usage section.Example diagram
