Check a sealed record yourself
BTC Pact seals agreements with cryptography that anyone can check. This page shows exactly how, and lets you run the checks here.
What a seal proves
A seal proves that a specific agreement text existed and was signed by specific keys at a point in time. It proves the agreement, not the coins: BTC Pact never holds keys and can never move money.
What exactly is hashed
The fingerprint of an agreement is the SHA-256 hash of its canonical text, the exact sealed markdown, encoded as UTF-8 bytes. The Bitcoin seal stamps a second digest: the SHA-256 of the text "documentHash:signatureBundleHash", which joins the agreement fingerprint with the hash of the members' signatures.
Snapshot report pages stamp a different digest: the SHA-256 of the text "logHash:capturedAt:pactId", where capturedAt is the capture time in ISO format. You never need to rebuild a digest by hand; the exact digest to verify is shown beside every proof download.
Compute a fingerprint
Paste the sealed agreement text below. The hash is computed in your browser; nothing you paste leaves this page.
Check a Bitcoin seal (.ots proof)
Upload the .ots proof and enter the digest it stamps. This check runs on our server for convenience. For verification that does not trust us at all, use the OpenTimestamps client:
ots verify -d <digest> proof.otsWhere to find your material
Members find the fingerprint, the digest to verify, and the .ots proof in the pact's seal dialog, and can copy the exact sealed text from the founding charter. Public log pages carry the same material for anyone holding the link.