Krux

This commit only changes test infrastructure. It replaces the garbage collector's collect() function with a no-op during automated tests so the test suite runs faster. It does not change any code that runs on real Krux devices or affect how user funds or data are handled.

This commit only changes a test file to make it run faster by faking the system clock. It does not modify any production code, so it has no direct security impact on users of the Krux device or software.

This commit only updates user documentation and the changelog to describe a recent user-interface change for generated mnemonics. It does not modify any code, cryptographic logic, or security behavior, so it has no direct security relevance.

This commit reorganizes the on-screen menu shown after a wallet key is generated or loaded in the Krux firmware. It splits the existing options into a two-level menu for newly generated mnemonics while keeping the old layout for existing ones. There is no security-relevant change visible in the code.

This commit only adds new automated tests for the wallet login flow. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly. The tests verify that menu navigation works correctly when a user creates a new wallet from a generated mnemonic versus loading an existing one.

This commit is a routine translation update. It adds or updates translated text strings for user interface labels such as "Continue", "Wallet Options", "Standard", and "Vertical" across multiple languages. There are no code logic changes, no security fixes, and no behavior changes.

This commit only updates user documentation. It adds new screenshots showing how to create a new wallet mnemonic and updates the script that automatically generates those screenshots. There are no code changes that affect security.

This commit is a simple code cleanup: it pulls duplicated code for drawing a wallet information screen into a single reusable helper function. There is no change to what the program does, no new behavior, and no security issue visible in the diff.

This commit is a routine dependency update that bumps the bundled 'embit' library to a newer commit. No actual code changes are shown, and no security relevance is stated in the commit message or title.

This commit only updates project documentation. It removes shopping links for a discontinued hardware device and adds a note that the device is no longer for sale. There is no code change and no security relevance.

This is a routine cleanup commit that deletes two unused color constants (LIGHTGREY and PURPLE) from a theme file. It does not change any behavior, fix any bug, or alter any security-related logic.

This commit only updates project documentation. It marks the Maix Amigo hardware device as discontinued and removes links to stores that used to sell it. There are no code changes and no security implications.

The commit title says it is a routine maintenance update ('chore') for two internal items named cUR and k_quirk in the MaixPy firmware file. No diff content is available, and no verified references were supplied, so there is no visible evidence of any security change.

This change locks the Docker build to one specific, unchangeable version of the GCC compiler image by adding a cryptographic fingerprint (SHA digest). Without this, an attacker who compromises the GCC image registry could silently replace the 'gcc:12-bookworm' image with a malicious one, potentially injecting backdoors into Krux firmware builds. Pinning by digest prevents the build from accepting a substituted image, but it does not fix any already-known vulnerability in the code itself.

This commit adjusts how a Python build tool (poe) finds the project's own source code when running commands. It adds the local 'src' directory to the PYTHONPATH environment variable for poe tasks. There is no indication this is a security fix; it is a development workflow fix to make local imports work correctly under the 'uv' packaging tool.

This commit fixes a bug in Krux, a Bitcoin hardware-wallet tool, where saving a new encrypted seed could silently overwrite a damaged seeds.json file. The patch makes the app detect corrupt or misshapen seed storage and stop the save, preserving the existing file so the user can recover it. It also prevents the seed list menu from crashing when the stored file is malformed. There is no evidence this was a malicious backdoor; it appears to be a defensive bug fix.

This commit fixes a small bug in how Krux loads saved encrypted seed data. Previously, if the saved file was valid JSON but shaped like a list instead of a dictionary, or if the requested seed ID was missing, the code could crash with an AttributeError instead of cleanly returning None. The fix makes the code treat those cases as 'nothing found' and adds tests to confirm it. The commit message says the on-device behavior is unchanged because the only caller already catches exceptions.

This commit is a defensive code cleanup, not an active vulnerability fix. It narrows four broad 'catch-everything' error handlers in the wallet's encrypted mnemonic storage module so they only ignore expected file/JSON problems. Unexpected errors (including serious ones like memory exhaustion or user cancellation) now surface instead of being silently swallowed. The change improves future bug detection and reliability but does not by itself create or close a known exploit.

This commit changes how Krux loads its encrypted seed storage file. Previously, if the file contained valid JSON but in the wrong shape (for example, a list instead of a dictionary), the app would silently treat it as empty and overwrite it on the next save. Now the app keeps the file's original contents and relies on a separate safety check to avoid crashing. The change is described as a code cleanup, but it also removes a behavior that could hide or destroy user data if a storage file were tampered with or corrupted.

This commit adjusts color values in the Krux device's user interface themes to improve text and icon contrast. It is purely a visual accessibility/usability fix and does not change any security-sensitive logic, cryptography, input handling, or network behavior.

This commit is a performance refactor, not a security fix. It caches a single copy of the app's settings object tree so it doesn't rebuild ~16 objects every time code asks for Settings(). The actual setting values are still read fresh from storage, so behavior should not change. A test helper is updated to clear that cache so a mocked wallet class gets picked up during tests.

This commit is a simple code cleanup: it replaces two copies of the same display-orientation check with a single shared helper method. There is no security-relevant change in behavior; the logic before and after is functionally identical.

This commit only updates developer documentation, replacing instructions that mentioned the Poetry Python tool with instructions for the uv Python tool. No code, dependencies, or security behavior changed.

This commit is a routine developer tooling change. It replaces the 'poetry' command with the 'uv' command in documentation and a screenshot-generation script, and adds a single trailing comma in one Python file. There is no change to the actual Krux wallet application that users run, and no security-relevant behavior is modified.

This commit swaps the project's Python virtual-environment and dependency-lock tooling from Poetry to uv. It deletes the old Poetry lockfile (poetry.lock), updates pyproject.toml to use uv-compatible metadata, and adds a new uv lockfile (uv.lock). There is no change to application source code, runtime behavior, or installed dependencies, and nothing in the commit indicates a security fix or vulnerability.