@BSVSearchon X · 2026-09-09
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-09 20:23 UTC.
Three days ago I said: the QR requests payment — check that the payment has arrived before completing the sale. Now the QR tool does the checking too! Introducing Sovereign Receiver 1.0 — it does everything Sovereign QR Maker does, and it also checks whether your payment has been 'detected' or 'confirmed' on your chosen BSV blockchain explorer. The newest addition to Sovereignty Tools. ✅ Enter your receiving BSV address, an optional amount (BSV or satoshis) and an optional note (readable by Sovereign Pay QR v1.4 or later, which can record the note in the transaction on the BSV blockchain) ✅ Show the QR on screen, save it as an image, copy the request, or print a payment sign ✅ Press Check payment — Receiver looks up your address and lists matching payments: amount, TXID, sending address, confirmation status ✅ Paste a payer's TXID to check one specific transaction ✅ Pick your explorer: WhatsOnChain, Bitails or BananaBlocks ✅ Checks run only when you press the button. No background polling, no webhooks, nothing phoning home. ✅ Receiver needs your public address only. No private key necessary. ✅ No account, no installation, no subscription. Free to use. ✅ A self-contained HTML file you can download, keep and use — QR creation works offline; checking needs a connection. ✅ Works on mobile, laptop or desktop. Mac, Windows or Linux. A 'Detected' payment is fine for a coffee. For a car, wait for it to be 'Confirmed'. Sovereign QR Maker stays available in the Archive. Sovereign Receiver replaces it going forward. Try it 👉 https://t.co/d8TTpLWxPJ Or explore the Sovereign suite of tools 👇: https://t.co/lab1a6UChC #BSV #Bitcoin #BitcoinSV #DigitalCash
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 52c5c14ba2908c443c21a9133b81a5c86164f4875a6ab1a14cd39bbaecef99fc; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 7f14e4d2afae07545e3e646d607c20a11f812b0afe6b486b6b99e0d27451802f, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 52c5c14ba2908c443c21a9133b81a5c86164f4875a6ab1a14cd39bbaecef99fc — the block's timestamp proves the post said this at or before that time,
with no trust in bsv.cx. Content archived via the X API.
