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
93d445f515d534b5e16d9e83cb95015cdaa3a5928bbde5f0acc3ba8d271c716a
*
2093f4cad183680c9aae0e129974de69b146a4d6d4e872705d18fab34cb475e8
f3257cfb862da7fd452b7fc8c29d3486baf5883edb3c147da45a30d25f401752
9d6fe162377d8fa82369b921040cc7bb8998bb651bbc5529b3c67232cd7c7986
c6887e2df1147255aa36f853270ee01dd61919ccfb95d66e42078eec3d652064
4ce2846c598dd3901ec88ae32c60ad5367f233afd472077564bfb3ca284106bb
e20469831bfe7cc0cc643d099b4e58520fa5856fb7f39452e6b0a35761a9fe3bTrust 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 964042 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 6b5ae24b5c6291014d577c1bc39b24b3b1bb393a12113b66a67138471088053b; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6b5ae24b5c6291014d577c1bc39b24b3b1bb393a12113b66a67138471088053b, and the block's
timestamp proves the page looked this way at or before that time.