Cake Wallet / Monero.com

This commit is an infrastructure change: Cake Wallet moved its automated build system from GitHub's standard runners to a third-party hosted service ('puzl-ubuntu-latest') and split the build into many smaller parallel jobs. It also adds a hard-coded developer test certificate and private key for CI builds. There is no direct change to the wallet's user-facing code, cryptography, or network behavior. The main security concern is that the new CI provider and the committed test signing material could, in theory, be misused if secrets or build outputs leak, but the commit itself does not introduce a known vulnerability in the app.

This commit changes how Cake Wallet verifies whether stored Bitcoin and Bitcoin Cash addresses belong to the 'hidden' (change) side of a wallet. Previously, the app re-checked every address on every wallet open, which could flip address labels incorrectly if a stored address didn't match either the normal or hidden chain. Now it checks each old address only once, marks it as checked, and only flips the label if the address actually re-derives from the opposite chain. New addresses created by the wallet are marked correct-by-construction and skipped. The change is a correctness/performance fix rather than a clear security patch, but a mislabeled change address could in theory cause a user to share or reuse an address unexpectedly.

This commit fixes a bug where a Bitcoin wallet's displayed balance could become stale or be overwritten with an outdated value. The changes make balance updates copy the new value instead of sharing a reference, recalculate balances per account, avoid updating balances when the network connection is lost, and make address validation non-blocking so it doesn't freeze the app. There is no direct evidence this was exploited or treated as a security vulnerability by the vendor.

This commit changes the wallet's rescan screen so that, for Monero and Zcash wallets, the starting block height is automatically filled in with the wallet's saved restore/birth height. This is a convenience feature that helps users avoid typing the wrong height when rescanning the blockchain. There is no direct security bug in the code, but it slightly reduces the chance that a user accidentally rescans from block 0 (which would be slower and expose more transaction history/metadata) or enters an incorrect height.

This commit updates Cake Wallet's built-in lists of cryptocurrency network servers. It replaces some single Tor/onion server addresses with new load-balanced Tor frontends, adds missing Tor server options for Bitcoin and Litecoin, and makes Bitcoin fee estimates use a Tor address when Tor mode is on. The changes are infrastructure/configuration updates rather than code fixes for a vulnerability. There is no direct evidence in the commit that this is a security patch, but routing traffic through Tor can improve user privacy.

This commit fixes a user-interface bug when receiving Bitcoin over the Lightning Network in Cake Wallet. Previously, the app showed the invoice amount in whole Bitcoin (BTC) instead of satoshis (sats), because an internal currency code was being remapped incorrectly. The patch makes the receive screen explicitly set the currency to the Lightning-specific code so the amount field displays in sats as intended. There is no indication this allowed theft, unauthorized access, or code execution; it is a usability/display fix.

This commit re-applies a change that makes wallet file encryption consistent across all platforms. It replaces an older, weaker encryption method (Salsa20) with a stronger one (XChaCha20) and adds automatic migration of old wallet files. The change also fixes how non-English characters are stored and how user-chosen versus app-generated passwords are handled. Because this is a security-hardening change that was previously reverted and then re-applied, it is relevant to security, but the commit itself does not describe a specific vulnerability or incident.

This commit adds a safety check in Cake Wallet's Monero wallet code. When a user tries to send Monero, the app now checks how many separate transactions would be created. If it is not exactly one transaction, the app stops and warns the user instead of proceeding. This appears to prevent a situation where a payment unexpectedly splits into multiple transactions, which could confuse users or cause funds to move in unintended ways.

A single throw statement in the Decred wallet code was replaced with returning the string 'closed'. Previously, calling syncStatus() after the wallet was closed would crash with an error. Now it returns a status string instead. This is a minor behavior change, not a clear security fix, and the commit message explicitly calls the throw 'pointless'.

This commit is a routine code cleanup in a single Flutter UI file. It replaces verbose 'return { ... }' function bodies with arrow syntax, adds 'const' keywords where Flutter can optimize widget rebuilds, and tweaks one loading-state update to check whether the widget is still on screen before calling setState. There is no visible change in behavior for users and no indication of a security fix.

This is a routine release-candidate commit for Cake Wallet version 6.4.5. Most of the changes are version bumps, translated changelogs, and a new user-facing string about Trezor locktime. The actual code changes are small bug fixes and usability improvements: making sure a mutex is always released, preventing concurrent updates to the Monero coin list, improving Trezor Bluetooth session handling, and temporarily disabling the Exolix exchange provider. Nothing in the diff clearly introduces a security vulnerability, and the vendor does not describe any of the changes as security fixes.

This update adds Bluetooth Low Energy (BLE) support for Ledger and Trezor hardware wallets in Cake Wallet and adds a mutex lock around Trezor operations to prevent multiple actions from running at the same time. The changes are mostly feature additions and hardening, not a clear fix for an active security bug. There is no vendor statement saying this commit resolves a security vulnerability.

