Verification Portal
Client-side SovereignAuditRecord (SAR) format checker. Does not perform cryptographic signature verification — see warning below.
SovereignAuditRecord (SAR) Format Checker
This tool does not cryptographically verify anything. The script below only checks
whether expected JSON fields are present (!!json.signatures.ed25519,
!!json.payload.context.previous_block_hash) — it never parses the Ed25519 signature,
never recomputes a hash, and never calls any signature-verification API. A file with a
fabricated signatures.ed25519 string of any value will show "✓ Verified." Do not use
this page as evidence of authenticity for legal or compliance purposes. For real
verification, use openssl against the RFC 3161 token (see
RFC 3161 Timestamp Verification) or the ledger's own
/verify endpoint (see Events API).
The ABS Core engine produces cryptographic proof of every AI agent decision in the form of a JSON SovereignAuditRecord.
The tool below is a format checker — it confirms a file has the shape of a SAR record and surfaces its fields for manual inspection. It is not a substitute for real signature/timestamp verification.
Drag & Drop SAR Verification
Your JSON file is parsed and validated entirely in your browser. No data leaves your machine.
Technical Details
The format checker inspects the following fields of the SAR v4.3.3 schema — it does not cryptographically authenticate any of them:
- Schema Check: Validates that
version,payload, andsignaturesobjects exist. - Ed25519 Signature Field: Checks that
signatures.ed25519is present. Does not parse or verify the signature. - Hash continuity: Checks the integrity of
previous_block_hashinsidepayload.contextagainst the ledger. - Goverance Policy Result: Extracts the exact AST decision (
payload.decision.authorization).