Cake Wallet / Monero.com

This commit improves how the Cake Wallet app reads and displays error messages when an Ethereum-compatible transaction fails due to not enough funds for fees. It adds support for more message formats and shows a simpler 'insufficient funds' message when the app cannot extract exact numbers. There is no direct evidence this fixes an active security vulnerability; it appears to be a user-experience and robustness improvement.

This commit fixes a user-facing bug where sending cryptocurrency through EVM chains (Ethereum, Polygon, Base), Solana, or Tron could produce an 'Already Known' error or fail to show the new transaction promptly. It adds a new method to refresh transaction history and calls it a few seconds after a successful send. The code also includes unrelated formatting cleanups and a small refactor of how EVM wallet types are detected. There is no direct evidence in the commit of a security vulnerability being patched.

This commit only changes user-facing text (translations) in the app. It updates the description for the hardware wallet restore option from mentioning only 'Ledger' to a more generic wording about linking hardware wallets from various manufacturers. No code logic, security behavior, or functionality was modified.

This commit fixes how Dogecoin transaction fees are calculated in Cake Wallet. Previously, the app likely relied on a Bitcoin-style size estimate that doesn't match Dogecoin's typical transaction structure. The change adds a Dogecoin-specific formula to estimate transaction size (and therefore fee) more accurately. An incorrect size estimate could lead to users paying too much or too little in fees, which in extreme cases can cause transactions to get stuck or be delayed.

This update fixes a user-interface bug where someone could accidentally trigger a cryptocurrency send twice in a row, for example by double-tapping a button. The app now disables the send button once a transaction has been successfully prepared, and it properly cancels the prepared transaction if the confirmation bottom sheet is closed without sliding to confirm. This reduces the chance of sending funds twice or leaving a half-prepared transaction open.

This commit removes a UI filter that previously hid transactions with a zero amount from the wallet's transaction history page. The change means users will now see zero-amount transactions (for example, some Polygon spam transactions or failed/minimal transfers) in their history instead of them being hidden. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a usability fix to ensure legitimate transactions are not accidentally hidden.

This is a small defensive fix in a mobile wallet's gift-card purchase screen. It checks that the Flutter UI context is still active before opening a bottom-sheet popup. Without the check, the app could try to display a popup after the user had already left the screen, which can cause a crash or a confusing error message. It is a stability/reliability improvement, not a security vulnerability fix.

This is a small UI hardening change in a wallet app's back-arrow button. It now checks whether the screen is still active and whether there is a previous screen before trying to go back. Without the guard, pressing the button at the wrong moment could trigger a harmless framework warning or a minor navigation error, but it does not appear to expose funds, keys, or sensitive data.

This commit adds support for a 'label' field when restoring a wallet from a backup or QR code created by another app called Cupcake. It simply copies that label into the wallet name fields during restore. There is no obvious security bug here; it is a small feature addition.