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
bffc6af4d8c90f210c6edf7d875197c938d4a5718e13e56eba55094a692a8a90
a24052d6aec03fb410f00cd02ca3cb939ab00e843a1961c6d750e574b2423b57
3db9f7edc59d7be53bd9c7b5c60ae2697fa03422aa5170cb9b63872c7ca91737
f836ff042745287024d3804f7c4bd4002ad866cd45ab6a802296429d2b0b1ae5
fd9ebd44f4bc22ee0443cf6b31cfc0d02385ffe6805e07bcd49944c57793f52e
39d1380a3a41facde33043808327285da4b5a54649ccd432f7ab265af04183e1
c2294e97248c3c37bb40e73de3eef1202864de7b643d9771099315f791868074
cd81d821d717665b18734cbe54868c4a61907b23e5b549287d95e4f488d925c2
7224c9a799a50d820a5b29c81b038f66a9eb5b1ad2c228a2bb08c7cf6b6c7f43
69c42b7f30966c815ef70dd74599012f21cc6659a706a12b26e4807c91741c31
5066242b509731901166f7d31f0d3c3149b0e492671a510ccfd55ffd8b9a7e5a
c7e3507b250e692da17d0b3d9a3bca6238376b9a4b8866a68af42152adee9a39
865a606d71c0e77afb0ff41057671d5097f8e41d3f81deafd68bc5a27a0b2042
d58c068194b8e147ef8607e9b2e71f264d9fe7dc1c10c5f01c52002f995b09e9
6aeb9dae150704f06b1ec5218069bff69a56608c87881b04131880b52a3e9062
6cdbe492ac82b18cea75c67e12ba231956306ce117d98f8753976e7a1331b4ee
7c837088f83f62e08e9e02e2d9f548693e7e843abe9a57ab6e8455b95ca332bbTrust 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 962329 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 4a49b8c4f80969d3c7fd03d17b986bd0608bbcc486b79ef490ade3a1560b277c; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4a49b8c4f80969d3c7fd03d17b986bd0608bbcc486b79ef490ade3a1560b277c, and the block's
timestamp proves the page looked this way at or before that time.