Cake Wallet / Monero.com

This commit is a routine user-interface feature patch. It re-adds a 'Filters' button to a new wallet design and adds the word 'filters' to translation files. There is no security relevance visible in the code changes.

This commit is a routine German translation update for the Cake Wallet app. It changes wording, grammar, and formality (for example, switching some phrases from informal 'du' to formal 'Sie'), but does not modify any program logic, security settings, or code behavior.

Cake Wallet was setting a Bitcoin transaction value (called nSequence) to 1 when enabling Replace-By-Fee (RBF). The value 1 does technically opt into RBF, but it also tells the network the transaction cannot be mined until 1 block has passed, which is a relative timelock. This is likely unintended, makes Cake Wallet transactions stand out as unusual, and can cause problems in collaborative transactions like PayJoin. The fix changes the value to 0xFFFFFFFD, the standard value wallets use for RBF.

This commit updates the QR code scanner in Cake Wallet so it can correctly track progress when scanning multi-part BC-UR QR codes (a format used for things like crypto transaction signing). It replaces a hand-rolled progress check with a dedicated 'fountain decoder' library. There is no direct evidence this fixes a security vulnerability; it appears to be a reliability/UX improvement for scanning animated QR codes.

This commit fixes how Cake Wallet displays balances for certain Solana tokens (SPL tokens) that do not use the standard 6 decimal places. Previously, the wallet could show incorrect token balances because it assumed all tokens had 6 decimals. The fix uses the raw balance amount reported by the Solana network and the separately provided user-facing amount, so the displayed balance matches reality. There is no direct evidence this is a security vulnerability, but incorrect balance display could theoretically lead users to make wrong transaction decisions.

This commit only changes the color of a block explorer link in the transaction details screen to make it more visible. It is a user-interface styling tweak with no security relevance.

This commit changes several parts of the Cake Wallet app so that, in normal use, unexpected stored values no longer crash the app. Instead, the app falls back to a safe default (usually 'medium' priority or 'descending' order). In debug builds, it still throws an error so developers can spot problems. The change is a defensive hardening fix: it reduces the chance that a corrupted or mismatched saved setting makes the wallet unusable, but it also means a bad value is silently accepted in production.

This commit adds a safety check in Cake Wallet's Ethereum-compatible wallet to prevent users from creating native (non-token) transactions when the account does not have enough balance to cover both the amount being sent and the network transaction fee. Previously, the app only checked that the send amount itself was covered by the balance, which could allow a transaction to be created that would later fail or leave the account unexpectedly short. The fix throws a specific fee-related error when the combined amount plus estimated fees exceeds the available balance.

This commit fixes three user-facing bugs in a crypto wallet app: it prevents a token-selection bottom sheet from appearing for non-EVM wallets, makes sure BSC (Binance Smart Chain) transactions display fees in BNB instead of ETH, and avoids a crash when a swap currency has no icon image. These are correctness and UI fixes rather than obvious security vulnerabilities, but the fee-currency mix-up could confuse users about transaction costs.

This commit adds a single extra step during a wallet migration path. When an older version of the app's token storage box is missing, the code now initializes the box and then immediately 'normalizes' its keys. The change is small and appears to be a data-consistency fix rather than a security patch, but the commit message gives no details about what problem it solves.

This commit fixes a bug where deleting a custom token in the Solana or Tron wallet could fail or behave incorrectly. The old code tried to delete the token object directly, which could throw an error if the storage box wasn't open. The new code checks that the storage box is open and deletes the token by its unique address instead. There is also a minor formatting-only change in the Tron wallet's transaction code with no functional effect.

This commit fixes a bookkeeping problem in Cake Wallet's handling of Ethereum-compatible tokens. Because Ethereum addresses are case-insensitive but the app was storing them with mixed-case keys, the same token could appear twice or get out of sync. The patch adds a one-time cleanup that converts all stored token addresses to lowercase and merges duplicates. It also updates the built-in token lists to use lowercase addresses. This is a data-consistency bug fix rather than an active remote hack, but if left unfixed it could have led to wrong balances, missing tokens, or in a worst-case scenario sending funds to or trusting the wrong contract address.

This commit adds support for the Binance Smart Chain (BSC) network identifier to the WalletConnect key service. It is a one-line addition listing a new supported blockchain chain. There is no indication of a security fix, vulnerability, or behavior change beyond expanding supported networks.

This update makes three small fixes in the Cake Wallet app: it stops using a hidden note field when decoding Zcash payment addresses, removes Jupiter swap limits for non-Solana trades, and adds missing Zcash QR-code restore labels. The Zcash memo change is the most security-relevant because it prevents a payment request from silently carrying an unexpected message, but the commit itself does not describe this as a security fix and no exploit is demonstrated.

