SeedSigner

This commit adds a friendly, specific error screen for when the SeedSigner device cannot talk to its camera. Previously, camera connection failures fell through to a generic 'unhandled exception' screen. The change reroutes that specific error to a new screen that tells the user to check the camera cable. It is a user-experience and diagnostic improvement, not a security fix.

This commit removes two redundant import statements inside a camera driver file. The same class (CameraConnectionError) is already available in the module, so the local imports were unnecessary. There is no security-relevant change.

This commit only changes the text on two on-screen buttons: one shown when an unrecognised QR code is scanned, and one shown after an unexpected system error. It does not change any security logic, input handling, cryptography, or network behaviour. It is a user-interface wording fix with no security relevance.

This commit changes how the SeedSigner camera code handles hardware camera failures. Instead of letting a low-level PiCamera error crash the user experience with a technical message, it now catches that error and raises a friendlier 'CameraConnectionError' telling the user to check camera connections. It is a reliability/usability improvement, not a security fix.

This commit is a large merge that appears to be adding documentation, build infrastructure, enclosure designs, and other project files to the SeedSigner repository. The commit title mentions adding a screenshot for a brightness tip during QR display. Based on the supplied diff, there are no code changes that introduce security vulnerabilities. The additions are primarily documentation, GitHub workflow files, Docker setup, 3D enclosure files, images, and PDF templates. No malicious or suspicious changes are visible in the provided materials.

This commit only rewords two sentences in a documentation file about SeedQR. There are no code changes, no configuration changes, and no security-relevant alterations.

This commit only edits a README document to make wording clearer. It does not change any program code, cryptographic behavior, or user-facing functionality. There is no security issue here.

This commit is a large repository merge that primarily adds documentation, build workflows, enclosure files, and project scaffolding. The only code change described in the title is a minor bugfix in toast.py that removes an unnecessary sleep delay to speed up the screenshot generator. There is no indication of any security vulnerability being fixed or introduced.

This commit only adds a new automated test to the project. It does not change any production code, so by itself it cannot introduce a security vulnerability or fix one. The test checks that the software can correctly handle PSBT files where wallet fingerprints are all zeros, which can happen when a wallet is created from an extended public key (XPUB) without a full derivation path. The test verifies the software can match the public keys against the seed and fill in the correct fingerprint.

This commit changes how SeedSigner handles Bitcoin transaction files (PSBTs) that contain placeholder '00000000' fingerprints. Normally, a fingerprint identifies which wallet seed a transaction belongs to. Some wallet software exports incomplete data (xpub only, no derivation path), leaving zeros in the fingerprint field. Previously, SeedSigner could not recognize these transactions as belonging to the user's seed, showing a '?' and potentially refusing to sign. The new code tries to reconstruct the correct fingerprint by deriving public keys from the seed and comparing them. This is a usability fix, not a vulnerability patch, but it touches security-critical matching logic.

This commit fixes a localization bug in a Bitcoin seed backup verification feature. It prevents BIP-39 seed words (which must stay in English) from being translated into other languages when displayed as quiz answers. Previously, translating these words could confuse users or make backup verification fail. There is no direct security exploit here, but it removes a usability/reliability issue in a security-sensitive workflow.

This is a small internal cleanup change in a Bitcoin hardware wallet project. It replaces a manual flag used only during screenshot generation with an existing renderer property that already tells the code whether it is running in screenshot-generation mode. There is no user-facing or security-relevant change.

This commit is a small internal cleanup that changes how the screenshot test tool tells the splash screen to skip animations and delays. It replaces a parameter passed into the splash screen with a property checked on the renderer object. There is no security-relevant change for end users.

This commit is a large merge that appears to be an initial repository import or branch synchronization for the SeedSigner project. It adds documentation, images, 3D enclosure files, CI workflows, Docker setup, and the full application source code. The commit title refers only to excluding hardware drivers from test coverage. There is no code change in the diff that fixes a security vulnerability, introduces a security feature, or alters cryptographic, wallet, or secret-handling logic.

This commit is a large merge from the 'dev' branch into 'enable_persian'. The visible changes are almost entirely documentation, images, printable PDF templates, 3D enclosure files, GitHub workflow files, Docker setup, and project metadata. No source code changes that handle private keys, seeds, PSBTs, QR parsing, or cryptographic operations are visible in the supplied diff. There is nothing in the provided materials that indicates a security vulnerability.

This commit only changes two button labels from title case to sentence case ("Discard Transaction" to "Discard transaction" and "Approve Transaction" to "Approve transaction"). It is a cosmetic text change with no security relevance.

This commit only renames user-facing text strings. Every occurrence of 'PSBT' shown to the user is changed to 'Transaction' or 'Proposed Transaction' (for example, 'Review PSBT' becomes 'Review Transaction'). There are no code logic, security, or behavior changes.

This commit is a simple code cleanup (refactor) in the SeedSigner project. It removes an unused intermediate screen that asked users to choose a BIP-85 'application mode' and instead takes them directly to choosing 12 or 24 words. The actual behavior for users remains the same because only one application mode (BIP-39 child seed) was ever supported. There is no security issue here.

This commit is a large merge of a test-only pull request titled 'exhaustive_psbtparser_tests'. The visible diff shows only new documentation, CI workflow, Docker, and project metadata files being added; no changes to the PSBTParser source code or runtime security logic are present in the supplied diff. It appears to be an initial repository population or a merge that brings in testing infrastructure and documentation rather than a security patch.

This is a minor code cleanup (DRY = Don't Repeat Yourself) in the user interface of a Bitcoin seed-signing device. It merges two nearly identical blocks of code that update the on-screen title into one shared block. There is no security-relevant change.

This commit simply moves a log message one line earlier in the code, placing it above a comment instead of below it. There is no functional change, no security fix, and no behavior change. It is a minor code cleanup (refactoring).