Skip to main content
CosmWasm deployments are frozen, and inbound IBC is being disabled. Per Proposal 115, no new CosmWasm contracts can be uploaded or instantiated on Sei. Proposal 116 additionally disables inbound IBC transfers, so IBC assets bridged from Cosmos chains can no longer arrive on Sei. The interoperability features described on this page apply to already-deployed CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed via precompiles. For new smart contract development, build directly on the EVM. See SIP-3 for the full migration context.

​
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.
Both addresses are derived from the same public key, ensuring seamless asset integration across formats. You can find your corresponding wallet addresses directly in the Sei Dashboard. For more details on interoperability, explore our article here.

​
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

Interoperability Enabling seamless access to all tokens and contracts on Sei