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
ca1476cf7888dce06c8e695db796c3753f737f6a029f7eb294ebe97da8228929
2989739b1dd5da37476c9a6cd1518a1eed946dca856d7240ac4a1d5c6b91f3f8
6915a977efcc46355fccd816028674cf2b274c9eb4ae52e770ce1a46f982c4c1
dfbeac3b27287b87c66911ea59adb209239c2bad806e9deaa422f5bffd43195e
5cd007f7d87e32fee248e91f9e29f1a279660d16a8cdc6940216086f6f87a6ce
e07fb56523398879d3323707f2dc2436e56a1ad7f5d1591d8f5d90488a047bd1
c6f17a57dcaa8a25e40b8be92daa39bf1348d4e5d691022e649d26290e3c3e2a
37b2217e5044cac4074fdd2a0662c564e655077892ac98092e84827cd5d5823c
9dae6c072525752e98aa19432dbdd0e59e4da6990a80a60a0a6ca080f9790f9f
bd2788408b3858d6812124beed22b8713e720787a4d96bb2bc9aac819158e089
29eb6f46cdbd6dfae9df30f3f587f2868d103ef9290fb590f8447edd7bcbbc59
4891bc018b882b6630f12871308a322d3df6ff5406aa217f2323d5305c6e5658
3d3b5b6ce6f8dbeab7d5ac11203a6a3e7a2cb8a8887a348b0cda826404c6adfe
4a40e972b13a47c6cd4e56cdd5f3e28087720f0c3dd6e95d89332e3b8d154fb3
6b60f2fc58d4620592967eec5dcc04f6b577e73fb208395766cab6eec26eab36Trust 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 972345 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 1b7558e581b7433e4bebd06b4a7615282713a012c8fb8a690f516b51de9213f7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1b7558e581b7433e4bebd06b4a7615282713a012c8fb8a690f516b51de9213f7, and the block's
timestamp proves the page looked this way at or before that time.