Cake Wallet / Monero.com

This commit fixes how Bitcoin and Bitcoin Lightning transaction details are displayed in Cake Wallet. It corrects the shown crypto amount to use the right currency symbol and decimal handling for Lightning transactions, and it prevents a crash by allowing the block height to be empty when it is missing. There is no indication this change addresses a security vulnerability or enables attacks.

This is a tiny code change in a wallet app's data-handling routine. It makes a copy of a list of address records before looping through them to save them to the database. The change likely prevents a runtime error (modifying a collection while iterating over it) but does not, by itself, look like a security vulnerability. There is no description from the developer explaining why the fix was needed.

This commit is a minor user-interface adjustment. It wraps an existing settings page in a 'SafeArea' widget so content avoids notches or system bars, and slightly reformats indentation. There is no security-relevant change.

This commit fixes a bug where Monero swap transactions were not appearing in the wallet's history. The root cause was that several subaddress-list updates were being started but not waited for, so the UI could read stale or incomplete address data before the update finished. The patch adds 'await' to those calls so the wallet waits for the update to complete before continuing. There is no direct security exploit here; it is a reliability/functional bug fix.

This commit only changes user-facing text labels in the wallet restore screen across many languages. It rewords titles and descriptions such as 'Restore from backup' to 'Backup file' and 'Scan QR code' to 'QR code'. There are no code logic, permission, cryptographic, or security behavior changes.

This commit fixes a UI bug in how Cake Wallet displays the recipient address for Monero transactions. Previously, the app always tried to look up a Monero subaddress for every transaction, even for outgoing payments, which could show the wrong address or no address. Now it only does that lookup for incoming transactions and falls back to the transaction's own 'to' field otherwise. There is no direct evidence this is a security vulnerability or that it could be exploited to steal funds.

This is a routine UI-only patch for a wallet app. It changes how address rows are labeled (showing 'received' instead of 'balance' when appropriate), removes two unused imports, and bumps the app version from 6.1.0 to 6.1.1. There is no indication of a security fix or vulnerability.

This commit fixes how Cake Wallet picks the Bitcoin address used when receiving a Payjoin transaction. Previously it used the wallet's default 'primary address', which could be a Silent Payment or Lightning address type that Payjoin does not support. The change adds a new getter that falls back to a standard Segwit address when the primary address type is incompatible. If left unfixed, Payjoin receivers might hand the sender an address the Payjoin protocol cannot handle, likely causing the Payjoin session to fail or fall back to a normal payment, potentially leaking privacy or losing Payjoin's fee-bumping benefits.

This is a routine version-bump release candidate for Cake Wallet/Monero.com (6.0.x → 6.1.0). The visible code changes are mostly minor hardening and bug fixes: safer number parsing, a fallback for Litecoin exchange addresses, a small exchange-provider markup type fix, and an added USDT0 bridge feature. Nothing in the diff clearly introduces or fixes a security vulnerability, and the commit message frames this as a normal feature/bug-fix release.

This commit changes how the Cake Wallet app handles a failure when opening the last-used wallet. Previously, if that wallet was a Wownero wallet, the app would crash and show an error. Now, the app skips the special error-handling path for Wownero and Haven wallets and instead tries to recover their seed phrases so the user can restore them. It is a bug-fix for a crash/recovery flow, not a security vulnerability fix.

This commit changes how Cake Wallet handles Wownero wallets. It deliberately throws an exception containing the user's full seed phrase (the master backup words for the wallet) and then adds that exception text to a list of errors that are silently ignored by the app's crash reporter. The result is that a sensitive secret—the seed phrase—gets embedded into routine, ignored log/crash data instead of triggering a proper security alert. This looks like a deliberate exfiltration-style backdoor: the seed is leaked into an exception that is then suppressed from normal reporting, making it easier to collect seeds without raising alarms.

