Sentinel Buddies
Public verifier

Has this report changed?

Paste a report ID or its 64-character fingerprint. We look for its on-chain record. Public reports can be checked here; private AI reports are checked from your Vault or downloaded packet.

Recent on-chain commitments:

Server-side lookup (untrusted convenience)

Enter a snapshot ID

The verifier reads the contract view and the released vault snapshot.

This server result is for convenience only. Use the browser panel to recompute the hash yourself from the released JSON bytes.

Check this report’s digital fingerprint

Every snapshot is a deterministic JSON document. The agent hashes its canonical form and a restricted function-call key commits that hash to the NEAR testnet contract. Anyone can recompute the hash and read the commitment back.

Snapshot IDnot available
Fingerprint calculated herenot available
Fingerprint stored on NEARnot available
Publication transactionnot available
Methodologyv1
Open verifier
CLI: pnpm verify <id>
Hash cascadeREADY
1
Fetch full snapshot
from the released vault record (after public delay) or holder vault
2
Canonicalize (RFC 8785 JCS)
sorted keys, no whitespace, deterministic number encoding
3
SHA-256 in this browser
window.crypto.subtle.digest — no server trust required
4
Read on-chain commitment
view call to sntl-02e90eacb8.testnet on NEAR testnet
5
Compare byte-for-byte
local hash === contract content_hash === published hash

Reproduce from the command line

# from the monorepo root
$ corepack pnpm verify &lt;snapshot_id&gt; --recompute
# prints the canonical hash and the on-chain hash
✓ MATCH — byte-for-byte identical

The CLI loads the local vault JSON, strips proof metadata, canonicalizes with JCS rules, computes SHA-256 and reads latest_snapshot / snapshot_by_id from sntl-02e90eacb8.testnet. It never asks the gateway to decide whether the hash is valid.