External anchors — the witnessed chain heads
NeuralRing publishes the head of its attestation chain to independent external witnesses and records their receipts in signed anchor events. This is the history. It proves WHEN a head existed — never where inference ran, never what a provider is.
loading…
Archive these heads
Every independent copy you keep is one more witness: if two auditors are ever shown two chains, the same anchor number with a different head hash is the proof. The public feed is at /.well-known/neuralring-anchors.json.
Verify this yourself
Zero dependencies (node:crypto only). Export your records, download the anchors and the receipts, then:
node scripts/verify-anchors.mjs export.json anchors.json receipts/ openssl ts -verify -digest <headHash> -in receipts/anchor-<n>-rfc3161-<tsa>.tsr -CAfile <TSA root>
What an anchor proves — and does not
- Proves: WHEN a chain head existed (no later than the witnessed moment recorded by each witness) and that every auditor sees the one chain (split-view detectable).
- Does not prove: where inference ran, what a provider is, or the quality of any claim. An anchor raises no assurance level, tier, ring or SEAL objective.
- RFC 3161 stamps are labelled qualified (eIDAS Art. 41) or non-qualified per TSA; a non-qualified stamp is never shown as qualified. The in-app parser structure-checks a token; openssl ts -verify is the cryptographic path.
- A witness failure is a recorded gap, never filled; if every witness failed the segment is unanchored and says so.