Cake Wallet / Monero.com

This commit simply updates a single URL in the README file, changing the user guides link from guides.cakewallet.com to docs.cakewallet.com. There is no code change and no security issue visible in the diff.

This commit is titled 'minor fixes' and mostly contains routine maintenance: pinning a shared library (on_chain) to a specific commit hash, a small UI spacing tweak, a test update, and a few app-logic hardening changes. The most notable security-relevant change is in the Jupiter exchange provider, where the code now explicitly checks that both the 'from' and 'to' currencies are Solana-based tokens before fetching prices or creating trades. Previously, the provider relied on a pre-generated list of supported pairs, which could be bypassed or become stale. Another change hides the recipient address after exchanges involving Zcash, matching the privacy behavior already used for Monero and Wownero. A Solana client cleanup removes an unused HTTP client field, and a send-sheet popup check adds a guard to avoid calling Navigator.pop when the dialog cannot be popped. None of these changes are described by the vendor as security fixes, and no external references or CVEs are supplied.

This commit fixes a bug where new Zcash wallets in Cake Wallet were created without receiving the user's recovery phrase (mnemonic seed). Instead of using the intended seed, the wallet likely fell back to generating or using a different seed internally. This could mean a user who wrote down their recovery phrase would later be unable to restore their Zcash wallet with that phrase, potentially locking them out of funds. It is a reliability/functional bug with possible loss-of-access consequences, not an obvious remote attack vector.

This commit adds a new Jupiter DEX (decentralized exchange) integration to Cake Wallet, allowing users to swap Solana-based tokens directly inside the app. It also changes how Solana transactions are parsed and how balances are updated after swaps. The changes are mostly feature additions and UI tweaks, not a security patch. There are some code-quality concerns—such as trusting external API responses, deriving counterparty addresses from the first account in an instruction, and adding referral fee configuration—but no direct evidence in the diff of an exploitable vulnerability.

This commit fixes two minor problems introduced when earlier code changes were merged together. One file had an unused import removed, and another file corrected a typo where a function was being called with square brackets instead of parentheses. The typo only affected the Zcash wallet fee-priority setting and would have caused a compile-time or runtime error rather than a silent security issue.

This is a tiny two-part patch. One change fixes a Flutter widget lifecycle check so a modal bottom sheet is shown only when the widget is still mounted. The other adds a harmless GPU-related error message to a list of exceptions that are ignored for crash-reporting purposes. There is no obvious security issue here.

This is a small defensive fix in Cake Wallet's Litecoin address handling. When the wallet tries to create a private 'change' address using the optional MimbleWimble (MWEB) feature, it now checks that an MWEB address actually exists before using it. Previously, if MWEB was enabled but no MWEB address had been generated, the code could try to use a non-existent address, likely causing a crash or returning an invalid change address. The change makes the wallet fall back to the normal change-address path instead.

This is a tiny one-line UI fix in a mobile wallet app. It adds an extra check before closing a bottom sheet during a cryptocurrency trade, likely to prevent a crash or visual glitch when the screen has already been dismissed. There is no clear security relevance in the commit itself.

This commit fixes how Cake Wallet handles custom Bitcoin account paths on Ledger hardware wallets. Previously, the app may have ignored a user's chosen derivation path when signing Bitcoin transactions with a Ledger, which could lead to signing from the wrong account or failing to find funds. The update also bumps the ledger-bitcoin plugin to a newer version. There is no direct evidence in the commit of a security vulnerability being exploited; it reads as a bug fix for correctness.

This commit changes how Cake Wallet handles Litecoin MWEB (privacy feature) peg-out transactions. Previously, the wallet treated all non-MWEB inputs as if they were 'hog-ex' peg-outs and required 6 confirmations before spending them. The new code actually detects real hog-ex transactions by looking at transaction script patterns and only applies the 6-confirmation rule to genuine peg-outs. This is a correctness and usability fix, not a vulnerability patch, though the old behavior could have caused unnecessary transaction blocking.

This commit adds fallback logic so that if a backup password is missing from secure storage, a new one is automatically generated. It also bumps app version numbers. The change looks like a defensive hardening fix: previously, code assumed the backup password was always present (using a force-unwrap `!`), which could crash or behave unpredictably if the value was absent. The patch replaces that assumption with a safe default and automatic regeneration.

This commit fixes a bug where the app did not wait for a check that a wallet name already exists before continuing to create or restore a wallet. Because the check was not awaited, the app could proceed before knowing the result, potentially allowing a duplicate wallet to be created or overwriting an existing one. The fix simply adds 'await' so the check completes first.

