Sovereignty Tools — Choose Your Tool and Work Safely

This short guide helps you choose Sovereign Keys or the appropriate Sovereign Pay edition, then begin with the safest practical workflow. Each tool has its own exact-version guide. Public Preview.

Start with practice, not meaningful funds. Sending a Bitcoin SV transaction to the network is generally irreversible. For a first attempt or a new workflow, use fabricated data without signing where possible. If you later choose a live rehearsal, use a tiny amount you can afford to lose and a destination you control.

Choose the smallest tool that meets your need

QR Editions 1.0 and 1.2 are both active. Edition 1.0 is the narrower choice, not an obsolete release.

The safe key sequence

1. Verify the exact Sovereign Keys 1.0 SHA-256 before opening the file.
2. Use a device, browser, printer, and physical space you trust; disconnect before real-value key work.
3. Charge the randomness bar, accept the risk notice only after reading it, and generate the key.
4. Make more than one accurate backup in separate secure locations.
5. Prove recovery produces the same address, compression choice, optional passphrase, and derivation path before funding it.
6. If you choose live funds, start with a tiny amount you can afford to lose and prove you can recover and spend it.

The safe payment sequence

1. Identify spendable coins. Check the source address and the confirmed amount. Pending incoming coins and coins already moving in the mempool are not available to spend.
2. Enter the destination and amount. A valid address checksum does not prove the address belongs to the intended recipient. Confirm it through a channel you trust.
3. Review change and both fees. Confirm the change address is yours. Sovereign Pay shows its 0.01% tool fee separately from the network miner fee.
4. Decide whether a note should be public. Embed notes on-chain is off by default. Leave it off unless public, permanent disclosure is intentional; tick it only before signing a transaction whose note you want embedded.
5. Sign only on a device you trust. Direct WIF entry is an expert, preferably offline workflow. Tick the risk acknowledgement only after reviewing the plan.
6. Review the decoded signed transaction. The result is decoded from the actual signed bytes. Check every recipient, amount, note, fee, and change output.
7. Send only when it is correct. “Send to the BSV network” means submitting the already-signed transaction to a network service. Provider acceptance does not guarantee mining or confirmation.

Treat different data according to its risk

• Secret: private keys, WIFs, mnemonics, BIP39 passphrases, wallet backups, and operational credentials. Never place these in email, cloud-synced photos, support messages, chat, screenshots, or AI prompts.
• Sensitive but not a private key: signing packages and signed transactions. They reveal payment details; a signed transaction may be broadcast by anyone who receives it. Do not publish them or send them to support or an AI.
• Public: addresses, transaction IDs, and confirmed UTXO references are blockchain information, but collecting them together may still reveal financial relationships.

Verify the file before trusting it

A Sovereignty Tools application or manual received from another person, website, storage service, message, or download source may have been changed accidentally or deliberately while keeping the expected filename. A modified application may not operate as designed, developed, or tested by BSVSearch.com. It could behave unexpectedly, display misleading information, expose private information, or construct an unintended transaction. A modified manual may contain incorrect, misleading, or unverified instructions that were not written or reviewed by BSVSearch.com. Either can produce unexpected, unintended, or unwanted results.

Verify before opening an application, entering a private key, relying on a manual, or using funds. Do not treat a familiar filename or appearance as evidence that the file is authentic.

1. Visit https://bsvsearch.com/sovereigntytools.web3 and identify the current version, exact filename, byte count, SHA-256 value, and inscription transaction ID (TXID).
2. Obtain the raw file identified by that TXID. If you received a copy through another channel, verify that copy against the same release record.
3. Calculate the SHA-256 of the exact file on your own device. Hash the ZIP when comparing with the ZIP record and the extracted HTML file when comparing with an HTML-file record; those are different artifacts with different hashes.
4. Compare all 64 hexadecimal characters with the published SHA-256. Letter case does not matter, but every character must otherwise match. Use the byte count as an additional check.
5. If the SHA-256 or byte count does not match, do not open or use the application and do not rely on the manual. Delete that copy and obtain the current release again from a source identified by BSVSearch.com.

An exact SHA-256 match confirms that the local file is byte-for-byte identical to the recorded release. The TXID identifies the immutable inscription, while the BSVSearch.com page identifies which inscription and version is currently recommended. These checks do not guarantee that the software is flawless, that every possible situation has been tested, or that the device on which it runs is secure.

Windows: calculate SHA-256 with PowerShell

1. Open PowerShell.
2. Run the following command, replacing the example path with the path to the exact file you are checking:

Get-FileHash -Algorithm SHA256 -LiteralPath 'C:\path\to\the-file.html'

3. Compare the value shown under Hash with the published SHA-256. Microsoft documents Get-FileHash in its official PowerShell reference.

macOS: calculate SHA-256 with Terminal

1. Open Terminal.
2. Type shasum -a 256 followed by a space, drag the file from Finder into the Terminal window, and press Return. The resulting command will resemble:

shasum -a 256 "/path/to/the-file.html"

3. Compare the first 64-character value in the result with the published SHA-256. Apple documents this shasum -a 256 method in its official guidance.

If these instructions no longer match the operating system, consult current official Microsoft or Apple documentation for an offline SHA-256 utility. Do not upload a Sovereignty Tools application, manual, or any file containing private or financial information to an online checksum website.

The BSVSearch.com URL is a version and advisory pointer, not a runtime dependency: the downloaded tools and these guides remain self-contained and do not contact it automatically.

Review status: the release has automated tests and independent peer-review evidence, but it has not received a formal security-audit certification. Not every device, browser, provider, or workflow has been tested.