Stack Wallet

This commit hides an 'anonymize all' button in cryptocurrency wallets that are in view-only mode. View-only wallets cannot spend or move funds, so the button was likely non-functional or confusing. The change is a UI cleanup rather than a fix for a vulnerability that could be directly exploited.

This commit is a straightforward user-interface improvement: it adds a new 'Type' field to the transaction-details screen for Salvium cryptocurrency transactions. There is no evidence in the diff of any security bug, vulnerability, or behavior change that could put user funds or data at risk.

This commit adds testnet support for the Salvium cryptocurrency in Stack Wallet. It lets developers or users create and use Salvium wallets on a local test network (localhost) instead of the real main network. There is no obvious security bug in the change itself, but it does add a hardcoded localhost node and changes how wallet network types are selected. The commit does not describe any security issue, and no independent security report is supplied.

This commit is a small cleanup of a code template used for the Salvium cryptocurrency integration. It updates an error message, removes some unnecessary fallback values, and fixes how transaction 'type' data is passed by using the underlying value instead of an object. There is no clear security problem visible in the diff itself.

This commit is a code cleanup and UI consistency change for the Stack Wallet app. It replaces repeated checks of a global Mimblewimblecoin transaction method with a single wallet-scoped helper. The visible effect is making sure the preview/send button shows the correct label ("Create slatepack" vs "Preview") based on whether the current wallet is using slatepack transactions. There is no obvious security vulnerability in the diff itself.

This commit adds a new user interface screen for creating Salvium staking transactions in the Stack Wallet app. It is purely a UI feature: it adds a text box to enter an amount, a Preview button, and wiring to route the user to the existing transaction confirmation flow. There is no indication in the commit that it fixes a security bug or introduces a vulnerability.

This commit refactors how the Monero and Wownero wallet code passes wallet objects around. Previously, many functions looked up a live wallet instance using only a wallet ID string, which could lead to the wrong wallet being used or a missing wallet being treated as present. The change makes wallet code explicitly carry and check a typed wallet object before calling sensitive operations such as viewing balances, creating transactions, and sending funds. It is a defensive fix that reduces the risk of accidental cross-wallet operations or crashes, but the commit message does not frame it as a security patch.

This commit only adds Dart 'const' constructors to a few internal interface classes and changes their instantiation sites to use 'const'. It is a code-quality/performance micro-optimization with no visible security relevance.

This commit updates the Salvium cryptocurrency wallet integration in Stack Wallet. It mainly changes how wallet objects are passed around internally (using a new WrappedWallet object instead of a wallet ID string) and adds support for creating Salvium staking transactions. There is no clear security fix or vulnerability being patched in the visible code changes.

This commit appears to update a pre-built macOS framework file inside the frostdart crypto plugin. No source code diff is available, and the commit message gives no indication of a security fix or vulnerability. It looks like a routine build artifact update for macOS compatibility.

This commit changes build scripts so that two cryptocurrency wallet libraries (Epic Cash and MWC) are only bundled into the main Stack Wallet app, not into the lighter Campfire and Stack Duo variants. It is a build-packaging tweak, not a fix for an active security flaw. There is no evidence it addresses a vulnerability.

This is a simple code cleanup: a Dart template file had a class named after the wrong project ('MwebdServerInterfaceImpl' instead of 'LibXelisInterfaceImpl'), and the patch renames it to match the Xelis (XEL) wallet integration it actually implements. There is no security-relevant change.

This commit updates macOS build configuration files for a Flutter wallet app. It removes an old dependency lock file, raises the minimum macOS version from 10.14 to 10.15, and cleans up references to several native libraries (such as frostdart, flutter_libepiccash, isar_flutter_libs, and wakelock_macos) from the Xcode project template. There is no code change that introduces a security vulnerability or fixes an obvious one. It appears to be routine build maintenance.

This commit updates a sub-project dependency called flutter_libmwc to include a macOS build fix. The title mentions a 'macos xcfw fix' (likely a macOS XCFramework build issue). There is no diff available and no description suggesting a security problem. It appears to be a routine build/dependency maintenance change.

This commit only updates the project's ignore rules and removes auto-generated Flutter plugin registration files from version control. It does not change any application code, cryptographic logic, or user-facing behavior. There is no security issue here.

This commit updates iOS build configuration files. The most notable change is the removal of debug code that called a function named `get_mnemonic()` and printed its output in the iOS app startup file. A mnemonic is the secret recovery phrase for a cryptocurrency wallet, so printing it could expose sensitive data during development or debugging. The commit also removes old references to an Epic Cash wallet library, deletes a generated Podfile.lock, and adjusts Xcode scheme settings. There is no evidence this was a remotely exploitable vulnerability, but it does remove a potentially unsafe debug practice.

This commit is a routine code cleanup for the Xelis cryptocurrency support. It moves the logic that checks whether a Xelis network node is reachable out of a general test file and into a generated interface file, while also fixing a missing import. There is no indication this change fixes a security vulnerability or introduces one; it appears to be a normal refactoring/bug-fix for build or import correctness.

This commit simply deletes four unused files that handled Tezos cryptocurrency data fetching and account/transaction model classes. There is no indication this fixes or introduces a security problem; it is routine code cleanup.

This commit makes the Tor privacy feature optional and configurable across the Stack Wallet app. It adds feature-gating so that Tor-related code, UI elements, and network routing are only active when the app configuration explicitly enables Tor. Most of the visible changes are formatting and minor refactorings; the substantive change is architectural, not a direct security fix.

This commit adds a new 'tor' option to the app's feature configuration. It is a straightforward feature-flag change that enables Tor support in three app variants (Campfire, Stack Duo, Stack Wallet). There is no indication of a security vulnerability or bug fix.

This commit moves a Monero cryptocurrency library dependency (monero_rpc) from an optional, commented-out XMR-only block to the always-included dependencies section of a Flutter package configuration template. On its own, this is a build/template fix rather than a direct security vulnerability. It could slightly widen the software's attack surface by ensuring the Monero RPC code is always compiled in, but there is no evidence in the commit of an exploitable flaw.

This commit refactors how the Stack Wallet app talks to the Xelis cryptocurrency library. Instead of importing the Xelis package directly throughout the app, it introduces a new internal interface layer (`libXelis`) that wraps the Xelis package. The main visible change is making this Xelis support optional at build time, controlled by a code-generation template. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be an architectural/build change.

This commit refactors how the Stack Wallet app uses the Firo Spark cryptography library. Instead of directly importing flutter_libsparkmobile everywhere, it introduces a generated interface wrapper so the library can be optionally included or excluded at build time. Most of the diff is code reformatting and replacing direct library calls with calls through the new wrapper. There is no obvious security bug in the diff itself, but the change touches sensitive wallet code (address generation, transaction signing, coin identification, fee estimation) and the generated template has placeholder error paths when Firo is not enabled.

This commit refactors how the Stack Wallet app talks to its FROST (multisignature) cryptography library. It replaces direct calls to a concrete 'Frost' service with calls through a new 'frostInterface' abstraction, and makes the underlying frostdart package import optional. The change is mostly architectural: it enables building the app without the FROST library present, and centralizes the interface. There is no direct evidence in the diff of a security vulnerability being fixed; it is a code-organization and build-flexibility change.

This commit only changes how one file imports another file inside the same project. It replaces a package-style import with a relative-path import and reformats the code. There is no security-relevant change.