Spectre

Introduction

Spectre is an implementation of IBC v2, with the goal of bringing IBC beyond Cosmos.

For maximum adoptability, it needs to be practical in production. With that in mind, we've carefully designed and built Spectre to keep:

  • Trustless security
  • Fast transaction speed
  • Low cost

Basically, all the strong features offered by IBC for the Cosmos ecosystem in the first place.

Since IBC was built specifically for Cosmos, it can only support Cosmos-to-Cosmos connections. The main problem is its verification component — the Tendermint light client is too heavy to execute on any other chain. To bring IBC to a non-Cosmos chain, we turn to ZK: instead of executing the Tendermint light client there, we enforce its logic by verifying a ZK proof of the light-client circuit. The circuit is carefully built so that it is relatively light-weight, keeping the proving process fast and cheap.

Spectre is built to drop in cleanly: it integrates into the IBC stack you already run, so any chain that adopts it should expect the same IBC UX it has today.

Read in this order

Introduction (you are here)

Foundations

  1. Overview of Spectre — architecture, mechanism, and flow at a glance.
  2. IBC v2 — orientation for readers who already know IBC v1.

Implementation

  1. Design choices — hybrid ZK, and the updateClient split.
  2. Optimizations — how the proof gets fast: ECIP-batched Ed25519, SHA tricks, bucketing.
  3. Components — Light client (ICS-07) · Relayer & prover.

Performance

  1. Benchmark — measured proving time, gas, and an honest end-to-end read.

Guides

  1. Running the relayer · Integrating an ETH app · Token transfer app.

Start → Overview of Spectre

On this page