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
2957f2f07eaace0ea56f33b6c870817af8126ca4354e6fa730f31e27c0a1778b
6c2136f279e2995da6a81a9fc05d64655a6a871aa6ca6ba39d1e49047fa00e6c
e5ab80e9b57d0027f7b77f02035c0f8d30878396c4497e528abf5eba76514bad
ccf8218434f2ba0222d5913bfbdbb00e403f75d1f41ba6f73d71829d4330121b
1231f8dfd919135a82d85c6c8bab050ba896c0a6b8524f6ead29eb74b0bbea78
c07fdcf4807ef1680f942dec5dfc4e6b93ebe8646ce6023589ff085ab27b6552
f5d2c7e3dea4793d7cb9833065d360be731772e3b5ebe730c4efb925b7aba811
3bc11365e022bc968fa9cbb6326a635a0f4db6063324fcf500d1d3153d1a2d93
6a09f935a0b4c862656d12e87efb0db86103cae7ee9927d3f960b29dd017398c
06f549babf6cf0828699926207258c5e1f49750e422fb435fbfcf529b47fe51c
02891013bf71c34f21a55e8751fb4d57cc2cb8efd7829d5bc4243053f27641d6
5b77cf288e3b71130ca0ba723e166cfc4ed7a27c31835b89710d9d7bfce94190
82c095911f77a2982ae214c13dae934ac86979e2d2662c4f93b33ab849b128abTrust 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 974757 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 2fe892208677a4d7a5231fae3c1cc002b94e6ed8416d4ed0c3d61e079ae0fe10; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2fe892208677a4d7a5231fae3c1cc002b94e6ed8416d4ed0c3d61e079ae0fe10, and the block's
timestamp proves the page looked this way at or before that time.