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
dc8d487c37c83768d54c6b4a5f264fde771cf21e81f7336715b553108ddd801a
78c7f54516a479f7d495a0897c91480f9aec13aeca142291979803fc170cc52c
31f50b3d427e6b2d6ed282fe365662506b3f3973c09e33a7533af5d9aebaeb08
12cea86ecc366af3b49a91064508f5fb6b8ec18bac72771ded7fb509c23179fc
4f1f720478b253e2821a211e9c3a7bb9281abf837fffd3228ef7a599e3a7f182
9bc4cc2ba79d39f20e3356081c0c3adda6766013bb196bbdbcaad3c8016382a9
1d47c4ba11e4e19e8040daf790251e91ea00db5ef3c8335a309cc8d1bead4beb
3fb6906cc5864858225c9b1bb1de4c3603a18f2155c51fb1bfd17418c78bab6b
320356231c7a612747303a96e1356721b8a23bd728998f57f54661d8f49a2352
0bb857f3b04d9cc00532ae5e30852480bb2f54fec1b29681a6148fc1b068e65fTrust 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 966556 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 64f09cbf6c57264b9957b4f6e5943f1abe1ba1fbdb03501d1ad4f7b04ff0f72a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 64f09cbf6c57264b9957b4f6e5943f1abe1ba1fbdb03501d1ad4f7b04ff0f72a, and the block's
timestamp proves the page looked this way at or before that time.