Time Anchoring

Anchor proofs to verifiable time without exposing internal timing infrastructure.

Time anchoring lets Fairseq proofs reference a verifiable time source while keeping internal timing infrastructure private. This gives downstream users a reliable timestamp for ordering guarantees without revealing sensitive implementation details.

What time anchoring guarantees

  • Verifiable timing: Each proof references an anchor that can be independently checked.
  • Ordering integrity: The proof ties ordering claims to a publicly verifiable time reference.
  • Auditability: Anchors can be reviewed by partners, integrators, or auditors without access to internal systems.

What proofs include

Proofs include only minimal anchor metadata, such as:

  • An anchor reference identifier
  • A time attestation linked to the proof
  • Optional commitment metadata (hashes) for audit workflows

These fields allow verification without disclosing internal scheduling, batching, or policy logic.

Deployment options

Fairseq supports multiple time‑anchoring models:

  • Hosted anchoring: Use Fairseq’s managed time‑anchoring service.
  • Self‑hosted anchoring: Run your own anchoring deployment for maximum control.
  • Custom anchoring: Integrate a trusted time source that fits your compliance or operational needs.

Privacy and trade secrets

Time anchoring is designed to keep proprietary details private:

  • No disclosure of internal timing topology
  • No exposure of batch construction or policy logic
  • Proofs share commitments, not implementation

If your ordering policy is sensitive, use a self‑hosted prover and minimize metadata to keep trade secrets protected.

Related docs

Was this page helpful? /
Back to docs