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
3763815a63f7536864876fed5ea33cb9c492eb2d335e8b52f39a582c367764e1
da8b08c70c1137356f1075b6e159202761210c88c6fc11cce5031c9660c6cc24
97351549585ad8734d7cf07a33c7eaa012c62a1cbaf24a55fd6e9bc9ab064f42
449c44e15b60de5595d8e62c5d86d9fd946a0f72f26a17f792a7e699b60161a0
42e81670c5ac1b65929ef49370edb21c5c0998ef987362222fee1bc8d272d17c
d8e7d60bb898a8356c361fafc5ebab23cace30090e839c1db306db0b97c818c0
7527686de24ea135e0dcb61ae5b58b1cf4f2523a7801384c4e83029805a17c19
c58d0301f4cd4fa811a344cde99a8f138c5e080f2fd0a77f178e79b55000afec
0203e12a2a3cd95d6279acae79b4e968506104a314f4af7b05bca32ed7a83dba
20156507bedd90c88884a35d205c9631bf1ae9a354175cc9a1deadd4c0eb5f4e
526cbb57b40cb017ec91015cf1ce5b74ab91ffe5134ddec58154f162f9903e26Trust 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 967973 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 d36e162aae2e826d2bade1cf2169adb184afdf58a12efe83a1c1f344e1b77df8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d36e162aae2e826d2bade1cf2169adb184afdf58a12efe83a1c1f344e1b77df8, and the block's
timestamp proves the page looked this way at or before that time.