Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — foundational services, anchored to Bitcoin
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
cb938d727362dddfa3bfa9e10c06f42590d9f7d059016ebd4bc966fb4537d315
9a3b0a39aec9c3607030a5db9fd9c78ddb849af28e5ec658bc39b91b745c46f4
447a0f39e82717f7f57c14235429985eb476ff623a2fd0b0b5529fac774978c8
7eae56269a38fcdc9bd35ec7220b32f209d6a86e58ca040ffabbfca7bdc3fc84
4313ab11defffecc9c843d599009879714a26112e5cd3d9256a103bd39f5c588
09eec7b5a55b53555cbbc62c36dbbfbf38fb28b6f08833a15b20cda5113037c5
5fc915fa2c47365f5369c15320d777268029c6c955bc9379126b52881353bb43
e0273923b01dc8ec218dd95ad2cef1e9943308bf374394257bbfe4207f2834d2
630f0d86c99ea3f77f325f537d911fd1f575807efd331f50ceeb61c264dda8f0
61f588654a3218b1541dbede91325ee64b3640ff9e86294aaf546189ba0b0633
5edfe2468d8999b416e0c9646e861de9f19b48917ddb3c2b8ce87c94a911804f
a4fd1894d92ddbcf40d67ef2f71c9ebbf699873419f284bde45a225d441f2608
d3df3af1125ccd5847661a5efe1555cb4a5985f6be6f7c0602f640de7ef55da1
2817063eabe564f4e66b2e074ee245a1a0298ab2cb1e6793aa4f2be36e2c4e64
1d53397c41f330d051e378c78925e8ffd52a6035b2152d9cb5f9c05f231fdb2b
cf1c32f580b889c25c4066220b140512dd649c9badab1a7acaa5ad307bb88deb
f7c7c067c39dd5c20e38815189291b1b43a149b533e3a0d7b1bd2ec08072f5fdTrust 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 959010 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 aa0454ed8c8ac0414dcbae8de0275bdf1aaa03e2d1078ea01d8ed1021c8c1c5d; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / aa0454ed8c8ac0414dcbae8de0275bdf1aaa03e2d1078ea01d8ed1021c8c1c5d, and the block's
timestamp proves the page looked this way at or before that time.