Immediate Finality
The L2 subnet uses CometBFT-style block commit — every committed block is final. No probabilistic waiting, no reorg risk. Cross-chain message delivery is bounded by validator checkpoint signing, not L1 reorg windows.
The Interplanetary Consensus L2 Platform
IPC is an EVM-compatible L2 that combines immediate finality, low-cost stablecoin-denominated gas, a dual EVM + CosmWasm runtime, and first-class cross-chain messaging — built for ecosystem partners that need to move fast without sacrificing architecture.
Why IPC
Four architectural decisions that separate IPC from a generic EVM L2.
The L2 subnet uses CometBFT-style block commit — every committed block is final. No probabilistic waiting, no reorg risk. Cross-chain message delivery is bounded by validator checkpoint signing, not L1 reorg windows.
Gas is stablecoin-denominated, keeping transaction costs stable and predictable for applications and their users.
Build Solidity contracts today and deploy CosmWasm contracts for richer on-chain logic when you need it — both running on the same chain, with the same block and finality guarantees.
EVM applications can call bank, staking, distribution, ERC-20, and IBC module functions directly through precompile addresses — no external bridge or wrapping contract required.
Feature highlights
Each feature maps directly to working implementation and scripted test paths.
Dispatch arbitrary byte payloads between EVM-compatible chains. Proven end-to-end via raw message and PingPong contract-to-contract round-trips.
A stablecoin ERC-20 moves between chains via a Hyperlane warp route: collateral locked on the origin, synthetic minted on the L2. Deposit and withdraw paths fully scripted.
The same chain binary exposes full EVM JSON-RPC alongside CosmWasm and Cosmos REST — one environment for Solidity and WASM contract developers.
Static precompiles for bank, staking, distribution, ERC-20, and IBC are activated at genesis. EVM contracts call chain-native functionality without wrapping.
Blockscout for EVM transaction inspection, a Hyperlane Explorer for per-message traces, and a live message-log dashboard — all opt-in via a single make target.
Docker, Foundry, and jq are the only host dependencies. No Node.js required. The entire environment — chains, agents, explorers — is brought up with one command.
All features backed by working implementation in the open repository.
How it works
Every asset transfer and arbitrary message follows the same path: dispatch, sign, relay, execute.
App calls Mailbox.dispatch() on the origin chain. Mailbox emits a message and updates the merkle tree.
Hyperlane validators observe the new merkle root and publish signed checkpoints to their storage syncer.
The relayer assembles a multisig proof from validator checkpoints and calls process() on the destination Mailbox.
The ISM verifies the proof, then the Mailbox calls handle() on the recipient contract with the original payload.
Trust and scope
We are launching our testnet and will publish connection details shortly. The architecture is built for rapid iteration — every design decision and upcoming milestone is documented openly.
Current v1 constraints
Production roadmap