IBC v2
Foundations · 2 of 2 — orientation for readers who already know IBC v1.
Classic IBC (v1) connects Tendermint chains: each side runs a light client of the other and verifies the counterparty's consensus directly — trustless, no multisig in the path. Its constraint is reach. The light client is inexpensive for Tendermint↔Tendermint, but a non-Cosmos chain cannot afford to execute a Tendermint light client, so trustless IBC remained Cosmos-only.
IBC v2 is the streamlined revision of the spec, designed to cross that boundary (cosmos/ibc · IBC_V2, ibc.cosmos.network). v1's layered stack — clients → connections → channels → ports — collapses to three constructs: clients, a router, and apps. The connection and channel handshakes are removed; a packet now references a source + destination client ID (rather than a port/channel pair), carries payloads (app data + a pluggable encoding — Cosmos↔Ethereum uses ABI to reduce gas), and times out on timestamp only. That reduction is what makes IBC implementable as a contract suite on a non-Cosmos chain.
The roles you already know carry over:
| IBC v2 role | What it does |
|---|---|
| Light client (ICS-02 / ICS-07) | Holds the counterparty's trusted consensus state. updateClient advances it; verifyMembership / verifyNonMembership check whether a packet is (or isn't) committed, via ICS-23 Merkle proofs; misbehaviour freezes on conflicting headers. |
| Router (ICS-26) | The packet gateway: sendPacket → recvPacket (+ ack) → ackPacket / timeoutPacket. Routes each packet to the right app by port. |
| App (e.g. ICS-20) | Token transfer or any message app; receives onRecvPacket / onAck / onTimeout callbacks. |
| Relayer | Off-chain; carries packets and client updates between chains. Untrusted — it can only forward valid state. |
The hard part of any IBC v2 implementation is the light client on Ethereum: verifying Tendermint finality requires checking the validator set's Ed25519 signatures, which is prohibitive on the EVM. The standard solution is a ZK light client — e.g. Interchain Labs' IBC Eureka, which proves the Tendermint check in Succinct's SP1 zkVM (blog.succinct.xyz); on the Cosmos side, an 08-wasm CosmWasm light client verifies Ethereum's sync-committee finality (cw-ics08).
Spectre is a separate IBC v2 implementation of that same shape — but where Eureka proves with SP1, Spectre proves with a purpose-built Groth16 circuit. Eureka is one implementation of the spec, and our benchmark — not our base. That single substitution is the only material difference; the following pages detail how each component maps and what we modify.
Sources: IBC v2 spec · ICS-02 client semantics (IBC v2) · ICS-07 Tendermint client · ICS-04 packet semantics (IBC v2) · ibc-go docs · IBC v2 announcement · solidity-ibc-eureka · Eureka walkthrough · Succinct SP1 ZK-IBC