01 — Current maturity
What Public Preview means
These releases have passed tests and checks, most of which are documented here. They are now available for public preview. As with anything involving Bitcoin or other cryptocurrencies, use them with care, and consider sharing feedback and data that may help other users and support further development. It does not mean that every device, browser, camera, network condition, recovery procedure, or payment situation has been tested.
Source-visible code, local processing, checksums, transaction previews, and signature verification are useful controls. They do not guarantee that a device is uncompromised, a destination is correct, a private key is safe, or a transaction can be reversed after it is sent to the network.
Broadcasting is the final step of sending an already-signed transaction to a BSV network service so it can reach miners. It is unrelated to radio or television broadcasting. It does not send your private key, and acceptance by a service does not guarantee that the transaction will be mined or confirmed.
02 — Completed
Checks applied to the current files
- Executable inline scripts parse without syntax errors.
- Live document IDs, direct script references, and manual anchors are checked for consistency.
- Protected product identity, attribution, configuration anchors, review gates, and the Sovereign Pay fee mechanism are checked.
- Sovereign Pay excludes unconfirmed incoming coins, coins already being spent by a pending transaction, and duplicate outpoints; it rechecks every input immediately before network submission.
- Edition names, plain-language labels, Public Preview notices, and QR target boundaries are checked.
- On-chain note embedding starts off in every Pay edition and requires an explicit user opt-in before signing.
- Release copies, byte counts, SHA-256 records, checksum files, and archive contents are compared for agreement.
- Application self-tests and the maintained release gate are run where the current fixtures cover the feature.
Automated checks show that the tested conditions behaved as expected. They are not a security audit and cannot cover every real-world environment.
03 — User feedback
Where user feedback is most useful
If you choose to provide feedback, the following observations can help other users and inform further development:
- Camera and QR use: the device and browser used; how camera permission, denial, retry, shutdown, and image fallback behaved; and whether the decoded result matched what you expected.
- Browser and device conditions: the browser and operating system, device type, screen size, printing experience, offline reopening, and recovery workflow.
- Payment workflow: the stage involved (coin lookup, review, signing, network submission, or confirmation), together with what you expected and what you observed.
- Key, signing, transaction, or QR observations: reproducible steps using redacted or throwaway information, never a live private key, seed, wallet backup, or signing package.
- Web3 access and file integrity: the route, resolver or gateway, content type, file SHA-256, and whether those values matched the release information.
04 — Careful use
If you choose to use a Preview release
For Sovereign Keys, use a trusted offline device and prove that the intended backup and recovery process works before receiving meaningful funds. For Sovereign Pay, begin with a small amount you can comfortably afford to lose and verify every address, amount, note, tool fee, miner fee, change output, and decoded transaction preview before signing or sending the transaction to the BSV network.
Use the simplest edition that meets the actual need. Do not scan private keys or signing information merely because an edition supports it. Stop if the file hash, interface, decoded information, or result differs from what you expected.
05 — Feedback
Report unexpected behaviour without sharing secrets
Use the publisher or distributor channel from which you received the release. Include the product and edition, file SHA-256, browser and operating system, device type, the action taken, the expected result, and the observed result.
Do not send private keys, WIFs, seeds, mnemonics, wallet backups, credentials, unredacted signing packages, or live-fund test data in a report, screenshot, chat, shared document, or diagnostic log.
06 — Graduation
When the Preview label can be reconsidered
The status can be reconsidered after a certain period to allow for it to be used by many people, using different browsers, devices, situations and configurations.
Testing status updated 8 August 2026, Gregorian calendar, in Belgium. English-language edition.
Return to the tools