This commit makes small Solana-related fixes in the Cake Wallet app. It shortens a network-request delay, removes an unnecessary Observer wrapper from a QR-code address page, wraps a send-confirmation sheet in an Observer so the slide-to-send button reacts to connectivity changes, dims the slide icon when disabled, and adds a user-friendly error message for expired Solana block hashes. None of these changes appear to be security fixes; they are usability and reliability tweaks.

This commit stops users from using Replace-By-Fee (RBF) on Bitcoin transactions that were sent to Silent Payment addresses. RBF lets someone bump a low-fee Bitcoin transaction to speed it up, but doing it with Silent Payments could break privacy or cause the recipient's address to be reused or revealed in a harmful way. The fix checks the saved recipient address and disables the RBF option when it matches a Silent Payment address pattern.

This commit removes a single debug print statement that logged a wallet object to the console. It is a cleanup change with no security relevance. There is no vulnerability, no exploit path, and no user-facing behavior change beyond preventing a wallet object from appearing in logs.

This commit fixes two practical bugs in Cake Wallet's Bitcoin 'silent payments' feature. First, it corrects the source URL used to look up the date of a silent-payment transaction, switching from an old/invalid Cake mempool endpoint to the current one. Second, it clears stale silent-payment address records during wallet startup and only uses the first generated silent address when building the address list. There is no direct evidence in the commit of a security vulnerability being exploited; the changes are bug fixes and cleanup.

This commit fixes several bugs in Cake Wallet's handling of hardware wallets (Ledger, Trezor, BitBox, etc.). It makes sure hardware wallet users are prompted to connect their device before sending funds, using a savings feature, or approving transactions. It also adds a missing error handler and prevents the app from crashing when an unexpected wallet type appears during Ledger setup. There is no direct evidence this is a security patch, but the changes reduce the chance of failed or misrouted transactions for hardware wallet users.

This commit changes how Cake Wallet's Bitcoin wallet handles transaction history from Electrum servers. When refreshing balances, it now deletes any stored Bitcoin transactions that send to the wallet's address but are no longer returned by the Electrum server. The stated goal is to remove transactions that were replaced or invalidated, such as RBF (Replace-By-Fee) replacements. This is a data-cleanup fix, but it could affect what transactions the user sees and what the wallet believes is spendable.

This update fixes a bug where iPhones could accidentally delete or fail to find the app's wallet database, which could make users think their wallets were lost. It also patches related problems where restored wallets might pick the wrong address type (derivation path) after the database move. The release notes only say 'Bug fixes' and do not describe the security relevance.

This is a small defensive UI fix in the cryptocurrency wallet's send/swap flow. Before popping a screen, the code now checks that the widget is still active and that there is actually a screen to go back to. This prevents a potential app crash if a user triggers the swap flow when there is no previous screen to return to, or after the screen has been closed.

This commit fixes a bug where the backup password was not being restored or applied correctly in Cake Wallet. It removes a separate in-memory 'SecretStore' class and instead has the backup screen and backup-password editing screen share one view-model directly. The change also adds a guard so you cannot export a backup when no password is set. There is no direct evidence in the commit of a security vulnerability being exploited; it reads as a reliability/bug-fix, though a missing backup password could weaken backup security.

This commit fixes a crash when restoring a cryptocurrency wallet from a QR code. The old code tried to convert an 'xpub' value even when it didn't exist, which would cause an error. The fix only runs the conversion if the value is actually present. There is no direct evidence this is a security vulnerability, but a crash during wallet restore could disrupt user access to funds.

This is a tiny one-line change that adds an empty catch block so an error during a Monero wallet blockchain-height refresh does not crash the code path. It is a defensive stability fix, not a security patch, and there is no indication it addresses a vulnerability.

This commit simply removes a temporary debugging job from an Android build workflow. It deletes steps that printed GitHub context and pull request details during CI runs. There is no change to application code, secrets, permissions, or security behavior.

This commit changes a GitHub Actions workflow file for Android test builds. It removes automatic triggers for regular pushes and for pull_request_target events, leaving only standard pull_request triggers. It also adds a large commented-out block showing an alternative workflow path for external fork pull requests. The change appears to be a debugging or hardening adjustment to how CI runs, not a code change in the app itself. There is no direct evidence this fixes a security vulnerability, but narrowing CI triggers can reduce attack surface for supply-chain-style abuse.