Stack Wallet

This commit adjusts two on-screen selection sheets in the Stack Wallet mobile app so they respect the phone's safe area (notch, gesture bar, etc.) and fixes some padding. It also removes a duplicate spacer in one sheet. There is no indication this fixes a security vulnerability; it appears to be a UI/UX follow-up to an earlier pull request.

This commit is a routine cleanup of build scripts. It removes old shell scripts that manually compiled cryptocurrency plugin libraries and updates the build instructions to rely on Flutter's newer native-assets system. There is no indication of a security fix, vulnerability, or malicious change.

This commit simply updates a dependency reference for libmwc (a Mimblewimble Coin library) from one Git commit hash to another. There is no description of what changed in the library, no mention of security fixes, and no diff showing actual code changes in Stack Wallet itself. On its own, this commit does not demonstrate any security issue.

This commit changes how the Stack Wallet app pulls in its Epic Cash cryptocurrency library. Previously, the library was included as a local Git submodule inside the project. Now, the app fetches it directly from a specific Git commit on GitHub as a 'native asset' dependency. The commit also removes the user-facing display of the Epic Cash build commit hash from the About screen and deletes the code that checked whether that commit was the latest one. This is primarily a build-system and UI cleanup change; there is no direct evidence in the diff of a security vulnerability being fixed.

This commit changes how the app pulls in a supporting cryptography library called frostdart. Previously it was included as a local submodule; now it is fetched directly from its GitHub repository at a specific commit. There is nothing in the commit that fixes, introduces, or discusses a security vulnerability. It is a routine build/dependency plumbing change.

This commit changes how the Mimblewimblecoin (MWC) crypto library is bundled in the Stack Wallet app. It removes the old Git submodule setup and instead pulls the library directly from a specific Git commit. It also re-enables MWC support on macOS and removes some on-screen build-commit information for MWC. There is no obvious security vulnerability in the diff itself, but the change shifts trust to a pinned external Git reference and removes a visible transparency check.

This commit updates the SQLite-related Dart/Flutter packages used by the Stack Wallet app. It bumps versions of the database library (drift), the underlying SQLite bindings (sqlite3), and related tooling. The change also removes the direct dependency on sqlite3_flutter_libs and adds sqlcipher_flutter_libs as a transitive dependency. The commit message gives no reason for the update, so we cannot tell from the diff alone whether it fixes a security bug, a compatibility issue, or something else. Updating dependencies is a routine maintenance action, but because this touches the encrypted local database layer of a cryptocurrency wallet, any underlying vulnerability could have high impact.

This commit updates the Stack Wallet app to require newer Flutter and Dart versions. Most changes are routine housekeeping: reformatting code, removing the 'final' keyword from function parameters to match new language rules, updating iOS/macOS build files, and bumping dependency versions. There are a few small logic tweaks, such as adding null-assertions ('!') to some wallet scanning code and changing how the app detects iPads, but nothing in the diff clearly introduces or fixes a security vulnerability.

This is a one-line fix in a test file that updates an import path from an old package name ('paymint') to the current package name ('stackwallet'). It does not change any production code, user-facing behavior, or security logic. It simply allows a unit test to compile and run correctly.

This commit updates the Stack Wallet app so it can correctly identify a newer kind of Firo cryptocurrency transaction (Spark V2 spends). Previously, the wallet only recognized one transaction type as a Spark spend; now it also recognizes type 11. This is a small correctness fix that helps the wallet display balances and transaction history accurately for Firo users. There is no direct evidence in the commit that this is a security vulnerability or that it was exploited.

This commit updates the Stack Wallet app so it can correctly identify a newer kind of Firo cryptocurrency transaction (Spark V2 spends, type 11) in addition to the older Spark V1 spends (type 9). Before this change, the wallet only recognized type 9 as a spend, so a type-11 spend might have been misclassified or mishandled in the user's transaction history and balance calculations. There is no direct evidence in the commit that this misclassification could be exploited by an attacker to steal funds, but it is a correctness fix that could affect balance display and user trust.

This commit fixes a UI crash (gray screen) that occurred when confirming a transaction sent to a Spark name. The crash happened because the code tried to read the first recipient address from an empty list. The fix safely checks whether a recipient exists before reading its address, falling back to Spark-specific recipient data when needed. There is no indication this is a security vulnerability; it is a robustness fix for a user-facing navigation/display error.

This commit re-enables sending private Firo (Spark) funds to exchange addresses, which had been temporarily blocked. It also upgrades the wallet to support a newer Spark transaction format (Chaum V2) that allows multiple inputs, and it adds safety checks to prevent broadcasting insecure multi-input transactions using the older format. The change is described by the developer as a 'partial revert' ahead of a network fork, not as a security fix.

This commit updates the Stack Wallet app's integration with the Firo Spark privacy library. It adds support for a new Spark transaction version ("H2" / Chaum V2) that activates on mainnet at block 1,371,000, while keeping older behavior on test networks. The change is a dependency and protocol upgrade, not a clear security fix, but it touches sensitive code that creates private transactions and could affect whether coins are spendable after the network upgrade.

This commit updates the Windows build pipeline for a small helper program called mwebd, which Stack Wallet uses for Litecoin MWEB privacy features. It bumps the mwebd version from v0.1.8 to v0.1.19, switches to a newer Go compiler, removes an old workaround that disabled part of the upstream plugin, and fixes a checksum comparison bug caused by Windows file paths. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies and removing workarounds can have security side effects.

This commit updates the project's Docker build image to install the Go programming language toolchain. It downloads Go 1.24.13 from the official Go website, verifies the file's integrity using a published SHA-256 checksum, extracts it, and adds it to the container's system PATH. The change appears to be a routine CI/build environment update rather than a security fix or vulnerability patch. There is no direct evidence in the commit that this addresses a security issue.