Skip to content
Akashi

How verification works

What an Akashi proof contains and how it is produced.

1. Fingerprint while recording

Your browser hashes every byte of the recording with SHA-256 as it is produced, streaming chunks to storage at the same time. The fingerprint exists the moment you press stop, before the file has finished uploading.

2. Independent re-check

Our server re-reads the stored file and recomputes the fingerprint on its own. If it differs from the browser's, the video is marked mismatch and is never attested.

3. Witness attestation

The Akashi witness key signs one attestation on the Ethereum Attestation Service on Base Sepolia. The schema is:

bytes32 contentHash,uint64 sizeBytes,uint32 durationMs,uint64 recordedAt,string videoId,address creator,bytes creatorSig

Schema UID: 0xc13a279bd0e8665d7a669c9f2c62588efc9319bffed2d911bfdd546f7d1e9af4. Attestations are non-revocable and never expire.

4. Optional creator co-signature

If you link a wallet, you sign an EIP-712 message over the fingerprint, size, length, recording time and video id. The signature and your address are included in the attestation, so anyone can check the recording came from your wallet. Signing is free and sends no transaction.

5. Anyone verifies

A verifier hashes a file, asks Akashi which attestation matches that fingerprint, then reads the attestation directly from the chain and checks the schema, the fingerprint, the witness address (published at /.well-known/akashi.json) and the creator signature. Akashi can help you find the record but can't change what it says.

What a proof does not say

A proof shows that a specific file was recorded through an Akashi account at a specific time and hasn't changed since. It does not prove that what's on screen is true or wasn't staged.

Privacy

Only the fingerprint and metadata go on-chain. Private and password-protected videos still get proofs, but lookups never reveal their links.

NextOpen-source verifier→