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
46a07a30fa90cfe45230f7772a67fa24440422314fc4881ce0bb06d53c83b4ac
4f090cb258d391924b66fbc5a2a15f010e9f15f868782a7c09fc0a955c784818
0136142861fd834d75fd87af1c93c7e8f5dd8635d42373b2cde1d031a081e0f9
f71e2b2286891a603e6eea1cd1b60d8e7cd7a493e1df9996c93a8ce34e165205
bccb55f6f43539275b71ec0d7425db8fe6f20245792d857dcb1d97b502a4038c
695f0dda30adc3709bfd218d8ee200821466c64ddb46c43e974f293310473ae3
db232f7189d8c1b3526bbe6ba1fae8559128e9c62f816c948aa82b826945b880
08486b7e2c4f86ea766b4edd99bfab6a6b1b0a1da99cf3234ea4e11dfb43b0ad
68996d09d243675bac4d02c03fd8200c1b02549bee6902d68332f7399163284e
29d9fc4bc8e5ce61ad9666896bfe57ce5ae864f57b2536061ca90b5b24097e4d
e5f4cf060ad65625ab9fe729df4593f7ac9d7d96ce13bcc9c908fddf8dff804d
55440f95ff705d2f5445373a1869f2a40555ca24e4749dd05ef19b25c0693ecb
585978b79a63c5849239948e888a6a533b1280805e6f954ea444f9305347532d
6b2127a60e4ea60909dd4436be7b4bf631a48967ba7cfaac715738b419465959
5c6b55833315a639ba7d1bb4910f32ec2e86ae6e11f9edf72c635263d3ccf2c2
d2f1daa6d498ca21acf56e04bff56595da57607191d00d1b6e1506ab335a7487
fcbfe6625290e78c2e4831a6a1dad349d61a582d549ae05e23506dd6211dc295
282740c70b8ed7f745ad8dd902b410561ef87d7f7b1454c05eb7248158d90260
53d2490a3083c314707abd731a83c5073e73bc406903d37e926eb76cee552b8eTrust 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 972185 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 6b6482c9f78e98d7f072c8165352e97e90fd765912952959e0e72e56290b4da9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6b6482c9f78e98d7f072c8165352e97e90fd765912952959e0e72e56290b4da9, and the block's
timestamp proves the page looked this way at or before that time.