Skip to main content

Network Topology

A blockchain is not just software — it is a network of machines working together. Understanding who does what in the Specter network helps you understand how the system stays healthy, fast, and private.

The Players​

Validators​

Validators are the backbone of the network. They run CometBFT consensus, propose blocks, vote on block validity, and collectively maintain the canonical state of the chain. Each validator stakes GHOST tokens as collateral — their skin in the game that incentivizes honest behavior.

Validators communicate with each other in a peer-to-peer mesh, gossiping transactions and participating in consensus rounds. The validator set is permissionless: anyone with sufficient stake can join.

Relayer Services​

Privacy creates a unique infrastructure challenge. When commitments are stored as hashes in a Merkle tree, someone needs to maintain the full tree so that users can generate proofs against it. That is where relayer services come in.

Relayer services are off-chain infrastructure that supports the privacy layer:

  • Merkle Tree Indexer: Watches the chain for new commitments and maintains the complete Poseidon Merkle tree off-chain. Without this, users would need to reconstruct the entire tree themselves to generate a proof.
  • Commitment Hasher: Pre-computes hashes for efficient tree updates, keeping the indexer fast even as the tree grows.
  • Proof Generator: Helps thin clients (like mobile wallets) generate zero-knowledge proofs without needing the full proving key locally. This is a convenience service — users with sufficient hardware can always generate proofs themselves.
  • Bridge Relay: Monitors external chains (Ethereum, Base, Arbitrum) for deposit events and relays them to Specter, and vice versa. This is the heartbeat of the Hyperlane bridge system.

Relayer services are designed to be run by multiple independent operators. While a single relayer going offline would degrade user experience, it would not compromise security — the chain continues to operate, and users with local tree data can still generate and submit proofs directly.

Clients​

Clients are the user-facing layer. This includes web-based dApps at specter.foundation, mobile wallets, and standard Ethereum wallets like MetaMask. Clients connect to validators via JSON-RPC (just like on Ethereum) and to relayer services for Merkle tree data and proof generation assistance.

Because Specter is fully EVM-compatible, any Ethereum client library — Ethers.js, Viem, Web3.js — works out of the box.

External Chains​

Specter does not exist in isolation. Through the Hyperlane bridge, it connects to Ethereum, Base, and Arbitrum. Bridge relay nodes monitor lock/mint events on both sides, ensuring that tokens can flow freely between Specter and the broader crypto ecosystem. Privacy does not have to mean being an island.

Resilience​

The network is designed so that no single point of failure can take down the system. Validators are distributed and incentivized by staking. Relayer services can be run by anyone. Clients can connect to any available validator. And the bridge relay is operated by multiple independent parties. Even if pieces of the infrastructure go offline temporarily, the core chain — and its privacy guarantees — remain intact.