Stack Wallet

This commit simply runs a cleanup tool on three SVG image files used for the rsFIRO cryptocurrency icon. It removes unnecessary formatting and metadata from the image files without changing their visual appearance. There is no security relevance.

This commit is a routine merge from a staging branch that mostly tidies up build scripts and CI. The only user-visible change is that the Firo wallet now groups 'revoked' and 'banned' masternodes together under a single red 'banned' label, instead of showing them as two separate statuses. It also updates a privacy-related internal dependency and makes sure empty API key templates are created automatically during builds and tests. There is no obvious security vulnerability in the diff itself.

This commit removes the user-facing 'operator reward' field from the Firo masternode registration screen and hard-codes that value to 0. The change simplifies the form and prevents users from entering an operator reward percentage. There is no direct evidence in the commit that this fixes an active security vulnerability, but it does eliminate a potential source of user error or misuse in how masternodes are registered.

This commit is routine build and continuous-integration housekeeping. It adds missing placeholder API key entries for several exchange partners (including Trocador) to test and prebuild scripts, removes some stale gitignore entries, and fixes a minor string formatting issue in an error message. There is no indication of a security vulnerability being fixed.

This commit simplifies how the Stack Wallet app displays Firo masternode status. Previously, the app distinguished between masternodes that were 'banned' and those that were 'revoked'. Now both conditions are shown as 'BANNED' with a red color. This is a user-interface labeling change; it does not appear to alter wallet security, transaction handling, or private keys.

This commit simplifies how the Stack Wallet app labels Firo masternodes. Previously, the app distinguished between 'banned' and 'revoked' masternodes, showing banned ones in orange and revoked ones in red. Now both states are treated as 'banned' and shown in red. This is a UI/status-label change; it does not appear to alter how transactions are signed, validated, or how funds are handled.

This commit is a routine merge that improves how the Stack Wallet app displays Firo masternode status. Previously, a masternode was shown as simply 'ACTIVE' or 'REVOKED' based only on whether it had been revoked. Now it can also show 'BANNED' when the masternode has been banned for misbehavior (a 'poseBanHeight' value other than -1). The colors in the UI were also updated so banned nodes appear orange instead of green or red. There is no indication this fixes a security vulnerability; it is a user-interface accuracy improvement.

This commit is purely cosmetic and CI-related. It reformats several Dart UI files to match the project's code style and removes a redundant fallback block in the GitHub Actions test workflow that wrote empty placeholder API keys when real keys were not supplied. There is no functional change to app behavior or security-sensitive logic.

This commit simply swaps the source of the rsFIRO token icon from a network-downloaded image to a local SVG file bundled inside the app. It is a cosmetic/user-interface change with no security implications.

This commit reorganizes how Stack Wallet and its related apps choose which Ethereum tokens appear by default. It does not fix a security bug and does not introduce an obvious vulnerability. The main change is moving the default token list from a single shared file into per-app configuration scripts, and adding a new rsFIRO token for the Campfire app. The token contract addresses shown in the diff match well-known public Ethereum addresses, so there is no direct evidence of malicious token substitution.

This commit fixes the masternode status display in the Firo wallet. Previously, the UI only showed a masternode as either 'ACTIVE' or 'REVOKED' based on a single check. Now it correctly distinguishes three states: active, banned, and revoked. This is a user-interface bug fix with no apparent security impact.

This commit fixes how the app displays the status of Firo masternodes. Previously, a masternode was shown as either 'ACTIVE' or 'REVOKED' based only on whether it had been revoked. Now it also recognizes a 'BANNED' state (when the node has been banned for misbehavior). This is a UI/accuracy improvement, not a security vulnerability fix.

This is a very large routine merge of 'various fixes' for the Stack Wallet Flutter app. The visible changes mostly update build tooling (Flutter 3.47.2, Android Gradle Plugin 9, Go/Rust versions), switch several crypto plugins from Git submodules to native-assets/prebuilt builds, reformat code, regenerate Isar database schema files, and fix a handful of UI/amount-handling bugs. There is no explicit security disclosure in the commit message or diff, and no single clearly exploitable vulnerability is introduced. The most security-relevant code-level changes are hardening touches: Android secure-storage options now disable reset-on-error and enable backup migration, ElectrumX ping now returns false on timeout instead of throwing, and MWEB peg-out UTXOs now enforce an extra maturity check before being considered spendable. However, the patch is huge (234 files, thousands of lines changed), so a complete security review is not possible from the supplied excerpt alone.

This commit updates a dependency called mobile_app_privacy from version 0.0.3 to a specific commit hash (0.0.4). The change appears to be a routine dependency bump to incorporate Swift Package Manager support, but the commit message gives almost no detail. Without seeing what actually changed inside the mobile_app_privacy library, we cannot tell whether this fixes a security issue, introduces one, or is purely a build/dependency change.

This commit is purely a code-formatting cleanup. It changes whitespace, line breaks, and indentation across many Dart files so the project's automated style checks (CI) pass. No program logic, security behavior, or user-facing functionality was altered.

This commit changes only the recorded dimensions of the iOS launch screen image in a storyboard file, from 512×373 to 512×512. It is a routine Xcode/auto-update style tweak with no visible security relevance.

This commit updates several software building blocks (dependencies) and the automatically generated code that matches them. The main change is moving the Isar database library from a pre-release test version (3.3.0-dev.2) to a stable release (3.3.2), along with related tools like build_runner, analyzer, hive_ce, and mockito. It also removes a workaround that pinned an older analyzer version. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as routine maintenance to keep the project compatible with newer tooling.

This commit updates the Stack Wallet app to use a newer version of its Tor privacy plugin and switches to prebuilt native assets downloaded from GitHub. There is no direct evidence in the commit of a security vulnerability, but changing how sensitive privacy components are fetched and built is a security-relevant configuration change.

This commit updates dependency versions for Xelis cryptocurrency support in Stack Wallet. It switches from the upstream xelis-flutter-ffi library to a fork maintained by Cypher Stack (the same organization as the wallet), and bumps flutter_rust_bridge from 2.12.0 to 2.13.0. The commit title says 'xelis native assets,' suggesting feature work rather than a security fix. There is no direct evidence in the diff or commit message of a vulnerability or security issue.

This commit simply updates the version of an external library called 'epiccash' used by the Stack Wallet app. It changes which exact code snapshot and prebuilt download the app will use, but the commit message gives no details about why the update was made or whether it fixes any security problem. Without seeing the actual changes inside the epiccash library, we cannot tell if this is a routine update or a security patch.

This commit simply updates the version of an internal backup library (stack_wallet_backup) used by the Stack Wallet app. The change points the app to a newer commit of that library and bumps its declared version from 0.0.1 to 0.1.0. There is no information in the commit itself about what changed in the backup library or whether any of those changes relate to security.