Seed phrase QR code safety: SeedQR, payments and PSBTs

Learn to tell encoding from encryption in Bitcoin QR codes and what to check before scanning a seed, payment, PSBT or xpub.

Seed phrase QR code safety: SeedQR, payments and PSBTs

A seed phrase QR code is not safe merely because you cannot read it at a glance. In SeedQR, the format can turn words into numeric indexes or binary data for transport; that is encoding, not encryption. A scanner that shows strange numbers, unreadable characters or no text does not prove that the secret is protected. If it contains a real phrase, protect it with the same precautions as the words and do not test it with a phone, website or generic app.

What a SeedQR contains

The SeedSigner SeedQR documentation describes a representation of a BIP39 mnemonic. SeedQR assumes and recommends the English BIP39 word list; the list is ordered and each word is replaced by its index. In the standard format, each index uses exactly four decimal digits in the same order as the phrase. The result may look like a block of numbers, but it still encodes the seed.

CompactSeedQR uses binary data for the same information in a smaller format and omits the mnemonic checksum because it can be reconstructed during decoding. A reader expecting text may misinterpret it or display symbols that make no sense. That appearance is not an encryption layer. The format also does not carry a word-list language identifier. Do not translate a mnemonic to make it compatible: preserve the words and list required by the wallet, and use the official import or recovery flow.

A plain SeedQR is a carrier for the mnemonic: an optional BIP39 passphrase is not included. A QR phrase alone does not recover a passphrase-protected wallet; that passphrase and the relevant wallet settings are also required. Check how the exact format documents those data before treating the backup as complete.

Do not create a scannable image of a real phrase to share, and do not keep a screenshot in a synchronized photo library. A QR is another way to present the same data. The camera, scan history, device backup or an app that records diagnostics can turn an apparently local operation into disclosure. Do not upload even an unreadable QR to a forum, chat or support service for troubleshooting: keep the original offline and consult the format's official documentation.

A payment QR is not a seed QR

Payment QRs serve a different purpose. The current reference for Bitcoin payment URIs is BIP321: a URI can carry an address, amount and descriptive parameters to request a payment. That is transaction-request information, not recovery material. Even so, a wallet should ask for authorization and show what will be paid before signing.

Check the network, destination address, amount and fee on the wallet's trusted display. A label or readable name does not replace the address you are authorizing. A QR that does not contain a seed is not automatically harmless: it can lead to a phishing site, request payment to an unexpected recipient or carry data that exposes your activity. Identifying the format is the first control, not the last.

PSBTs and connection QRs: different data, different risks

A BIP174 PSBT transports an unsigned or partially signed Bitcoin transaction together with information signers need. It is not a seed phrase and should not contain the private key needed to sign. A PSBT can still reveal inputs, outputs, amounts, change and other transaction details. Review those details on every device before authorizing, even when a known wallet generated the QR.

Connection QRs between a desktop wallet, mobile wallet and hardware wallet do not have one universal format. Depending on the software, they may include an xpub, fingerprints, derivation paths, descriptor configuration, a URL or pairing metadata. An xpub cannot sign by itself, but it can allow addresses and activity to be reconstructed and watched. BIP32 defines extended keys and their limits; BIP380 documents output script descriptors and their checks. The receiving app should explain which format it accepts and what it exports.

A QR is a carrier, not a guarantee about its content. Some wallet backup formats may encrypt their payload, while others only encode data. Verify the exact format name, its encryption documentation and how its keys are recovered before extending SeedQR's conclusions to another QR.

A descriptor is not automatically public either: BIP380 supports expressions containing private keys as well as public keys. Treat any descriptor you cannot identify as sensitive, and confirm that the export is the intended public or watch-only version before sharing it.

Do not accept a connection request just because it displays your wallet's logo. Confirm the account name, network, pairing purpose and the domain or device you expected. If the flow asks for a seed phrase, private key or unexpected file, cancel it: a legitimate connection does not need you to paste the master secret into a web reader.

How to review a QR without exposing a seed

Before bringing the camera close, identify the source and expected action. Then use this checklist:

  • Distinguish a seed, payment, PSBT and connection configuration. If you cannot identify it, do not scan it.
  • For a seed, work only with the wallet's device and official procedure. Do not use a generic QR reader, browser or online tool.
  • For a payment, verify network, address, amount and fee in the wallet; do not trust only the text next to the QR.
  • For a PSBT, check inputs, outputs, change and fees on every signer before approving.
  • For a connection, use only the expected documented export; do not share a connection or pairing QR or assume that it is public. Review permissions, account, network and receiving party, as well as xpubs, descriptors or URLs.
  • Rehearse the procedure with an empty wallet and synthetic data. A rehearsal checks interface steps, not recovery of real funds.

A valid word list or checksum also does not prove that the backup is complete. The BIP39 specification defines mnemonics, word lists and an optional passphrase, but it does not turn a photo, QR or file into secure storage. Keep the original medium until a controlled check is complete, and never publish an image to ask for help.

SeedAddress's boundary

SeedAddress derives a BIP39 phrase in the browser from selected coordinates, an input password, word-list language and word count. The selected location and other inputs may be public or guessable; the process adds no independent random entropy. Therefore 24 words describe an output length, but do not guarantee the security of 256 random bits. The generated phrase should not be treated as a strong backup merely because it has 24 words.

SeedAddress does not create a multisig policy, xpub, PSBT or encrypted QR for you. If you have chosen to keep a result, store an independent offline copy of the phrase that does not depend on repeating the calculation. Document the configuration needed to check compatibility separately. Keep the phrase out of photographs and cloud storage, and do not store the password beside it. The SeedAddress recovery guide explains compatibility; translating a BIP39 phrase can break it, and the guide to migrating from a deterministic wallet covers moving to a wallet created from random entropy.

The article on hardware-wallet connection versus seed import helps separate those flows. To check a backup medium, use the offline backup-check guide, never entering your words into a web service. Practice with synthetic data teaches the operation; it does not validate a real backup.

Sources