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
49e1e73e73dda45ecc45fe65b3db32c180bb0fe9e17658dd54eb486820b5305c
794f6fab94693ee7607760d2d230cf949b9b074ff6afd8a5f178c127702b0adb
96f8bb1940668a2e9f1560d7ae5aa784a0bf9bf0a3824b3b6dc55731edf3a431
14133c42c3f52554709e0c008439f0c570055fa5bd93f0b74ad46610fd76cf94
05e864505bbf9a3d533b11e38e27a834a876adc206434eb06119879d66424e62
beaa839185e2d5bfacbbe615507a9d475d3180143d063fc3dfa403169284a100
d7719cfa148079ad748568283cc938d58ada6527df0e1e8ce72b71ed8ae3d894
21f8305c637be77bccd91bbc33afd67b50f5497fd7ca96e1eb74f6c725bc7ccd
10e21bebde07256607b014682ad5d8e223e3466267c29b89daee79de685ec5b5
03516f8eeb797a35c40f3a1585ad2f7a9fc1217859f749f57c0a26f77a8506a2
9db2335204ba57f9e3489601e169c878a5e5d4d7644f744c30a77e8b1042db31
0544cd5530194bfbdf00b9a9e9b2e157231f721a6b2484ce4a4d47ba10871a91Trust 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 968236 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 4a40d517f8737ced9caf6901e84661edb2f13628b9a157f350b3274d2c2a20fc; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4a40d517f8737ced9caf6901e84661edb2f13628b9a157f350b3274d2c2a20fc, and the block's
timestamp proves the page looked this way at or before that time.