Anchoring

Publication of an attestation batch’s Merkle root on a ledger we do not control. That is what makes precedence assertable: without anchoring, a signature only proves that a key holder signed, not that they did so before today. The anchor driver is pluggable — a local driver exists so the stack runs offline, and it anchors nothing in the above sense.

Related notions

What the blog says

  • Who Owns the Proof?

    Elinor Ostrom (Nobel 2009), the governance of the commons, and the question that killed the agricultural-data platforms: proof whose value lies in its mass can only belong to those who create it.

  • Everything Was Fine the Day Before

    Taleb’s turkey, the optimization that hides its trade-off, the aviation industry that learns: why an opaque chain breaks silently, then all at once.

  • A Proof Is Not a Fact. It Is a Path.

    What makes a proof is neither sincerity nor precision, but continuity: a chain of transformations in which every link remains reversible.

  • Who Keeps the Register?

    Power does not reside in knowledge but in the place where inscriptions converge. The real question is not “do we need a register”, but who audits it.

  • Signer, relier, publier

    Un système de preuve fait trois choses distinctes. Pourquoi la signature vient d’abord, pourquoi relier fait le vrai travail, et à quel moment une chaîne devient nécessaire.

Where it is implemented

  • lib/onchain-anchor.ts
Canonical identifier: https://veratrace.xyz/ontology#Ancrage