Stack Wallet

This commit fixes a bug where scanning a QR code could accidentally close the same screen multiple times in rapid succession. The change wraps the scan handler so it only runs once, and also cancels the camera stream before closing the screen. Repeated pops could cause navigation glitches or minor app instability, but there is no direct evidence it could be used to steal funds or keys.

This commit swaps the app's QR code scanning library on Android from one that uses Google's ML Kit to an older one that does not. The change is framed as a privacy move to avoid sending camera frames to Google's ML services. The diff also adds null checks on scanned QR results, which prevents some crashes when a scan returns no content. There is no direct evidence in the commit that this fixes an active security vulnerability, and the bulk of the diff is formatting changes unrelated to security.

This commit adds a placeholder UI message ('WIP') for sending Solana tokens on the desktop wallet view. It does not implement actual token-sending logic, nor does it change any security-sensitive code. The change is purely a UI stub to avoid falling through to the generic token-send widget for Solana wallets.

This commit adds a user-facing toggle that lets Bitcoin wallet owners choose whether to generate older-style "legacy" (P2PKH) addresses. Previously, the app hid legacy addresses for Bitcoin wallets when other address types were available. The change is a feature addition, not a bug fix, and does not appear to address any security vulnerability.

This commit is a defensive bug-fix in the desktop wallet UI. It prevents the app from crashing when a Solana token wallet is selected, because the shared UI components were originally written only for Ethereum-style token wallets. The changes replace hard assumptions (that a token wallet always has an Ethereum contract object) with null checks, try/catch guards, and placeholder labels. There is no evidence of an exploitable vulnerability; it is a robustness improvement.

This commit refactors how Stack Wallet saves wallet addresses during wallet recovery and rescanning for ElectrumX-based coins. It centralizes repeated address-gap-checking logic into a single helper function and changes how the highest used address index is tracked. The change appears intended to fix a bug where unused addresses beyond the gap limit could be incorrectly stored, which could lead to missing transactions or an incomplete wallet balance after restore. There is no clear evidence in the commit of a traditional security vulnerability such as theft of funds, but a bug in address discovery could affect wallet correctness and user funds visibility.

This commit adds a new 'Sign/Verify message' feature to Stack Wallet, letting users cryptographically sign messages with their wallet keys and verify signatures from others. It also corrects the message-prefix byte lengths for Dogecoin, Firo, and Namecoin so signatures match what other software expects. There is no clear security bug in the diff, but the signing code is new and touches private keys, so it deserves careful review.

This commit adds the ability for users to select and add Solana-based tokens (SPL tokens) inside the wallet's token editor. It is a feature addition that branches the existing Ethereum-only token flow to also support Solana wallets. There is no direct evidence in the commit that this fixes or introduces a security vulnerability; it is primarily a UI and data-handling change.

This commit adds a new desktop screen for viewing Solana token (SPL) details in Stack Wallet. It is purely a user-interface feature with no security-sensitive code, no network calls, no cryptographic operations, and no changes to permissions or data handling. There is nothing in the diff that suggests a security vulnerability or fix.

This commit adds the ability for users to select Solana-based tokens (SPL tokens) in the Stack Wallet app. It is a feature implementation, not a security fix. The new code includes placeholder/stub functions that do not yet perform real Solana blockchain checks, and it adds debug logging that prints wallet addresses and selected token details during development. There is no direct evidence in the commit of a vulnerability being fixed or introduced.

This commit adds new code to support Solana SPL tokens in Stack Wallet. It introduces a way to store token mint addresses in wallet metadata and two placeholder data providers for retrieving those addresses. The actual token detail fetching is left as a TODO and returns an empty list. There is no evidence of a security fix or vulnerability being addressed.

This commit simply turns on a feature flag indicating that the Solana wallet now supports SPL tokens. There is no code change that fixes a bug, closes a security hole, or changes how funds are handled. It is a normal product feature enablement.

