Cake Wallet / Monero.com

This commit fixes a bug where restoring the same hardware wallet twice could create duplicate wallet entries. The change makes the wallet creation code reuse a single WalletInfo object instead of creating a separate copy, ensuring that saving updates the existing record rather than potentially writing a new one. There is no direct evidence of a security vulnerability such as theft of funds; the issue appears to be a data-integrity/duplicate-record bug.

This commit makes three small, unrelated changes: it updates iOS dependency lock files to include SQLite-related libraries, removes a 'throw e' after an error dialog in a Nano representative-change screen, and adds 'context.mounted' checks before showing bottom sheets during payment flows. The UI fixes prevent harmless Flutter exceptions when a widget is no longer on screen, while the Podfile.lock change is a routine dependency bookkeeping update.

This commit is a cosmetic update for iOS app icons. It adds new dark-mode and tinted icon variants for Cake Wallet and refreshes the icon set for Monero.com. There are no code changes that affect security, privacy, or how the app handles money or data.

This commit is a small privacy/usability fix for the send screen. It makes the wallet's available balance respect the user's 'hide balance' setting, and lets them tap to temporarily reveal it. There is no security vulnerability being fixed here.

This commit removes a single line that saved wallet metadata to persistent storage after creating a Monero wallet from a BIP39 seed phrase. The change could mean wallet details are not written to disk at this point, which might affect recovery, wallet listing, or data consistency. There is no clear evidence in the commit itself that this is a security fix, exploit, or intentional vulnerability patch.

This commit fixes Linux and Tails-specific app-data handling, switches SQLite to a desktop-compatible implementation, and corrects a broken icon asset. It is primarily a compatibility and bug-fix patch. There is no direct evidence in the commit that it addresses a security vulnerability, but the changes touch sensitive areas: where wallet data is stored, how old data directories are migrated, and how Tor/SOCKS proxy settings are parsed on a privacy-focused OS (Tails).

This small patch fixes two minor issues in a cryptocurrency wallet app. One change makes sure a settings toggle waits for its background task to finish before continuing, which could prevent a race condition or incomplete state. The other change makes the app correctly recognize when its Tor privacy feature is disabled, so it doesn't try to stop a service that was never running. These are defensive bug fixes rather than obvious security holes, but they touch privacy and notification settings.

This commit is a routine user-interface redesign for the Cake Wallet app's dashboard. It replaces the old dot-style page indicator with a new labeled pill-style indicator, adds new icons, shortens the bottom navigation dock, and updates translations for labels like 'Apps', 'History', and 'Home'. There is no security-relevant change visible in the code.

This commit fixes how the wallet's sync progress bar estimates and displays remaining time. It changes when the app shows 'blocks remaining' versus a percentage, smooths the ETA calculation, and makes the connection-status check correctly show 'disconnected' if the network drops while syncing. There is no direct security vulnerability being patched; it is a user-experience and reliability improvement for sync feedback.

This commit is a routine bug-fix and performance-improvement patch for Solana (SPL token) handling in Cake Wallet. It batches token balance and transaction fetching, fills in missing token metadata via a new Moralis API, improves error messages, and fixes a wallet-connect compatibility check. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a stability/usability improvement.

This commit is a routine bug-fix patch titled 'Minor Fixes'. It mainly does two things: it prevents users from accidentally sending cryptocurrency while their wallet is still synchronizing, and it makes WalletConnect URI handling more robust by trimming whitespace, stripping stray '@' prefixes, and handling session expiry errors more gracefully. There is no direct evidence in the commit that these fixes address an active security exploit; they appear to be defensive hardening and usability improvements.

This commit fixes a user-interface bug where a decorative gradient overlay on the wallets page was accidentally blocking taps on buttons underneath it. The fix wraps the gradient in an IgnorePointer widget so it no longer intercepts touches, while keeping the actual buttons tappable. There is no security relevance in this change.

