Stack Wallet

This commit is a routine UI cleanup for work-in-progress gift-card and shopping features. It swaps custom text fields and dialogs for shared reusable widgets, removes unused focus nodes, and fixes small layout and error-message details. There is no clear security problem in the changes, and nothing in the commit message or diff indicates a security fix.

This commit moves where a secret API file is created for the Mimblewimblecoin wallet. Previously, the file was created while reading the wallet configuration. Now, it is created when the wallet node is updated. The change appears to be a code cleanup (refactor) to ensure the secret is written at a more appropriate time, but the commit message and diff do not clearly explain any security problem being fixed.

This commit fixes a database migration for Mimblewimblecoin (MWC) wallets in Stack Wallet. Older versions left behind a stale 'wallet handle' key in secure storage. The patch moves cleanup of that stale key from normal wallet startup into a one-time database upgrade routine, so it is reliably cleared for all users upgrading from older builds. A leftover wallet handle could potentially be reused or leaked across wallet instances, which is a security hygiene issue, though the commit itself does not describe an active exploit.

This commit only reformats a single line of code to match Dart style rules. It does not change what the code does, so it has no security impact.

This commit fixes user-experience and minor reliability bugs in Stack Wallet's masternode collateral flow. It prevents users from accidentally creating a FIRO transaction that leaves them with less than the required 1000 FIRO collateral because of a hidden network fee. It also fixes a 'black screen' bug that could happen if a user cancels a send while the app is still building the transaction. A small Particl wallet change adds a flag but its security effect is unclear from the diff alone.

This commit fixes a Flutter widget state check in a cryptocurrency selection screen. It changes `mounted` to `context.mounted` before navigating back. The rest of the change is automatic code formatting. The fix prevents a potential app crash when a user presses the back button after the screen has already been disposed.

This commit is mostly a cleanup and visual refactor of the gift-card purchase screens. It splits a large widget into smaller pieces, replaces a generic gift-card icon with a reusable credit-card icon, and switches money amounts from floating-point (double) to a more precise Decimal type. There is no obvious security fix here; the changes are housekeeping and UI consistency.

This commit only updates a dependency reference (flutter_libmwc) for the MWC cryptocurrency plugin. No code changes are shown, and there is no information about what changed in the dependency itself. Based on the available materials, this looks like a routine maintenance update rather than a security fix.

This commit refactors how Stack Wallet stores the live Mimblewimblecoin (MWC) wallet handle. Previously, the app saved a process-scoped Rust pointer in secure storage, which could be reused after an app restart and cause crashes or memory corruption. Now the handle is kept only in memory for the current process, and stale pointers are deleted from secure storage. The change reduces the risk of crashes and undefined behavior, but it is a defensive refactor rather than a confirmed remote exploit fix.

This fix prevents the Mimblewimblecoin wallet from reusing a stale wallet handle left over from a previous app launch. The old handle is a raw memory pointer stored in secure storage; using it after the app restarts would crash the app. The patch now deletes any leftover pointer unless it was created by the currently running app process, then opens the wallet fresh.

This commit adds diagnostic logging for the Mimblewimblecoin (MWC) wallet. It initializes a Rust-side trace logger the first time an MWC wallet is opened, so that if the underlying native code crashes silently, developers have a log file to inspect. It is a debugging/diagnostic improvement, not a fix for an exploitable vulnerability.

This commit updates a cryptocurrency plugin dependency (flutter_libmwc) used by Stack Wallet for MWC coin support. The title says it fixes how the wallet asks the MWC library for the current chain height, and the message mentions adding panic handling and fallback logic in that plugin. The actual code change is only one line in a submodule reference, so we cannot see what really changed inside the plugin. There is no clear security claim by the project, and no independent report is cited.

This commit is purely a code-style cleanup: it runs the Dart formatter on six files related to PayNym features. No logic, behavior, or security-sensitive code was changed. It is not a security fix and does not introduce any obvious vulnerability.

This commit is a routine UI cleanup. It removes a hidden developer-only feature that let testers manually override CakePay order statuses on their own device, and replaces several copy-pasted loading spinner widgets with a single shared loading widget. There is no indication this was a security fix or that the removed feature could be exploited by normal users.

This commit is a code reorganization: the Exolix exchange API code is split from one large file into several smaller files (DTOs, helpers, and the API client). The actual logic, behavior, and security checks remain the same. There is no indication this fixes a security bug or introduces a new vulnerability.

This commit adds Exolix as a new cryptocurrency exchange provider inside Stack Wallet. It introduces roughly 1,500 lines of code for API communication, trade creation, rate quotes, currency caching, and UI icons/status handling. There is no claim in the commit or supplied references that this fixes a security bug; it is a feature integration. The code does touch sensitive areas (network requests, API keys, transaction status parsing, decimal handling for money), but the diff itself does not show an obvious vulnerability. A few spots deserve closer review: the API key fallback uses a hard-coded placeholder check, the new exchange is marked as possibly supporting Tor, and transaction status strings are parsed with broad fallbacks. These are normal integration risks rather than confirmed flaws.

This commit is purely a code formatting cleanup in a single theme file. It adds spaces to comment markers and rewraps long function calls onto single lines. There are no functional changes, no security fixes, and no behavior differences.

This iOS build change switches the FROST cryptographic library from being compiled from source during app building to being downloaded as a prebuilt binary. It also removes a pinned Rust compiler version. The change itself is a build-system convenience, but it slightly increases supply-chain risk because the app now relies on a prebuilt library whose contents are not rebuilt from public source at build time, and the Rust compiler version is no longer fixed.

This commit updates the Firo masternode user interface in Stack Wallet. It changes how the app guides users to create a 1000 FIRO collateral transaction, switches some dialog navigation to use the root navigator, and removes the automatic masternode registration flow that previously followed a successful collateral send. There is no clear security vulnerability introduced, but the changes touch navigation and state handling in ways that could affect stability or user experience.

This commit only reformats code in a single Dart file. It splits one exception message across multiple lines and collapses a multi-line fee calculation into a single line. There are no functional changes, no bug fixes, and no security-related modifications.

This commit simply moves three Dart files from one folder to another and updates the corresponding import paths. It is a routine code organization change with no visible security implications.

This commit is a purely cosmetic user-interface update for the desktop ShopInBit setup screen. It swaps some visual widgets, removes an unused focus highlight, adjusts padding and layout, and makes the dialog height adapt to the window size. There is no security-relevant change.

This commit is a minor user-interface layout fix. It changes a dialog box so it only expands vertically when its content actually needs the extra space, rather than always stretching to fill available screen height. There is no indication this relates to security.

This commit updates a single cryptocurrency plugin dependency (flutter_libmwc) to version 0.1.2, with the stated reason being an iOS checksum ('shasum') fix. The actual code changes are not visible because the diff was not provided. A checksum fix normally means a downloaded file's hash was corrected so the build can verify it was not corrupted or tampered with during download. It is a build-integrity issue, not a live vulnerability in the wallet itself, unless the wrong checksum was hiding a malicious replacement. There is no evidence in the supplied materials of malicious intent or a security breach.

This commit only updates three submodule pointers (flutter_libepiccash, flutter_libmwc, and frostdart) with the stated purpose of fixing a macOS download portability issue. No actual code changes are shown, and no verified references were provided. There is no direct evidence in the commit of any security vulnerability.