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
bc36bc1afe93ce6db248b94d50edce4205950e61a5e22f61b77dab16a0a6755d
8fc82104bd3ab4fd0236605d92a4a6e6aa33e7ed0720181f478525c337498fa9
03b8b9e262044d86e8589e4f7db309fcc21c8658e9b08172961300299d94ca2e
ba0b8a4e2a805346971badd765e6139cc3d5685173eae0bb10994a7efac80b1f
7a1f96dd742e0c8184e73f34d366743c3d3c6ae8deb7b15c35ba311dc5075c05
c11241f740284b37ed7c3b6f0e84bca7108e1019f0c311ab559c509ba0e84509
466803e4d29dead0d8dffd9da34254b65923dca212410aae4302a6bc66522c57
699e62508b3df402812fde09e87f854abb9c63f9db96dc63d6de8195514027b1
697b209e3ff7f1de1ee8d7616b94a8a03d51edef5bb0b0346c6984e03d96efe8
f3e62b788758d98c37f40b35d3f6d16103e12bfaca2d7c3e19452ab90a431173
6c6b36f576628fdfd2f38f6ffdaf5fe983314e9022a03c63dc5ca2e17a760fd4
27fe6569f22af44664dc28dfe94cf394b71ccb02ba1505f3b0e92f4a7338134d
3792bf27be84fb169463b791ca17925412256e7e4e16279711417a9d03213395
dfad1fb327f7991cc6fc1ac4ea52b9cb2a7c249451f7595765b8203c498f2656
725f0cf027b82dbf56e25a3e2917e96fcfeadfd0a4ff26d08de1a3a9660a631eTrust 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 965106 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 1b2b82115a798e010610d9a40b7645307e0a56dbda0500ddce17938775f94a9a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1b2b82115a798e010610d9a40b7645307e0a56dbda0500ddce17938775f94a9a, and the block's
timestamp proves the page looked this way at or before that time.