Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
7a0c07c63699e4a70e17f616a6cea258844906c638b228f23e8e32d98d829dec
86a6a47ecb5cfbdf949aca75fa395966b4efedfa8d25b7b786a0f6501307adfa
4c5705e47f89a37c2a4fde30745f2399d1bab3b8174cada521e8a5e3fd6a1500
a3afcd294b0603feb8619b05c46322f3e5fca39e50f715b2c91c98bc0b24928c
e906e25509de0e04a093f035787fd07de57453d2a5f8f8d08756c729c1ac62f8
e0e19b7c36d140074c47e800c7b33221c8834a0b2b3233782e58234bf264b464
1129a2fc18107dc64ac09aed32ec165aa6be3a4bba000bd7ed9dc010640acd60
c8a3352ec055644fd5aed39961989efc62b16cba9a3dc47ae2e1c296f1518912
62bdf5ed75325598ee8a249e3e0add0f43f256609e3147af3b398786cd2cb2ba
99dceece5edd2260b8e736093d4362f1066d230da4bbf492fd5f1feb5c5ed2a7
aab5a5d1cc615872368b7b4434bf3b2a757587db5ef834c844b7c3fbe8fad6ecTrust 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 964683 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 b25f76c2d44c9c986b57854c7cdee1f52f83945fa812ef2d415947c9fcf2b3e8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b25f76c2d44c9c986b57854c7cdee1f52f83945fa812ef2d415947c9fcf2b3e8, and the block's
timestamp proves the page looked this way at or before that time.