Public-safe decoder
Reads JSON, TXT, HTML, SVG, and PDF with a focus on extracted evidence, without publishing raw sensitive content.
Cryptographic batch signing · live demo
Sign in batches. Verify forever.
Cross Examination is a public-safe cryptographic framework. Hash your files with SHA-256, build a Merkle Tree V2 NO-DUP, and export a verifiable audit manifest — all running in your browser with zero server custody. The HEXAGONAL MVP VECTOR Seal anchors the visual identity; the proof lives in the root hash.
Enterprise Signing
SHA-256 Batch Signing Environment
Hash files and compute Merkle roots entirely in your browser. No data leaves your device — powered by the Web Crypto API under a Zero Trust / No Custody architecture.
ragdata://batch-signing-v2
Client-Side · Zero Trust
Drop files here or click to browse
Files are hashed locally — nothing is uploaded. Supports any file type.
Computing SHA-256...
#
File
SHA-256
Size
Status
No files queued. Drop or select files to begin batch hashing.
⬡ Merkle Root V2 NO-DUP
Disclosure
What this proves (and what it doesn’t)
Clear separation between technical integrity evidence and legal evidentiary value.
Integrity scope
What it proves
- Each file’s SHA-256 fingerprint at the time of hashing.
- A single Merkle Root that represents the entire batch.
- Any change in any file changes the Merkle Root (tamper-evidence).
What it does not prove
- Identity of the author or signer (no digital signature here).
- Legal timestamp by itself (requires timestamping / trusted time).
- Chain of custody (requires procedures, logs, and governance).
The Merkle Root provides technical integrity evidence. Legal evidentiary value depends on custody, signature, timestamping, audit trail, and applicable jurisdiction.
9 Endpoints
Fixed profile reflecting blocks, hashes, timestamps, fees, transactions, and relevant endpoints with auditable status.
Merkle V2 NO-DUP
Canonical leaves, SHA-256 hashing, and odd-node promotion without duplication — eliminating artificial padding in reports.
Vector seal
The root feeds the visual compensation of the seal. The drawing is verifiable as identity, but does not replace the proof.
The blockchain should receive only the root hash or the manifest hash. Personal data, integral logs, private keys, and client payloads remain outside the public layer by principle of minimization and internal control.
Cryptographic Pipeline
How Batch Signing Works
Five deterministic steps from raw file to verifiable proof — fully client-side, zero custody.
Step 01
Select Files
Drag & drop or browse. Any file type accepted — PDFs, images, JSON, SVG, code.
Step 02
SHA-256 Hash
Each file is hashed in-browser via Web Crypto API. Nothing leaves your device.
Step 03
Merkle Tree
Hashes become leaves. Pairs are sorted and re-hashed. Odd nodes promote without duplication (NO-DUP).
Step 04
Root & Seal
The final Merkle root is the single proof that anchors the entire batch. Sealed visually by the vector.
Step 05
Export Manifest
Download a JSON audit manifest with all hashes, Merkle root, timestamp, and batch ID — ready for audit.
Enterprise Licensing & Forensic Audit
For enterprise integration, licensing of the RAGDATA Method, or forensic audit inquiries — reach out directly to the Chief Developer.