Snapshot-attestation coverage, disclosed.
This page reports the internal attestation rows and chain links that currently exist. Those counts can change as backfills run. No provenance fact currently links deterministically to a signature.
b01b487e5c9a… (expand)
b01b487e5c9a8f4ffded8148b32b3b5bea788504c150311171118eda245f00d4On July 12, 2026, independent validation found that 0 of 162 stored OpenTimestamps proofs validated against authentic Bitcoin-mainnet block headers. Fonteum therefore does not present any stored proof as externally confirmed. The database status is an internal operational field, not mainnet evidence. [corrected on 2026-07-12] Machine read: /api/v1/chain/anchors.
How the chain works
Snapshot taken
A captured source observation records source, date, row count, and a SHA-256 field. Historical attestations do not all hash complete source bytes; the inspection surface identifies the object each digest covers.
Snapshot signed
When an attestation row carries an Ed25519 signature, its recorded digest and signature can be checked with the published public key. That attests the signed object; it does not establish that every source row is signature-linked.
Snapshot chained
A snapshot attestation is in this chain only when a chain link references its attestation id. Newer unattached attestations are not chain members. Chain membership still does not create a deterministic signature relationship to provenance facts.
Inspect any snapshot
This endpoint currently returns a clearly labelled illustrative response shape; the field-level historical store required for a real snapshot diff is not live. Set an issued FONTEUM_API_KEY before trying the integration stub:
curl -s https://fonteum.com/api/v1/snapshots/diff \
-H "Authorization: Bearer $FONTEUM_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"dataset": "nppes",
"from_snapshot": "2026-04-01T00:00:00Z",
"to_snapshot": "2026-05-01T00:00:00Z",
"fields": ["taxonomy", "addresses"]
}'Response shape
{
"dataset": "nppes",
"from_snapshot": { "digest": "…", "signature": "…", "signing_key_fingerprint": "…" },
"to_snapshot": { "digest": "…", "signature": "…", "signing_key_fingerprint": "…" },
"changes": [
{
"npi": "1234567890",
"field": "taxonomy",
"change_type": "modified",
"before": { "value": "…", "provenance": { /* 14-tuple */ } },
"after": { "value": "…", "provenance": { /* 14-tuple */ } }
}
],
"summary": { "total_changes": 2, "added": 0, "removed": 0, "modified": 2 }
}Full reference: /docs/api/snapshots-diff
4d00161d451385d6a6976175bfb13841b90975aebf9ac70f7d8c3e7e768be7e6Inspect the evidence that exists.
Browse stored snapshot metadata and chain coverage. The snapshot-diff endpoint uses an issued key and is an illustrative integration stub, not row-history replay.