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
1e1653ede6a524f6e6c72e880bf0db475639bd4fe42b2cdb6546e3da07a9b6c9
22230ec77fe200024e1c58d070629bfe3acbb1b70ebd1a53f08bb77711ab3ca6
7e66f5331c1921a140716ac9f98c6474c1e97c724c58d26ca46a8db89a7a4279
bcba01bca74213531449bd42de750315b548781bb1b26f94f79ae4aa7d7eddbf
dbff0ac1506e9447ec2a01cf102ce2132019827bf0a0d3c8647a847719a04811
d4335efd5c9714e4de411819c46f06561b8ef7319f8a2e5b5fb964809d543a88
0bf1f2e50f1c7e9b83ddebbe1a7247cbf5d1ba9d29a534fd841cf0ef1e08cb0c
7677064ba9f35ee92bc2439393089bc539afb357e031f61a2b4197a395546b88
a85d18cc0b9e2cdf69fe543e1af1cacd1636f1e86f209ddc52fdd0d66e8c6997
06effb16858e05b5037c1a7b87243a557b810e83e4b08324341258fd7322455b
65249cc55aadddf2aa6ae830145737ee5128f2b1bba3cdf8542f8e176ea19dc0
09a6191ec8a0b037f359816f3943045e677c20172b30cc35bcbd94d2a11df59f
c5f4f84f20cce3b360dc6bd061ee387698dba1fa28750859dc5ba12720629497
603839813d5cb9f83daafaa230faebe73c2e7cad4bed376385d11db98377b106
9fbe38b259699c3e55bbf17561759377b8881ec7f251364c3d7e76db7f78d086Trust 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 964442 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 f478f4e796330d4f8bd77fed75b417134acc5f23c3a2782539f5dfed5e368eb6; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f478f4e796330d4f8bd77fed75b417134acc5f23c3a2782539f5dfed5e368eb6, and the block's
timestamp proves the page looked this way at or before that time.