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 34 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.

Security candidateCW-1581-trezor-fixes-enhancements (#3462)by Konstantin Ullrich · feeec2e4 · Aug 6, 2026 · 46 filesMessage 76 · AdequateLow 27Details
Commit message · Konstantin Ullrich

CW-1581-trezor-fixes-enhancements (#3462)

* feat: add Trezor auto connect

* chore: update `trezor_flutter`

* fix: correct method name for retrieving Trezor auto-pairing credentials

* fix: update device connection prompt text across all languages [skip ci]

* feat: add Trezor key image synchronization ui and improve hardware wallet UX

* feat: add sync-balance icon asset for settings row visuals [skip ci]

* feat: add sync-balance icon asset for settings row visuals [skip ci]

* fix: remove unused Monero and sync key images settings actions from menus [skip ci]

* fix: re-enable routing for UR QR Animated Page [skip ci]

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
credential or privilege stateprivacy or spend-authorization protocolsigning or wallet path
AI analysis · Low 27/100

This commit improves how Cake Wallet connects to Trezor hardware wallets and synchronizes Monero 'key images' (data that proves coins haven't already been spent). It adds automatic reconnection, a new user interface for syncing key images, and stores an encrypted Trezor pairing state on the device. The changes are mostly user-experience and reliability fixes rather than a clear security patch, though they touch on sensitive areas such as encrypted storage, hardware wallet pairing, and transaction signing flow.

Security candidatefix:quick actions cold start (#3476)by Serhii · 061f36a6 · Aug 5, 2026 · 4 filesMessage 68 · AdequateInformational 17Details
Commit message · Serhii

fix:quick actions cold start (#3476)

* fix:quick actions cold start

* route receive links to new receive page

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
authentication path
AI analysis · Informational 17/100

This commit fixes a bug where app shortcuts (quick actions) didn't work correctly when the wallet app was started from a cold state. It also updates the 'receive' shortcut to open the newer receive page instead of the older address page. There is no clear security issue here; it is a routine UI/UX bug fix.

Security candidateWrap long passphrase value on the wallet seed/keys screen (#3480)by claude[bot] · 0e42f162 · Aug 5, 2026 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · claude[bot]

Wrap long passphrase value on the wallet seed/keys screen (#3480)

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

This commit is a minor user-interface fix that makes very long wallet passphrases wrap to multiple lines instead of overflowing the screen. It does not change security behavior, cryptography, or how secrets are stored or protected.

AI review queuedcw-1584-ironwood-migration-modal (#3481)by malik1004x · 0257f5cf · Aug 4, 2026 · 11 filesMessage 76 · AdequateInformational 18Details
Commit message · malik1004x

cw-1584-ironwood-migration-modal (#3481)

* ironwood migration modal

* auto-show when migration begins

* remove restricted import

* new condition

* string fix

* only activate if ironwood is active

* reaction safeguards

* migration*

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 · Informational 18/100

This commit adds a user-interface feature for Zcash wallets that displays an informational modal when the user's funds are being automatically migrated to the new Zcash 'Ironwood' network upgrade. It does not change how funds are secured, sent, or received; it only shows explanatory text and a 'Learn more' link. There is no indication of a security vulnerability in this change.

AI review queuedfix: hide dust balance from "confirming" (#3456)by cyan · dc213417 · Aug 3, 2026 · 2 filesMessage 65 · AdequateLow 26Details
Commit message · cyan

fix: hide dust balance from "confirming" (#3456)

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

This commit changes how Cake Wallet's Zcash wallet calculates and displays balances that are still 'confirming' or otherwise unavailable. It filters out tiny 'dust' notes from the unavailable balance, adjusts which note pools are considered spendable during the Zcash Ironwood network upgrade, and changes the bitmask used when building transactions. The main user-visible effect is that small unspendable notes no longer appear as 'confirming' balance, which could previously make users think they had funds that were not actually usable.

AI review queueda11y: dashboard and navigation semantics (navbar, cards, sync, switchers) (#3468)by Seth For Privacy · a6bcf7c9 · Aug 3, 2026 · 19 filesMessage 81 · StrongInformational 15Details
Commit message · Seth For Privacy

a11y: dashboard and navigation semantics (navbar, cards, sync, switchers) (#3468)

* Label new-UI dashboard navigation and sync status for screen readers

Each bottom-nav tab becomes one button node carrying its localized name, its
selected state and mutual exclusion; the pill text no longer duplicates the
selected tab. The assets/history tabs gain selected state, the Bitcoin/Lightning
switcher becomes a labeled toggle, and the sync bar becomes a single button whose
label is the localized status (plus Tor/MWEB/Silent Payments badges) with a hint
pointing at node management. Compact mode's pulsing dot and the chain icon's
progress ring now have text equivalents, and the invisible pointer-absorbing
strip behind the nav bar is excluded from traversal.

* Make new-UI dashboard cards, lists and menus operable by screen readers

Collapse the wallet-name row into one labeled button (hardware-wallet glyph
folded into the label, inner accounts button no longer a second stop) and give
balance cards a labeled, selectable node with a long-press action for show/hide
balance. Balances hidden behind AnimatedOpacity, card artwork and decorative
glyphs leave the semantics tree; the 3-dots customize target and the card action
buttons are now named buttons. Assets/history rows, the history header, the MWEB
promo, long-press menu items, the account cards and the add-account and
generate-name controls become single button nodes, the phantom action chip in the
assets header is built conditionally instead of drawn at opacity 0, and app cards
get a close tooltip plus an 'opens externally' hint.

* Use expression bodies for the new a11y helpers

* Restore untouched expressions in cards_view

* Address review: state-aware balance hint, tooltip-free close label

* Address review: keep header height without the chip, name the selected index

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 improves accessibility for screen-reader users in the Cake Wallet app's new dashboard. It adds labels and roles to navigation tabs, balance cards, buttons, and status indicators so assistive technology can describe them properly. There is no security-relevant change here.

Security candidatesecurity: require app-level vulnerability proofsby sethforprivacy · 42019d86 · Aug 3, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sethforprivacy

security: require app-level vulnerability proofs

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
explicit security languagedocumentation-only discount
AI analysis · Informational 15/100

This commit only updates the project's security policy document (SECURITY.md). It tightens the rules for vulnerability reports by requiring proof-of-concept code that actually runs against the Cake Wallet app, and it asks contributors not to use AI-generated comments. There are no code changes, no bug fixes, and no direct security impact on the app itself.

AI review queued26-08-03_Update Translation_de_DEby bsn21m · e946627e · Aug 3, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · bsn21m

26-08-03_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 is a routine German translation update. It changes wording in user-facing text (for example, replacing 'Tausch' with 'Swap' and 'Gelder' with 'Guthaben'), adds a few missing translated strings, and updates navigation instructions. There are no code, logic, or security changes.

Security candidatea11y: expose ModernButton, CoinActionButton and ModalTopBar as single labeled button nodes (#3463)by Seth For Privacy · 26a16a4e · Aug 2, 2026 · 75 filesMessage 91 · StrongInformational 21Details
Commit message · Seth For Privacy

a11y: expose ModernButton, CoinActionButton and ModalTopBar as single labeled button nodes (#3463)

* Give ModernButton and CoinActionButton one labeled a11y node

ModernButton, CoinActionButton and the ModalTopBar chrome buttons were
icon-only IconButtons with no tooltip and a detached caption sibling, so
screen readers announced an unnamed "button" plus unrelated static text.

- Add optional semanticLabel to ModernButton; wrap the control in
MergeSemantics + Semantics(button: true, label: semanticLabel ?? label)
and exclude both the icon and the visible caption so exactly one node
is exposed. No visual or pointer change.
- Give CoinActionButton the same treatment, reusing the label callers
already pass (dashboard Send / Receive / Swap / Scan).
- Add leadingSemanticLabel / trailingSemanticLabel to ModalTopBar,
defaulting the leading button to "Close", and mark a non-empty title
as a semantics header.
- Migrate every ModernButton / ModalTopBar call site to pass a localized
label, and drop the now-redundant external Semantics wrapper in
base_page.dart so the back button is not labeled twice.
- Localize the hard-coded "Settings" modal title in settings_page.dart.

New English keys: rotate_address, swap_reverse_direction, switch_camera,
switch_input_currency, test_node_speeds, turn_flash_off, turn_flash_on.

* Require explicit accessible names on ModalTopBar and ModernButton icons

ModalTopBar defaulted every leading icon's accessible name to "Close", so
the ~40 callers that pass a back arrow announced the wrong action, and
trailingSemanticLabel was optional, leaving the trailing icon controls
unnamed.

- Drop the "?? close" fallback in ModalTopBar: the leading ModernButton
now gets exactly leadingSemanticLabel, and constructor asserts require a
non-empty label whenever leadingIcon / trailingIcon is supplied. Callers
that pass leadingWidget / trailingWidget instead are unaffected, and a
null icon still builds no button at all.
- Assert in both ModernButton constructors that the control has a name:
either semanticLabel or a non-empty visible label.
- Pass the matching localized label at every ModalTopBar call site: "Go
back" for back arrows, "Close" for close icons, and the action name for
trailing icons (History, Configure, Export CSV, Save, Scan, Close).
- Label the last unnamed ModernButton (wallet accounts, wallet_info.dart).

No new localization keys; all labels reuse existing strings_en.arb keys.

* fix(a11y): put ModalTopBar header flag on the title Text node

On-device audit (CW-1574, defect D2) found zero [heading] nodes in the
Android accessibility tree on the Receive page: Semantics(header:) wrapped
the AnimatedSwitcher rather than the Text inside it, so the flag never
landed on the node that carries the title label.

Move the header semantics inside the AnimatedSwitcher, directly around the
Text. The ValueKey(title) moves with it onto the Semantics wrapper, since
AnimatedSwitcher switches on its direct child's key -- keying the Semantics
by title preserves the existing switch/animation behavior exactly.

No test or robot resolves the title ValueKey through a Text-typed finder,
so the key relocation is not observable from the test suites on this branch.

* Set headingLevel so Android surfaces modal titles as headings

The Flutter 3.41 engine drives AccessibilityNodeInfo.setHeading from
headingLevel, not the IS_HEADER flag (which 3.35 used). Proven by an
on-device probe: header:-only headings print on a 3.35-engine build and
vanish on the 3.41-engine CI build.

91/100 · StrongMessage clarity
✓ Specific, 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
signing or wallet pathauthentication path
AI analysis · Informational 21/100

This commit is an accessibility (a11y) improvement, not a security fix. It makes icon-only buttons and modal titles readable by screen readers by attaching proper labels to them. There is no vulnerability being patched and no way for an attacker to exploit these changes.

Security candidateEnforce passphrase confirmation match on the restore and create wallet flows (#3474)by claude[bot] · f6566e3b · Aug 2, 2026 · 2 filesMessage 81 · StrongModerate 52Details
Commit message · claude[bot]

Enforce passphrase confirmation match on the restore and create wallet flows (#3474)

* fix: enforce passphrase confirmation in restore passphrase bottom sheet

The confirm-passphrase field in AddPassphraseBottomSheet already had a
validator comparing it to the first field, but the fields were not inside
a Form and nothing ever called validate(), so the validator never ran.
Tapping "Restore" restored the wallet with the first field's value even
when the confirmation did not match, defeating the typo check.

Wrap both fields in a Form and validate it before completing the restore,
matching the existing pattern in advanced_privacy_settings_page.dart.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019DtLNfYw1H81p7zZrkNDXM

* Validate passphrase confirmation when the passphrase field is empty

---------

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
access controldefensive validationsigning or wallet pathauthentication path
AI analysis · Moderate 52/100

This commit fixes a bug in the wallet restore and creation screens where the 'confirm passphrase' field was not actually being checked. A user could type one passphrase and a different confirmation, yet still proceed. The wallet would then be created or restored using only the first passphrase, which could lock users out of their funds if they made a typo. The fix wraps the fields in a proper form and validates the confirmation before continuing.

Security candidatezec ironwood (#3425)by cyan · 92c2c5e0 · Jul 27, 2026 · 38 filesMessage 59 · ThinLow 35Details
Commit message · cyan

zec ironwood (#3425)

* initial

* wip

* ironwood detection, migration

* dev: zec address validation on rt

* fix: ironwood spend

* ironwood regressions

* fix: tx history

* bump: zkool2

* fix: tx amounts on pending
fix: ironwood pending balance
fix: orchard->ironwood migration
fix: orchard->any pre ironwood txs
fix: ironwood -> any txs
fix: WrongSpendAuthorizingKey
fix: tx history
fix: autoshield to ironwood
fix: zkool to latest version
break: my sleep schedule :sweating: :worksonmymachine:

* thx fable

* downgrade frb to 2.11.1

* fix: tx amounts in history

* Migating... / migration label for O->I txs

59/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
update trustsigning or wallet path
AI analysis · Low 35/100

This commit adds support for Zcash's Ironwood network upgrade to Cake Wallet. It changes how wallet balances, transactions, and addresses are handled when Ironwood activates, and it lets advanced users pick mainnet, testnet, or regtest for Zcash. The changes are mostly functional upgrades and bug fixes rather than a clear security patch, but they touch sensitive areas like balance calculation, transaction construction, and address validation. Because the commit is large and partially hardcodes dev-network settings (for example, a regtest node at 10.0.2.2), there is some risk of misconfiguration or incorrect balance reporting, though no direct exploit is visible in the diff.

Security candidateShuffle change output on hardware wallet and Bitcoin Cash sends (#3432)by Cindy · b73c46ac · Jul 26, 2026 · 5 filesMessage 81 · StrongLow 49Details
Commit message · Cindy

Shuffle change output on hardware wallet and Bitcoin Cash sends (#3432)

* Shuffle change output on hardware wallet sends

Hardware wallet BTC/LTC sends passed outputs to the PSBT/device in the
given order (change last), a position fingerprint. The outputOrdering
param was plumbed but ignored. Add orderOutputs() and apply it in both
buildHardwareWalletTransaction paths; set the send call site to shuffle.

Refs #3376 (the software send + RBF paths were covered by #3420).

* Shuffle change output on Bitcoin Cash sends

The BCH send path built via ForkedTransactionBuilder with
outputOrdering: none, leaving change deterministically last. The builder
shuffles natively and change is found by isChange, not position, so flip
it to shuffle (matches the BTC software path from #3420).

Refs #3376.

* Update cw_bitcoin/lib/electrum_wallet.dart

Co-authored-by: Omar Hatem <omarh.ismail1@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 49/100

This commit fixes a privacy weakness in Cake Wallet's Bitcoin, Litecoin, and Bitcoin Cash sending flows. Previously, when using a hardware wallet or sending Bitcoin Cash, the app's own 'change' output was always placed last in the transaction. That predictable ordering acts like a fingerprint, making it easier for outside observers to identify which output belongs to the sender and trace the user's funds. The patch shuffles output order so the change output no longer sits in a fixed, telltale position.

AI review queueddisable exolix [skip ci]by Omar · 6c54a4ee · Jul 26, 2026 · 2 filesMessage 28 · OpaqueLow 32Details
Commit message · Omar

disable exolix [skip ci]

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

This commit disables the Exolix cryptocurrency exchange provider in the Cake Wallet app. It adds a one-time settings migration that turns Exolix off for all users and bumps the migration version so the change runs on app startup. The commit message gives no reason, and there are no supplied references explaining whether this is a security fix, a business decision, or a response to an incident.

AI review queuedfix btc address lookup (#3422)by Serhii · 24a884b3 · Jul 25, 2026 · 1 fileMessage 53 · ThinLow 44Details
Commit message · Serhii

fix btc address lookup (#3422)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 44/100

This commit fixes how Cake Wallet looks up Bitcoin addresses when checking transaction history. Previously, the code mixed up 'change' (internal) addresses and 'receive' (external) addresses, and did not properly separate newer standard addresses from older legacy addresses. The fix organizes addresses into four clear groups—standard receive, standard change, legacy receive, and legacy change—and checks each group separately. This likely prevents the wallet from missing transactions or incorrectly marking address gaps, which could affect balance accuracy. There is no direct evidence in the commit that this was a security vulnerability or that it could be exploited by an attacker.

AI review queuedupdate build numbersby Omar · a04171bd · Jul 23, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Omar

update build numbers

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 updates the app's version and build numbers in build scripts for Android and iOS. It does not change any code that handles money, user data, security, or app behavior. There is no security issue here.

AI review queuedfix: stop resetting coin control on swap (#3433)by Konstantin Ullrich · 8056cfec · Jul 22, 2026 · 2 filesMessage 65 · AdequateLow 26Details
Commit message · Konstantin Ullrich

fix: stop resetting coin control on swap (#3433)

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

This commit fixes a bug where the user's coin-control choices were being reset when swapping between send screens. Coin control lets a user choose exactly which coins (UTXOs) are spent. Previously, the app called a reset function after initial setup, clearing any selections the user had made. The patch removes that reset and also makes the code that tracks coins compare them by their unique transaction hash and output index rather than by a looser object equality, which should make coin tracking more reliable.

AI review queuedupdate build numbersby Omar · 7a05544c · Jul 22, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Omar

update build numbers

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 increments the app's build number from 4415 to 4416 on Android and from 425 to 426 on iOS. It changes no code, fixes no behavior, and has no security relevance visible in the diff.

AI review queuedfix: address leaks (#3426)by cyan · 7dd048d2 · Jul 21, 2026 · 1 fileMessage 55 · ThinLow 49Details
Commit message · cyan

fix: address leaks (#3426)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 49/100

This commit changes how Zcash wallet addresses are stored in the app's local wallet info. Instead of saving the full address map to persistent storage, it now saves an empty map, while still saving related metadata like address info, used addresses, and hidden addresses. The commit title says this fixes 'address leaks,' which suggests the previous behavior may have exposed or stored more address data than intended. However, the diff alone does not show what specific sensitive data was leaking, to whom, or under what conditions.

AI review queuedupdate app versionsby Omar · e4f1660a · Jul 21, 2026 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · Omar

update app versions

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 updates version numbers and build numbers across platform-specific build scripts. It does not change any application code, cryptographic logic, network handling, or user-facing behavior. There is no security relevance.

AI review queued26-07-21_Update Translation_de_DEby bsn21m · 0070c612 · Jul 21, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · bsn21m

26-07-21_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 adds a few German translations for user-facing text strings (for example, labels related to passphrases and an 'Autoshield' feature). There are no code changes, no security fixes, and no behavior changes.

Security candidatev6.3.0 Release Candidate (#3414)by Omar Hatem · 544cbec0 · Jul 21, 2026 · 15 filesMessage 76 · AdequateLow 45Details
Commit message · Omar Hatem

v6.3.0 Release Candidate (#3414)

* v6.3.0 Release Candidate
- the new transaction history
- Radar in Apps screen
- Zcash update
- Flutter update
- Parts of the Refactor
should improve how amounts are handled in the app and fix any issue with amounts
improve handling sending to aliases

- Improvements for Cake Pay mobile
- Bug fixes

* don't use memo for note/message values

* save message in QR locally in the notes field

* Make stealth addresses generated from silent payment, not reliant on output index (#3420)

* - fix swaps showing only on primary account
- switch tron default node
- privacy fixes

* - enlarge destination tag and make it copiable
- migrate users on hashvault
- minor fix

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
privacy or spend-authorization protocolsigning or wallet pathauthentication path
AI analysis · Low 45/100

This is a routine version-bump release candidate for Cake Wallet/Monero.com v6.3.0. The visible code changes include several privacy-related tweaks: Bitcoin transaction output ordering is now shuffled instead of fixed, a Tor/onion exchange provider now uses HTTPS instead of HTTP, default Tron and Monero nodes are switched/migrated away from TronGrid and HashVault, and a hardware-wallet passphrase field disables autocorrect. There are also UI fixes for destination tags and QR-code payment notes. The commit message itself mentions 'privacy fixes' but does not describe a specific vulnerability or disclose a security incident.

AI review queuedrefactor: remove deprecated payment URI classes and unify URI handling with `ERC681URI` implementation (#3423)by Konstantin Ullrich · b336da4a · Jul 20, 2026 · 3 filesMessage 93 · StrongInformational 14Details
Commit message · Konstantin Ullrich

refactor: remove deprecated payment URI classes and unify URI handling with `ERC681URI` implementation (#3423)

* refactor: remove deprecated payment URI classes and unify URI handling with `ERC681URI` implementation

* refactor: apply lint [skip ci]

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 14/100

This commit is a code cleanup: it removes several old, near-duplicate payment-URI classes for Ethereum-compatible chains (Polygon, Base, Arbitrum, BSC) and makes every EVM chain use a single shared ERC-681 URI builder. It also adds a parser to read those URIs back. The change is mostly a refactor with no obvious security bug, but it touches code that formats crypto payment amounts and addresses, so a small risk of accidental parsing/formatting mistakes remains.

Security candidatesecurity: harden vulnerability disclosure policy (#3419)by Seth For Privacy · 41e2cba3 · Jul 20, 2026 · 1 fileMessage 98 · StrongInformational 15Details
Commit message · Seth For Privacy

security: harden vulnerability disclosure policy (#3419)

* security: harden vulnerability disclosure policy + Slack routing

* security: add discretionary reward policy and marketing-site out-of-scope

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
explicit security languagedefensive validationdocumentation-only discount
AI analysis · Informational 15/100

This commit only updates the project's written security policy (docs/SECURITY.md). It does not change any application code, fix a bug, or patch a vulnerability. It clarifies how researchers should report security issues, adds safe-harbor language, defines scope, and introduces a discretionary reward policy. There is no direct security risk or security improvement to the software itself.

Security candidatetrezor-monero-passphrase-modal (#3337)by Konstantin Ullrich · 9d685d46 · Jul 17, 2026 · 17 filesMessage 76 · AdequateLow 25Details
Commit message · Konstantin Ullrich

trezor-monero-passphrase-modal (#3337)

* trezor monero passphrase modal

* feat: add Trezor passphrase support for wallet restoration process

* revert: send page changes

* chore: format code

* chore: format code

* chore: reorganize imports and improve code formatting in send_page.dart [skip ci]

* auto-reformat

* fix: trezor usb device refresh race condition

* fix: ui bugs in relation to trezor

* fix: only show passphrase option for trezor devices

---------

Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com>
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
access controlsigning or wallet pathauthentication path
AI analysis · Low 25/100

This commit adds support for using a passphrase with Trezor hardware wallets when restoring a Monero wallet in Cake Wallet. It also fixes a small race condition when refreshing the list of connected USB devices. There is no clear security vulnerability in the diff itself; it is a feature addition with some minor hardening.

AI review queuedCw 1539 lightning enhancements (#3400)by Konstantin Ullrich · 03edd658 · Jul 17, 2026 · 18 filesMessage 86 · StrongInformational 24Details
Commit message · Konstantin Ullrich

Cw 1539 lightning enhancements (#3400)

* feat: add Lightning transaction URL support in transaction details view model

* fix: update currency selection logic in WalletAddressListViewModel and ReceivePage

* feat: integrate computed transaction amount and fee getters in TransactionDetailsViewModel, refactor CopyWrapper logic in TransactionDetailsModal

* refactor: apply lint rules

* refactor: apply lint rules and improve LNURL handling with new methods for withdrawal requests and error checks

* auto-reformat

* fix: receive_page regression

* fix: Withdraw lightning to other btc wallet gives LN address

* chore: update .lock files [skip ci]

---------

Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com>
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This is a routine feature and bug-fix update for Cake Wallet's Lightning (Bitcoin layer-2) support. It adds the ability to handle LNURL withdrawal requests, fixes currency selection when receiving Bitcoin vs Lightning, and cleans up transaction-detail display. There is no clear security vulnerability in the diff, but the new network code that calls external Lightning services and parses invoices is a place where future bugs could matter, so it deserves normal review and testing.