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

916 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
101commits · 30 days
176commits · 60 days
504commits · 180 days
821commits · 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
220Strong · 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 Privacy421424085
Blazebrain191012058
tuxsudo23714058
Omar65649035
Serhii49619067
Robert Malikowski73555029
claude[bot]2158078
Analysis record

Published AI watches

Last scanned 47 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 queuedupdate app versionby Omar · bedf18df · Nov 1, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Omar

update app version

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 only bumps the app's version numbers and build numbers, plus makes two minor formatting-only changes to a Dart money-handling class. There is no security-relevant change.

Security candidatechore: fix type casting and safety across multiple coin packages (#3791)by Omar Hatem · 89f5de4b · Oct 30, 2026 · 20 filesMessage 93 · StrongLow 47Details
Commit message · Omar Hatem

chore: fix type casting and safety across multiple coin packages (#3791)

* chore: fix type casting and safety across multiple coin packages

* **cw_decred**: Add explicit type casts for JSON decoding in wallet and address management, including transaction history, unspents, and sync status. Fix `amount` and `fee` decoding to handle `num` values from Go.
* **cw_evm**: Apply type safety to Trezor transaction credential parsing and Etherscan API response handling. Fix potential crashes in transaction merging and spam filtering.
* **cw_solana**: Add explicit casts for RPC response data, transaction signatures, and SPL token metadata.
* **cw_tron**: Ensure proper type casting for transaction info, balances, and TRC20 transaction models.
* **cw_zcash**: Fix `crc32` byte validation and add explicit casts to `YwalletAccountInfo` migration logic.
* **cw_wownero**: Explicitly type `newWptr` as `wownero.wallet`.
* **cw_monero**: Cast serialized wallet cache to `Map<String, dynamic>`.

* Update cw_decred/lib/api/libdcrwallet.dart

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

---------

Co-authored-by: malik1004x <malikowskirobert@gmail.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 boundarycredential or privilege statesigning or wallet path
AI analysis · Low 47/100

This commit is a broad cleanup across multiple cryptocurrency wallet packages that adds explicit type casts when handling JSON and binary data. The changes mostly prevent runtime crashes caused by unexpected data types (for example, a number arriving as an integer instead of a decimal, or a string where a list was expected). In a few places, the casts also make the code safer when parsing values that could be attacker-influenced, such as Etherscan API responses or Trezor hardware-wallet transaction data. The patch is defensive and does not appear to introduce new vulnerabilities, but it is also partial: it fixes many symptoms without addressing the underlying lack of structured validation, so some edge cases may still crash or behave incorrectly.

Security candidateSummary of changes:by Omar · ec61b405 · Oct 30, 2026 · 8 filesMessage 61 · AdequateLow 26Details
Commit message · Omar

Summary of changes:

* **Tests**:
* Added `proxy_wrapper_prefer_ipv6_test.dart` to verify IPv6 connection handling and fallback logic in `ProxyWrapper`.
* Added `auth_pin_unreadable_test.dart` to test `AuthService` behavior and error states when PIN codes are unreadable from secure storage.
* Renamed `crypto_amount_format.dart` to `crypto_amount_format_test.dart`.
* **iOS/macOS Configuration**:
* Bumped app versions and build numbers in `scripts/ios/app_env.sh` (Monero.com to 6.5.2, Cake Wallet to 6.5.2).
* Increased the `MACOSX_DEPLOYMENT_TARGET` from 12.0 to 13.0 in the macOS `Podfile`.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
access controlcryptography-sensitive pathauthentication path
AI analysis · Low 26/100

This commit is mostly a routine test-and-version update. It adds tests for network IPv6 fallback and for PIN-unreadable error handling, bumps app versions, raises the minimum macOS version, and switches two dependencies from local paths to Git references. The only functional code change is a single commented-out error-reporting line in the authentication view model, which stops sending a crash report when the device's stored PIN cannot be read. There is no direct evidence in the commit that this fixes an active security vulnerability.

AI review queuedminor [skip ci]by Omar · 02252601 · Oct 28, 2026 · 1 fileMessage 28 · OpaqueInformational 23Details
Commit message · Omar

minor [skip ci]

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 23/100

This commit adds a try/catch around a balance lookup for Ethereum-based tokens. If the network call fails, the wallet now silently records a zero balance instead of crashing or showing an error. On its own this looks like a stability improvement, but it could hide real balances if a node or network problem makes the lookup fail.

AI review queueddon't run Zcash address init twice when opening a wallet (#3784)by malik1004x · 72498e87 · Oct 28, 2026 · 1 fileMessage 81 · StrongInformational 20Details
Commit message · malik1004x

don't run Zcash address init twice when opening a wallet (#3784)

The ZcashWalletAddresses constructor set addressPageType through its setter, which calls init(). ZcashWallet.init() then runs walletAddresses.init() again, so every create/open/restore did the full address init (rotation pool queries plus an address book save, ~1 s on a low-end phone) twice in parallel. Set the backing field in the constructor instead; ZcashWallet.init() always follows and applies the address type.

Co-authored-by: Claude Opus 5.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 20/100

This is a performance fix, not a security fix. When opening or creating a Zcash wallet, the app was accidentally running the same address-setup work twice in parallel. The change makes the wallet do it once, saving about a second on slow phones. There is no indication this caused funds to be lost, stolen, or misdirected.

AI review queueddon't wait for SharedPreferences writes when switching wallets (#3782)by malik1004x · cf7d8088 · Oct 28, 2026 · 2 filesMessage 81 · StrongInformational 19Details
Commit message · malik1004x

don't wait for SharedPreferences writes when switching wallets (#3782)

On Android the legacy SharedPreferences API commits synchronously to disk, so awaiting the current wallet name/type and the background sync trigger writes added tens of ms to every wallet switch and open. The in-memory cache is updated immediately, so nothing reads stale values.

Co-authored-by: Claude Opus 5.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 19/100

This change makes two SharedPreferences (app settings) writes run in the background instead of waiting for them to finish when switching wallets. The goal is to speed up wallet switching on Android, where these writes were slow. The in-memory values are updated immediately, so the app should not read old data. There is no clear security bug here, but making disk writes asynchronous can slightly raise the risk of data loss or inconsistent state if the app crashes before the write completes.

AI review queued[performance] write wallet addresses to the database in one batch (#3772)by malik1004x · 0568f492 · Oct 28, 2026 · 2 filesMessage 81 · StrongInformational 15Details
Commit message · malik1004x

[performance] write wallet addresses to the database in one batch (#3772)

* batch wallet address book writes

saveAddressesInBox rewrote the address map, address infos and used/hidden/manual lists with one sqflite insert per row, each its own transaction and platform-channel round trip. For a new Bitcoin wallet that's hundreds of round trips (~125 ms on a low-end phone), and it also queued up other DB reads behind it. Each setter now writes through a single batch (one transaction, one round trip), and saveAddressesInBox writes all five in one batch via setAddressBook.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* cleanup

---------

Co-authored-by: Claude Opus 5.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 15/100

This commit is a performance optimization, not a security fix. It changes how a cryptocurrency wallet app saves address book data to its local database so that many records are written in one batch instead of one at a time. This reduces delays, especially when creating a new wallet, but does not change what data is stored or how it is protected.

AI review queueddrop the duplicate default-token pass after EVM wallet init (#3774)by malik1004x · 2527ac60 · Oct 28, 2026 · 1 fileMessage 81 · StrongInformational 19Details
Commit message · malik1004x

drop the duplicate default-token pass after EVM wallet init (#3774)

EVMChainWallet.init() already runs initErc20Tokens() (which calls addInitialTokens()) and then save(), but every create/open/restore path in EVMChainWalletService called addInitialTokens() and save() again right after it, re-writing all default tokens and the wallet file a second time.

Co-authored-by: Claude Opus 5.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 19/100

This commit removes redundant code that was adding default cryptocurrency tokens and saving the wallet file twice whenever an Ethereum-compatible (EVM) wallet was created, opened, or restored. The duplicate work was already being done inside the wallet's initialization routine, so the extra calls were unnecessary. It is a cleanup/refactoring change with no apparent security impact.

Security candidatefix old migration issues (#3761)by Omar Hatem · ca930515 · Oct 28, 2026 · 6 filesMessage 86 · StrongModerate 59Details
Commit message · Omar Hatem

fix old migration issues (#3761)

* fix old migration issues

* fix: trust the wallet file's derivation type before the mnemonic

resolveUnknownDerivation let the mnemonic override a type the wallet file
had explicitly recorded. _validateWalletInfoBoxData re-creates WalletInfo
rows without a derivation on every launch, so an Electrum-stretched wallet
restored from a BIP39 phrase re-opened as bip39 and persisted it.

Precedence is now: the type recorded in the wallet file (electrum/bip39),
then the type the mnemonic proves, then the pre-existing fallback. Files
that predate derivation tracking load as electrum, which every such wallet
used.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* test: cover resolveUnknownDerivation precedence and defaults

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

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
secret or key materialdefensive validationsigning or wallet path
AI analysis · Moderate 59/100

This commit fixes a bug in Cake Wallet where the app could misidentify how a wallet's keys are derived. Specifically, when reopening a wallet, the app sometimes recreated the wallet's metadata row without its saved derivation type, then let the mnemonic phrase override the type that the wallet file had explicitly recorded. That could cause an Electrum-stretched wallet (restored from a BIP39 phrase) to be reopened as a BIP39 wallet and persisted that way, potentially deriving different addresses than before and making existing funds appear missing. The fix gives precedence to the type recorded in the wallet file, then to what the mnemonic proves, then to a safe fallback. It also ensures an empty derivation path is treated as missing rather than as the master key itself.

AI review queuedfix: use derivation indexes, not record counts, for new and discovered addresses (#3762)by Omar Hatem · 53784d2f · Oct 28, 2026 · 3 filesMessage 100 · StrongModerate 64Details
Commit message · Omar Hatem

fix: use derivation indexes, not record counts, for new and discovered addresses (#3762)

* fix: use derivation indexes, not record counts, for new and discovered addresses

New receive/change addresses took their index from the number of records on the
page, and discovery started at the branch length. On BTC P2PKH/P2SH/P2TR pages
the count included legacy-derivation records, so "+" could jump from index 21 to
44 and leave a hole that a restore never scans.

- generateNewAddress / getChangeAddress use the lowest free index on the standard
chain (legacy records count only when they derive the same keys)
- discovery starts after the highest index on the branch, and the gap checks
compare derivation indexes instead of list positions

For branches with no holes (every restore) the numbers are the same as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: cover derivation index helpers

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WdXRtX9wtPwW9gHVi5GZTa

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 64/100

This commit fixes a bug in Cake Wallet's Bitcoin address handling. Previously, the wallet chose new receive/change addresses by counting how many address records existed, rather than by checking the actual derivation index. On some Bitcoin address types (P2PKH, P2SH, P2TR), this count could include legacy-derivation records, causing the wallet to skip ahead and create address 'holes' (for example, jumping from index 21 to 44). A wallet restored from seed would not scan those skipped indexes, so any funds sent to them could appear missing after restore. The fix makes new addresses use the lowest unused derivation index and makes address discovery continue from the highest used index, with added unit tests.

AI review queuedfix: Electrum wallets stuck on Connecting after a failed connect (#3763)by Omar Hatem · 4688efd4 · Oct 28, 2026 · 5 filesMessage 100 · StrongModerate 50Details
Commit message · Omar Hatem

fix: Electrum wallets stuck on Connecting after a failed connect (#3763)

* fix: Electrum wallets stuck on Connecting after a failed connect

One failed connect left BTC/LTC/BCH/DOGE wallets on the Connecting
spinner until the app was restarted, and switching nodes or toggling
Tor did nothing. connect() set `connecting` before its `failed` checks,
so failures were never reported; the wallet's 5 s reconnect only
handles NotConnected/LostConnection; and connectToNode returned early
while Connecting. A stalled TLS or SOCKS handshake had no timeout, so
it never even reached the failure path.

- ElectrumClient.connect always reports `failed`, so the existing
retry takes over. A per-attempt counter, bumped by connect() and
close(), keeps a superseded or closed attempt from installing its
socket, reporting status or flipping useSSL; its late socket is
destroyed.
- ping() no longer reports `connected` when there is no socket
(callWithTimeout returns null instead of throwing), which flipped a
dropped connection back to Connected and stopped the reconnect.
Replies from a replaced socket are ignored.
- A replaced socket's late onDone/onError no longer destroys its
successor.
- ProxySocket.connect bounds the whole connect, SOCKS and TLS
handshakes included: 20 s on clearnet, 60 s over Tor. Sockets that
connect after the deadline are destroyed and a timed-out SOCKS
session is closed. Node reachability checks share this path, so a
hung check now fails at the deadline instead of never finishing.
- connectToNode only skips an exact repeat of the attempt in flight
(same node, same Tor state).
- The app-resume reconnect skips startSync() when the connect failed,
instead of syncing a dead client into a false "Synced".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: re-subscribe addresses after switching Electrum nodes

The previous commit stops an old socket's late close from reporting
"disconnected". That event was what reset the wallet's script-hash
subscription map on a node switch, Tor toggle or app-resume reconnect,
so the new server never got blockchain.scripthash.subscribe and incoming
payments were not pushed. Reset the map wherever the client is closed
for a reconnect.

Also correct two comments, and add tests for each connection case,
run against the real ElectrumClient and ElectrumWallet with local fake
servers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: close failed Tor sessions and stop retries after wallet close

Now that failed connects are retried every 5 s, two leaks that used to
happen once would repeat:

- When Tor answers the SOCKS handshake with a failure, socks_socket
throws without closing its connection to Tor. Close it before
rethrowing.
- The 5 s reconnect timer was never cancelled, so it could reopen the
client of a wallet that had already been closed (e.g. after switching
wallets). Keep it and cancel it in close().

Also test that the app-resume reconnect re-subscribes the addresses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: don't reconnect an Electrum wallet closed mid-sync

Cancelling the retry timer in close() only covered an idle wallet. A
sync still running against the closed client ends in Failed or Lost,
which scheduled a new retry and reopened the client. Mark the wallet
closed and skip scheduling retries for it.

Also fix the resume-path comment: a sync with no socket fails, it does
not end in "Synced" as previously claimed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: ignore late replies on a replaced Electrum socket and reconnects of a closed wallet

Two guards from review, in code the previous commits already touch:

- A replaced socket's data handler gets the same identity check as its
onDone/onError. A clearnet socket still delivers replies after close()
half-closes it, and close() restarts request ids at 0, so a late reply
from the old server could complete a same-id request of the new session.
- connectToNode() and the app-resume reconnect return early on a closed
wallet, before and after the client close they await. The LTC/BCH/DOGE
connectivity check captures the wallet and awaits a node probe before
calling connectToNode(); a wallet switch during that probe closed the
wallet and then reconnected it, leaving a socket and a keep-alive timer
with no owner.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

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
signing or wallet pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Moderate 50/100

This commit fixes a bug in Cake Wallet where Bitcoin-family wallets (BTC, LTC, BCH, DOGE) could get stuck showing 'Connecting' forever after a failed network connection. The root causes were: failed connections were not reported, retries only handled some disconnect cases, and slow or hanging network handshakes had no timeout. The patch makes failures visible, adds timeouts, prevents old/replaced connections from interfering with new ones, and stops closed wallets from reconnecting on their own. It also fixes a related issue where switching servers could stop incoming payment notifications because address subscriptions were not re-sent.

AI review queuedCW-1400-add-zcash-support-to-ledger (#3699)by Konstantin Ullrich · de159ddb · Oct 27, 2026 · 61 filesMessage 76 · AdequateInformational 24Details
Commit message · Konstantin Ullrich

CW-1400-add-zcash-support-to-ledger (#3699)

* feat: add restore Zcash Ledger hardware wallet support

* fix: ZcashHeight.getTimeByBlockHeight with the correctly timestamped checkpoints

* feat: add Ledger Zcash sending support

* feat: refactor zcash autoshield

* feat: add UI for manual shielding support

* refactor: replace Theme-based text styles with explicit TextStyle in Zcash manual shield modal

* feat: Added a reusable `ensureDeviceConnection` method to streamline hardware wallet connection checks across various components. Updated shielding, swapping, and integration flows to utilize this helper, reducing code duplication and improving maintainability.

* fix: resolve parameter formatting in `unconfirmed_balance_widget` and correct conditional usage in `_minSweepThreshold`

* fix: update parameter formatting in `getBirthHeight` and track the last auto-shield timestamp

* fix: pass walletType to `HardwareWalletAccountOptionsPage` and update zkool dependency to latest commit

* fix: only show hardware wallet compatible zcash address types

* fix: track last auto-shield timestamp and adjust sweepable balance display

* Update cw_zcash/lib/src/zcash_wallet.dart

Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>

* Update cw_zcash/lib/src/zcash_wallet.dart

Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>

* refactor: extend ZcashLedgerException from CakeException for consistent error handling

---------

Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>

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: broader security terminologysecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 24/100

This commit adds Zcash support for Ledger hardware wallets in Cake Wallet. It lets users restore a Zcash wallet from a Ledger, sign Zcash sends and shielding transactions on the device, and adds a manual shielding UI because hardware wallets cannot auto-shield. It also refreshes checkpoint timestamps and dependency versions. There is no direct evidence of a security vulnerability in the diff, but it is a large feature change touching sensitive code paths (transaction signing, hardware wallet connection, balance display), so it warrants careful review.

Security candidateImprove wallet open speed (#3719)by malik1004x · e2c55515 · Oct 27, 2026 · 16 filesMessage 78 · AdequateLow 38Details
Commit message · malik1004x

Improve wallet open speed (#3719)

* improve bip39 derivation performance

* improve wallet startup time further

* remove debug prints

* add unit test

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathseed or entropy pathsigning or wallet path
AI analysis · Low 38/100

This commit is a performance improvement that replaces the app's BIP39 mnemonic-to-seed conversion with a new shared helper. The change touches many wallet types (Bitcoin, Litecoin, Ethereum/EVM, Solana, Tron, Monero, Zano) and adjusts how Bitcoin/Litecoin silent-payment keys and HD wallet keys are derived. The new helper is backed by an extensive unit test comparing its output to the previous implementation, which is good. However, because it changes the exact code that turns a recovery phrase into the master secret for many cryptocurrencies, any subtle bug here could affect all funds derived from BIP39 mnemonics across the app. The commit itself does not claim to fix a security issue, and there is no disclosed vulnerability or independent attribution.

Security candidateios ci (#3632)by malik1004x · 9488b544 · Oct 27, 2026 · 20 filesMessage 71 · AdequateInformational 20Details
Commit message · malik1004x

ios ci (#3632)

* [wip] ios ci

* ci

* ci

* add linux runner that puts torch in cache

* bump torch hash

* ci

* sed dark magic to get reown to build

* whoops

* add retries to download_moneroc_prebuilds.dart because github is shit

* ci

* add validation for the provisioning profile so we don't wait an hour every time

* ci

* remove dependence on brew

* ci

* ci

* ci

* add protoc because we need it for building breez sdk

* ci

* ci

* ci

* fix so mweb for ios builds without building for android first + some debug asserts [remove these after ci succeeds]

* fix reown pubspec... again

* ci

* show proper build info in testflight

* remove debugging crap

* ci

* ci

* fix functions.sh in docker

* ci

* screw it we're retrying on every failure

* make app name shorter so it appears fully on large fonts

* add dart defines for ci overlay

* fix mailer

* ci

* disable showing changelog on ci builds

* ci

* update runs-on

* remove container:

* build monero_c in ci

* fix simplybs, apparently?

* push one more commit to see if cache works

* use keychain properly

* make modified ffigen config a temporary file

* ci

* adjust to new github "feature"

* build monero as nonroot

* env

* move signing to separate runner

* pin actions to hash

* ci

* ci

* user key not team key

* ci

* ci

71/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryaccess control
AI analysis · Informational 20/100

This commit is almost entirely about adding and fixing an automated iOS build pipeline (CI) for the Cake Wallet app. It introduces GitHub Actions workflows, Docker images for building native libraries, scripts to sign and upload the app to Apple's TestFlight, and small app tweaks to support CI builds. There is no obvious malicious code, but the CI pipeline handles signing certificates and App Store API keys, so a compromise of the CI system or a pull request from a malicious branch could in theory lead to a tampered app being signed and uploaded. The commit itself does not show such an attack; it is a build-infrastructure change.

AI review queuedAwait Monero wallet close before deleting its files (#3757)by claude[bot] · 162a688d · Oct 25, 2026 · 1 fileMessage 81 · StrongModerate 54Details
Commit message · claude[bot]

Await Monero wallet close before deleting its files (#3757)

The close was fire-and-forget on mobile and stored the cache while the
wallet directory was being deleted, so the delete could fail and leave
the WalletInfo row (and the wallet in its group) without a .keys file.


Claude-Session: https://claude.ai/code/session_01TRAFFJYMG2SKj7U4n9d8ZN

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 54/100

This change fixes a bug in Cake Wallet's Monero wallet deletion. Previously, when a user deleted a wallet, the app started closing the wallet in the background and immediately tried to delete its files. Because the wallet was still writing its cache to disk, the deletion could fail or leave behind a broken wallet record in the app's database. The fix makes the app wait for the wallet to fully close before deleting anything, preventing incomplete deletions and leftover database entries.

AI review queuedadd arbitrum to moonpayby Omar · 98fa3e44 · Oct 25, 2026 · 1 fileMessage 28 · OpaqueInformational 16Details
Commit message · Omar

add arbitrum to moonpay

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

This commit adds support for the Arbitrum network when generating currency identifiers for the MoonPay cryptocurrency purchasing integration. It is a straightforward feature addition with no apparent security implications.

AI review queuedadd extra checks to verify that the returned transaction for an RBF, matches the original oneby Omar · 0fe6dde2 · Oct 25, 2026 · 1 fileMessage 60 · AdequateModerate 61Details
Commit message · Omar

add extra checks to verify that the returned transaction for an RBF, matches the original one

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 61/100

This commit adds safety checks to a Bitcoin wallet feature called Replace-By-Fee (RBF), which lets users resend a transaction with a higher fee if it's stuck. The wallet now verifies that the transaction data returned by the Electrum server actually matches the transaction the user asked to replace, and that each input's previous transaction also matches. Without these checks, a malicious or buggy server could return the wrong transaction data, potentially causing the wallet to build an RBF replacement that spends different coins than intended or reveals private information.

Security candidatefix: restore LNURL.getPayRequestAmount signature (dev compile break) (#3753)by Seth For Privacy · ec6fd6a8 · Oct 23, 2026 · 1 fileMessage 98 · StrongInformational 20Details
Commit message · Seth For Privacy

fix: restore LNURL.getPayRequestAmount signature (dev compile break) (#3753)

2caafc677 dropped the method signature line in cw_core/lib/lnurl.dart,
leaving its body directly inside `class LNURL`. cw_core no longer parses,
so mobx_codegen fails ("90:5: Expected a class member") and every app,
unit_tests and internal-build CI job on dev and open PRs goes red.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.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
signing boundary
AI analysis · Informational 20/100

This commit fixes a simple Dart programming mistake where a method declaration line was accidentally deleted, causing the app code to fail compilation. It restores the missing line so the method works again. There is no security issue here—just a build break on the development branch.

AI review queuedfix: convert decoded JSON list instead of casting in solana_signAllTransactions (#3671)by KShot · 03f27548 · Oct 22, 2026 · 1 fileMessage 93 · StrongLow 37Details
Commit message · KShot

fix: convert decoded JSON list instead of casting in solana_signAllTransactions (#3671)

params['transactions'] arrives as decoded JSON (List<dynamic>), so the
hard cast 'as List<String>' threw a TypeError on every
solana_signAllTransactions request, which the handler mapped to
MALFORMED_REQUEST_PARAMS after the user had already approved.
Convert with List<String>.from(... as List<dynamic>) instead — the same
pattern already used for decoded JSON in lib/buy/buy_quote.dart.
Malformed (non-string) elements still throw inside the same try block,
so invalid requests are still rejected as malformed.

Fixes #3659

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

This commit fixes a bug in Cake Wallet's Solana WalletConnect feature. When a user approved signing multiple Solana transactions, the app incorrectly tried to force the incoming transaction list into a specific Dart type (List<String>), but the data arrived as a generic decoded JSON list (List<dynamic>). This caused a TypeError every time, which the app then reported to the connected dApp as 'MALFORMED_REQUEST_PARAMS' even though the user had already approved. The fix safely converts the list to the expected string type instead of hard-casting it, restoring normal functionality for multi-transaction signing requests.

AI review queuedfeat: add unit tests CI workflow (#3640)by David Adegoke · 49b48988 · Oct 22, 2026 · 12 filesMessage 98 · StrongInformational 15Details
Commit message · David Adegoke

feat: add unit tests CI workflow (#3640)

* feat: add unit tests CI workflow

* fix: update workflow to pull prebuilt dependencies and handle cache misses

* fix: update unit tests job to the new ci and fix the red tests

---------

Co-authored-by: Omar <omarh.ismail1@gmail.com>

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds a new automated unit-test workflow to the project's GitHub Actions CI pipeline and fixes several existing tests that were failing. It also makes a small UI improvement (adding a 'truncateLabel' option for settings rows) and updates a secrets-import helper to include Bitcoin configuration. There is no security-relevant change here.

AI review queuedmiscellaneousby Omar · 2caafc67 · Oct 22, 2026 · 4 filesMessage 18 · OpaqueInformational 18Details
Commit message · Omar

miscellaneous

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

This commit is mostly housekeeping. It adds documentation showing users how to verify that downloaded Cake Wallet files are genuine, updates the README to point to that guide, expands .gitignore to avoid accidentally committing signing secrets, and adds a 10-second timeout to a Lightning/lnurl network request so the app won't hang forever if a server is slow or missing.

AI review queuedWallet picker follow-ups to #3717 (#3729)by Omar Hatem · aaaea05e · Oct 21, 2026 · 7 filesMessage 76 · AdequateLow 48Details
Commit message · Omar Hatem

Wallet picker follow-ups to #3717 (#3729)

* fix(address-book): wallet picker follow-ups to #3717

- addressForBuy now skips hiddenAddresses, like the receive page's own
address selection. Every swap hides its refund address, so on the
Lightning/Silent Payments page the picker's on-chain "Active" entry
(from #3717) could be that refund address. Buy-provider payouts stop
landing on hidden addresses too.
- The picker decided "active" with name.contains('Active'), but the name
is localized first ("Aktiv", "Activo", ...), so BTC/LTC wallets were
missing from it in every language but English. WalletContact now
carries the raw address-map label and the filter matches on that.
- On the Silent Payments page the SP address is marked active again,
next to the on-chain one. The picker offers SP addresses only when the
caller opts in; the send page does for software Bitcoin wallets.
Hardware/air-gapped senders can't build SP outputs, and swap or
Lightning-withdraw inputs never opt in.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(address-book): trim comments; gate SP picker on hasSilentPaymentsScanning

Bugbot: wallets restored from an xpub have no hardwareWalletType, so they were
offered Silent Payments addresses they can't pay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(address-book): offer SegWit instead of Silent Payments/MWEB in wallet picker

Reverts the Silent Payments opt-in. A Bitcoin wallet on its Silent Payments or
Lightning page, and a Litecoin wallet on its MWEB page, now expose a plain SegWit
address as 'Active', so every sender gets an address it can pay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(litecoin): use addressForBuy for the MWEB page's address-book entry

Litecoin's addressForBuy now returns a regular address on the MWEB page, so the
buy flow and other wallets' address books both get an address every sender can pay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(address-book): offer a Litecoin wallet's MWEB address when it's on the MWEB page

A user who left wallet A on MWEB expects other wallets to send to that MWEB
address. Litecoin's addressForBuy still returns a regular address there, so
the buy flow is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(bitcoin): drop the unneeded Litecoin activeAddress parameter

Litecoin only has P2WPKH and MWEB pages, so its active address is always
`address`. electrum_wallet_addresses.dart is back to dev's version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

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: security-sensitive path
AI analysis · Low 48/100

This commit fixes address-selection bugs in Cake Wallet's address book and wallet picker. Before the fix, the app could suggest Bitcoin/Litecoin addresses that the sending wallet couldn't actually pay (for example, a hidden swap refund address, a Silent Payments address for a hardware wallet, or a Litecoin MWEB address). It also relied on the English word 'Active' in a translated name, so non-English users saw fewer wallets. The patch makes the picker choose only plain, broadly-supported addresses for buy/exchange flows and uses an untranslated label to decide which address is active.

Security candidatefix: make the wallet-access 2FA step non-dismissable (CW-1711) (#3742)by Seth For Privacy · 5aec35b4 · Oct 20, 2026 · 1 fileMessage 93 · StrongModerate 51Details
Commit message · Seth For Privacy

fix: make the wallet-access 2FA step non-dismissable (CW-1711) (#3742)

* fix: make the wallet-access 2FA step non-dismissable

TotpAuthCodePage ignored isClosable since the New Design rewrite (#2797):
the back arrow was always shown and popped the route. On the resume lock
that returned to the app without the TOTP code; on cold start it left a
black screen. The Android back gesture could pop it too.

Hide the back arrow and block pops with PopScope when isClosable is false.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: keep the 2FA page title when the back arrow is hidden

Without a leading button ModalTopBar's row has no height and clips the title.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

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 control
AI analysis · Moderate 51/100

This commit fixes a bug in Cake Wallet's two-factor authentication (2FA) screen. Previously, when the app required a 2FA code to unlock the wallet, users could bypass that requirement by pressing the back arrow or using Android's back gesture. The fix removes the back arrow and blocks the back gesture when the screen is meant to be mandatory, so the wallet cannot be accessed without entering the 2FA code.

AI review queuedCW-1509: Add BTCMap.org to apps (#3715)by Patrick · 75fa8961 · Oct 20, 2026 · 33 filesMessage 68 · AdequateInformational 20Details
Commit message · Patrick

CW-1509: Add BTCMap.org to apps (#3715)

* add BTCMap.org to apps

* launch btcmap.org/apps instead of btcmap.org

* localize btcmap subtitle

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 20/100

This commit adds a new promotional tile called "BTC Map" to the app's dashboard. Tapping it opens the website btcmap.org/apps in the phone's external browser. It also adds translated subtitle text for the new tile in many languages. There is no security vulnerability visible in the change.

AI review queuedclearer error when restoring unavailable wallet from qr (#3743)by malik1004x · c579e50e · Oct 20, 2026 · 1 fileMessage 58 · ThinLow 32Details
Commit message · malik1004x

clearer error when restoring unavailable wallet from qr (#3743)

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

This commit adds a clearer error message when a user tries to restore a wallet type that is not available in the current app. It prevents confusing behavior by throwing a specific exception early in the QR-code restore process, rather than letting the restore proceed with an unsupported wallet type.