Stack Wallet

This commit fixes how Stack Wallet's desktop app parses token amounts for Solana tokens and other tokens. Previously, the app used simple string replacement for commas and periods, which could misinterpret numbers depending on the user's locale. For example, in some countries '1,000' means one thousand, while in others it means one. The fix uses locale-aware parsing and rejects inputs containing plus, minus, or space characters. The change also affects how displayed amounts are formatted, using the token's own decimal places instead of the coin's.

This commit fixes a bug in the Stack Wallet app where Firo (a cryptocurrency) address validation was incorrectly accepting Bitcoin-style 'bc1' and 'tb1' addresses. Because Firo does not use SegWit/Bech32 addresses, treating these as valid could let a user accidentally send Firo funds to a Bitcoin address, likely resulting in permanent loss of money. The patch changes the wallet to reject Bitcoin Bech32 addresses and adds tests to make sure it does so.

This commit fixes a bug in how Stack Wallet prepares Nano cryptocurrency sends. Previously, the app calculated the remaining balance after a send using a locally cached balance, which could be outdated. It now fetches the live balance from the network and explicitly checks that the user has enough funds. If the cached balance was higher than the real balance, the old code could have created an invalid or over-spending transaction.

This change updates three Flatpak app permission files so the apps can create their own data folders (like ~/.stackwallet) on first launch. Previously, the apps could only access those folders if they already existed, which could cause first-run setup to fail. The change is a sandbox permission tweak, not a fix for a code vulnerability.

This commit changes how Ethereum transaction fees are calculated in Stack Wallet. Previously, the wallet set the maximum base fee equal to the current network base fee, which could cause transactions to fail if network fees rose even slightly. The fix doubles the maximum base fee for preset fee options to give transactions more headroom. It also removes a check that prevented the priority fee from exceeding the maximum base fee. The commit adds extra logging for fee values but does not otherwise change security-sensitive code.

This commit changes how the Stack Wallet mobile app handles private Firo (Spark) transactions. It temporarily blocks sending private Firo funds to exchange addresses, and rewrites the internal logic for preparing and broadcasting Spark spends so that each transaction uses only a single Spark coin input. It also adds a new planner that can split one payment across multiple single-input transactions when needed. The change appears to be a defensive measure rather than a fix for an active exploit, but it touches sensitive transaction-building code and removes some previously available functionality.

This commit changes how transaction fees are calculated for a specific type of Litecoin transaction called 'mwebPegIn' (Mimblewimble peg-in). Previously, the fee was estimated once and the transaction was built. Now, for mwebPegIn transactions, it loops: builds the transaction, checks the actual fee based on the final transaction size, and rebuilds if the fee is too low. This is a bug fix to ensure users pay the correct network fee and their transactions don't get stuck or fail. There is no clear security vulnerability here; it appears to be a correctness/reliability improvement.

This commit removes two blocks of code that added an API key to outgoing requests for a cryptocurrency exchange integration called CypherGoat. The commit message calls this 'pointlessness,' suggesting the API key was unused or unnecessary. There is no direct evidence in the commit that this fixes a security vulnerability, but sending API keys when they are not needed can slightly increase exposure risk if those requests or logs are intercepted.

This commit is a minor cleanup: it swaps two ordinary print statements for Flutter's debugPrint (which only shows in debug builds), removes a leftover debug print of a transaction map, and stops sending an API key in requests to the CypherGoat exchange service. The API-key removal is the only change with any security angle, but the diff does not show what the key was, how it was stored, or whether it was sensitive. There is no evidence of an active vulnerability being fixed.

This commit updates a database migration in the Stack Wallet app. It bumps the database version from 2 to 3 and changes the upgrade logic so that, when upgrading from any version below 3, two tables related to a 'Shop in Bit' feature are deleted and recreated, plus an app notifications table is created. The commit message and code comment state this is needed to 'recreate sib tables correctly.' There is no explicit mention of a security issue in the commit or supplied references. The main risk is that deleting and recreating tables during migration could cause data loss if the tables already contained user data, but the developer comment claims the feature was not used before this point. No independent security disclosure or vendor security advisory was provided.

This commit makes several small adjustments to the CypherGoat exchange integration in Stack Wallet. It adds a new 'other' field to trade records to store a tracking URL, makes some CypherGoat API response fields optional instead of required, filters out some competing exchange providers from CypherGoat rate quotes, and fixes a minor error-message formatting bug. There is no clear security vulnerability being patched, and the commit message does not describe any security relevance.

This commit simply adds three identical SVG image files for a new exchange partner icon named 'cyphergoat' to the project's asset folders. It is a routine asset-only change with no code modifications and no apparent security relevance.

This commit only updates the .gitignore file to ignore the android/build/ directory. It is a routine repository hygiene change with no security relevance.

This commit fixes how Stack Wallet handles Firo masternode collateral UTXOs. Previously, the wallet could auto-freeze a UTXO, the user could deliberately unfreeze it, and then a later sync would re-freeze it automatically. The patch prevents that automatic re-freezing once a user has unfrozen a UTXO, while still allowing a first-time auto-freeze when masternode collateral is newly detected. It also improves the labels shown to users when collateral is detected with certainty versus only suspected. The pubspec.lock changes update unrelated dependencies and are not directly security-relevant.

This commit simply removes one travel booking option ('Full Service') from a list of choices in the Stack Wallet app's ShopinBit travel form. It is a routine product or UI change, not a security fix.

This commit is a UI refactor for the masternode feature in Stack Wallet. It removes a hard-coded note-based detection system for masternode collateral transactions and instead lets the user explicitly start the masternode registration flow from the masternode screen. It also fixes a couple of small UI bugs, such as showing the wrong error message text in slatepack/slate failure dialogs and properly formatting pre-filled amounts in the desktop send form. There is no obvious security vulnerability introduced, but the change removes a large block of auto-detection logic that previously tried to identify 1000-FIRO self-sends as collateral.

This commit hardens how Stack Wallet's CypherGoat exchange integration handles API responses. It replaces imprecise floating-point math with exact decimal arithmetic for money amounts, and stops silently substituting default values (like 0 or empty strings) when expected fields are missing. Instead, the app now throws a clear error if required fields are absent or malformed. This reduces the risk of incorrect trade amounts being shown or accepted, and makes the app fail more safely if the exchange server sends an unexpected or malformed response.

This commit updates the Stack Wallet app's ShopInBit payment flow to support a new version of the ShopInBit backend API (1.0.7). It mainly adds handling for expired and underpaid invoices, allowing users to refresh or retry invoices instead of being stuck. There is no clear security vulnerability in the diff itself; it appears to be a feature/bug-fix update for payment recovery.