This commit adds two new Dart files that manage UI state for Solana token wallets. One tracks which token wallet is currently active, and the other returns a hard-coded mock balance of 1000.00 for development purposes. There is no security-sensitive code, no cryptographic handling, no network calls, and no user data processing. It is a routine feature addition with no apparent security relevance.

This commit adds a new placeholder/mock implementation of a Solana token wallet for user-interface development. The code is explicitly labeled as a mock, contains only stub methods, and does not perform real transactions, balance lookups, or fee handling. There is no indication of a security flaw in the added code.

This commit changes how the Stack Wallet app handles a helper program called mwebd on Windows. Instead of using a built-in library, it now extracts a separate mwebd.exe file from the app bundle, writes it to disk, checks its SHA256 hash, and runs it as a standalone process. The change also updates build instructions and dependency versions. There is no claim in the commit that this fixes a security issue, but the new code introduces a few security-relevant patterns worth reviewing: it executes a bundled binary, relies on a compile-time hash check, and uses a dynamic object wrapper to hide platform-specific server types.

This commit simply moves one line in a configuration script so that a cryptocurrency called Mimblewimblecoin appears in a different position within an internal list. There is no security-relevant change visible in the diff.

This commit changes how Stack Wallet initializes Monero-style (XMR, WOW, SAL) wallets. During setup, it now briefly opens the wallet, updates network node settings, immediately closes it, and clears the reference. The stated goal is to avoid leaving wallets open when they are already opened elsewhere. The change is defensive and cleanup-oriented rather than a clear fix for an active attack.

This commit updates a single commented-out dependency version in a template file used to configure the Linux build. It is a routine version bump for an optional Wownero cryptocurrency library and contains no active code changes or security fixes.

This commit updates a single dependency version number for a Wownero-related Flutter library from 2.0.0 to 2.0.2 in a template file. There is no indication in the commit itself that this fixes a security vulnerability. It appears to be a routine dependency bump.

This commit is a work-in-progress code cleanup that introduces a shared 'CryptonoteWallet' interface for Monero-like wallets (Monero, Wownero, Salvium). It replaces repeated checks for individual wallet classes with checks against the new shared interface. There is no direct security fix here; it is a refactoring change that could slightly reduce future bugs by making the code more consistent, but it also changes behavior in a few places by broadening which wallets match certain conditions.

This commit is a large refactor that splits the Wownero (WOW) cryptocurrency support out of the shared Monero (XMR) library path and into its own dedicated library (cs_wownero). It updates wallet creation, address validation, fee estimation, and restore logic to use the new Wownero-specific code instead of the old combined Monero/Wownero code. The commit message calls it a 'dirty dirty minimal get-it-running mess,' suggesting it is a rough, temporary implementation rather than a polished security fix.

This commit updates two internal cryptocurrency plugin libraries (flutter_libepiccash and flutter_libmwc) for compatibility with iOS 26. No code diff is available, and the commit message gives no indication of a security fix. It appears to be a routine platform-compatibility dependency bump.

This commit simply bumps the version of a third-party library called flutter_mwebd from an early pre-release version (0.0.1-pre.8) to a slightly newer pre-release version (0.0.1-pre.10). The change appears in dependency lock files only. There is no description of why the update was made, no mention of security fixes, and no diff showing what actually changed inside the library. On its own, this commit does not show a vulnerability, but updating a pre-release library can sometimes include bug or security fixes.

This commit only updates three submodule pointers (flutter_libepiccash, flutter_libmwc, frostdart) with a message saying they contain 'macos framework fixes'. No actual code changes or diff content are available, and no verified references describe what those submodule fixes do. There is no direct evidence this is a security patch.

This commit changes the Tor privacy service in Stack Wallet so that only one instance of the service is created and reused, rather than creating a fresh one each time. This is a code-quality and reliability fix. It does not by itself fix a known exploit, but running multiple Tor service instances could previously have caused inconsistent privacy states, resource waste, or subtle bugs that might weaken privacy guarantees.