Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx
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
9caef90ab26fb04d0ebfb6ce5232c3671fb67f1f88c705d9afe27b2bb6eb0dff
67873c0ec66b97bb3df6a17354e61a0f9e021a0740ebc23a0973b3b94e841dcc
e6289840a66159c3985a8adcb4c180a054da679735e3b8775287b9fdbc90334d
6dd66e2df3670e5e08f718ab2448435b454b0ba48aa6353db9471329a31ef6c1
e5aedf6d1d5648ff86db8fa90a9187b0256900863224638204f84aa4602289da
d0a435f65c4795efac97c6adbdb1767d6222fdf9faba4afa5c5dba3a2eeb4630
b6c265d5b9e89cc3c3e8ea883b2092587d83ebe23b45d111b1af92d62aa879d5
60e252daa9954ccb7f42650f390c115f4cc33aa119869fb161bdbeed7de78e3a
5cfefa352b88d8d3f8d8e952cac59fcd7b22deb6fe8b5914c361248542c38a15
07752154857db439cf2ed7d0194ba9adfbcf9ed8bb8e8f5c1814218bb9f11b72
e42ee1a21b504438f6a522e97702fc7d47e60c84dbde803fdbaa66113d256663
b70bb4cc504919094fe62773dfe886494ebc89bc860601f9823cee6826012a19
50852b3e05e10dc841309b8e85398035ac3d0f7e0932d9e0974ca3e293a0a65f
5989083c87b35cc2e1b5da0280209d08d5c93f193c7d8b2b828fb96dbdc66233
45c8af0a32763529fe8c1beaeb31fcfb659c3247287625e306b6c7cfdda41644
02de055484f5cef0a164f430f058de3d0c12da133b4168da98142a77be68f397
772af6dad1a3a0d5d9dfa795c9b07ac0e06a94124d0d9fced3053b55a5290628
8f86898f67c0038d9d215c6790b90a3c672858b5978f220932cf2e5c2ccbc8ba
23f73605be544fce6bfd4ee1b6ef1d882f491d9d77d6677349eeab6085af416bTrust 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 973567 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 a770855c304dc434304e97ff6f81c62bda93e6b35ba683a53316d05aa28fe26c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a770855c304dc434304e97ff6f81c62bda93e6b35ba683a53316d05aa28fe26c, and the block's
timestamp proves the page looked this way at or before that time.