EVIDENCY SANDBOX + ETHEREUM MAINNET

Construction records that can verify themselves.

Create a real SHA-256 evidence record and client-encrypted backup, then export one canonical Evidence Report containing the visible exact original. Evidency sandbox time has no legal effect, so final “sealed” status stays disabled.

From capture to an independently checkable proof bundle

The workflow separates live web capture from imported files, hashes the original and its manifest locally, requests only a test-only RFC 3161 sandbox token in the current alpha, batches evidence digests in a Merkle tree and anchors the root on Ethereum mainnet.

Two external proof rails with different limits

The Evidency sandbox rail is cryptographically checked but is not qualified and has no qualified eIDAS legal effect. The public-chain rail records a Merkle root in a finalized Ethereum transaction so an independent reader can recompute inclusion from the exported leaf and path.

Proof of integrity is not proof that a depicted event is true

SiteSealed distinguishes cryptographically proven integrity from server-bound or browser-reported context. It does not prove that a scene was unstaged, that pixels came from a physical sensor, or that an imported file was created at its upload time or location.