Drag files or a folder here, or browse files

Make or check a BitGraph

Drop files in the box and this page makes a real BitGraph of them: a position on the public sequence, floored by an Ethereum block, with the proof returned to you. Nothing here is a simulation. The position is permanent, and BitGraph keeps a public copy of each proof that cannot be deleted for ten years, so choose files whose fingerprints you are happy to have in public.

Stays on your machine
Your files. Each one is read and hashed in your browser and never uploaded. The new fused files are built in memory here too.
Is sent
A request for a position (nothing about your files), then the SHA-256 digest of each new fused file together with the slot record. The service also sees your network address.
Comes back
A bitgraph/1 proof: the slot record, both counters, the enclave’s signature and attestation, the floor block, and the marker naming the placement and the original’s digest.
Save
The proof, beside the originals. The page that opens after a drop has an export that packages the proof, the files and the bracketing anchors as a zip. The service keeps a copy of the proof too, but the copy you hold is the record.

What you will see

  • ReadingThe file is being hashed in your browser. Large files take a few seconds; nothing has been sent yet.
  • BitGraphingA position has been allocated and the digest is being committed under it. This is the only step that talks to the service.
  • RestartingAround 23:59 UTC the enclave restarts for its daily key renewal and holds commits for about a minute. Your file is hashed and waiting; recording resumes on its own.
  • DoneA single file opens its proof page. Several files become one set at one position and are listed with a row each; open any row for its proof.
  • Not madeIf the service cannot be reached or refuses (for example, no anchor has landed yet in a fresh epoch), the page says so and nothing was recorded. Try again in a minute. A file over 256 MB is recorded by its digest rather than fused in the browser.

Check a proof you were given

Drop a proof.json into the same box, with the original file if you have it, and the checks run in your browser: the signature, the slot binding, the attestation, and whether the file matches. A check you would stake something on should run outside this website, because a page served by the party being checked is trusted exactly as far as that party is. Use the command-line audit tool on the export:

Shell
npx @mikeargento/bitgraph-audit ./BitGraph-export/ --out ./audit

What the checks establish, and what they cannot: verification. To record from your own systems instead: the integration guide, or connect an agent over MCP.