Stack Wallet

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.

This commit changes the Tor privacy service in Stack Wallet so only one copy of the service can run at a time (a 'singleton'). Before, each call could create a fresh instance, which could lead to multiple Tor connections or inconsistent state. The patch itself is a defensive code-quality fix; it does not show an active attack or known breach.

This commit is purely a code formatting change (Dart autoformat) on a single file. It only adjusts whitespace, line breaks, and indentation without changing any logic, variable names, function calls, or behavior. There is no security relevance.

This commit adds a new utility module for handling Electrum-style cryptocurrency seed phrases, plus tests. It does not fix any bug or change existing behavior; it is a work-in-progress feature addition. There is nothing in the commit that suggests a security vulnerability or a security patch.

This is a large routine release merge for Stack Wallet v2.4.0. It adds thousands of project files including source code, assets, build scripts, tests, and GitHub workflow files. There is no specific security fix or vulnerability patch visible in the supplied portion of the diff, and no security-relevant description from the vendor.

This commit is a large merge from the 'main' branch into 'staging' for the Stack Wallet project. It adds many files including project configuration, assets, source code, tests, and documentation. There is no indication in the commit message or visible changes that this is a security fix or introduces a security vulnerability. It appears to be a routine synchronization of branches.