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…
This commit only updates translated text strings in the app. It adds or rewrites a user-facing message explaining that the Zano cryptocurrency will be removed from Cake Wallet in a future version because of maintenance burden. There are no code, logic, or security changes.
Security candidatefix out of bounds index in card customizer (#3733)by malik1004x · 71cd9cf6 · Oct 19, 2026 · 1 fileMessage 58 · ThinInformational 22Details
Commit message · malik1004x
fix out of bounds index in card customizer (#3733)
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
memory safety
AI analysis · Informational 22/100
This commit fixes a UI bug in Cake Wallet's card customizer. Previously, when picking a card color, the app could compute an index that pointed past the end of the available color list, which could cause a crash or display glitch. The fix uses the actual filtered color list when computing the selected index and falls back to the first color instead of an invalid position.
Security candidatefix: honor Require PIN after timeout on resume (CW-1707) (#3726)by Seth For Privacy · d665e308 · Oct 19, 2026 · 3 filesMessage 98 · StrongModerate 59Details
Commit message · Seth For Privacy
fix: honor Require PIN after timeout on resume (CW-1707) (#3726)
* fix: honor Require PIN after timeout when returning from background (CW-1707)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: ignore stale requireAuth result once the app is backgrounded again
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: ask for the PIN when the last auth time can't be read (CW-1707)
On Android the secure storage read can throw: a value that fails to decrypt comes back as a PlatformException. requireAuth() let that escape, so the resume handler never set _requestAuth and the app came back without the PIN. Return true instead, so every caller asks for the PIN when the timeout can't be checked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: arm Require PIN after lock in the session a wallet is created or restored (CW-1709) (#3736)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Omar <omarh.ismail1@gmail.com>
98/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✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Moderate 59/100
This commit fixes a bug in Cake Wallet where the app could resume from the background without asking for the PIN, even when the user had turned on 'Require PIN after timeout.' In some cases, especially on Android, a secure-storage read error could silently prevent the lock screen from appearing. The patch makes the app ask for the PIN whenever the last-auth time cannot be read, and it also tightens the lifecycle handling so the PIN prompt is honored when returning from the background after a wallet is created or restored.
* iOS only, display why keychain failed to get the read key of PIN
* offer app reset if restored from icloud backup and the keychain data is missing
* fix review comments
88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
authentication path
AI analysis · Low 33/100
This commit improves how Cake Wallet handles a specific iOS situation: when a user restores their phone from an iCloud backup, the app data comes back but the iOS Keychain (which stores the PIN and wallet passwords) does not. Previously the app could silently fail or behave oddly. Now it detects the missing keychain, explains the situation to the user, and offers to wipe the unusable local wallets so the user can restore them with their recovery phrases. It is a defensive UX and error-handling improvement, not an attack vulnerability.
Security candidatefix: open external links outside the app so the PIN lock can show (#3737)by Seth For Privacy · f80ac4df · Oct 19, 2026 · 9 filesMessage 93 · StrongModerate 64Details
Commit message · Seth For Privacy
fix: open external links outside the app so the PIN lock can show (#3737)
Links opened with the default launch mode use SFSafariViewController on iOS. While it covers Flutter no lifecycle events reach Dart, so returning from the background showed the browser without asking for the PIN.
Refs GHSA-329m-5v92-587r, CW-1707
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.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
access controlsigning or wallet path
AI analysis · Moderate 64/100
This update changes how the app opens web links so they launch in the device's regular browser instead of an embedded browser sheet. The problem was that on iOS the embedded sheet (SFSafariViewController) hid the app from normal background/foreground events, so when a user returned from viewing a link the wallet reappeared without asking for the PIN. That could let someone with brief physical access to an unlocked phone browse back to the wallet without re-entering the PIN. The patch forces links to open externally, restoring the normal app lifecycle and letting the PIN lock screen appear.
AI review queueduse on-chain address in wallet picker (#3717)by Patrick · df6051b5 · Oct 18, 2026 · 1 fileMessage 53 · ThinInformational 23Details
Commit message · Patrick
use on-chain address in wallet picker (#3717)
53/100 · ThinMessage clarity
✓ 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 23/100
This commit changes how Cake Wallet picks which Bitcoin-style address to display as 'Active' in the wallet picker. Previously, the app always used the main on-chain address, even when the user was on a Lightning or Silent Payments address page. Now, for Lightning and Silent Payments pages, it uses the on-chain address associated with those features, and passes that chosen address into the address-type labeling logic. This is a UI/UX consistency fix rather than a cryptographic or network security change. It could affect what address a user sees or copies, but there is no direct evidence it enables theft or unauthorized transactions.
Security candidatevalidate swaptrade networks against /get-coins (#3724)by Patrick · 4ef592e4 · Oct 16, 2026 · 3 filesMessage 81 · StrongModerate 58Details
Commit message · Patrick
validate swaptrade networks against /get-coins (#3724)
* validate swaptrade networks against /get-coins
* fix swaptrade order status decoding + error handling
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Moderate 58/100
This commit changes how Cake Wallet's SwapTrade exchange integration validates which cryptocurrencies and networks are supported. Instead of relying on a hardcoded internal list of network names, it now fetches the supported coins and networks from the SwapTrade API at runtime and validates the user's chosen currency/network against that live list. It also improves error handling and fixes how trade statuses are decoded. The change reduces the risk of sending funds on an unsupported or mismatched blockchain network (which can cause loss of funds), but the commit itself is a defensive correctness fix rather than a confirmed vulnerability patch.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathsigning or wallet pathauthentication pathparser or protocol path
AI analysis · Low 31/100
This is a large code-quality and error-handling refactor across the Cake Wallet app. It replaces generic 'throw Exception(...)' calls with a new family of specific exception types (CakeException subclasses), adds a custom lint rule to prevent future generic exceptions, and makes related CI/build cleanups. The change does not introduce new user-facing features or, on its own, fix a known exploitable bug. It improves maintainability and lays groundwork for better error diagnostics, but because it is a broad refactor touching many wallet modules, any mistake could affect how errors are caught and displayed to users.
AI review queuedupdate zano removal reasonby Omar · 6c1d5583 · Oct 14, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Omar
update zano removal reason
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only changes the wording of an in-app message explaining why the Zano cryptocurrency is being removed from Cake Wallet. It is a text-only update to a user-facing string and does not modify any code that handles money, cryptography, network connections, or user data.
AI review queuedipad share issue, mehby Omar · 688c5d71 · Oct 14, 2026 · 1 fileMessage 28 · OpaqueInformational 22Details
Commit message · Omar
ipad share issue, meh
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 22/100
This commit fixes an iPad-specific bug where sharing text or files could fail or crash. The root cause was that the share sheet was being anchored to a rectangle covering most of the screen (the page context) instead of a small point, leaving no room for iPadOS to display the popover. The fix shrinks oversized anchor rectangles to a single point and silently ignores duplicate share attempts caused by rapid double-tapping. There is no security vulnerability here; it is a UI/UX stability fix.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a routine visual redesign of the app's light color theme. It changes colors for charts, buttons, backgrounds, and icons, and swaps a few image assets to light/dark variants. There is no security-relevant change.
Security candidateCharts: fix 'Cannot compare money in different currencies' crash (#3713)by claude[bot] · 76e355d0 · Oct 13, 2026 · 2 filesMessage 81 · StrongInformational 18Details
Commit message · claude[bot]
Charts: fix 'Cannot compare money in different currencies' crash (#3713)
* Charts: load prices with the currency the cache round-trips to
PriceData rows are cached by CryptoCurrency.apiString ("crypto.$title", no tag), so cached rows for e.g. usdterc20 come back as generic usdt while fresh API rows keep usdterc20. Mixing both in one asset's list made ChartsLoaded.changeDataFor throw "Cannot compare money in different currencies". Round-trip the requested currency through currencyFromApiString before loading so API and cached rows match, falling back to the original currency when it can't be parsed.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VWCtnJuzXyYpP7nMbgyaKk
* Map AVAX title to avaxc in CryptoCurrency.fromString
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VWCtnJuzXyYpP7nMbgyaKk
* Charts: drop fallback now that every picker currency round-trips
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VWCtnJuzXyYpP7nMbgyaKk
* Charts: drop comment
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VWCtnJuzXyYpP7nMbgyaKk
---------
Co-authored-by: Claude <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
cryptography-sensitive path
AI analysis · Informational 18/100
This commit fixes a non-security crash in the app's price charts. The chart screen could mix cached and freshly downloaded price rows that were tagged with slightly different currency names (for example, 'usdterc20' versus plain 'usdt'), causing a 'Cannot compare money in different currencies' error. The fix makes the chart request prices using the same currency tag that the cache uses, so the two sources line up. It also adds a missing nickname mapping for the AVAX token. There is no indication this was a security vulnerability or that it could be exploited.
✓ 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 48/100
This is a routine release-candidate commit for Cake Wallet v6.5.0. The most notable change is a rewrite of how Tron (TRX) transaction history is parsed. Previously, any smart-contract interaction that had a 'contract_address' was blindly treated as a TRC20 token transfer and the app tried to decode the receiver/amount from the call data. That caused crashes or wrong history entries for common calls such as token approvals, deposits, or swaps. The patch now checks whether the call data really is a standard TRC20 transfer, falls back to showing the TRX value for other contract calls, adds timeouts and error handling around TronGrid history requests, and caches token metadata so the wallet does not hammer the RPC provider. Other changes are minor: a Bitcoin balance type refactor, re-enabling Decred wallets, disabling one exchange provider, and build-number bumps.
Security candidateCW-1513/CW-1610: Add account archival and UI improvements (#3600)by Patrick · 20f1ceb6 · Oct 10, 2026 · 108 filesMessage 100 · StrongInformational 18Details
Commit message · Patrick
CW-1513/CW-1610: Add account archival and UI improvements (#3600)
* add ability to hide accounts
* remove import
* merge
* merge
* fix loading accounts when styleSettings are not saved yet
* merge
* auto-reformat
* small fixes
* proper reload on card unhide
* block hiding last card
* fixup
* revert formatting-only changes
* liner fixes
* fix overflows
* card layout as separate class to prevent index errors
* fix mini card on addresses page
* block opening customizers if wallet is syncing
* switch to BlocProvider.value to prevent auto dispose
* pass account balances as Money and format at display
* use fresh full balance for account archival check
* refactor BalanceCard w/ MoneyText + cleanup
* minor card_customizer cleanup
* rework card customizer flow
---------
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com> Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
memory safetyfuzzing or regression evidencesigning or wallet path
AI analysis · Informational 18/100
This commit is a large feature update for the Cake Wallet app that adds the ability to hide (archive) cryptocurrency accounts, customize account cards, and reorganize wallet settings. It is primarily a user-interface and data-management change. There is no direct evidence in the commit that it fixes a security vulnerability; it looks like a normal product feature release.
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.
Security candidatechore: add new images for robinhood (#3689)by David Adegoke · 098e1ea0 · Oct 7, 2026 · 2 filesMessage 90 · StrongInformational 15Details
Commit message · David Adegoke
chore: add new images for robinhood (#3689)
* fix: add new images and fix integration tests
* fix: round robinhood network icon and align card background.
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit only replaces two Robinhood-themed image files (SVG graphics) with updated versions. It changes the visual design, dimensions, and colors of icons and a card background. There is no code change, no executable logic, and no security-relevant behavior.
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.
Security candidatefix: add new images and fix integration tests (#3679)by David Adegoke · ad93901a · Oct 5, 2026 · 17 filesMessage 80 · StrongInformational 15Details
Commit message · David Adegoke
fix: add new images and fix integration tests (#3679)
80/100 · StrongMessage clarity
✓ Specific, 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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a routine product update for the Cake Wallet app. It swaps in new Robinhood-themed icons and card backgrounds, adjusts a color gradient, adds Robinhood to integration-test wallet lists, fixes a QR-code image reference to point at the new Robinhood QR asset, and tweaks how stablecoins are filtered in the currency picker. There is no code change that introduces a security vulnerability.
Security candidateAdd Robinhood Chain (#3398)by David Adegoke · 046e57c5 · Oct 4, 2026 · 143 filesMessage 76 · AdequateLow 35Details
Commit message · David Adegoke
Add Robinhood Chain (#3398)
* fix android CI
* feat: Add Robinhood Chain, all major flows done. minor issue now is our providers don't support it yet as its still pretty early, two weeks from launch
* feat: Add Robinhood Chain, all major flows done. minor issue now is our providers don't support it yet as its still pretty early, two weeks from launch
* Cleanup
* auto-reformat
* fix ui issue and contact listing for tokens
* fix: missing icons and crash for fee priority in settings
* chore: cleanup
* fixes from feedbacks
* fix: review issues and sync to latest dev feat: switch history api to etherscan, add history toggle to privacy settings, exclude robETH from exchange pickers, skip tokens discovery for chains that moralis hasn't indexed, add tests
* fix: address Robinhood review comments
* fix: show Solana token icons in history
* fix: address review comments and default Robinhood to PublicNode
* fix: revert filter and refuse unmapped networks in provider
---------
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com>
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet path
AI analysis · Low 35/100
This commit adds support for a new blockchain, "Robinhood Chain" (chain ID 4663), to the Cake Wallet app. It is a large feature patch that wires the new chain into wallet creation, sending, receiving, exchange providers, transaction history, settings, and UI assets. There is no direct evidence in the commit of a security vulnerability, but the size and breadth of the change introduce ordinary implementation risks typical of adding a new EVM chain.
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.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlsigning or wallet path
AI analysis · Informational 23/100
This commit prepares Cake Wallet to remove support for Zano and Decred wallets. It adds a new database table to store encrypted seed phrases for wallets that are being deprecated, shows warning popups to users so they back up their seeds, and stops new Zano/Decred wallets from being created. It also fixes a minor cleanup bug where a cached Zano wallet might not be closed before deletion. There is no direct evidence in the commit of an exploitable security vulnerability; the changes are primarily user-facing deprecation and data-preservation work.
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.