Overview of Spectre
Foundations · 1 of 2 — Spectre at a glance: architecture, mechanism, and operation.
Spectre is not a new protocol — it is an implementation of IBC v2. Every component maps to a standard IBC spec; the only component we re-design is the light client. This page is the high-level overview; the subsequent pages go into implementation details.
Architecture
| Component | Where | IBC role | |
|---|---|---|---|
| Spectre client | Ethereum, on-chain | The modified ICS-07 Tendermint light client — verifies Cosmos consensus updates, packet membership, and misbehaviour. | |
ICS26Router contract | Ethereum, on-chain | The ICS-26 router — the standard IBC v2 packet lifecycle, dispatched to apps by port. | |
ICS20Transfer contract | Ethereum, on-chain | The reference ICS-20 token app — wraps Cosmos tokens as ERC-20, escrows native ETH. | |
IBC Core (ibc-go) | Cosmos, on-chain | Vanilla ibc-go — the standard Cosmos IBC core (clients, router, apps). No Spectre-specific changes. | |
Non-Cosmos chain light client (08-wasm) | Cosmos, on-chain | The connected chain's light client on Cosmos — an ICS-08 wasm client. For Ethereum, cw-ics08-wasm-eth verifies sync-committee finality (the Eth→Cosmos leg). | |
| Relayer | Off-chain | The relayer carries packets and client updates; it now integrates a Groth16 prover that generates the necessary proofs. |
ibc-goThe detail pages: Light client · Relayer & prover.
Mechanism
The light client is the heart of IBC — it verifies the data coming from a source chain. Everything else layers on top: channels define how data moves, the router how it's dispatched. The light client is what decides whether that data is true.
Spectre's innovation lives there. We re-implement the Cosmos light client — via ZK, named Spectre client, so a non-Cosmos chain can consume Cosmos data secured by the source chain's own consensus rather than a trusted intermediary.
That splits the work across the components above:
- Relayer + prover (off-chain) — carries packets and client updates, and generates the proofs.
- Light client (on-chain) — the verifier; checking a proof is the consensus check.
Even inside the light client, only the heavy part is proven in ZK — the validator-signature check; the rest runs as ordinary on-chain logic. This is the hybrid model, and it keeps the circuit small.
Beyond the Spectre client, used for Cosmos → non-Cosmos data transfer, the stack is mostly standard IBC. Take the Ethereum → Cosmos direction for example: to verify Ethereum data on Cosmos, we reuse the standard 08-wasm Ethereum light client.
Operation
Spectre operates almost identically to standard IBC — the one difference is the split in updateClient:
updateConsensusState— refreshes the validator set; runs every 24 hours.updateApplicationState— advances block state; runs on each received packet.