Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This commit fixes a bug in the Cake Wallet Litecoin wallet where, when renaming a wallet, stored MWEB (a privacy feature for Litecoin) transaction records were being copied to a new storage box by reusing the exact same object references. …
Data migration now clones objects instead of sharing referencesPrevents potential state corruption when renaming Litecoin walletsNo explicit input validation or cryptographic change present
This is a routine update to the project's automated iOS build pipeline. It changes which Apple computer (runner) and Xcode version are used to compile and upload the iPhone app, so the app meets Apple's upcoming App Store requirement to us…
This commit is a routine mix of small fixes and test-tool updates. It makes a UI key more specific to avoid list-item conflicts, adds a safety check before showing a post-transaction popup, updates a test helper to match new app settings, …
Flutter BuildContext used across async gap now guarded by context.mountedNo explicit security keywords, CVE references, or advisory links in commit or titleChanges are split across UI, test tooling, and fixture scripts with no coherent security theme
This is a large accessibility and test-automation improvement for the Cake Wallet Flutter app. It adds stable identifiers to buttons, text fields, lists, and dialogs so screen readers and automated UI tests can find them. The patch also re…
Removed user-data interpolation from accessibility identifiers (tx ids, wallet names, seed words, addresses)Added stable, index-based or enum-based semantics identifiers across UI componentsAdded custom lints and CI workflow to prevent future user-data interpolation in test keys
This commit adds three new automated testing pipelines for the Cake Wallet mobile app: one for Android, one for iOS, and a weekly overnight test. These are explicitly marked as 'reply-only' experiments, meaning a failure will not block rel…
New CI/CD pipeline handling wallet seed phrases and API keysUse of `NO_REPLY` / `continue-on-error: true` to avoid blocking mergesExplicit mitigation: avoids `npx` on macOS to prevent environment-variable leakage via process title
This is a large cleanup of how the app labels its on-screen buttons and fields for automated testing and accessibility tools. Previously, many test labels were accidentally built from private user data such as wallet names, transaction IDs…
Accessibility identifiers derived from PII/sensitive data (wallet names, transaction IDs, seed words, addresses) are replaced with static or index-based identifiersNew custom lint rule no_string_interpolation_in_test_key blocks string interpolation in test keys except for int indexes and enum .nameNew custom lint rule require_test_key_semantics_identifier ensures framework interactive widgets with _key keys expose a Semantics identifier
This is a very large code refactor of the cryptocurrency swap/exchange feature in Cake Wallet. It rewrites how exchange rates are fetched, how trades are created and tracked, and how trade history is stored in the local database. The commi…
Large-scale rewrite of trade creation, rate fetching, and status monitoringDatabase schema migration for Trade table with data reconstruction from old columnsNew amount parsing helper (Money.safeParse) and exchange-rate math (ExchangeRate.fromAmounts)
This commit expands Cake Wallet's Lightning Bitcoin feature so it works across multiple Bitcoin accounts instead of being locked to the primary account only. It also fixes address selection so the app picks an unused Segwit address that be…
Account isolation logic changed: Lightning and Segwit address selection now account-awarePrevious code could return a Segwit address from a different account than the one currently selectedRemoval of hard-coded account index checks suggests prior account-boundary assumptions were too restrictive
This commit is a large internal refactor of how Bitcoin-style wallets in Cake Wallet store and derive account keys. It replaces scattered maps of HD keys with a single shared 'ElectrumAccounts' model, initializes those keys earlier during …
Refactor of BIP32 HD key derivation and account key storage across multiple coin modulesWallet keys view model now exposes master xPrv and xPub instead of per-account private keyChange in how legacy change HDs are identified, with a new regression test for Litecoin MWEB change addresses
This commit deletes four leftover Android Java files that were no longer used. The app's namespace was already fixed to 'com.cakewallet.cake_wallet', so these old copies of the main activity and application class under different package na…
This commit fixes visual layout bugs in the Cake Wallet mobile app where long Tamil translations were being drawn off-screen or clipped. It also fixes a broken unit test by adding a missing mock object. There is no security vulnerability h…
This commit adds new language translations (Bengali, Marathi, Tamil, Telugu), fixes Hindi translations, and introduces automated tools to check translation quality. It also makes a small formatting fix so cryptocurrency amounts display wit…
No changes to cryptographic, authentication, networking, or storage codeNo permission changes or new entitlementsNo changes to dependency versions or external URL endpoints
This commit is a routine user-interface redesign for the Cake Wallet app. It adds a new 'More Actions' menu (a floating plus button), moves Contacts and Buy/Sell options into that menu, and introduces first-time explainer pop-ups for gift …
No security-relevant code changes identifiedUI-only refactor with no new network, storage, or crypto logicNew URL launch to cakepay.com in gift card explainer uses standard url_launcher external application mode
This commit improves accessibility for screen-reader users. It adds spoken labels to buttons that were previously unlabeled, announces which cryptocurrency each wallet holds, removes a duplicate invisible tap target, and makes the currentl…
This commit improves screen-reader accessibility in the Cake Wallet mobile app. It makes settings switches announce their name (e.g., 'Auto generate addresses, switch, off') and makes choice options like 'Enabled / Tor only / Disabled' tel…
This commit makes small GitHub workflow and documentation tweaks. It adds read-only permissions to four pull-request check workflows, deletes an already-commented-out lint workflow, and updates a Windows installer filename and release note…
Workflow least-privilege hardening: four PR workflows now declare read-only repository permissionsRemoval of an inactive lint workflow that contained commented-out build steps and external download commandsDocumentation-only update for Windows installer filename and release history
This commit is a routine version bump and changelog update for the Cake Wallet/Monero.com v6.5.4 release candidate. It updates translated changelog text, version/build numbers across Android, iOS, Linux, and macOS, and makes minor UI fixes…
This commit fixes a bug in how Cake Wallet signs Bitcoin-style messages. Previously, the app could not correctly sign messages with 'change addresses' (a special type of address used when sending leftover funds back to yourself). The fix m…
Refactor centralizes address validation and derivation-path construction for hardware signingChange addresses are now included in address lookup, fixing a functional signing bugTaproot and MWEB addresses are explicitly rejected for message signing
This commit fixes a bug in Cake Wallet's Bitcoin message signing. Previously, if a user chose a silent payment address (a newer privacy-focused Bitcoin address type), the app would still sign the message using the wallet's main key. That s…
Cryptographic signature produced for a different identifier than the one presented to the userSilent fallback to main wallet key when selected address cannot be derivedMessage signing bypass for silent payment / unheld addresses
This commit is a straightforward user-interface performance fix. It wraps each tab of the app's main dashboard in a Flutter widget called TickerMode, which pauses animations in tabs that are not currently visible. Before the change, a load…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedfeat: enhance Bitbox ViewModel with connection tracking and refactor imports (#3706)by Konstantin Ullrich · 9f1f82fd · Oct 9, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Konstantin Ullrich
feat: enhance Bitbox ViewModel with connection tracking and refactor imports (#3706)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine feature and cleanup change for the BitBox hardware wallet integration in Cake Wallet. It adds a simple connection-tracking timer, refactors import statements (mostly changing quote style and sorting), and removes an unnecessary 'await' keyword. There is nothing in the diff that introduces a security vulnerability or fixes an obvious one.
AI review queuedKeep Enable Lightning toggle visible after disabling it (#3702)by claude[bot] · 8b05da8e · Oct 9, 2026 · 2 filesMessage 58 · ThinInformational 22Details
Commit message · claude[bot]
Keep Enable Lightning toggle visible after disabling it (#3702)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 22/100
This commit changes how the app decides whether to show the 'Enable Lightning' toggle and when to close the Lightning wallet. It keeps the toggle visible after a user turns Lightning off, and it now closes the Lightning wallet connection when Lightning is disabled. There is no clear security bug being fixed; it looks like a UI/UX and resource-cleanup improvement.
AI review queuedfix: handle wallet delete flushbar dismissal (#3697)by David Adegoke · 91738ea7 · Oct 8, 2026 · 1 fileMessage 70 · AdequateInformational 17Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This is a small UI bug fix in a wallet management screen. It changes how a progress notification (a 'flushbar') is closed when deleting a wallet, preventing a possible crash or visual glitch if the notification was already gone or its route was no longer active. There is no indication this affects money, keys, passwords, or network security.
AI review queuedV6.5.0 rc (#3674)by Omar Hatem · 5f91c4d2 · Oct 6, 2026 · 22 filesMessage 79 · AdequateInformational 24Details
Commit message · Omar Hatem
V6.5.0 rc (#3674)
* bump: monero_c to v0.18.5.3
* revert deprecated seeds table
* update monero_c
* update monero_c
* update monero_c
* v6.5.0 Release candidate Things to test: - Robinhood (new evm wallet) - Monero update (test monero in general) - Restore from backup that is created in previous versions - Charts - Bitcoin accounts (please also test that ltc, bch, doge are working fine without issues) - quick bitcoin sync (also verify other wallets above are working fine)
* v6.5.0 Release candidate Things to test: - Robinhood (new evm wallet) - Monero update (test monero in general) - Restore from backup that is created in previous versions - Charts - Bitcoin accounts (please also test that ltc, bch, doge are working fine without issues) - quick bitcoin sync (also verify other wallets above are working fine)
✓ Subject identifies a change✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 24/100
This is a routine release-candidate commit for Cake Wallet/Monero.com version 6.5.0. It bumps the Monero core library version, adds a new Robinhood Chain wallet, enables price charts and Bitcoin accounts, reverts a database table that was intended to store deprecated wallet seeds, disables the Exolix swap provider, and fixes an Alchemy API key fallback. None of these changes are explicitly described by the vendor as security fixes, and there is no direct evidence in the diff of an exploitable vulnerability. The most notable security-adjacent change is the removal of the DeprecatedWalletSeeds table, which suggests a deliberate reduction of seed-storage surface area, but the commit does not frame it as a security patch.
AI review queuedDon't force max brightness when showing seed QR (#3682)by claude[bot] · c6f5865a · Oct 6, 2026 · 1 fileMessage 81 · StrongLow 26Details
Commit message · claude[bot]
Don't force max brightness when showing seed QR (#3682)
Tapping Show QR on the wallet keys/seed page wrapped the navigation in BrightnessUtil.changeBrightnessForFunction, which set the display to full brightness and only reset it if the route returned normally, leaving brightness stuck at max in some dismiss paths. Show the seed QR at the user's normal brightness instead.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 26/100
This commit removes a feature that automatically cranked screen brightness to maximum when showing a wallet's seed/keys as a QR code. In some cases the brightness stayed stuck at max after closing the QR screen, which could let someone nearby more easily see or photograph the sensitive QR code. The fix simply shows the QR at whatever brightness the user already had set.
AI review queuedchore: migrate to hosted scalable CI (#3620)by cyan · 77e4b946 · Oct 3, 2026 · 23 filesMessage 65 · AdequateInformational 16Details
Commit message · cyan
chore: migrate to hosted scalable CI (#3620)
65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 16/100
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.
AI review queuedonly check address validation once for old addressesby Omar · 1972efd0 · Oct 3, 2026 · 3 filesMessage 50 · ThinLow 29Details
Commit message · Omar
only check address validation once for old addresses
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100
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.
AI review queuedfix balance being stale cuz it's overriden by an old valueby Omar · 1de16191 · Oct 2, 2026 · 3 filesMessage 50 · ThinLow 33Details
Commit message · Omar
fix balance being stale cuz it's overriden by an old value
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 33/100
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.
AI review queuedfeat: prefill rescan height with the saved Monero and Zcash restore height (#3669)by Seth For Privacy · 0503d542 · Oct 2, 2026 · 5 filesMessage 85 · StrongInformational 19Details
Commit message · Seth For Privacy
feat: prefill rescan height with the saved Monero and Zcash restore height (#3669)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
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.
AI review queuedAdd onionbalance Tor frontends to default node lists (#3431)by Seth For Privacy · c8cad835 · Sep 26, 2026 · 5 filesMessage 81 · StrongInformational 21Details
Commit message · Seth For Privacy
Add onionbalance Tor frontends to default node lists (#3431)
* Add onionbalance Tor frontends to default node lists
Update the primary Monero and Zcash onion nodes to the new load-balanced onionbalance frontends, add missing Cake Wallet Tor nodes for Bitcoin and Litecoin, and use the mempool onion frontend for Bitcoin fee fetching when Tor is enabled. All Cake Tor nodes are marked isOfficial so they get the official-node badge.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Remove per-instance Zcash Tor #2 node, superseded by onionbalance frontend
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 21/100
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.
AI review queuedfix: enter Lightning invoice amounts in sats (#3525)by Omid · fdb82675 · Sep 26, 2026 · 2 filesMessage 93 · StrongInformational 19Details
Commit message · Omid
fix: enter Lightning invoice amounts in sats (#3525)
LN receive remapped btcln to BTC, so the default "sats (LN)" display mode never applied and the amount field stayed in BTC.
Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Konstantin Ullrich <konstantin@cakewallet.com>
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
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.
Revert "Revert "fix: unify encryption across platforms (#3470)" (#3634)" (#3635)
This reverts commit dd58455ea6d2629eb1a28991e40bf6f9953d41d3.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
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.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 57/100
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.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100
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'.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
* Apply patches for BLE session, locktime prompt, and monero coincontrol on hww [skip ci]
* include the fix for bluetooth prompt showing on app start
* include the fix for bluetooth prompt showing on app start
69/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 33/100
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.
AI review queuedAdd thread-safety and BLE support for Ledger and Trezor devices (#3638)by Konstantin Ullrich · 3d03a62e · Sep 18, 2026 · 9 filesMessage 81 · StrongLow 35Details
Commit message · Konstantin Ullrich
Add thread-safety and BLE support for Ledger and Trezor devices (#3638)
* feat: support BLE device detection for Ledger and Trezor wallets, update trezor-flutter dependency
* feat: add BLE connection state listener for Trezor devices, handle disconnect events, and clean up resources on close
* feat: add mutex locking to MoneroTrezorService for thread-safe operations
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 35/100
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.
Revert "fix: unify encryption across platforms (#3470)" (#3634)
This reverts commit 90e25afc11f8e32a997d62abe5b8bed5428924b1.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 59/100
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.
AI review queuedfeat: restrict history api calls when toggle is off in privacy settings (#3615)by David Adegoke · 3a04c7ff · Sep 16, 2026 · 6 filesMessage 93 · StrongLow 41Details
Commit message · David Adegoke
feat: restrict history api calls when toggle is off in privacy settings (#3615)
* feat: restrict history api calls when toggle is off in privacy settings
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 41/100
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.
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 17/100
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.
AI review queuedfix: sign and verify for evm wallets (#3599)by David Adegoke · 96e5329b · Sep 14, 2026 · 1 fileMessage 75 · AdequateLow 35Details
Commit message · David Adegoke
fix: sign and verify for evm wallets (#3599)
75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100
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.
AI review queuedAdd more guards to amounts being zero or infinity (#3612)by Omar Hatem · 3bb64b71 · Sep 12, 2026 · 9 filesMessage 73 · AdequateHigh 79Details
Commit message · Omar Hatem
Add more guards to amounts being zero or infinity (#3612)
* Add more guards to amounts being zero or infinity
* Add more guards to amounts being zero or infinity
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · High 79/100
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.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 49/100
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.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 61/100
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.