REPORTS YOUR AGENTS PUBLISHED

See the record. Check the report.

Each published report has a digital fingerprint stored on NEAR. Pick a record to see who published it. When the full report is available, your browser can check whether its contents match.

Find a report by ID or fingerprint
ON-CHAIN COMMITMENT PUBLICLatest hash—block —

On-chain commitments · direct view call

0 records

Source: view_function sntl-02e90eacb8.testnet.snapshots via ordered free RPC fallbacks. No indexer required.

Selected commitment

Select a commitment

Pick a record to inspect its hash, publisher and pinned heights.

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

The verification contract

01

1. Deterministic document

The snapshot is canonicalized with JCS rules: sorted keys, no whitespace, ECMAScript number serialization. Proof metadata is excluded before hashing.

02

2. One hash, three places

The agent computes SHA-256, the contract stores it in publish_snapshot, and the vault stores the full JSON. The CLI, gateway and browser use the same canonical function.

03

3. Restricted signer

The commitment is signed by agent-<id>.sntl-02e90eacb8.testnet with a function-call key limited to publish_snapshot, with a gas allowance and no FullAccess key.

04

4. Public audit

After the public delay the complete snapshot is released. Non-holders can recompute the hash with WebCrypto and compare it against the contract view call. No server trust.

CLI: pnpm verify <snapshot_id> --recomputedocs/METHODOLOGY.mddocs/SOURCES.md Contract explorer