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
176651c76601258f7ad9d60c3715ea10daf961be9718d0e3a47e8ba143116037
2d73403a3b88403fec818c81cac133c0683889fcbc3278902e22f375eae6c1f4
1d0f7acde705f4e511ed39102ffb85c229e253f3689c832e2d9197c3817692d7
7ff28d423d9b6a4f35b934bf77980000c3baef6c142bc561a9f8ec65f81296cf
86e33dcfc8f19fd9caef8aa32707b0f73e71e2e6c1013a69190604a81903e2d9
c21f10236886cf4127f00e0b5adad78ad3a927def0110e9d19a6e027a378e1c9
ec6c5d2d31b0b2e81ecc32e27bee6fe0d164bdf59acff711c2973497dfe3596c
d8896b3108eb274e93d071722e83e9ea4b8528953e0f0432271392f819b45241
66d3dc74b16d1b9cee1edc37effc80217b1c51986e2d7b58463790ecec1df10f
995f11a3a68aa51de6b57da78210d826dd3b0c3460081474c07769a35228f50d
f457ab37dabe64d0b2ea3e9539839c29c95e29c1274fcb73269f80af77b0c3ad
12d9b62b7d3c4625a69528fe89a074cbe31165c6d7134ddfcd7681069fd2f8ff
004796ed744f9d769642b8a1784149b479a55f49891a09b1cf972cb021a57687
1e4fcb3dc199eb3c6aec8a08f19e3f7b101f80735337ad4c34376b2f201cd6d8
d27162f90e3945437a182423c8364790af2e94bf57dbe9dc5a456a39e18cc552Trust 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 965041 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 6b573e6e60fcf639e95c85178fa342450e16527a05614494df16d1ad70a5b419; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6b573e6e60fcf639e95c85178fa342450e16527a05614494df16d1ad70a5b419, and the block's
timestamp proves the page looked this way at or before that time.