Stack Wallet

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.

This commit is purely a code-formatting cleanup. It adjusts line breaks, indentation, and whitespace across six Dart files to match the project's style rules. No functionality, logic, or security behavior was changed.

This commit changes a single flag in the Firo cryptocurrency wallet code. When creating a special 'ProReg' transaction used for masternode registration, the wallet now marks a small recipient output as 'not change' rather than 'change.' In many wallet designs, change outputs are handled differently from payment outputs—potentially affecting how fees are calculated, how the output is selected in future spending, or how the transaction is displayed to the user. The change is too small and context-free to conclude it fixes a serious vulnerability, but it is a plausible correctness or security-related fix for a coin-specific transaction type.

This commit makes a small UI safety tweak in the transaction confirmation screen of a cryptocurrency wallet. It moves a database lookup slightly later in the code and ensures a state update happens after the screen has finished its initial build, which helps avoid a rare Flutter framework error. There is no direct evidence this fixes a security vulnerability, but it is a defensive safeguard against possible app crashes or inconsistent UI state when checking whether a transaction would accidentally spend a valuable 'ordinal' asset.

This commit updates a submodule called frostdart to version 0.1.3. The stated reason is to pin two related software libraries (openssl and openssl-sys) to versions compatible with an older Rust compiler version (1.71). There is no code change visible in the commit itself, only a submodule pointer update. No security issue is described or evident from the materials provided.

This commit only updates a Git submodule pointer for 'frostdart' inside the Stack Wallet repository. No actual code changes are shown, and no security-related description is provided. On its own, this tells us nothing about whether the submodule update fixes or introduces a security issue.

This commit adds an optional shortcut for Windows builds that downloads a pre-built 'mwebd.exe' program from the internet instead of compiling it from source. It checks the downloaded file against a published SHA-256 hash, but the download itself uses plain HTTPs and the source URL can be overridden by an environment variable. There is no claim in the commit that this fixes a security issue; it appears to be a build-convenience change.