SeedSigner

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).

This is a small internal code cleanup in SeedSigner, a hardware wallet project. It moves the creation and starting of a background restart thread from a setup method into the main run method. There is no obvious security problem introduced by this change, and no security relevance is stated by the project.

This commit reverts a test-only change in the screenshot generator. The original change made the test delete any existing screenshot file before generating it, then verify a new file was actually created. The revert removes that explicit cleanup and verification. This is a testing/quality-of-life change, not a security fix or vulnerability introduction.

This commit removes a single blank line from a test screenshot generator script. It is a cosmetic code cleanup with no functional, security, or behavioral change.

This is a small cleanup change in a test screenshot generator script. It removes some leftover debug toast notifications and a custom exception used to exit a screenshot loop. There is no security relevance visible in the commit.

This commit adds a quality-check to the project's internal screenshot-generation test tool. It counts how many screenshots are produced and raises an error if a test view fails to render one. There is no change to the actual SeedSigner wallet application or its security.

This change improves a test helper that creates screenshots for documentation. It now deletes any old screenshot before generating a new one and throws an error if the new file is not created. This is a quality improvement for tests, not a security fix for user-facing code.

This commit simply moves a log message that says 'Restarting SeedSigner' from one place in the code to another place inside the restart thread. It does not change what the program does, only when a status message is recorded. There is no security issue visible in this change.

This commit fixes a screenshot-generation test issue. Previously, the RestartView skipped rendering entirely when used by the screenshot generator, so no PNG image was produced for the restart screen. The change now renders the reset screen but only starts the actual restart thread when not in screenshot mode. There is no security issue here.

This commit is a massive initial repository import or merge of the entire SeedSigner project into the branch. It adds documentation, images, 3D enclosure files, GitHub workflows, Docker files, and source code. The commit title mentions only one file (psbt_screens.py), but the actual diff covers 328 files and is almost entirely additive. There is no evidence in the supplied materials of any security vulnerability, malicious change, or code defect.

This commit is a straightforward internal code cleanup: it replaces direct calls to a screen's `.display()` method with a new helper called `self.run_screen()`. The user-visible behavior appears unchanged; it is a refactoring, not a security fix.