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
0592829880b11ac9ee8f0dc349797a3779b300f2e625c1103d18c78eb8c56e14
d97bc503974445747aec3b318f367cdde8c5c30e7fb3f38b8f95e6ec0f764a70
27dd018c163338969423b04f1a03df77f5f9911582cbc2fdffd3bcd94f59b9e0
75ac93ed7507882f36936afc2b5278bb6583f5041b8ba898533693f51949f785
75c0a5505410d681aef4e43641c1ce305622cb8c2b91707654dffa8d1a208eee
0c7dd0c29f7a3e2b6802078740b0e2782e412ab2ebfaf7b815b57ff00c9278b9
7b2ad0bc8c9d0c483d9ca85e7d045847c9d24f7c664b8a3772186b98796a6d0f
b176cb3131f19c35a29d59b7f034e10f6564c6bf897d869031b97404e94ffbf6
decd79e880165db4d5a8da178b60cfb0aa9cdffe15436a9b66a7de9962c9754e
98646318707615fc16e1cef52f41edbe1274cbff97e9d5a8005d83db9826c626
6e8dea5e8418c94fa4cac1884fe8dbff0ed8b639208510c3a8ab745136e9fdd1
cdff6bc4fe960ee10aa7fd81f8d29e0f8ccde08189a97854420edbd116c878b3
3fffd512e9b752d581b0643077aab2d5ca8e99b6962e01ea5e0c39c444c73338
4d62e7f1dd5c63ee8e86efd8fcb9cf9d8f5b346da9024ac05cbb1db08f2d90ea
d2fa148b6290b8066802f55336636b2724e7c06372f23e621735b1c3522d0f00
8b743cffcbeaaf1760abd82927f2543d6b442700913cde4dde253163a657828c
f6007bbe142e1584528ac012087990f57e4aae885a366a19f35cc98417f777d3
ddc104786674959617e5ecdee3ff3bcce5c52f142e7c10ef950de9c59b08bda4
bc2157036787b50f69abb48db7411aa2db92ae2bb54f9cf9dc97523b7b4aef08
645417fa7c7a06d9b380277732f717bab358f2407f275e094690b098bbf2006aTrust 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 964942 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 28b9349ad971cf5a18264c7f699ae3322a309bb2caa526a92b85f458c0af306a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 28b9349ad971cf5a18264c7f699ae3322a309bb2caa526a92b85f458c0af306a, and the block's
timestamp proves the page looked this way at or before that time.