> ## Documentation Index
> Fetch the complete documentation index at: https://seilabs-docs-evm-cookbook.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Sei Network Interoperability Framework

> Understand how Sei enables seamless interaction between EVM and Cosmos ecosystems through its dual address system and precompiles.

<Info>
  **CosmWasm deployments are frozen, and IBC is disabled in both directions.** Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei. Proposals [116](https://seistream.app/proposals/116), [120](https://seistream.app/proposals/120), and [121](https://seistream.app/proposals/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](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md), [Tokenfactory is not supported](/cosmos-sdk#tokenfactory-is-not-supported), and the [SIP-03 Migration Guide](/learn/sip-03-migration).
</Info>

## 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.

Both addresses are derived from the same public key, so your assets work across
both formats. You can find your corresponding wallet addresses in the Sei
Dashboard.

For more details, read our
[article on interoperability](https://blog.sei.io/sei-v2-interoperability/).

## 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](/evm/precompiles/example-usage) section.

## Example diagram

<img src="https://mintcdn.com/seilabs-docs-evm-cookbook/IhEyu7GQ2MVOnsHK/assets/interoperability.png?fit=max&auto=format&n=IhEyu7GQ2MVOnsHK&q=85&s=87a04ee423e5a0f5a289996571b8bee8" alt="Interoperability" width="1746" height="1168" data-path="assets/interoperability.png" />

*Access to all tokens and contracts on Sei*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.