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
77ab3ed43f5f1edf245fdf6f9fc624017a5a47197e23c605fee048ecc41396b0
181c01e6f15756bae5c4077e63bc9bdf6a327cc8f3798b20970b1a6a4ea9dec0
44f718c70c8fcc74673ab3348d0c8a7dde767fba27422fb672532f025c246a5e
563c008d1c112b77cc78af97ba828d49d975d9df8e5a72097b2b7659516b410c
bcce7c7745c460e04e0849fb3e5fa10e4a4725d837a5c17ef6b81c005d0151eb
f3b33ea02738f80a0bcc8eb0334fb1f63f7ac37dc2874792ca9e4c962e2df7cc
a817d0e7ee411e34ff863a10b6af18ca51654c6638edd06768956cf0735948c7
c9aaf1dcae9ab41667e3808e70fee7ece9dd04bcd6fe2a8aaba80de3b160178b
e717a1b752b2190c79fdc65d730e6d8ab502bf23967bf8cafd667d2c0682d63a
27d206aaf2552e0c7b83b9a619b6ac91b0c52d2d80655d1958ed250d190d5132
89b447d2f0d5c5bd092ff20a661038a8cf4303bb68b717e0f7564c19eb9abc7d
8efd7093044a467fb0e2c12badbd3897f49d2583432148383781b9b439256cd7
54820fa8808859fda2162c010b03ff9ab4ce791bc487867f7941941355203405
ddaafba8e412691389d4d64185a46f0df8c5d2cda1c19281f2235521fbadccd2
ffbd47eb1294afacea792fae077e3908e1e1a3ce753778f1c6ecfce7b6ac7c90
ad256f5ab62992b477da935d6e36189fda0bbf83a2a1801f5cb83908d3518a2b
59ae98487665fd5e88c5137376157ffdc28a99ec93ba454a108bcb295aeff208
82b96a0ee1c0595d23f44cb85feb3dd19ff54ede1d7b21eeeb6c00c3007c6ad5
9dd06d9bfd088ccd9880b65740ff8bc50f4efc7eab302b8f9b7e34e8e36eb79bTrust 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 973752 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 8e8b53afd91fe773e3b26dfca79029ea66268770d8eb67cbee814822550dedbc; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 8e8b53afd91fe773e3b26dfca79029ea66268770d8eb67cbee814822550dedbc, and the block's
timestamp proves the page looked this way at or before that time.