Stack Wallet

This commit swaps the source of the Mimblewimblecoin (MWC) library used inside Stack Wallet. It replaces a direct import of an external Flutter package called flutter_libmwc with a project-specific wrapper interface named libmwc_interface. The actual address-validation logic still calls the same validateSendAddress function, just through the new wrapper. There is no obvious security bug being fixed here; it looks like a routine code reorganization to make the wallet use an internal abstraction layer instead of a third-party package directly.

This commit refactors how the Epic Cash cryptocurrency support is wired into the Stack Wallet app. Instead of importing the Epic Cash library directly everywhere, the code now uses a generated interface that can be turned on or off at build time. The visible changes are mostly code reorganization and formatting; there is no obvious new security vulnerability introduced, but the patch is incomplete because the generated implementation file is only a template and the real generated file is not shown.

This commit is a routine code refactor for how the app retrieves the version string of the Mimblewimble Coin (MWC) library. It moves the version lookup behind a generated interface so the app can check the plugin version consistently whether or not MWC support is enabled. There is no visible security relevance.

This commit is mostly a large internal refactor that swaps direct calls to the cs_monero and cs_salvium libraries for a new generated interface layer. It also adds Salvium wallet support and fixes some restore-height logic. There is no obvious malicious code, but the change touches sensitive wallet code (keys, addresses, transaction creation, balance queries) and introduces a new abstraction layer whose generated implementation is only partially shown. A few spots look like real bug fixes or hardening (for example, checking whether a wallet instance exists before overwriting it during restore), while other spots move security-critical operations behind a new interface that reviewers cannot fully inspect from this diff alone.

This commit is a minor code cleanup in a Dart template file used to generate wallet code. It removes redundant assignments inside a switch expression, making the code shorter and clearer. There is no visible change in behavior, no security fix, and no indication of a vulnerability.

This commit fixes a bug where a user-specified custom fee amount was not being passed along when building Mimblewimble (MWEB) transactions in the Stack Wallet app. Without the fix, the wallet could ignore the user's fee choice and use a default or calculated fee instead, potentially leading to unexpected transaction costs or failed transactions.

This commit refactors how Stack Wallet imports the Monero/Wownero foreign-function-interface (FFI) package. Instead of directly importing the cs_monero library everywhere, the app now routes those calls through a generated interface file. The change is mostly an architectural cleanup to make the FFI package optional/importable on demand. There is no obvious security bug in the diff, but because the patch is large and partially reformats code, it is hard to fully verify that no sensitive behavior changed.

This commit is a large merge from the 'staging' branch into the 'docs' branch for the Stack Wallet project. It adds many files including issue templates, a CI workflow, project configuration, assets (icons, themes, animations), and a large amount of Dart source code. There is no indication in the commit message or diff that this is a security patch or that it addresses any vulnerability. It appears to be a routine code/documentation synchronization or initial import.

This commit fixes formatting in a build configuration template and tightens the script that enables optional cryptocurrency features. It changes how the script recognizes marker comments so it only matches exact lines, not partial ones, and removes an unused helper function. There is no indication this is a security fix or that it addresses any vulnerability.

This commit updates build configuration scripts for two app variants (Campfire and Stack Duo) and restructures a shared template that lists software dependencies. It wraps optional cryptocurrency and privacy features (such as Firo, Xelis, Epic Cash, Tor, Monero, Salvium, and Mimblewimble) in conditional placeholders so each app variant can enable only the components it needs. There is no direct evidence in the commit of a security vulnerability or malicious change; it appears to be a build-system cleanup.

This commit is a work-in-progress refactor that changes how the Mimblewimblecoin (MWC) wallet code talks to its underlying library. Instead of calling the library directly, it introduces a generated interface layer so the same wallet code can work whether or not the MWC feature is enabled at build time. There is no obvious security bug in the diff itself; it is a build-time feature-toggle and code-organization change.

This commit simply renames a build template file from 'pubspec.template' to 'pubspec.template.yaml' and updates the build script that references it. The file contents are unchanged. There is no security relevance.

This commit changes the Stack Wallet app to download a cryptocurrency library (xelis_flutter) from a different GitHub account and a specific commit hash instead of a numbered release version. On its own, this is a routine dependency update, but it also introduces supply-chain risk: the app now trusts code from a fork controlled by the Stack Wallet team rather than the original xelis-project repository, and it pins an exact commit rather than a tagged release. There is no evidence in the commit that this fixes a known security bug or that the change itself is malicious.

This commit updates the Tor networking library used by Stack Wallet to a newer version. The change itself only swaps one pinned code reference for another and adds a Kotlin build directory to the ignore list. There is no direct evidence in the commit that this fixes a security vulnerability, but updating a privacy-critical networking component like Tor is commonly done to pick up bug or security fixes in the upstream library.

This commit simply bumps the version of a third-party library called flutter_mwebd from an early pre-release version (0.0.1-pre.7) to the next pre-release version (0.0.1-pre.8). The commit message gives no reason for the update, and the diff shows only version number and package hash changes. There is no direct evidence in the commit that this fixes a security flaw, but updating a pre-release library can sometimes include bug or security fixes.

This commit only changes which version (commit reference) of an external library called coinlib Stack Wallet uses. The actual code changes are in the separate coinlib repository, not shown here. Without seeing what changed inside coinlib, we cannot tell whether this update fixes a security issue, adds a feature, or is just routine maintenance.

This commit only updates a reference to an external library (libsparkmobile) used by the Stack Wallet app. The change itself does not show any security issue in the Stack Wallet code, nor does it explain why the library was updated. Without seeing what changed inside the external library, we cannot tell whether this update fixes a security problem, adds a feature, or is routine maintenance.

This commit updates build configuration files to make the Android version compile. It bumps the Kotlin plugin version and switches to a newer version of an internal Monero compatibility library. There is nothing in the changes that directly affects user security or introduces a known vulnerability.

The commit message only says 'update frostdart' and the actual code diff is unavailable. There is no visible information indicating what changed, whether it fixes a security issue, or whether it introduces any risk. Without the diff, no meaningful security assessment can be made.

This commit is a large automated regeneration of generated Dart files (code produced by build tools like Drift, Isar, Hive, and Mockito). The visible changes are purely formatting and code-style updates produced by newer generator versions, with no hand-written logic changes. There is no indication of a security fix or vulnerability being addressed.

This commit swaps the app's local database library from the original 'hive' package to a community-maintained fork called 'hive_ce' (Community Edition). Most changes are mechanical import renames and formatting. There is no direct evidence in the commit that this fixes a specific security vulnerability, but replacing an unmaintained dependency with a maintained fork can reduce long-term security risk. The commit does not describe any security issue or credit a researcher.

This is a large routine maintenance commit that updates the app's Flutter framework and switches the local database library from the original 'isar' package to the community-maintained 'isar_community' fork. Most visible changes are automatic import renames and code formatting. There is no direct evidence in the commit of a security vulnerability being fixed or introduced, but any database-layer migration in a wallet app can affect how keys, transaction data, and backups are stored. The change should be reviewed for compatibility and data-integrity risks rather than treated as a security patch.

This commit simply updates the iOS project's .gitignore file to exclude two additional build-related files and folders from version control. It is a routine housekeeping change with no security relevance.

This commit appears to remove or silence a debug print statement that was outputting a wallet's secret seed phrase (mnemonic) in the MWC cryptocurrency plugin. A seed phrase is the master key to a wallet; printing it to logs or console could let anyone with access to those logs steal funds. The actual code change is in a submodule (crypto_plugins/flutter_libmwc), so the exact fix is not visible in the main repository diff.