Paxeer Interoperability Framework
Understand how Paxeer enables seamless interaction between EVM and Cosmos ecosystems through its dual address system and precompiles.
CosmWasm deployments are frozen, and inbound IBC is being disabled. No new CosmWasm contracts can be uploaded or instantiated on Paxeer. Inbound IBC transfers are disabled, so IBC assets bridged from Cosmos chains can no longer arrive on Paxeer. 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.
Dual Address Support
Paxeer utilizes two distinct address types:
- EVM (0x) address: Ethereum-style addresses, with "0x" prefix.
- Cosmos address: Bech-32 addresses, with "pax1" prefix.
Both addresses are derived from the same public key, ensuring seamless asset integration across formats.
Virtual Machine Interoperability
EVM and existing CosmWasm-based smart contracts co-exist on Paxeer, 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, Paxeer exposes Cosmos-SDK modules and already-deployed CosmWasm contracts to the EVM via precompiled contracts. New smart contracts on Paxeer should be deployed on the EVM directly.
Precompile Contracts
Paxeer precompiles are smart contracts embedded directly within the Paxeer 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
Enabling seamless access to all tokens and contracts on Paxeer