Cake Wallet / Monero.com

This commit is a purely cosmetic UI fix for the wallet type selection screen in the Cake Wallet app. It wraps a list container in a rounded clipping widget, slightly increases row height from 48 to 50 pixels, and adjusts indentation. There is no security-relevant change.

This change stops Payjoin transactions from using unconfirmed (0-confirmation) coins as inputs when the wallet is acting as the receiver in a Payjoin swap. Before the fix, the receiver could accidentally propose or sign a Payjoin that relied on coins that had not yet been mined into a block. Such coins can disappear, be double-spent, or get replaced, which could cause the Payjoin to fail, be invalid, or expose the receiver to loss or confusion. The fix adds an optional 'confirmed only' filter and turns it on for Payjoin receiver candidate inputs.

This commit strengthens the wallet's automatic detection and handling of scam, spam, and impersonator tokens on Ethereum-compatible (EVM) chains and Solana. It adds checks for suspicious names/symbols (e.g., fake 'ETH', 'SOL', 'USDC', or tokens with 'airdrop', 'claim', URLs), prevents auto-enabling tokens that look like well-known coins but aren't verified, and uses Moralis API data such as price, value, verified-contract status, and security score to decide whether a discovered token should be shown as enabled. It also re-runs a one-time cleanup on existing tokens to reclassify any previously missed scams. There is no direct exploit fixed in the diff; rather, it is a defensive hardening change against social-engineering/token-spam attacks.

This commit changes how Cake Wallet handles Bitcoin transactions when it cannot fetch all of their 'input' transaction data from the Electrum server. Previously, such transactions were skipped entirely and not shown in the wallet. Now they are still parsed and displayed, but with a warning ('Transaction has missing data') and a null fee. The change also makes the list of input transactions nullable and adds null checks in fee-calculation and replace-by-fee code paths, throwing errors if input data is missing there. This is primarily a robustness/usability fix, but it touches transaction parsing and fee logic, which are security-sensitive areas.

This is a large code refactor of Cake Wallet's address resolver feature, which turns human-readable names (like Twitter handles, ENS domains, or email-style addresses) into cryptocurrency addresses. The change reorganizes existing lookup logic into a cleaner provider/service pattern and adds new address sources such as Nostr, BIP353, and Zcash names. It is primarily a structural rewrite rather than an obvious security fix, but because it touches many parts of how the app decides where to send money, any bugs in the new resolver could lead to payments going to the wrong address.

This commit adds a new piece of information—the Lightning Network payment preimage—to the transaction details screen. The preimage is a proof that a Lightning payment completed, and it is already stored in the wallet's existing payment data. The change simply displays it to the user, similar to showing a receipt number. There is no indication it introduces a security vulnerability.

This commit contains three small, unrelated fixes. One adds a safety catch around a Lightning wallet disconnect call so the app doesn't crash if disconnect fails. Another trims spaces and trailing currency text from amount inputs before converting them to numbers, which could prevent user input errors or unexpected parsing. The third is an Italian translation correction for the word 'change'. There is no clear security vulnerability being patched.

This commit simply changes an error message shown to users when no cryptocurrency exchange provider can create a quote. Instead of a generic failure message, the app now tells the user which specific cryptocurrency could not be quoted. There is no security issue here.

This commit is a routine Flutter UI fix. It wraps a top bar widget in an 'Observer' so the interface automatically updates when the underlying app state changes. There is no security relevance visible in the change.

This is a minor user-interface layout fix. It swaps which corner of a history page header is rounded based on a setting, reduces vertical padding slightly, and only shows a divider line when the bottom is not rounded. There is no security relevance visible in the change.

This is a small bug-fix patch in Cake Wallet's buy/sell cryptocurrency screen. It rounds the calculated crypto amount to the correct number of decimal places before converting it into a Money object. Without the fix, certain exchange rates or fiat amounts could produce a value with too many decimal places, causing a 'decimals exception' (an app crash or error). The change is defensive and improves reliability, but it does not appear to be a security vulnerability on its own.

