Stack Wallet

This commit rewrites how the Stack Wallet app handles typed-in money amounts. It makes the rules for what counts as a valid amount much stricter: only digits and the user's locale-specific decimal separator are allowed, grouping characters (like commas in 1,000) are rejected, and the code now keeps a separate 'canonical' parser for trusted sources like QR codes. The change also adds recovery logic for on-screen keyboards that compose characters in unusual ways, so the app doesn't get stuck with an unparseable amount. The main risk is that a user could previously enter an amount that the app misread by a factor of 1,000 (for example, treating '1.000' as one thousand instead of one), which could lead to sending far more cryptocurrency than intended.

This commit only rewords the iOS permission message shown to users when the app requests access to the photo library. It changes a generic 'Photo Library Access Warning' into a clearer explanation that the app only reads images the user selects (for example, a QR code photo) and does not access the library automatically. There is no code change that alters what the app actually does or fixes a security flaw.

This commit only rewords the iOS permission message shown to users when the app wants to access photos. It changes a generic 'Photo Library Access Warning' to a clearer explanation that the app only reads images the user selects (for example, a QR code photo) and will not access the photo library automatically. There is no code change that alters what the app actually does or fixes a security flaw.

This commit simply swaps an old, deprecated 'Share' button function for the newer 'SharePlus' package equivalent in the PayNym screen. It is a routine maintenance/dependency update with no visible security change.

This commit updates several third-party software libraries (dependencies) and adjusts the code that shares QR-code images so it uses the newer library's API. It is a routine maintenance/cleanup change. There is no direct evidence in the commit that it fixes a security vulnerability, but keeping dependencies up to date can remove known bugs in older library versions.

This commit fixes a wallet bug where Litecoin MWEB peg-out transactions could be spent before they were actually valid on the network. MWEB peg-outs require six confirmations to mature, but Stack Wallet was treating them like normal transactions that only need one confirmation. The patch detects these special outputs and enforces the six-block wait, preventing users from accidentally creating invalid or rejected transactions.

This commit refactors how Stack Wallet builds Bitcoin-like transactions and calculates fees. It introduces a new fee planner that handles three modes: normal fixed-amount sends, 'subtract fee from amount' (the recipient gets slightly less so the sender doesn't need extra funds for the fee), and sweep/all sends. The change consolidates previously scattered fee logic into one place and adds unit tests. It is a code-quality and feature refactor; there is no direct evidence in the commit that it fixes a known security vulnerability, but any change to transaction-fee logic can affect whether users accidentally overpay, underpay, or create invalid transactions.

This commit fixes a UI bug in Stack Wallet where the custom/preset fee selection could get out of sync between the fee picker and the actual transaction being built. Previously, whether a custom fee was active was tracked in a separate local variable that could drift from the shared state provider. The patch makes the send flow read the fee mode directly from the shared state provider at the moment the transaction is prepared, and adds a helper that only supplies a custom fee value when custom mode is actually selected. The risk is that a user might have a preset fee selected while the app still uses an old custom fee value, or vice versa, leading to an unexpected transaction fee.

This commit adds support for 'memos' or 'destination tags' when swapping cryptocurrencies through third-party exchange providers. Some coins (like XRP, XLM, ATOM, etc.) require these extra identifiers so the receiving platform knows which customer account should get the funds. Previously, the wallet always sent these fields as empty/null, which could cause swapped funds to be lost or misattributed when sent to an exchange or custodial address that requires a memo. The change also parses memos from scanned QR payment URIs and shows input fields only when the chosen currency commonly needs one.

This commit is purely a code-formatting cleanup in a single Dart file that builds the QR-code generation screen. It rewraps long lines, adjusts indentation, and replaces a deprecated SVG color property with a newer colorFilter property. No security-sensitive logic, permissions, or data handling changed.

This commit hardens how Stack Wallet stores the desktop password 'key blob' on disk. It prevents creating a new password blob when one already exists, verifies writes actually landed, makes password changes more atomic, and lets the app recover when the stored version number doesn't match the blob. The changes reduce the risk of ending up with a corrupt or mismatched password state that could lock a user out or leave an old password usable unexpectedly.

This is a one-line bug fix in a mobile/desktop cryptocurrency wallet's auto-backup screen. The developer changed which folder path is recorded as the backup destination: previously the code saved the user's original picked path, and now it saves a computed 'pathToSave' variable. Without more context we cannot tell whether this fixes a security problem or merely a functional/UI bug, but it could affect where sensitive backup files are written.

This commit tightens how Stack Wallet parses account information for Nano cryptocurrency sends. Previously, if the Nano node returned an error or a malformed balance, the code could crash or behave unpredictably. Now it explicitly checks for error responses and invalid balance values before continuing. This is a defensive hardening fix that prevents bad node responses from causing app crashes or incorrect send calculations.

This commit fixes a network-labeling bug in the Nanswap cryptocurrency exchange integration. Before the fix, the code sometimes mixed up the currency/network a user was supposed to send in with the one they would receive out. That could mislead users into depositing funds on the wrong blockchain or network, which in the worst case could mean lost or stuck funds. The patch adds helper getters so the correct network is always chosen, and adds a unit test to confirm the behavior.

This commit fixes a cleanup bug in Stack Wallet: when a user deleted a FROST (multi-signature) Bitcoin wallet, the app was leaving behind sensitive key material and configuration data in secure storage and the local database. The patch now explicitly deletes those leftover FROST records during wallet deletion, reducing the risk that a deleted wallet's secrets could be recovered or reused later.