This commit fixes a logic bug in how the Zcash wallet loads cryptographic 'proving' files. Previously, the app would load the files from app assets, then immediately overwrite those loaded bytes by reading from a local cache—even if the asset load had succeeded. After the fix, the app only falls back to the cache when the asset load produced empty data. This prevents silently using stale or corrupted cached parameters and avoids unnecessary network downloads.

This commit changes the Cake Wallet app so that it no longer ships with two large Zcash cryptographic files inside the app bundle. Instead, the app downloads those files from download.z.cash the first time it needs them, and saves them to the app's cache folder. The same commit also adds the wallet's restore height to the seed/keys screen for Zcash wallets. The change is a size optimization, but it introduces a new network download of security-critical parameters and stores them on disk, which could matter if the download or storage is tampered with.

This commit fixes two bugs in Cake Wallet's WalletConnect integration for Ethereum-compatible chains (including Arbitrum/ARB). First, it corrects how the app picks the right network node when building transactions, so it no longer tries to use a non-EVM wallet's node for EVM chains. Second, it now respects gas values supplied by the connected dApp instead of always overwriting them, and it handles cases where the dApp only provides some gas fields. A third small fix prevents a crash when an auto-closing WalletConnect bottom sheet tries to close after it has already been dismissed. The commit is described by the vendor as a transaction-approval bug fix, not as a security vulnerability.

This commit fixes a simple Japanese translation typo by adding a missing closing quotation mark in a language file. It has no security relevance.

This is a routine version-bump release candidate for Cake Wallet/Monero.com (5.8.0 → 5.9.0). It adds BNB Smart Chain support, swaps a Zcash library dependency from a personal GitHub fork to a Cake Labs fork, updates the bundled Monero node list, and bumps build numbers across Android, iOS, Linux, macOS, and Windows. The changes are mostly configuration and dependency metadata; there is no direct evidence in the diff of a security vulnerability or a security fix.

This commit makes two user-facing changes in the Cake Wallet app: it turns off a default 'estimated time remaining' display for wallet syncing, and it stops silently forcing a hardcoded Cake-run Bitcoin server when scanning certain private transactions. Instead, the app will use the server the user already picked, only falling back to the hardcoded one if none was chosen. The commit also slightly increases a network keep-alive timer. There is no direct evidence in the commit that this fixes an active security vulnerability, but it reduces privacy and trust risks by giving users more control over which server handles their transaction data.

This commit removes Zcash 'Warp' wallet-sync components from the macOS build of Cake Wallet, bumps the macOS app build numbers, slightly increases a startup delay, and changes one error case to return false instead of throwing an exception. There is no direct evidence in the commit that this fixes an active security vulnerability; it looks like a build cleanup and minor hardening change.

This commit contains three small fixes: a loop bug in Zcash address handling, a reclassification of a Ledger error message, and routine build number bumps. The Zcash fix changes two mistaken index references from 'i' to 'k' inside a loop, which likely caused the wrong wallet account to be checked for hidden/used transparent addresses. This could affect address rotation or privacy behavior for Zcash transparent addresses, but it is a correctness bug rather than an obvious exploit. The Ledger change moves 'transport error' from a list of known Ledger errors to a list of ignored/generic exception strings, which may reduce false crash reports but does not appear security-sensitive. The build number changes are administrative.

This is a routine version-bump release candidate (v5.8.0) for the Cake Wallet family of apps. Most changes are feature work: adding Arbitrum, improving EVM chains, integrating Jupiter swaps for Solana, and fixing several Zcash wallet bugs. The Zcash fixes include making sure hidden/used transparent addresses are not reused for exchanges, falling back to an offline formula if the server cannot provide a block height from a date, and removing a stale view-model that was breaking wallet-group functionality. There is no vendor statement that this commit fixes a security vulnerability, and the changes read like ordinary bug fixes rather than a security patch.

This commit updates Cake Wallet's Solana support so it can work with both the older standard SPL token program and the newer Token-2022 program. It fetches the correct token program from the blockchain for each token and uses that program when finding or creating associated token accounts and when building transfer instructions. The change is a feature enhancement, not a stated security fix. There is a small risk that if the code picks the wrong program ID or an attacker-controlled RPC returns bad data, transactions could fail or funds could be sent to incompatible accounts, but the diff itself does not show an obvious vulnerability.

This commit polishes the new Jupiter DEX swap feature for Solana wallets in Cake Wallet. It makes balance updates faster, fixes a transaction-history display quirk, and tweaks how swap details are copied to the clipboard. There is no clear security bug being fixed; it reads as ordinary feature hardening and UI cleanup.