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, so no asset can be bridged into or out of Sei over IBC. The interoperability features described on this page apply to already-deployed CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed via precompiles. Tokenfactory is not a supported development path, and you should 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 utilizes two distinct address types:- EVM (0x) address: Ethereum-style addresses, with “0x” prefix.
- Cosmos address: Bech-32 addresses, with “sei1” prefix.
Virtual Machine Interoperability
EVM and existing CosmWasm-based smart contracts co-exist on Sei, but live in different execution environments. This creates a challenge for users, who use wallets that typically only support a single execution environment. Likewise for developers, existing tooling and libraries can only interact with either EVM or Wasm (Think EthersJS vs CosmJS). To bridge the gap between EVM and Wasm, Sei exposes Cosmos-SDK modules and already-deployed CosmWasm contracts to the EVM via precompiled contracts. New smart contracts on Sei should be deployed on the EVM directly.Precompile Contracts
Sei precompiles are smart contracts embedded directly within the Sei EVM environment. They provide a gateway for users and developers to access Cosmos-SDK functions through the EVM RPC interface. For instructions on utilizing EVM precompiles, refer to the Example Usage section.Example Diagram
