Proof

Receipts, not reassurances.

Any fact in the record can be asked for its receipt: a portable proof bundle tying the value to the captured page it came from and to a public timestamp anchor. You verify it yourself, with open-source tooling. Trusting Bixel is optional.

The capture

The original observation is stored permanently and content-addressed: its identifier is the hash of the bytes, so the evidence cannot drift from its name.

The chain

Captures are committed into hash-chained manifests, so removing or altering any past observation would break every link after it.

The anchor

Manifests are anchored with OpenTimestamps, placing an independent, public bound on when the evidence existed. Bixel cannot backdate its own history.

The bundle

A proof request assembles all of it: the fact, its capture reference, the chain path, and the anchor, as one portable document.

ask any fact for its receipt

GET /v1/companies/{domain}/facts/{key}/proof

{ "fact", "capture", "chain", "anchor",
  "verify_with": "github.com/bixel-ai/bixel-verify" }

# verify offline, without trusting us:
$ bixel-verify proof.json

The honest edge case: a fact whose capture predates a given evidence layer answers proof_not_available rather than pretending. A receipt system that cannot say no is not a receipt system. The full pipeline is on the methodology page.