This commit reverts a previous change that unified wallet file encryption across all platforms. It brings back two separate encryption paths: a newer XChaCha20-based method for direct user passwords, and an older Salsa20-based method for generated keys. The older Salsa20 path is not authenticated, meaning a wrong password can produce believable-looking garbage instead of failing cleanly. The revert also removes safety checks and migration logic that prevented accidental re-encryption of files with wrong passwords, and deletes the related security tests. Because this is a partial revert and the surrounding context is limited, the exact security intent is unclear, but the change reintroduces weaker, less-safe cryptography and removes test coverage for it.

This commit adds a privacy toggle that stops EVM and Tron wallets from calling third-party blockchain history APIs (like Etherscan, PolygonScan, TronGrid) when the user turns the feature off in privacy settings. It also fixes preference key names for Base and Arbitrum scan providers so the toggle actually controls the right service. Previously, even with the toggle off, the app may have kept querying these external providers, potentially leaking the user's wallet address and transaction history to them.

This commit removes a Linux-specific workaround that manually loaded a bundled SQLite library and switches to a newer Flutter mechanism for copying native assets. It appears to be a build/packaging fix rather than a security patch. There is no indication in the commit that it addresses a security vulnerability.

This commit fixes how Cake Wallet's EVM (Ethereum-compatible) wallets sign and verify messages. It switches message encoding from ASCII to UTF-8, removes a third-party signature utility, and adds stricter checks on the address and signature format. The change appears to be a bug fix for incorrect or unreliable signature verification, which could previously fail or behave unexpectedly for non-ASCII messages or malformed inputs.

This update fixes a bug where entering special non-number values like 'Infinity' or 'NaN' as a crypto amount could slip past safety checks. Because the wallet treats an amount of zero as 'send everything' (sweep-all), a bad amount that collapsed to zero could unexpectedly drain the whole account. The patch adds stronger checks in the amount-parsing code and refuses to create transactions with zero or infinite amounts.

This is a tiny UI timing fix in a cryptocurrency wallet's dashboard screen. It moves a changelog popup so it runs after the current frame is rendered, rather than immediately after a short delay. There is no security-relevant change visible in the diff.

This patch fixes a bug where Cake Wallet's Monero module could skip actually opening a wallet and instead leave the user looking at the previously opened wallet without any warning. The old code tracked the 'last opened wallet' path and, if the requested path matched it, simply did nothing. That state tracking was unreliable and could become stale, so the app might appear to load a wallet while silently staying on the wrong one. The fix removes that shortcut and always performs the real open-wallet work, including error checks.

This commit changes how Cake Wallet encrypts and decrypts wallet backup files. It removes an older, weaker encryption method (Salsa20) and switches to a stronger one (XChaCha20) for all platforms. It also adds automatic migration: when the app opens an old Salsa20 wallet file, it re-encrypts it with the stronger method. The change touches code that handles wallet seeds/private keys, so a mistake here could put users' funds at risk, but the patch itself appears to be a hardening fix rather than an introduction of a new vulnerability.

This commit is a routine user-interface redesign for the Cake Wallet home screen. It moves the wallet name and account customizer into a new top bar, adds an 'Accounts' entry in settings, and adds or updates widget tests. There is no indication in the commit that it fixes a security vulnerability or changes security-sensitive logic such as authentication, encryption, key handling, or transaction signing.

This commit makes two small UI/logic fixes in the buy/sell flow of the Cake Wallet app. It disables the Continue button when the amount field is empty, and it avoids a crash when converting an empty fiat amount to crypto or when no exchange rate is available. These are defensive hardening changes rather than a fix for an active security vulnerability.

This commit only updates documentation. It replaces placeholder build instructions in the README with links to current platform-specific guides, fixes two broken links in a developer guide that pointed to a renamed file, and updates copyright years from 2018-2023 to 2018-2025. No code, configuration, or executable files were changed, so there is no security impact.

This is a routine version-bump release candidate for Cake Wallet/Monero.com (6.4.4). The visible code changes are mostly version numbers, localized changelogs, dependency updates, and two small functional tweaks: disabling the 'Swaps.XYZ' exchange provider by default and adding a re-entrancy guard to the Solana NFT send button so it cannot be double-pressed while the authentication prompt is showing. Nothing in the diff clearly indicates a security vulnerability or a malicious change, but the patch is a release candidate rather than a focused security fix, so the actual security-relevant code is only a small fraction of the commit.

This commit is a feature update for Cake Wallet that improves Solana NFT support (sending, ownership badges, persistent imports) and adds several security hardening measures. It does not appear to be a patch for an active exploit. The security-relevant changes include sanitizing NFT names/descriptions to stop malicious metadata from hiding or reordering text, restricting image URLs to HTTPS/IPFS gateways to avoid unsafe schemes, verifying an asset really is an NFT before sending, and adding safety checks when fetching off-chain metadata. There are also unrelated Monero background-sync and dependency changes.