CW
← All projectsCake Wallet

Cake Wallet / Monero.com

Noncustodial mobile and desktop wallet code for Cake Wallet and the Monero-only Monero.com wallet.

MoneroPrivacy protocolsSoftware walletsNormal
Repository coverage

917 commits in the local evidence base

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.

152security candidates388second-pass queue540AI analyses
102commits · 30 days
177commits · 60 days
505commits · 180 days
822commits · 365 days
Backfill bands
Sep 27 → Mar 31329 seen44 candidatesComplete
Mar 31 → Jul 29266 seen28 candidatesComplete
Jul 29 → Aug 2891 seen17 candidatesComplete
Aug 28 → Sep 2765 seen18 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

62/100 average clarity
221Strong · 80–100
291Adequate · 60–79
256Thin · 40–59
149Opaque · 0–39
5security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
cyan781038268
David Adegoke1112774178
Omar Hatem751353171
malik1004x1522170065
Konstantin Ullrich631640076
Seth For Privacy431424084
Blazebrain191012058
tuxsudo23714058
Omar65649035
Serhii49619067
Robert Malikowski73555029
claude[bot]2158078
Analysis record

Published AI watches

Last scanned 25 minutes ago

Informational 23 AI analysisMessage 35 · Opaque
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

fix litecoin renaming issue

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
e45d45b1by Omar+12−11 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

