Public receipt-tier calls are written to an append-only, SHA-256 hash-chained ledger when they fire, and again when they resolve, red rows included. Edit, delete, reorder, or back-date any past entry and the chain breaks where anyone can see it.
Glass Ledger currently covers CORE receipt tiers sweet and liqsqueeze, plus Research Lab super public receipts when applicable. Historical alpha receipts may remain verifiable when they were public, but alpha is paused and not live delivery. That is intentionally broader than the CORE-only public signals API while still excluding admin, private, shadow, trap, wallet, subscriber, and non-public signal data.
Existence, timestamp, tier, entry context, resolution context, and the hash chain. It is proof that the record existed before the outcome was known, not a promise about what future calls will do.
https://sentinelresearch.app/api/ledger/verifycurl -s https://sentinelresearch.app/verify.mjs -o verify.mjs node verify.mjs https://sentinelresearch.app # → "N events, chain intact, 0 tampered. Head: <hash>"
The script re-derives every hash from public data using only Node's built-in crypto. If a past entry has been quietly edited, it prints the exact sequence number that breaks.