Skip to main content

The specifications are written

CoRelayer
CoRelayer
Cooperative Relayer Infrastructure for Autonomous Transactions

The six core specifications that define CoRelayer are complete and are now the source the code, the types and this documentation are generated from.

What was fixed​

SpecificationWhat it settles
APIEvery route, every schema, the authentication rings, the rate limits, idempotency, pagination, and the full error catalogue. Version 1.0.0-draft.1.
ContractStorage, roles, the five pause scopes, the deposit flow, the event schema, the invariants.
PricingThe Relay Unit formula, the tariff and its guard rails, the tier ladder, deposits, the plan lifecycle.
Relay intentThe lease, the validation pipeline, the commit point, the intent state machine, the re-sign ladder.
SettlementHow usage is reported back to the contract and bounded.
DistributionThe relayer registry, weights and the payment split.

Decisions worth naming​

  • One price lever. A single integer on chain — micro-USDC per Relay Unit, initially 10,000 — from which every price is derived. No second value carries a USDC price anywhere in the system. (The tariff)
  • One signature per action. No multi-variant signing exists anywhere in the product. The SDK enforces it structurally rather than by convention. (One signature)
  • Errors are addresses. Every error is an RFC 9457 problem document whose type is a page on this site. A code that exists in the API without a page fails the documentation build. (Error catalogue)
  • Milliseconds, and no keeper. Every time value is milliseconds of block time, and every schedule activates lazily when somebody next touches the state. Nothing depends on a job running at the right moment. (Timestamps)
  • Measured numbers only. No SLA percentages and no service credits at launch, because there is nothing measured to base them on. (Status and SLOs)

What this means for an integrator​

The API document is the contract: /openapi.yaml. Client types are generated from it, this reference is generated from it, and the plain-Markdown summary agents read is generated from it. Nothing hand-writes a response shape, in any of the three.