ci: build iOS on the Mac Studio runners (canary), Xcode 27 (#3872)

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…

1ab697f6by Seth For Privacy+22−21 file
No security note in commit
Informational 17 AI analysisMessage 18 · Opaque
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

miscellaneous

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
ee39fd83by Omar+76−184 files
No security note in commit
Low 39 AI analysisMessage 100 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Fix screen-reader gaps that block accessibility-tree automation (#3693)

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
be835c03by Seth For Privacy+2128−2260 files
Vendor flagged security relevance
Low 27 AI analysisMessage 100 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

QA: report-only e2e lanes (android / iOS / cache nightly) (#3700)

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
12f17920by Seth For Privacy+801−04 files
No security note in commit
Low 30 AI analysisMessage 100 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Add TestId helper, identifier plumbing for shared widgets, and test-key lints (#3690)

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
e5505f89by Seth For Privacy+2086−630164 files
Vendor flagged security relevance
Low 48 AI analysisMessage 100 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Refactor swap logic and state management (#3472)

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)
d62183e3by malik1004x+26666−15194257 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

CW-1681-4-Bitcoin-Accounts-code-enhancements-lightning-deposit (#3825)

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
30658bb3by Serhii+14−145 files
No security note in commit
Low 32 AI analysisMessage 81 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Cw 1681 bitcoin accounts code enhancements (#3728)

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
2388fd70by Serhii+500−37317 files
No security note in commit
Informational 15 AI analysisMessage 81 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Remove unused Android MainActivity and Application copies (#3849)

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…

06f6e5bfby Omar Hatem+0−1874 files
No security note in commit
Informational 22 AI analysisMessage 96 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

i18n: fit the long Tamil strings on the new UI (#3878)

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…

8c3365fdby Seth For Privacy+232−1446 files
No security note in commit
Informational 20 AI analysisMessage 100 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

i18n: add Bengali, Marathi, Tamil, Telugu and repair Hindi (#3859)

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
87a71a84by Seth For Privacy+9719−10618 files
No security note in commit
Informational 20 AI analysisMessage 86 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Add "More Actions" UI (#3667)

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
3cd46aaeby malik1004x+1765−60831 files
No security note in commit
Informational 15 AI analysisMessage 81 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

a11y: Wallets tab screen-reader fixes (edit labels, coin names, single rows, current wallet) (#3752)

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…

0b121b07by Seth For Privacy+53−116 files
No security note in commit
Informational 19 AI analysisMessage 96 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

a11y: name settings switches by their row title and expose selected state on Fiat API choices (#3808)

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…

b4192b14by Seth For Privacy+198−125 files
No security note in commit
Informational 18 AI analysisMessage 18 · Opaque
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

miscellaneous

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
613ced85by Omar+14−1106 files
No security note in commit
Informational 15 AI analysisMessage 76 · Adequate
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

v6.5.4 Release candidate (#3851)

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…

1c80aca3by Omar Hatem+120−9539 files
No security note in commit
Moderate 51 AI analysisMessage 50 · Thin
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

- Fix signing messages to include change addresses as well

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
40ffab7dby Omar+260−1368 files
No security note in commit
Moderate 60 AI analysisMessage 98 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

fix: refuse Bitcoin message signing for an address the wallet cannot derive (#3826)

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
a2e88dadby Omid+72−43 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 81 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

[ui perf] pause animations in hidden dashboard tabs (#3806)

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…

95b8b05aby malik1004x+8−33 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedbump: torch_dart (#3542)by cyan · e9dec675 · Aug 20, 2026 · 1 fileMessage 36 · OpaqueLow 25Details
Commit message · cyan

bump: torch_dart (#3542)

36/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100

This commit updates a script that downloads a third-party software package called torch_dart used by the Cake Wallet app. It changes the expected fingerprint (a Git commit hash) of the package from one value to another. On its own, this is a routine dependency bump, but because the commit message only says 'bump' and gives no details about what changed in torch_dart, we cannot tell from this diff alone whether the new version fixes a security issue, introduces one, or is benign. The change is not suspicious by itself, but it is also not verifiable as safe without inspecting the upstream torch_dart repository.

Security candidateCW1612: AnyPay Service Layer (#3516)by David Adegoke · 3b100eae · Aug 20, 2026 · 67 filesMessage 76 · AdequateLow 38Details
Commit message · David Adegoke

CW1612: AnyPay Service Layer (#3516)

* fix android CI

* feat: add anypay core models, parser and routing engine

* feat: add anypay resolver, anypay service and wallet switch service

* refactor: route the send page payment flow through anypay service

* fix: show message when there's no swap providers for a pair and reset the trade guard on dismissal

* refactor: merge the swap from network and send to network decision pages together and clean up anypay widgets

* feat: reapply deep links to a currently open send flow and register the solana scheme

* feat: add support for zcash address detection to anypay and other minor fixes

* refactor: remove trailing icon

* feat: hide swap flow for sp and mweb addresses

* feat: enhance zcash address detection and deeplink handling

* fix: pin bitcoin_base

* refactor: Move the anypay decision navigation out of the send page and address minor review comments

* refactor: Move the anypay decision navigation out of the send page and address minor review comments

* feat: handle exception in switch service and mvoe balance compute to call site

* refactor: combine anypay entry points to one and extract selected mode widget

---------

Co-authored-by: Czarek Nakamoto <cyjan@mrcyjanek.net>

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlcryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Low 38/100

This is a large feature commit that introduces a new 'AnyPay' service layer for routing cryptocurrency payments and swaps inside Cake Wallet. It refactors how the app parses payment requests, detects recipient networks, switches wallets, and handles deep links. The changes are mostly architectural and user-facing, but because they touch sensitive flows such as wallet switching, address parsing, and cross-chain swaps, they could introduce security bugs if the new routing logic makes incorrect decisions. The commit does not appear to be a disclosed security fix, and no CVE or vendor security statement is present.

AI review queuedMigrate EVM/Sol/TRX tokens to SQL (#3450)by David Adegoke · 4cc14956 · Aug 20, 2026 · 23 filesMessage 76 · AdequateLow 27Details
Commit message · David Adegoke

Migrate EVM/Sol/TRX tokens to SQL (#3450)

* fix android CI

* feat: Migrate EVM, Sol and Tron tokens to SQL

* handle rename edgecase

* refactor: enhance token migration logic and improve database handling

76/100 · AdequateMessage clarity
✓ 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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 27/100

This commit replaces the way Cake Wallet stores EVM, Solana, and Tron token lists: it moves them from Hive (a local key-value store) into SQLite (a local SQL database). It also adds migration code that copies existing token data from the old Hive boxes into the new SQLite tables when the app starts or restores a backup. The change is a large data-layer refactor, not a clear security fix or vulnerability. There are some migration edge cases (duplicate wallet names, interrupted migrations, case-insensitive EVM contract addresses) that are explicitly handled and tested.

AI review queuedfix: move `updateBleState` to connection page initialization (#3539)by Konstantin Ullrich · 86906a7f · Aug 19, 2026 · 3 filesMessage 70 · AdequateInformational 16Details
Commit message · Konstantin Ullrich

fix: move `updateBleState` to connection page initialization (#3539)

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 16/100

This commit moves a Bluetooth status check so it runs when the device-connection screen first appears, rather than when the wallet view model is first created. It appears to be a timing or state-refresh bug fix for hardware wallet pairing, not a security vulnerability. There is no evidence in the commit of malicious behavior, exploitation, or a disclosed security issue.

Security candidatePrivacy: randomized coin selection (BnB changeless + single random draw) (#3408)by Cindy · 3b098e35 · Aug 19, 2026 · 5 filesMessage 100 · StrongLow 38Details
Commit message · Cindy

Privacy: randomized coin selection (BnB changeless + single random draw) (#3408)

* Randomize coin selection with single random draw

The greedy selection walked the unspent pool in a predictable order (address generation order, then per-address server order), a fingerprint an analyst can exploit. Shuffle the pool before the accumulate-until-covered loop so the input set is chosen non-deterministically (single random draw). MWEB coins are still kept last.

Branch-and-bound (changeless exact match) is a larger follow-up.

* Add BnB + SRD coin selection primitives

Pure, wallet-independent coin selector: branch-and-bound for an exact
changeless match within the cost-of-change window, single-random-draw
fallback (shuffled, injectable RNG) when no exact match exists, and
selectCoins tying them together over effective values.

This is the basis for replacing the greedy accumulation in _createUTXOS
so sends produce no change when possible and a non-deterministic
selection otherwise. Validated with dart test (9 cases); wiring into
_createUTXOS is a separate step.

* Use BnB changeless matching in coin selection

Before the shuffled greedy walk, run branch-and-bound over effective
values (value minus per-input fee cost) looking for an input set whose
excess over amount plus fee stays below dust. When found, order those
inputs first and cap the walk at their count: the caller then computes
a change below dust, drops the change output, and absorbs the residue
into the fee, producing a changeless transaction with no residual
change fingerprint.

When no match exists, selection falls back to the shuffled pool, which
the greedy walk turns into a single random draw. BnB is skipped for
sendAll, forced input counts and pools holding MWEB coins.

changelessMatch filters non-positive effective values and maps indices
back to the original pool.

* Cover changeless fee bounds and BnB termination

Assert the end-to-end arithmetic the wallet performs around a
branch-and-bound match: with the 68/34/10 vBytes model, the leftover
the caller absorbs into the fee is never negative (no re-selection
loop) and never exceeds the dust limit (bounded fee overpay).

Also pin termination: a large pool with no possible match returns null
through the maxTries cap instead of exploring the full search tree.

* Use a secure RNG for coin selection randomness

The selection shuffle and the single-random-draw fallback exist to be
unpredictable, so seed them from Random.secure() instead of the default
PRNG, matching what Core and bdk use for coin selection. Pool sizes are
small, so the cost is negligible. Tests keep injecting a seeded Random
for determinism.

* Randomize RBF and payjoin input candidate order

Two secondary paths still consumed unspentCoins in wallet scan order
(address generation order, then per-address age), the same predictable
order removed from the main selection path:

- replaceByFee walked the unused-UTXO list in scan order when the fee
bump needed extra inputs
- the payjoin receiver handed input candidates to the payjoin library
in scan order, letting ties inside its selection mirror that order

Shuffle both with a secure RNG so no input-selection path exposes the
wallet's address or coin age ordering.

* ci: skip Linux PR build on forks (no secrets access)

* Account for script-type sizes in changeless matching

* Keep coin selection order stable within a transaction build

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✓ Names security-relevant behavior explicitly
Why it was queued
explicit security languageentropy or randomnesssigning boundaryaccess controldefensive validationsigning or wallet path
AI analysis · Low 38/100

This commit improves Bitcoin/Litecoin privacy in Cake Wallet by making coin selection less predictable. Previously, the wallet chose coins in a fixed order (based on address creation and age), which outside observers could use to fingerprint the wallet or trace its funds. The patch shuffles candidate coins using a secure random source, tries to build changeless transactions when possible, and also randomizes coin order in RBF fee-bump and PayJoin flows. It also adds a CI guard to skip Linux builds on fork pull requests because secrets are unavailable there.

Security candidateSet anti-fee-sniping locktime (exact-tip) on bitcoin sends (#3385)by Cindy · ca00370c · Aug 19, 2026 · 5 filesMessage 81 · StrongLow 30Details
Commit message · Cindy

Set anti-fee-sniping locktime (exact-tip) on bitcoin sends (#3385)

* Set anti-fee-sniping locktime on bitcoin sends

Current tip (exact-tip) via shared helper, wired into normal sends (path A) and payjoin/PSBT (path B). 0 when unsynced. Converges with the exact-tip cluster (payjoin-cli, ldk-node, Bull Bitcoin) and skips the ~10% backdate.

* Update cw_bitcoin/lib/locktime.dart

Co-authored-by: Konstantin Ullrich <konstantinullrich12@gmail.com>

* Update cw_bitcoin/lib/locktime.dart

Co-authored-by: Konstantin Ullrich <konstantinullrich12@gmail.com>

* Update cw_bitcoin/lib/locktime.dart [skip ci]

---------

Co-authored-by: Konstantin Ullrich <konstantinullrich12@gmail.com>
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.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 boundarysigning or wallet path
AI analysis · Low 30/100

This commit changes how Cake Wallet sets the 'locktime' field on outgoing Bitcoin transactions. Previously, Cake Wallet apparently left this value at zero, which made its transactions stand out and easier to track. Now it sets the locktime to the current blockchain height when the wallet is synced, matching common behavior used by other Bitcoin wallets. This is a privacy improvement, not a fix for a vulnerability that lets someone steal funds directly.

Security candidatefeat: pin all dependencies to git sources (#3381)by cyan · be694edc · Aug 18, 2026 · 64 filesMessage 65 · AdequateLow 27Details
Commit message · cyan

feat: pin all dependencies to git sources (#3381)

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
access controlsigning or wallet path
AI analysis · Low 27/100

This commit changes how the Cake Wallet app manages its software building blocks (Dart/Flutter dependencies). It removes many per-package lock files, pins more dependencies to specific Git commit hashes instead of branch names, adds shared override files, and updates CI build scripts. The main security angle is supply-chain hardening: pinning to exact Git commits makes it harder for an attacker to silently swap in a malicious version of a library. However, the commit is a broad refactor, and the diff does not show a specific vulnerability being fixed or any malicious code being introduced. It is best treated as a defensive hygiene improvement.

AI review queuedrefactor: remove `toDouble` method and reverted other changes (#3531)by Konstantin Ullrich · 1f0f51fe · Aug 18, 2026 · 4 filesMessage 70 · AdequateLow 34Details
Commit message · Konstantin Ullrich

refactor: remove `toDouble` method and reverted other changes (#3531)

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 · Low 34/100

This commit removes a shortcut method that converted cryptocurrency amounts directly into regular 'double' numbers and reverts some earlier helper-function changes. It also fixes one spot where Solana transactions were looking up the wrong asset type. The overall effect is to make amount formatting and parsing go through string-based conversions again, which reduces the risk of tiny rounding errors or precision loss when handling very small crypto balances.

AI review queuedfix: sanitize Electrum fee estimates (#3499)by Seth For Privacy · 86db8991 · Aug 16, 2026 · 2 filesMessage 98 · StrongModerate 59Details
Commit message · Seth For Privacy

fix: sanitize Electrum fee estimates (#3499)

* fix: sanitize Electrum fee estimates

* chore: drop test changes from this PR

Removes the test additions/modifications introduced by this branch so the
test design is left to the maintainers. Production code is unchanged.

98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This commit hardens how Cake Wallet handles Bitcoin fee estimates from Electrum servers. Previously, a malicious or misbehaving Electrum server could return extreme or negative fee numbers, which could lead to users paying far too much, far too little, or creating invalid transactions. The patch now clamps fee rates between 0 and 2000 sat/vB, rejects all-zero fee lists, and refuses to build transactions when the computed fee is zero or negative. Most of the rest of the diff is just code formatting cleanup.

AI review queuedfix: validate EVM restore mnemonic checksum (#3498)by Seth For Privacy · 8a366129 · Aug 16, 2026 · 3 filesMessage 100 · StrongModerate 62Details
Commit message · Seth For Privacy

fix: validate EVM restore mnemonic checksum (#3498)

* fix: validate EVM restore mnemonics

* chore: drop test changes from this PR

Removes the test additions/modifications introduced by this branch so the
test design is left to the maintainers. Production code is unchanged.

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 62/100

This commit adds a missing safety check when users restore an Ethereum-compatible (EVM) wallet from a seed phrase. Before the fix, the app accepted any 12 or 24 words that looked like a mnemonic, even if the words were wrong or the checksum was invalid. That could let a user create a wallet from a typo-ridden seed and later be unable to access their funds. The fix validates the seed phrase's checksum before restoring, and shows a clear error if it is invalid.

AI review queuedmove chain iconby Robert Malikowski · 694b8eaf · Aug 12, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Robert Malikowski

move chain icon

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit slightly increases the size of a small UI box that displays a token icon together with a tiny chain/network badge. It is a visual layout tweak with no security relevance.

Security candidatev6.4.1 Release Candidate (#3506)by Omar Hatem · 8f38ba6b · Aug 12, 2026 · 39 filesMessage 81 · StrongInformational 15Details
Commit message · Omar Hatem

v6.4.1 Release Candidate (#3506)

* v6.4.1 Release Candidate

* fix changelog overflow (#3510)

* update ios min version

---------

Co-authored-by: malik1004x <malikowskirobert@gmail.com>

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Informational 15/100

This commit is a routine version bump to 6.4.1 plus a small user-interface fix for a changelog text overflow and an iOS minimum version update. It also refreshes translated release notes and updates a dependency reference for the Trezor hardware wallet integration. There is no indication of a security fix or vulnerability being addressed.

AI review queued"synced" indicator (#3512)by malik1004x · 3a71f6ad · Aug 11, 2026 · 34 filesMessage 43 · ThinInformational 18Details
Commit message · malik1004x

"synced" indicator (#3512)

* "synced" indicator

* safeguards

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 18/100

This commit is a user-interface change that adds a brief 'Synced' indicator when a wallet finishes synchronizing. It does not change how funds, keys, or network connections are handled, and it does not fix or introduce any security issue visible in the diff.

AI review queuedadd new currency selectionby Robert Malikowski · a6abf1bf · Aug 11, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Robert Malikowski

add new currency selection

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 is a routine user-interface update for Cake Wallet's buy/sell flow. It adds a new fiat-currency picker and a small widget that shows a token icon with its chain/network badge. There is nothing in the changes that suggests a security vulnerability or fix.

AI review queuedadd emojis to FiatCurrencyby Robert Malikowski · 1cf97874 · Aug 11, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Robert Malikowski

add emojis to FiatCurrency

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 is a straightforward user-interface enhancement: it adds country-flag emoji icons next to fiat currency entries in the Cake Wallet app. There is no security-relevant change—no new network calls, no altered permissions, no cryptographic changes, and no data handling modifications.

AI review queuedadd if(mounted) guardsby Robert Malikowski · 399dabe1 · Aug 11, 2026 · 1 fileMessage 28 · OpaqueInformational 18Details
Commit message · Robert Malikowski

add if(mounted) guards

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100

This commit adds safety checks in a buy/sell screen so the app doesn't try to show pop-ups or navigate after the user has already left the page. It also adds a screen-reader label to the close button and reformats some code. There is no clear security vulnerability being fixed.

AI review queuedfix: sorting of transactions (#3494)by cyan · 19653afe · Aug 11, 2026 · 3 filesMessage 88 · StrongInformational 23Details
Commit message · cyan

fix: sorting of transactions (#3494)

* fix: zcash address for exchange

* fix: honour the restore height the user entered

- Make Zcash rescan work in both directions by resetting sync from the new birth height
- Keep the entered height when restoring a wallet from keys
- Tolerate grouping separators in typed restore heights

* fix: sorting of transactions
fix: tx fee for outgoing transactions

---------

Co-authored-by: Vik Sharma <vik@cakewallet.com>
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>

88/100 · StrongMessage clarity
✓ 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 23/100

This update fixes how Cake Wallet displays Zcash transactions. Previously, outgoing transaction fees were shown as zero and transaction timestamps could be wrong or missing. The patch makes fees show the real network fee and improves date/time handling for transactions. There is no direct evidence in the commit of a security vulnerability being exploited, but incorrect fee and time data could mislead users or cause accounting problems.

AI review queuedfix: zcash address for exchange (#3491)by cyan · 3b16f2fb · Aug 11, 2026 · 5 filesMessage 88 · StrongLow 42Details
Commit message · cyan

fix: zcash address for exchange (#3491)

* fix: zcash address for exchange

* fix: honour the restore height the user entered

- Make Zcash rescan work in both directions by resetting sync from the new birth height
- Keep the entered height when restoring a wallet from keys
- Tolerate grouping separators in typed restore heights

---------

Co-authored-by: Vik Sharma <vik@cakewallet.com>

88/100 · StrongMessage clarity
✓ 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 42/100

This commit fixes two user-facing bugs in Cake Wallet's Zcash handling. First, it ensures the correct transparent Zcash address is used when sending funds to an exchange, which could previously lead to deposits going to the wrong address type. Second, it makes wallet restore respect the block height the user typed in, and allows that height to contain grouping separators like commas. The changes are bug fixes rather than a disclosed security vulnerability, but the wrong-address issue has clear financial-impact potential.

AI review queuedGive ConfirmSwiper an accessible-navigation button fallback (#3464)by Seth For Privacy · 8ed08fb1 · Aug 11, 2026 · 5 filesMessage 58 · ThinInformational 21Details
Commit message · Seth For Privacy

Give ConfirmSwiper an accessible-navigation button fallback (#3464)

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 21/100

This commit improves accessibility for users who rely on screen readers (VoiceOver on iOS, TalkBack on Android). The app's 'swipe to confirm' control did not work well with screen readers because they intercept swipe gestures. The change adds a plain button fallback when a screen reader is active, so blind or low-vision users can still confirm transactions and approvals. It is an accessibility/usability fix, not a security vulnerability fix.

AI review queuedCW-1523-AnyPay Redesign (#3383)by David Adegoke · 90194f71 · Aug 11, 2026 · 69 filesMessage 98 · StrongLow 34Details
Commit message · David Adegoke

CW-1523-AnyPay Redesign (#3383)

* feat: Add network selector and compatible networks screen to send page for EVMs

* feat: add redesigned payanything flow and handle cases for evms, solana and tron

* feat: adding the swap part to the entire flow

* refactor: update navigation and error handling in send and swap flows

* adjust structuring and use the chain badge icons, also fix crypto and currency values not consistent on single network picker

* fix: modify guard for non-evm chains and minor cleanup

* use multipicker layout for receive section, streamline send to available balances and adjust colors as needed

* handle btc case for picker, update style and images across

* fix all pending issues with scanning qr and network handling for both evm and non evm, plus token and amount resolving

* fix all pending issues with scanning qr and network handling for both evm and non evm, plus token and amount resolving

* fix: expand fetch for tokens across networks and fix other issues regarding scanning from homepage

* auto-reformat

* fix conflict

* handle evm qr scan from homepage and add guards for swap and switch flows

* chore: Cleanup

* chore: set estimated fee to 0 when switching wallet

* fix merge conflicts

* fix to review comments and reformatting for lints

* fix: root cause for token bug reported

* chore: cleanup

* feat: add improved anypay swap screen which focuses on the receive amount
fix: fiat input toggle erro (also present on prod)
reformat: anypay related widgets

* feat: add alert for unsupported networks in payment requests

* fix: prevent rate and provider from showing until amount is calculated and loaded
fix: remove send icon in rate widget and align to center
fix: adjust network badge in swap confirm widget

* feat: embed tokens for solana and tron in QR generated for swap from external

* test: add unit tests for Tron, Solana, and ERC681 URI handling and detection

* fix: review comments

* fix: handle more edgecases

* feat: enhance ERC681URI to support raw token amounts and decimals

* refactor: streamline EVM chain ID retrieval in send page and recipient network row

* fix: minor review comments

---------

Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com>

98/100 · StrongMessage clarity
✓ 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
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 34/100

This is a large user-interface redesign for Cake Wallet's 'AnyPay' payment flow. It changes how the app parses payment QR codes and links for Ethereum, Solana, and Tron, adds network selection, and integrates swaps when the scanned payment is on a different network than the current wallet. The commit also fixes several amount-formatting bugs for tokens that do not use 18 decimal places, which could previously cause wrong payment amounts to be sent.

AI review queuedguard regeneration of lightning addressby Omar · 931b6fb9 · Aug 9, 2026 · 4 filesMessage 45 · ThinLow 37Details
Commit message · Omar

guard regeneration of lightning address

45/100 · ThinMessage clarity
✓ 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 37/100

This commit prevents users from rotating (regenerating) a Bitcoin Lightning address in the Cake Wallet app. Previously, the app may have allowed address regeneration for Lightning addresses, which could cause confusion, lost incoming payments, or funds sent to an old/unexpected address. The fix adds a guard that throws an error if code tries to rotate a Lightning address, and updates the UI logic to recognize when a Lightning address type is selected.

Security candidatefeat: show Bitcoin master fingerprint in wallet keys (#3489)by Seth For Privacy · b60b5a59 · Aug 7, 2026 · 4 filesMessage 98 · StrongInformational 15Details
Commit message · Seth For Privacy

feat: show Bitcoin master fingerprint in wallet keys (#3489)

* feat: show Bitcoin master fingerprint in wallet keys

Add the BIP-32 master fingerprint (XFP) to the Bitcoin wallet keys shown
under Settings > Seed & Keys > Keys, labeled "Master fingerprint".

* fix: keep xPub in Keys tab by splitting silent payment keys into a dedicated list

The Keys tab / Silent Payments tab split relied on a hardcoded item index
(`items.sublist(0, 4)` / `sublist(4)`) that assumed the first four items
were always WIF/private key/public key/xPub. Adding the master fingerprint
as the first item pushed xPub into the Silent Payments tab.

Route Bitcoin silent payment keys into their own `silentPaymentItems` list
instead, and render each tab from its list.

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
secret or key materialsigning or wallet path
AI analysis · Informational 15/100

This commit is a user-facing feature, not a security fix. It adds a new 'Master fingerprint' value to the Bitcoin wallet keys screen and fixes a small UI bug where adding that new item accidentally moved another key (xPub) into the wrong tab. There is no indication of a vulnerability being patched.

AI review queued26-08-07_Update Translation_de_DEby bsn21m · 6728f75b · Aug 7, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · bsn21m

26-08-07_Update Translation_de_DE

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 updates German translation strings in a single language file. It removes a few duplicate entries, fixes typos, rewords some user-facing messages, and adds new German translations for recently introduced app features. There are no code or security changes.

AI review queuedfix: display proper address in zcash transactions (#3457)by cyan · c93843f3 · Aug 7, 2026 · 2 filesMessage 70 · AdequateInformational 22Details
Commit message · cyan

fix: display proper address in zcash transactions (#3457)

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 22/100

This commit fixes how Zcash wallet transactions display recipient addresses. Previously, the app could misidentify which addresses belong to the user's own wallet, causing it to show the wrong address (or even the user's own address) as the destination for a payment. The fix builds a single, authoritative list of addresses the wallet actually owns and uses that to decide which outputs are real external payments. There is no direct evidence this is a security vulnerability that can be exploited by an attacker; it appears to be a UI correctness bug that could confuse users or make transaction records less trustworthy.

AI review queuedAdd tbb to solana default tokens (#3461)by David Adegoke · 14d2862b · Aug 6, 2026 · 41 filesMessage 86 · StrongLow 28Details
Commit message · David Adegoke

Add tbb to solana default tokens (#3461)

* fix android CI

* deat: add The Bitcoin Bull to solana default tokens list

* add verification status for solana tokens

86/100 · StrongMessage clarity
✓ Descriptive subject✓ 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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 28/100

This commit adds a new Solana token called 'The Bitcoin Bull' (TBB) to Cake Wallet's default token list and introduces a Jupiter verification check to help flag potentially scam tokens. It also includes many unrelated translation string updates. The main security-relevant change is the new Jupiter verification lookup, which makes the wallet trust tokens verified by Jupiter when users add custom Solana tokens. There is no direct evidence of a vulnerability being fixed or introduced, but the change alters how the app decides whether a token is trustworthy.