SpectreGuides

Guide — integrating an Ethereum app

Guides · 2 of 3 — build on Spectre, or onboard your chain.

For your chain, Spectre is IBC-compatible and drops into your existing IBC stack — it sits under the Ethereum path. No migration, no new standard, no new trust assumption for users.

Build an app on Spectre

  • Implement the IIBCApp callbacks — onRecvPacket / onAcknowledgementPacket / onTimeoutPacket — and register your port on the ICS26Router. Packets are single-payload (IBC v2).
  • Access control: the relayer entrypoints (recvPacket / ackPacket / timeoutPacket / updateClient) are gated by an AccessManager (RELAYER_ROLE). Proofs are cryptographically verified regardless of caller — the gate is operational, not a trust assumption.

Onboard a new source chain

Spectre is an IBC implementation, so a source chain is a Cosmos (CometBFT) chain feeding Ethereum. Every Cosmos chain shares the same Tendermint / Ed25519 consensus, so they all reuse the same proving circuit, prover and relayer — adding one is configuration, not new cryptography:

  • point the relayer's cosmos_to_eth module at the new chain's RPC, and
  • stand up an ICS-07 Groth16 light client for it on Ethereum (via create-clients).

No new circuit and no bespoke consensus code — the Tendermint bucket circuits and the prover are chain-agnostic across Cosmos. (A fundamentally different consensus engine would need its own circuit, but that is outside the Cosmos↔Ethereum IBC path Spectre targets.)

You provide: your running IBC stack and node/RPC access for the relayer. We provide: the Spectre branch, the relayer + prover, the on-chain light client + router, and the shared Tendermint circuit — plus integration and maintenance.

On this page