Krux

This commit only adds translations for two existing warning messages in the Krux Bitcoin hardware wallet software. It does not change any code logic, security behavior, or fix any vulnerability. The messages warn users that displayed fees may be understated and that input amounts are unverified, but those warnings already existed in English; this change just makes them available in more languages.

This commit tightens error handling in Krux's wallet parsing. Previously, the code used bare 'except:' clauses that would catch everything, including KeyboardInterrupt and SystemExit. Those special exceptions should normally be allowed to propagate so a user can cancel an operation or the program can shut down cleanly. The change replaces the bare catches with 'except Exception:', which still handles ordinary parsing errors but lets KeyboardInterrupt and SystemExit through. A new test confirms KeyboardInterrupt now propagates from all three parsing fallback paths.

This change fixes a bug where pressing a device's cancel/back button during address parsing could be ignored or misreported as an 'invalid address' instead of letting the user exit. The code previously caught every possible error (including user interrupts) and treated them all as address validation failures. Now it only catches actual address-format errors from the embit library, allowing legitimate user interrupts to propagate normally.

This commit only removes historical changelog-style comments from the code and rewrites the remaining comments to describe the current behavior. No code logic was changed, so there is no security impact.

This fix closes a hole where a Bitcoin address that looks valid (correct checksum) but belongs to no known network could be accepted by Krux's address parser. Before the patch, the parser only caught thrown errors; because the underlying library quietly returns nothing for an unknown address version, such an address slipped through as valid. The patch now checks that a real script output was produced and rejects the address otherwise. This could matter if a user scanned a malformed or wrong-network address and the device treated it as valid.

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 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 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 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 hardens the Krux documentation website by removing all embedded third-party content (YouTube thumbnails, Google Fonts, gitmind.com iframes) and adding a browser-level Content-Security-Policy. The goal is to prevent attackers who compromise a third-party service (like a CDN) from injecting malicious code into visitors' browsers when they read the docs. It is a preventive security improvement, not a fix for an active vulnerability in Krux's hardware wallet firmware itself.

This commit is a user-interface polish change: it adds a new green-colored success message method and switches existing success messages from the default text color to green. There is no security-relevant behavior change.

This update fixes two security issues in Krux, a Bitcoin signing device. First, it prevents the device from crashing when calculating fees for transactions that send no regular bitcoin (only data outputs like OP_RETURN). Second, it now rejects invalid multisig wallet setups where zero signatures are required or where more signatures are required than keys exist, which could otherwise allow unauthorized or impossible spending rules.

This commit simply adds two new hardware device names ('Embed Fire' and 'WonderK') to an internal release-signing script list. It does not change any security-sensitive logic, cryptography, or user-facing behavior. There is no indication of a vulnerability or security fix.

This commit is a code cleanup that changes how the Krux firmware imports and uses two libraries for handling Uniform Resource (UR) QR codes. It replaces broad 'import urtypes' statements with specific imports of individual modules, normalizes UR type string comparisons to uppercase, and simplifies one QR parser result return. There is no direct evidence in the commit that this fixes a security vulnerability.

This commit is purely a code-style cleanup. It removes an extra blank line and adjusts spacing around a comment so the code matches the project's formatting rules (the 'black' formatter). No behavior of the wallet software changes, and there is no security fix or vulnerability introduced.

This change relaxes how Krux checks the 'internal key' used in Taproot multisig wallets. Previously it required the wallet to use a specific deterministic chain code derived from the other public keys; now it only checks that the internal key is the well-known NUMS (provably unspendable) public key and ignores the chain code. This makes Krux compatible with wallets like Coldcard and Nunchuck that use different chain-code conventions, but it removes a validation step that ensured the internal key was constructed in a specific reproducible way.

This commit only removes blank lines between import blocks in eight Python files. It is a code-formatting cleanup with no functional changes and no security relevance.

This commit changes how Krux handles wallet descriptors. Instead of requiring users to manually set wallet type (single-sig, multisig, miniscript), network (mainnet/testnet), and address format, Krux now reads these directly from the descriptor. It also removes the old feature that tried to guess these settings from raw xpubs, which could make unsafe assumptions. When a loaded descriptor doesn't match the currently configured wallet, Krux now shows a clear warning and asks the user whether to switch settings automatically. Overall this is a security-hardening and usability improvement, not an introduced vulnerability.

This commit only updates user documentation for the Krux installer. It removes per-platform verification instructions and replaces them with a single new page explaining how to verify the installer's authenticity and integrity. No source code, build scripts, or cryptographic checks in the project itself were changed.

This commit only updates user documentation for installing the Krux desktop installer. It removes per-platform instructions for verifying downloaded files and replaces them with a single shared verification page. There is no code change, no firmware change, and no change to how Krux devices validate firmware. The only security-relevant aspect is that the docs still tell users to check file signatures and hashes before installing the desktop app.

This commit only updates the project's CHANGELOG.md file, adding two bullet points describing past bug fixes and improvements. No actual code changes are included, so this commit by itself does not introduce, fix, or alter any software behavior or security property.

This commit only updates documentation. It renames a wallet coordinator from 'Bull Bitcoin' to 'BULL Wallet' with a new link, and adds CSS margin styling to device images on the project homepage. There are no code or firmware changes, and no security implications.

This commit only updates documentation. It renames a wallet coordinator from 'Bull Bitcoin' to 'BULL Wallet' with a new link, and adds small margin styling to device images on the project homepage. There are no code or security changes.

This commit simply updates the list of supported hardware devices in the project's automated build system and release-signing script. It removes one device ('bit') and adds another ('tzt'). There is no code change that affects security, cryptography, or user-facing behavior.

This commit simply updates the list of supported hardware devices in the project's automated build script and release-signing script. It removes one device ('bit') and adds another ('tzt'). There is no security-relevant change in the code itself.