Byte identity
A changed byte produces a different SHA-256 value and a different commitment.
An AI SENSE product
Verifyum hashes a selected file and creates its private manifest in your browser. The original file stays on your device. You keep the portable result.
VERIFYUM
How it works
Verifyum receives no original file bytes. The browser creates the inputs needed for a proof package and gives the private parts back to you.
The file is opened by browser code on your device.
SHA-256, file size and a random nonce are combined in a versioned manifest.
The browser canonicalizes the manifest and derives a public commitment from it.
You download the draft and store it with the original file.
Current status
The current public service creates the private manifest and commitment locally. Solana anchoring is disabled while the isolated Devnet signer and its operating checks are completed.
This status is deliberate. Verifyum will not claim a public blockchain anchor until the transaction has been created, finalized and independently checked.
What you can use today
Create and download a private draft at verifyum.com/create. Nothing is uploaded.
Clear limits
It checks whether a file matches the bytes described by a private manifest and its public commitment. It does not decide who created the file or whether its contents are true.
A changed byte produces a different SHA-256 value and a different commitment.
The proof design keeps the inputs needed for independent checks outside the Verifyum database.
A future blockchain time can show when an anchor existed. It cannot prove when the original file was created.
A matching proof says the bytes match. It says nothing about authorship, ownership or accuracy.
Operated by AI SENSE AS
The original file stays on your device.
Open Verifyum