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
4d069836a8fe15b59d32516514c943525f4ee227c7b1722826ab6e89520d2bb9
fd9a426fcaf23491a77995dfa263f47313afcc4a9f16a981b60ab72ee3ed722a
f398397b679da2b52de19de73efd6941894aeff95caf52850428f05fe773d1ef
d0ad62c456bf4be3dafb3e283a6b308f450b5b2f8755568de187a1878e2ce1a6
528c59b1257e46d8d4dc37932e872e128f5f8d8a2d8a86eae2dc7281dd2a715c
16fb6a7b93e05ff58b9bef94e8b077a058d47f24becc514ee4931f54211d59f0
939a2ef66f377007c56895a53051dcdac41f053559096212283b021a8b4c0f5d
74c2766dd28cc4ddcb3bbd609d136c3533c11e495e46768edcac1b361e2dcadb
603ed183ab8e70c0f011c716e4bd7e818e4aefe7a3734951fe0874f95dad08ea
ecb7f022938e1657652777bf138b8cb7aec2a98a6c16a048556efd2239843a8eTrust 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 965808 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 d801b47be073f462a1107f13fde543621d7150912e7ef9fc1e7039812b509003; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d801b47be073f462a1107f13fde543621d7150912e7ef9fc1e7039812b509003, and the block's
timestamp proves the page looked this way at or before that time.