Session Attestation · Client-Side Verification

Verify what an agent did.
Trust no one — including us.

A sealed session is a tamper-evident record of agent behavior: every event hash-chained in order, committed to one Merkle root, signed with ML-DSA-65 (NIST FIPS 204), and anchored to the public Hedera ledger. This page re-derives the cryptography in your browser. Our servers only hand over data — they are not trusted for a single check below.

The default is the first production session ever sealed (2026-08-07). Raw data: manifest · self-verifying statement

Checks

Each proof row re-derives one event of the session from raw bytes; first, middle and last are sampled here, and every event has its own proof at /v1/session/<id>/proof/<n>.
Press Verify.

Session Facts — From the Verified Manifest

—

The Public Anchor

—

Independent path: fetch the message from any Hedera mirror node and confirm its payload_hash equals the session root above. Full post-quantum signature verification: npm i @rubric-protocol/verify → verifySessionSignature(root, manifest.signature).

Construction: SHA3-256 · RFC-6962 domain tags · promote-odd · forest wrap — Rubric Verify Spec v1.0.0-rc2 §7.5-7.7/§9. Everything below the ledger anchor is arithmetic anyone can recompute; the anchor and the signature bind it to the world.

ML-DSA-65 · NIST FIPS 204SHA3-256 MerkleHedera HCSEU AI Act Art. 12© 2026 Echelon Intelligence Group LLC