This commit is a purely cosmetic UI layout fix. It adds a rounded-bottom toggle to a history top bar widget and adjusts padding so the bar looks correct when there are no items below it. There is no security relevance.

This commit is purely a code reformatting (whitespace and indentation cleanup) across seven user-interface files. It does not change app behavior, fix a bug, or alter security logic. The only non-whitespace change is a minor adjustment to the exception handler's debug-mode ignore condition, which is also a low-risk formatting/condition restructuring with no security impact.

This commit is a routine feature update that redesigns the buy/sell cryptocurrency flow in the Cake Wallet app. It adds new screens for selecting amounts, providers, payment methods, confirming trades, and redirecting to third-party payment services. It also updates icons and translations. There is no clear security vulnerability in the code changes themselves, but the commit touches code that handles financial transactions and redirects to external providers, which is always a sensitive area.

This commit fixes how many decimal places are shown for EVM (Ethereum-compatible) token amounts in the transaction history screen. Previously, the app likely showed the wrong number of decimals, making token amounts appear much larger or smaller than they actually are. This is a user-interface bug, not a way to steal funds or attack the wallet.

This is a tiny UI fix that changes how the date is displayed on a transaction details screen. It swaps one date-formatting helper for another so the date appears in the user's chosen language. There is no security issue visible in the change.

This commit is a work-in-progress (WIP) refactor of the buy/sell cryptocurrency flow in the Cake Wallet app. It restructures how the buy/sell mode is passed through the dependency injection system, replaces some UI placeholders, and adds a new custom amount input widget. There is no indication of a security fix or vulnerability being addressed.

This commit is a routine work-in-progress UI feature for buying and selling cryptocurrency inside the Cake Wallet app. It adds a new screen where users can pick preset fiat amounts (like $50, $100, $500) or enter a custom amount. There is nothing in the changes that fixes a security bug, opens a vulnerability, or handles sensitive data in a risky way. It is normal product development code.

This commit is a work-in-progress (WIP) UI change for Cake Wallet. It adds a new buy/sell amount page, wires it into the app's dependency injection system, and connects a selector modal so users can open the new page. There is nothing in the code that touches security-sensitive behavior such as sending funds, storing keys, handling passwords, or network requests. It is purely user-interface scaffolding.

This commit is a routine user-interface work-in-progress change. It adds a new bottom-sheet modal that lets users choose between buying or selling cryptocurrency, adds two new icon images, and updates the English text strings. There is no security-relevant change in the code.

This small update tightens how the app handles fee-estimate responses from an EVM (Ethereum-compatible) network API. Before, if the server returned a successful HTTP status but the 'result' field was not a list, the app could crash while trying to process it. Now the app checks that 'result' is actually a list before using it. The second file change is just a routine dependency lock-file cleanup and appears unrelated to security.

This is a small UI stability fix in the cryptocurrency swap screen. It replaces a forceful 'this widget must exist' access with a safer 'if it exists' check for the receive-amount field. The change prevents the app from crashing if the receive-side widget has not finished building when the user types or changes settings. There is no indication this allows theft of funds, bypass of security checks, or remote exploitation.

This commit fixes how dates are formatted in the wallet's transaction history so they match the user's selected language/locale. It also slightly reorganizes the buttons shown at the top of the assets/history tabs by moving their definitions into a shared data class. There is no security-relevant change.

This is a one-line UI bug fix in a Flutter/Dart mobile wallet app. The change corrects which boolean value is checked when deciding what subtitle text and color to show for a swap-history filter checkbox. Previously it used the checkbox's own value; now it uses the app's trade-filter store state. There is no security relevance visible in the commit.

This commit fixes how the app groups transactions on the dashboard. Previously, transactions from the last 24 hours were labeled as 'today'; now only transactions from the current calendar day are labeled 'today'. It is a cosmetic UI change with no security relevance.