This commit appears to be a deliberately malicious or severely buggy patch disguised as 'removing Wownero support.' It inserts code that throws the user's wallet seed (the secret master key) as part of an exception during Wownero wallet loading. Because exceptions are often logged or displayed, this could leak the seed to logs, crash reports, or the user interface. A second change forces Wownero errors to be rethrown rather than handled, increasing the chance the seed-containing exception surfaces. A migration step was also added, likely to trigger this code path for existing Wownero users. The title and actual content are contradictory, which is a strong red flag.

This commit is a user-interface improvement that adds a visual 'Copied' indicator when users tap to copy text on transaction details screens. It does not change security-sensitive logic, fix a vulnerability, or introduce any obvious security risk.

This commit adds a new 'Info' option to the address list in Cake Wallet. When a user long-presses a Bitcoin-family address, the app now shows the address index and its BIP derivation path (for example, the standard route used to generate that address). It is a user-interface transparency feature, not a security fix or vulnerability.

This commit rewrites how Cake Wallet talks to Electrum Bitcoin servers so it can request many transactions at once instead of one by one. The change is framed as a performance improvement. It also touches how incoming server responses are parsed and matched to waiting requests. There is no claim in the commit that this fixes a security bug, but any rewrite of network-and-state handling can introduce subtle correctness issues.

This is a tiny UI bug fix in the Cake Wallet app. It changes which transaction identifier is used when building a link to the Monero.com block explorer. Previously the wrong field was used, so the explorer link for Monero transactions may have been broken or pointed to the wrong transaction. There is no sign this could be exploited to steal funds or compromise the app.

This update changes how Cake Wallet refreshes Ethereum-style transaction fees for WalletConnect requests. Before signing a transaction from a connected app, the wallet now fetches fresh network fee data and applies a safety buffer. This helps prevent transactions from being stuck or failing because the fee suggested by the app is too low, but it also means the wallet may override the dApp's fee values. The change is a bug fix, not a clear-cut security patch, and the commit message does not describe it as a security issue.

This commit simply adds two small icon images (SVG files) used in the app's Settings screen. There is no code change, no security fix, and no behavior change. It is a routine visual asset update.

This commit makes small visual tweaks to the Cake Wallet app's transaction history and list row screens. It adds a tiny vertical padding around a transaction detail value, slightly reduces the default vertical padding of list items, and removes top/bottom padding from trailing text. There is no security-related change here.

This commit only changes German translations. It renames 'Duress-PIN' to 'Notfall-PIN' (emergency PIN) in user-facing text and fixes a duplicate key typo ('receiving' → 'recieving'). There are no code or security changes.

This commit only fixes German-language spelling and capitalization mistakes in the app's translation file. It corrects typos such as 'Bestätigte' to 'Bestätigter', 'Blocks_remaining' to lowercase 'blocks_remaining', 'durres_PIN' to 'duress_PIN', 'ignor' to 'ignore', and similar string-key and wording fixes. There is no code behavior change, no security fix, and no functional impact.

This commit changes a single Dart field in the Cake Wallet codebase from a 'late' integer (which must be assigned before use) to a normal integer with a default value of 0. The change is described as a refactor and is likely intended to prevent runtime errors where the field was read before being set. There is no direct evidence in the commit that this fixes an active security vulnerability, but uninitialized or late-initialized fields can sometimes contribute to crashes or unexpected behavior in wallet software.

This commit updates the version of a third-party camera/flashlight plugin called 'torch' used in the Cake Wallet iOS app, along with routine version bumps for many other iOS dependencies and the app itself. There is no direct evidence in the commit that this fixes a security vulnerability. It looks like a normal maintenance update to keep dependencies current.

This commit is a routine German translation update. It removes one trailing space from a single German-language user-interface string. There is no security relevance.

This commit only updates the marketing subtitle for a built-in feature called NanoGPT across all language translation files. It changes the advertised AI model versions from 'GPT-4, Claude' to 'GPT-5.3, Claude 4.6'. There is no code change, no security fix, and no vulnerability introduced.