Skip to main content

Data Anchor Registry

Purpose​

Store minimal anchor metadata for Data Packages so any client can verify payload provenance.

Scope​

This contract stores anchors. It does not store payloads or compute scores.

Actors and Roles​

  • Providers anchor their own Data Packages.
  • Adapters can anchor on behalf of API providers.
  • Gateways and verifiers read anchors for validation.

State and Storage Model (High-Level)​

  • Anchor records keyed by anchorId.
  • Each anchor stores provider, sourceProvider, schemaId, window, payload hash, and URI hash.

Core Flows​

  • anchorData for provider-signed packages.
  • anchorDataFor for adapter-attributed packages.
  • Read anchors by anchorId for verification.

Protocol Guarantees​

  • Anchors are immutable once written.
  • anchorId deterministically reflects the anchored metadata.

Security Invariants​

  • Only registered providers or authorized adapters can anchor for a provider.
  • Anchor contents must match the on-chain event for verification.

Integration Notes​

  • Always verify the anchor against the DataPackage envelope.
  • Treat anchors as the source of truth for provenance.