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
2432734f0c39a414fcbe3d4f04a377f0b2b89203623caecb2a87a59a78eeb1fe
4e0f93db64ae29e7d1d3e182687dd9805345ef3072c7f1d266eb551eef53663f
6109c4cd475599df3f65636733636ade49015bd71087c2a46f862daacfaaa266
bf24c7416bc5f394f71a9fad2c8ca2af1d706827b7dcb44fff8022b0aa8ffbba
1738fc49f8a6e5cbe1a6490867b7b475e63149dbc8e4e936b9528cd724ce42b7
5824778c6046b3cd324fcad75b505064f6f6bff0486a07df88cc9e5ac0540d16
a9df24e490e470098676851bb43ba7a4978dcff8f86a04b51ab8834a7d8752f2
7302cc414ad7ac3f8fcecb3f1573cf45a0fe902948d18d4ec672c68752909b01
1857f7f5b463558d00619ce0a82c0b9f3db8bbf1cd319f7bcf8007fbb8ec8f78
7ed2f00294bfd19e8730d3f01244c2927af41e8b5b14ad7029e6b94f1267cf0c
c618dccd00090b0acfe890904b8d508bde821b6d49e7cbf524d4d54ccb90b4b1Trust 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 971360 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 24176a10d8554fba72ed2ff359cdb17d101265f5db5289d609b1bc3a1e923900; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 24176a10d8554fba72ed2ff359cdb17d101265f5db5289d609b1bc3a1e923900, and the block's
timestamp proves the page looked this way at or before that time.