Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
Rendered page — archived HTML, sandboxed · click to collapse
Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen
WhatsOnChain · Banana Blocks
SPV proof & how to re-verify it yourself
086c2027821e1b4ece0d2b60c32a0cda664e7222c6bca9173a33fa8d2a4067d0
fc90acc626c9a48f54e6ba4851181257ca69702afe57d88aaf9549bffa72130d
4ae98f777f40aac206f990531c0445a26b68d9f2d65c8384a6f9a510cd485a3e
35848d80f61ba548e4dc629c9bc960f1c9f364980f4548346679a8ba7d9deac0
82f2352204e435f07b05cf98eb91ad73d5582fffa2db1701208f423eb8f2cfe0
faa84ced399a90a2a16c94800a8f3fe270252c58a80d1c53a838d86d23542b8b
d22343187f90ae07abe1bb9a4d1cf0094e4a8eed1c2ecb31d4e3e47993104f5f
7e017ebe66f02d3bd1aaa676ae520db69c48f955c7d48c8bf3696b1ff2943121Trust no one: double-SHA256 the txid up this branch — at each level your hash goes
left when index is even, right when odd, halving the index each step —
to get the block Merkle root, then confirm that root is the header at height 964567 on
any block-header source you trust. We verified it against headers we run ourselves; you
verify against yours — no explorer, and no bsv.cx, in the trust path.
Prefer to check it against a second independent source? Paste these fields into
our public verifier (POST /spv/verify) — it folds the root itself and
checks it against headers we sync, so it can only ever make a bad proof fail.
Or take it to your own tools in the ecosystem standard format:
BEEF (BRC-62, tx + proof) ·
BUMP (BRC-74, path only). Any @bsv/sdk client verifies
these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is b1d0c563f8b016cdc0f57fc3ece9e4e2f0aa26aecd96ba590db9cb88f373062c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b1d0c563f8b016cdc0f57fc3ece9e4e2f0aa26aecd96ba590db9cb88f373062c, and the block's
timestamp proves the page looked this way at or before that time.