Stack Wallet

This commit adds a single Dart getter that sets the Isar database transaction version to 2 for Solana token wallets. There is no visible security-relevant change in behavior, no bug fix, and no change to how funds, keys, or transactions are handled. It appears to be a schema or versioning update.

This commit is a code-quality refactor for Solana token handling in the Stack Wallet app. It replaces loose 'dynamic' types with concrete SplToken/EthContract types, removes unsafe casts, and makes the Solana token wallet constructor carry a full token object instead of separate fields. There is no direct evidence of a security vulnerability being fixed, but the changes remove patterns (dynamic casts and type confusion between Ethereum and Solana tokens) that can lead to crashes or incorrect balance/price display.

This commit tidies up how token icons are displayed in the Stack Wallet app. It switches Ethereum and Solana fallback icons from app-asset files to local files, adds a loading spinner while network icons load, and replaces a silent error with a logged error. There is no obvious security vulnerability here; it is primarily a UI cleanup.

This commit is routine housekeeping: it regenerates automatically generated Dart files (for database models and test mocks), updates a .gitignore rule, and tweaks a coin icon provider. There are no user-facing security fixes or obviously dangerous code changes in the diff itself.

A single debug logging line that printed pending transaction data has been removed. There is no indication this was a security vulnerability—it appears to be a routine cleanup of leftover debug output.

This commit refines how the Stack Wallet mobile app handles Solana (SPL) custom tokens. It separates default tokens from user-added custom tokens, passes the wallet ID when adding a custom token, and adds unique keys to token list items. There is no clear security vulnerability in the diff itself; it appears to be a feature/bug-fix improvement for token management.

This commit adds support for saving user-added custom Solana tokens and showing them alongside the wallet's default token list. It also includes minor code cleanup (removing an unused import and reformatting). There is no clear security vulnerability in the change itself.

This commit adds a fallback so that when a Solana token isn't on the built-in default list, the app looks it up in the user's own saved custom-token database. It also refreshes the token balance when the wallet view opens. There is no clear security bug in the change itself; it is a feature/fix for missing custom-token metadata and stale balances.

This commit adds a new screen that lets users manually add custom Solana SPL tokens to their Stack Wallet. It checks the mint address format, tries to fetch token details from an API, and lets the user type in details if the API has no record. The change also replaces the old fixed list of Solana tokens with this custom-add flow. There is no clear security bug in the diff, but the new code trusts user-supplied token metadata and does not verify on-chain that the token really exists or that the wallet holds it, which could let a user be tricked into adding a fake or misleading token.

This commit adds a new storage field to the wallet's metadata for remembering custom Solana token mint addresses. It is a straightforward feature addition with no visible security implications in the code changed.

This commit changes the Stack Wallet app so that users with a 'view-only' wallet can no longer see buttons to buy or renew Spark names (a Firo cryptocurrency feature). It also makes sure the 'Names' menu appears only for the correct wallet types. The change is a UI restriction, not a server-side security fix, and appears aimed at preventing users from accidentally trying actions their wallet cannot perform.

This commit fixes how the Firo/Spark wallet identifies its own change address. Previously, code compared a transaction output's address against the raw 'sparkChangeAddress' object instead of its string value. The fix exposes the change address as a string getter and updates comparisons to use that string. If left unfixed, the wallet could fail to recognize its own change outputs, which might cause incorrect balance calculations or transaction history display, but it does not appear to let an outsider steal funds directly.

This commit makes several user-interface and wallet-management tweaks for Firo 'view-only' wallets in the Stack Wallet app. It adds a new option to create a Spark-specific view-only wallet, moves the 'Spark view key' display behind an authentication step, and cleans up how Spark addresses are generated and saved. There is no clear security vulnerability in the diff itself; it mostly reorganizes existing functionality and adds a new view-only path.

This commit changes the destination address used when paying fees to register a Spark name in the Stack Wallet app. It switches from a 'development fund' address to a 'community fund' address, and updates the underlying library version. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine destination-address update, though a typo in one generated constant name (kStage3DCommunityFundAddressTestNet) is introduced.

A developer commented out a redundant call to wallet.init() in the wallet view screen. The change is described as cleanup because the initialization is already performed earlier when entering a wallet. There is no direct evidence in the commit that this fixes a security vulnerability.

This commit is a minor user-interface tweak. It moves the 'Names' button for Spark wallets out of a hidden 'more' menu and into the main visible navigation bar. There is no security change.

This commit removes an unused 'controller' feature from a Flutter UI widget called Options. The change only deletes dead code and reformats some lines for readability. There is no visible security relevance.