Stack Wallet

This commit removes a special workaround that previously skipped status and message updates for car-research tickets in a shopping feature. Now those tickets will call the same backend endpoints as other tickets. The change appears to be a functional bug fix rather than a security fix, but it slightly increases the amount of data exchanged with the backend for car-research tickets.

This commit changes how the Stack Wallet app handles unexpected status values from its ShopInBit partner service. Previously, if the server sent an unknown status string, the app silently replaced it with a default value (e.g., treating an unknown ticket state as a brand-new ticket). Now the app throws an exception instead. The commit also moves some UI label/color code into the enum definitions and removes duplicate code. The change is a defensive fix that prevents the app from misrepresenting order or webhook states, but it could also cause crashes if the server ever introduces new status values that older app versions don't recognize.

A developer commented out a special-case skip that prevented 'car research' support tickets from having their status checked. The change makes the app try to fetch status for those tickets too, fixing a UI hang where the request appeared to stay pending forever. There is no clear security problem in the diff itself; it is a functional bug fix.

This commit is a large code cleanup that splits one big ShopinBit order form file into smaller, easier-to-maintain pieces. It does not appear to change what the app does or how user data is handled; it mostly moves existing UI code around. There is no clear security problem visible in the diff, but because the change is so large and was labeled as 'testing AI refactoring,' it could accidentally introduce subtle bugs that would need normal testing to catch.

This commit fixes a typo in the build instructions: it removes an unnecessary backslash before the PowerShell script name so the command works correctly. There is no security issue here.

This commit swaps out an older, simpler method for choosing which coins to spend in Bitcoin-like wallets for a newer algorithm provided by an external library called coinlib. It also changes which fork of coinlib the app uses, from one maintained by a Stack Wallet contributor to one maintained by a community contributor. The change is described as a feature, not a security fix, and there is no disclosed vulnerability or incident tied to it. The main things to watch are whether the new coin-selection logic handles unusual transaction types correctly and whether the new coinlib fork is trustworthy and maintained.

This commit is a user-interface refactor for the desktop ShopinBit (crypto concierge shopping) flow. It replaces a brittle pattern of opening and closing separate dialogs for each step with a single dialog that contains its own nested navigator. There is no clear security bug being fixed; the changes are about navigation consistency and code maintainability. The only security-relevant observation is that the new route generator validates that navigation arguments are the expected order model, which slightly hardens type handling, but this is a normal defensive coding practice rather than a fix for a known vulnerability.

This commit only updates the Windows build instructions in the project's documentation file (docs/building.md). It changes software version numbers, adds steps for installing tools like CMake, NuGet, and CppWinRT, and clarifies how to run build scripts. There is no change to application code, no bug fix, and no security-related content.

This commit is a routine GitHub Actions CI maintenance change. It adds the 'staging' branch to automated build triggers and fixes a Windows build problem where the CI runner could not create symbolic links (shortcuts) for app assets, so the workflow now copies those asset folders instead. There is no indication this affects user security or wallet safety.

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 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 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.