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
9ab7ce73d7af0fdfcc4a253ec0768349fea843fbaebfc6dc627687a51ed89e95
7ef1ddacc6af777c538a19cd6cb45fa613a9d1f84ac794f250e760ce33334c2a
f384ab1c09920e245fac91eab75a21214180a84611abd9caf338141a351dc9dd
782ff8d51b928988f817018e0bb61dc21a219403f9ece4d18edb83a7963cc0ac
bcb56177c2ebc05fd9fdc5350c6bbc17ece1039d6e8b0a6f182923f0ddc1b669
c3b4521a1b908f8d5c3916237ec1aa0eb3de5b69510611f561bf5c5d63961ae1
cbbe3da5790439fef050106c8cc67b819dadaa5b01725185f0a03fe5a04cf1f8
66b7d95c1762b7cf494fcfb507812e337d84a5b99e0116d1859420b496cf811c
44edeb419354bc856550c7851e836420f4fa3202d04104eca2e3b88d9f74ac07
7ef20de6492aa43c1633ff71a194af6edaad858737594b5ad4a212817d512acf
d47e5df3f1213974e93d692681e0ca8073797bffdd9ff406f77dfe6e5d05733c
7dd4173450c70a9e41f200de305dfeea646f185a2d321da7d58520c087aabc0a
5324f20ab9273968691218957fca3a595ab5438d7bda264e73bbb23e5870995c
e0c5df05f368a69e7fccbb884df3fc8c7039c721a9a6db0af945619decb425d3
cdd15691de809d02d75a3af319c3efa5c107aab40ef40f3b8db480dfd99d8435
f7a481dbcdd3d8216d10d1185f6c435a9c3f3bded08ec87aad40a9f2c076af53
8e58f2c2df93c2fe7b4128fe52b3b4aaa288487b12e990b9ecd1c31b2ff69c41
854a8c638afb33c391fe179e657d84d6c736e9d67f0f7c4ecce7e667f4c26f15Trust 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 964647 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 d648d5371667c49053a0a41455d478f2b67d5157a18f2cadbd2405a0f24a5fa2; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d648d5371667c49053a0a41455d478f2b67d5157a18f2cadbd2405a0f24a5fa2, and the block's
timestamp proves the page looked this way at or before that time.