This page is a conceptual overview of how EVM and native execution interact. For the canonical compatibility matrix and JSON-RPC notes, see EVM Compatibility. For exact precompile signatures, see Precompile ABI Reference.
What stays familiar
| Area | Behavior |
|---|---|
| Contracts | Solidity bytecode deploys and executes through the EVM. |
| Wallets | EVM-compatible wallets sign and submit transactions for chain ID 2184 on mainnet. |
| Tooling | Foundry, Hardhat, Remix, ethers, viem, and web3.js use standard EVM RPC flows. |
| Receipts and logs | EVM transactions produce Ethereum-compatible receipts, status fields, logs, and bloom filters. |
| Token standards | ERC-20, ERC-721, ERC-1155, and ordinary Solidity interfaces work as expected. |
What is extended
| Extension | Why it exists | Learn more |
|---|---|---|
| Native module access | Contracts can query or invoke selected Cosmos module behavior without reimplementing it in bytecode. | Modules & Precompiles |
| Cross-chain verification | Contracts can participate in IBC and proof-carrying cross-chain flows. | Cross-chain Verification |
| Cryptographic verification | Contracts can verify signatures, proofs, and randomness more efficiently than pure Solidity. | Cryptographic Verification |
| Hashing and data utilities | Contracts can use native hashing and structured-data helpers. | Hashing, Data Ergonomics |
EVM and Cosmos transaction paths
| Transaction path | Submitted through | Executes in | Typical reader |
|---|---|---|---|
| EVM transaction | eth_sendRawTransaction or wallet RPC | EVM, with optional precompile calls into native modules | Solidity developers and dapps |
| Cosmos SDK transaction | Cosmos transaction broadcast | Cosmos SDK module handlers | Operators, module integrators, Cosmos tooling |
| EVM precompile call | EVM transaction calling a fixed precompile address | Native implementation behind an EVM-compatible call boundary | Hybrid EVM/Cosmos applications |
Practical rules
- Treat precompiles as system interfaces: use the documented addresses and ABI reference for signatures.
- Keep exact method signatures in Precompile ABI Reference; Learn pages should explain when and why to call a precompile.
- Estimate gas against the target network because native execution and SDK metering can affect costs.
- Use EVM Compatibility for compatibility differences and JSON-RPC API for method availability.