This commit changes an Android build script to delete leftover files from a previous download before downloading a fresh copy of a software package called reown_flutter. On its own, this is a routine cleanup step in a CI/CD build pipeline. There is no direct evidence in the commit that it fixes a security vulnerability, but it removes a potential source of stale or tampered files being reused accidentally during builds.

This commit refactors how gas fees are calculated for Base, Polygon, Ethereum, and Arbitrum wallets in Cake Wallet. It moves chain-specific priority fee logic out of shared code into each chain's wallet class, fixes a mismatch between the fee shown on the send screen and the fee shown on the final confirmation screen, and increases the safety buffer used when sending the entire balance on Base. There is no direct evidence this fixes an active exploit or security vulnerability, but it does reduce the risk of users accidentally overpaying or underpaying fees and improves consistency in fee display.

This commit removes an unused 'change your asset' button and its related code from the send-money screen. It only affects the Haven wallet type, which no longer shows a currency picker during sending. There is no security issue here—it's purely cleanup of dead UI code.

This commit mostly disables the Arbitrum cryptocurrency across build scripts and rewrites fee-estimation code. It also adds two small safety checks: one to prevent a crash when a Wownero wallet pointer is null, and another to wrap a Nano network call in a try/catch so an unexpected node response doesn't crash the app. There is no clear security vulnerability being fixed; it looks like routine cleanup and hardening.

This commit adds a standard GitHub feature-request template. It is purely a project-management/documentation change and does not touch any code, configuration, or security controls.

This commit makes the Cake Pay gift-card/order feature more forgiving when a vendor response does not include payment details for every supported cryptocurrency. Previously the app would crash if a field such as BTC or XMR was missing; now it accepts null values and removes a couple of fallback empty-string defaults when building the order record. The change is primarily a robustness/crash-fix, not a clear security patch.

This commit pins the 'grpc' networking library to a specific older version (4.0.1) instead of allowing newer compatible versions. It also downgrades a related Google authentication package from 2.0.0 to 1.6.0. The change appears to be a build-stability or compatibility fix rather than a response to a known security vulnerability, but pinning dependencies can affect which security patches are received in future builds.

This commit improves how the Cake Wallet app handles failures when opening a third-party cryptocurrency exchange website. It adds error messages so users see clearer warnings (for example, if the exchange blocks Tor connections), fixes a typo in variable names, and prevents a possible app crash when dismissing a wallet-loading warning. There is no direct evidence this fixes an active security vulnerability, but it makes the buy/sell flow more robust and user-friendly.

This commit simply updates the version (commit hash) of an internal dependency called trezor_connect in three package configuration files. There is no code change in the Cake Wallet repository itself, and no security-related explanation is provided in the commit.

This commit turns on HTTPS/SSL encryption for several built-in Ethereum and Polygon server connections in the Cake Wallet app. Without SSL, data sent between the wallet and those servers could be read or tampered with by attackers on the same network. The change is a security improvement, not a vulnerability introduction, but it fixes a real exposure for users who relied on these default nodes.

This commit adds support for a new Ledger hardware wallet model (Ledger Nano Gen 5) in the Cake Wallet app. It updates an internal device list, adds an icon, and switches the app to use a fork of the Ledger library maintained by Cake Wallet's own team. The code change also removes a redundant method argument when listening for device connection state changes. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine feature addition and dependency maintenance change.

This commit is a routine 'Cleanup and Bug fixes' patch for the Cake Wallet cryptocurrency app. It mainly refactors transaction-committing code, fixes a possible crash when closing a payment-result screen, adds retry logic for Payjoin network setup, and improves how the exchange screen decides whether the deposit currency matches the current wallet. There is no clear security vulnerability being fixed, but the changes do remove some fragile UI behavior and make transaction handling more consistent.

This commit improves how the Cake Wallet app reads and displays error messages when an Ethereum-compatible transaction fails due to not enough funds for fees. It adds support for more message formats and shows a simpler 'insufficient funds' message when the app cannot extract exact numbers. There is no direct evidence this fixes an active security vulnerability; it appears to be a user-experience and robustness improvement.