Theo Sera / The technical view

Trust the evidence.
Inspect the mechanics.

Client-side SHA-256. Signed registration evidence. Merkle inclusion proofs. Portable verification. Real cryptography without requiring custody of the source documents.

The path of a file

From local bytes
to verifiable evidence.

The current deployed staging architecture records the fingerprint and signs evidence without receiving the original document contents.

01 CLIENT FILE // stays with owner   → browser.crypto.subtle.digest('SHA-256', file bytes)02 HASH + METADATA // registered with Bagsey   → Bagsey reference + signed registration record03 DAILY BATCH // signed Merkle root + inclusion proof04 VERIFY // hash comparison, signatures, proof path   → MATCH or MISMATCH

The Bagsey reference is an identifier, not an encryption key. A SHA-256 digest is a one-way cryptographic fingerprint, not encryption.

Zero-upload demonstration

See your own file's fingerprint.

Drop a file into this box. The browser calculates its SHA-256 locally. No upload endpoint, no account, no Bagsey registration and no external script.

Change a single byte in the file, then calculate it again. The fingerprint changes. The same unchanged file will generate the same result.

This is a standalone demonstration of browser hashing, not a Bagsey certificate, registration, timestamp or verification transaction.

Choose a file or drop it here

Local SHA-256 · Maximum 50 MB in this demonstration

Local SHA-256 fingerprint
File content never leaves this demonstration.
Evidence stack

Existing and upcoming.
Clearly separated.

Technical transparency matters more than calling every tool “enterprise-grade”. These are the demonstrated components and the integration work that is not yet live.

Working staging

Browser-side SHA-256

The source file is read locally; the content hash can be calculated offline. Bagsey later registers the fingerprint, account/record metadata and proof material when connected.

Working staging

Ed25519-signed records

Bagsey signs its registration and sealing evidence. Signatures establish what Bagsey committed to; they don't independently certify who authored the file.

Working staging

Merkle batches & portable proof

Daily signed batches bind leaf evidence into a Merkle root. Proof paths and signed material support subsequent cryptographic verification and portable evidence export.

Built separately · inactive

RFC 3161 trusted timestamps

A provider adapter, offline token verification, durable evidence design and activation controls have been developed separately. No paid provider is active; automatic issuance is not connected or deployed.

No claim is made here that Bagsey is a qualified trust service, independently timestamped at present, or certified under UK or EU eIDAS.

A practical design decision

Evidence without taking custody.

The less confidential source material a system needs, the less it needs to protect on your behalf.

Bagsey still processes account details, fingerprints, descriptions and verification records, so those records have their own security and privacy responsibilities. But the source document bytes remain on the client side of the boundary.

What the cryptography does not establish

It cannot establish that an original file was true, approved, created at a claimed time, or legally binding. It can establish whether a file produces the same fingerprint as recorded evidence and whether the associated cryptographic records verify.

View the wider platform ↗
A deeper conversation

Want the details?
Ask the awkward questions.

For technical teams, auditors and partners evaluating evidence workflows, Theo Sera welcomes specific implementation and assurance questions.