Skip to content

General Attestation Layers

Problem

Off-chain agents and many L2 systems do not have a native trust layer. You cannot easily prove that a check was performed, a condition held true, or a message is safe to act on. Current approaches are permissioned, costly to extend, and lack clear economic guarantees or dispute paths.

Solution

Relay lets any agent or system produce a stake-backed, verifiable attestation about external state or completed actions. Attestations are checked on chain for quorum, freshness, and consistency, and bad behavior is slashable. Once verified, adapters can trigger actions such as mint, transfer, unlock, vote, or update state. One receipt format and one verifier work across L1s and rollups, so you can add new domains without rebuilding trust from scratch.

How it Works

  1. Register and bond. Agents or operators enroll for a task and lock stake that can be slashed.
  2. Define the condition. Specify what must be checked, the cadence or event trigger, and the dispute window.
  3. Observe and decide. Agents perform the check or computation and determine the outcome.
  4. Attest and aggregate. Agents sign the result with timing and context, and signatures are combined into one proof.
  5. Verify on chain. A verifier checks quorum, stake weight, freshness, and anti-replay.
  6. Trigger action. An adapter executes the approved action or writes the result for other contracts to consume.

Flow

Get in touch with Symbiotic Team

Application Examples

  1. L2 fast finality

Operators attest that an L2 block or batch is safe after specific checks, giving near-instant usable finality for bridges and apps while full finality catches up.

  1. Autonomous agent receipts

AI or automation agents attest to tasks they performed such as compliance checks, data validation, or workflow steps, unlocking funds or advancing pipelines only when receipts pass verification.

  1. Uptime and SLA monitors

Watchdogs attest liveness and performance of services such as sequencers or keepers and automatically apply penalties, rebates, or failover when thresholds are missed.

  1. Decentralized sequencer

A set of bonded operators attest that a given L2 block or batch is available, correctly ordered, and built under the declared rules. The attestation is stake-backed and verified on chain, then a small adapter accepts the batch, releases bridge messages, or advances state. Misbehavior such as equivocation, censorship beyond policy, invalid ordering, or missed slots can be disputed and slashed. You also get usable fast-finality receipts for bridges, liveness SLAs with automatic failover, and optional hooks to enforce fairness policies (e.g., inclusion lists or MEV limits) via the same attestation flow.

  1. Circuit-breaker signals

Publish slash-backed alerts for depeg risk, abnormal volatility, or halted markets that protocols use to tighten limits or pause actions.

References