Symbiotic Relay
- Name: Symbiotic Relay
- URL: https://github.com/symbioticfi/relay
- Category: shared-security middleware / validator-set derivation and signature-aggregation network / cross-chain attestation settlement infrastructure
- Tags: ethereum-ecosystem
- Summary: Symbiotic Relay is best cataloged as validator-set derivation, signature-aggregation, and settlement middleware rather than as a generic add-on inside Symbiotic’s broader shared-security marketplace. The current relay repositories show a distinct sub-protocol with its own offchain node network, onchain module stack, API surface, and deployment path. Its core job is to turn Symbiotic-backed operator sets into usable cross-chain attestations: derive validator sets from onchain state, collect signatures, aggregate them, and commit proofs to settlement contracts. That makes Relay a useful comparison class for other validator-sidecar and attestation layers because the real control surface is not just
restaking, but how validator sets are formed, who aggregates signatures, which proof systems are used, and how downstream apps consume those attestations. - What it does:
- Runs an offchain relay network with signer, aggregator, and committer roles layered on top of libp2p/GossipSub communication
- Derives and maintains validator sets across epochs from onchain state and keeps those sets available for downstream verification
- Aggregates validator signatures using BLS signatures or zero-knowledge-proof-based verification flows, depending on configuration and scale needs
- Exposes gRPC and optional HTTP/JSON gateway APIs so external applications can request signatures, watch proofs, and integrate relay attestations into their own workflows
- Ships a smart-contract module stack including voting-power providers, key registries, validator-set drivers, and settlement verifiers for chain-side enforcement
- Supports configurable onboarding and voting-power logic through modules such as operator whitelists/blacklists/jails, shared-vault and operator-vault models, multi-token support, and multiple stake-to-voting-power calculation schemes
- Key claims:
- The relay README describes Symbiotic Relay as distributed middleware for validator-set management, signature aggregation, and cross-chain coordination, which is the clearest reason to index it separately from Symbiotic Core
- The same README breaks the network into signer, aggregator, committer, and API-server components, showing that Relay is an operational protocol surface with its own role topology rather than a vague feature of restaking
- The contracts README says Relay is a peer-to-peer side-network designed to collect and aggregate validator signatures and maintain validator sets on settlement contracts, which sharply clarifies the mechanism
- The contract modules reveal where practical authority can concentrate: voting-power providers decide how stake becomes influence, key registries decide which keys count, settlement verifiers decide which proof systems are acceptable, and deployment scripts decide which modules are wired together on which chains
- The contracts repository supports both simpler compressed-validator-set verification and ZK-assisted verification paths, which suggests Relay is trying to scale validator attestations without collapsing every use case into one fixed verification mode
- The public README also warns that the code is still work in progress and not production-ready, which is important context: this is a technically meaningful control-plane design even though the implementation surface is still maturing
- Whitepaper: No standalone Symbiotic Relay whitepaper or litepaper surfaced in this pass. The clearest current sources were the public
relayandrelay-contractsrepositories plus the linked Symbiotic Relay docs surface; see../whitepapers/symbiotic-relay-primary-sources-2026-05-10.md. - Sources:
Internal linkages
-
Best anchors: parent stack symbiotic, fixed-shape validator-set export baseline interchain-security, and open-ended marketplace cousin karak.
-
Last reviewed: 2026-05-27 UTC