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

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.

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.

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.

Security candidatefix out of bounds index in card customizer (#3733)by malik1004x · 71cd9cf6 · Oct 19, 2026 · 1 fileMessage 58 · ThinInformational 22Details
Commit message · malik1004x

fix out of bounds index in card customizer (#3733)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Informational 22/100

This commit fixes a UI bug in Cake Wallet's card customizer. Previously, when picking a card color, the app could compute an index that pointed past the end of the available color list, which could cause a crash or display glitch. The fix uses the actual filtered color list when computing the selected index and falls back to the first color instead of an invalid position.

Security candidatefix: honor Require PIN after timeout on resume (CW-1707) (#3726)by Seth For Privacy · d665e308 · Oct 19, 2026 · 3 filesMessage 98 · StrongModerate 59Details
Commit message · Seth For Privacy

fix: honor Require PIN after timeout on resume (CW-1707) (#3726)

* fix: honor Require PIN after timeout when returning from background (CW-1707)

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

* fix: ignore stale requireAuth result once the app is backgrounded again

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

* fix: ask for the PIN when the last auth time can't be read (CW-1707)

On Android the secure storage read can throw: a value that fails to
decrypt comes back as a PlatformException. requireAuth() let that
escape, so the resume handler never set _requestAuth and the app came
back without the PIN. Return true instead, so every caller asks for
the PIN when the timeout can't be checked.

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

* fix: arm Require PIN after lock in the session a wallet is created or restored (CW-1709) (#3736)

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Omar <omarh.ismail1@gmail.com>

98/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Moderate 59/100

This commit fixes a bug in Cake Wallet where the app could resume from the background without asking for the PIN, even when the user had turned on 'Require PIN after timeout.' In some cases, especially on Android, a secure-storage read error could silently prevent the lock screen from appearing. The patch makes the app ask for the PIN whenever the last-auth time cannot be read, and it also tightens the lifecycle handling so the PIN prompt is honored when returning from the background after a wallet is created or restored.

Security candidateerror handling for keychain (#3720)by Omar Hatem · cc688d7e · Oct 19, 2026 · 37 filesMessage 88 · StrongLow 33Details
Commit message · Omar Hatem

error handling for keychain (#3720)

* iOS only, display why keychain failed to get the read key of PIN

* offer app reset if restored from icloud backup and the keychain data is missing

* fix review comments

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
authentication path
AI analysis · Low 33/100

This commit improves how Cake Wallet handles a specific iOS situation: when a user restores their phone from an iCloud backup, the app data comes back but the iOS Keychain (which stores the PIN and wallet passwords) does not. Previously the app could silently fail or behave oddly. Now it detects the missing keychain, explains the situation to the user, and offers to wipe the unusable local wallets so the user can restore them with their recovery phrases. It is a defensive UX and error-handling improvement, not an attack vulnerability.

Security candidatefix: open external links outside the app so the PIN lock can show (#3737)by Seth For Privacy · f80ac4df · Oct 19, 2026 · 9 filesMessage 93 · StrongModerate 64Details
Commit message · Seth For Privacy

fix: open external links outside the app so the PIN lock can show (#3737)

Links opened with the default launch mode use SFSafariViewController on
iOS. While it covers Flutter no lifecycle events reach Dart, so returning
from the background showed the browser without asking for the PIN.

Refs GHSA-329m-5v92-587r, CW-1707

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

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlsigning or wallet path
AI analysis · Moderate 64/100

This update changes how the app opens web links so they launch in the device's regular browser instead of an embedded browser sheet. The problem was that on iOS the embedded sheet (SFSafariViewController) hid the app from normal background/foreground events, so when a user returned from viewing a link the wallet reappeared without asking for the PIN. That could let someone with brief physical access to an unlocked phone browse back to the wallet without re-entering the PIN. The patch forces links to open externally, restoring the normal app lifecycle and letting the PIN lock screen appear.

Security candidatevalidate swaptrade networks against /get-coins (#3724)by Patrick · 4ef592e4 · Oct 16, 2026 · 3 filesMessage 81 · StrongModerate 58Details
Commit message · Patrick

validate swaptrade networks against /get-coins (#3724)

* validate swaptrade networks against /get-coins

* fix swaptrade order status decoding + error handling

* cleanup

* Trim SwapTrade network identifiers

Co-authored-by: OmarHatem28 <31170694+OmarHatem28@users.noreply.github.com>

---------

Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: OmarHatem28 <31170694+OmarHatem28@users.noreply.github.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
defensive validationcryptography-sensitive path
AI analysis · Moderate 58/100

This commit changes how Cake Wallet's SwapTrade exchange integration validates which cryptocurrencies and networks are supported. Instead of relying on a hardcoded internal list of network names, it now fetches the supported coins and networks from the SwapTrade API at runtime and validates the user's chosen currency/network against that live list. It also improves error handling and fixes how trade statuses are decoded. The change reduces the risk of sending funds on an unsupported or mismatched blockchain network (which can cause loss of funds), but the commit itself is a defensive correctness fix rather than a confirmed vulnerability patch.

Security candidatecw-1443-error-handling (#3410)by malik1004x · 0526d4dd · Oct 15, 2026 · 174 filesMessage 98 · StrongLow 31Details
Commit message · malik1004x

cw-1443-error-handling (#3410)

* add lints (wip)

* move to builtin custom lint api

* remove broken lint.sh

* remove use_decorated_box

* connect lint_check ci to lint.sh

* add typecast so app builds without disabling analyzer

* remove broken analysis_options from cw_* packages

* remove unneeded dependency override

* fix stupid naming

* add configure to ci

* move lint call to reusable-build.yml

* workaround weird analyzer bug by reordering linter rules

* return to old lint.sh to not format deps in scripts

* add super.key to BasePage constructor

* disable use_key lint because it's bugged

* Revert "add super.key to BasePage constructor"

This reverts commit 4869f0bab0777ea9b784299bc9a9144eb8090b72.

* add cw_* to lint.sh

* remove obvious type lint because it's bugged again (thanks google!)

* ABORT_ON_CHANGE

* exclude tool and cw_custom_lints from printV check

* exclude cw_custom_lints from http import check

* test add lint as separate action

* remove compile graphics from lint ci

* add container info to ci

* fix

* fix

* format only files after te 29th

* git-based date check

* remove lint from reusable-build.yml

* move lint.sh out of scripts

* ./

* test fix ci

* move lint.sh

* move lint.sh

* print all changed files

* fix ci hopefully

* revert

* try ci without cache

* fix torch, apparently

* nicer logging

* add bitbox

* remove zec

* add zec prep-only

* only detect changes in dart files

* add main.dart

* update lints

* fix printV warnings being displayed when editing printV

* (wip) add granular exceptions

* (wip) add granular exceptions

* temp-uncomment no bare catch rule

* add walletType field to BadWaleltTypeException

* ResponseCodeException

* fix lint rules

* switch to ResponseCodeException in the rest of the providers

* revert 3.44-related changes

* fix

* add toString

* fix test

* fix catch in backup viewmodel

* fix missed throw Exception in ltc wallet

* improve exchange provider classes

* fix exception class in ltc

* add CakeException extends to preexisting exceptions

* fix exception

* implements -> extends

* constructors

* add toString to cw_mweb

* replace all new throw Exception calls with CakeException subclasses

* fix accidental imports

* don't create another cakeexception for single mweb exception

* add name and type to walletnotfoundexception

* dedicated exception for overwriting wallet

* double quotes

* make evm exceptions extend generation exception

* unify cakepay exceptions

* implements -> extends

* fix imports in ledger vm

* fix walletswitchexception

* fix import

* missing exceptions

* fix CI and conflict with dev

* fix CI

---------

Co-authored-by: Czarek Nakamoto <cyjan@mrcyjanek.net>
Co-authored-by: Omar <omarh.ismail1@gmail.com>

98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy pathsigning or wallet pathauthentication pathparser or protocol path
AI analysis · Low 31/100

This is a large code-quality and error-handling refactor across the Cake Wallet app. It replaces generic 'throw Exception(...)' calls with a new family of specific exception types (CakeException subclasses), adds a custom lint rule to prevent future generic exceptions, and makes related CI/build cleanups. The change does not introduce new user-facing features or, on its own, fix a known exploitable bug. It improves maintainability and lays groundwork for better error diagnostics, but because it is a broad refactor touching many wallet modules, any mistake could affect how errors are caught and displayed to users.

Security candidateUpdate light theme colors (#3646)by tuxsudo · 12739314 · Oct 14, 2026 · 15 filesMessage 76 · AdequateInformational 15Details
Commit message · tuxsudo

Update light theme colors (#3646)

* Update light theme colors

* Update component colors

* Update selected address color

* Fix error container color

* More fixes

* Update heart color

* Fix image URLs

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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a routine visual redesign of the app's light color theme. It changes colors for charts, buttons, backgrounds, and icons, and swaps a few image assets to light/dark variants. There is no security-relevant change.

Security candidateCharts: fix 'Cannot compare money in different currencies' crash (#3713)by claude[bot] · 76e355d0 · Oct 13, 2026 · 2 filesMessage 81 · StrongInformational 18Details
Commit message · claude[bot]

Charts: fix 'Cannot compare money in different currencies' crash (#3713)

* Charts: load prices with the currency the cache round-trips to

PriceData rows are cached by CryptoCurrency.apiString ("crypto.$title",
no tag), so cached rows for e.g. usdterc20 come back as generic usdt
while fresh API rows keep usdterc20. Mixing both in one asset's list
made ChartsLoaded.changeDataFor throw "Cannot compare money in
different currencies". Round-trip the requested currency through
currencyFromApiString before loading so API and cached rows match,
falling back to the original currency when it can't be parsed.

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

* Map AVAX title to avaxc in CryptoCurrency.fromString

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

* Charts: drop fallback now that every picker currency round-trips

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

* Charts: drop comment

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

---------

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

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 18/100

This commit fixes a non-security crash in the app's price charts. The chart screen could mix cached and freshly downloaded price rows that were tagged with slightly different currency names (for example, 'usdterc20' versus plain 'usdt'), causing a 'Cannot compare money in different currencies' error. The fix makes the chart request prices using the same currency tag that the cache uses, so the two sources line up. It also adds a missing nickname mapping for the AVAX token. There is no indication this was a security vulnerability or that it could be exploited.

Security candidateCW-1513/CW-1610: Add account archival and UI improvements (#3600)by Patrick · 20f1ceb6 · Oct 10, 2026 · 108 filesMessage 100 · StrongInformational 18Details
Commit message · Patrick

CW-1513/CW-1610: Add account archival and UI improvements (#3600)

* add ability to hide accounts

* remove import

* merge

* merge

* fix loading accounts when styleSettings are not saved yet

* merge

* auto-reformat

* small fixes

* proper reload on card unhide

* block hiding last card

* fixup

* revert formatting-only changes

* liner fixes

* fix overflows

* card layout as separate class to prevent index errors

* fix mini card on addresses page

* block opening customizers if wallet is syncing

* switch to BlocProvider.value to prevent auto dispose

* imports

* fix fiat balance

* Improve homescreen layout and account access

* Add homescreen layout regression tests

* improve account management w/ education + archival flows

* reorganize wallet-specific settings

* preserve account archival during dismissal

* fix: align account visuals with design feedback

* minor account & archival visual corrections

* simplify wallet settings + account UI state

* generalise education carousel & dismissal tracking

* refactor account UI flows + minor improvements

* minor refactors and improvement

* pass account balances as Money and format at display

* use fresh full balance for account archival check

* refactor BalanceCard w/ MoneyText + cleanup

* minor card_customizer cleanup

* rework card customizer flow

---------

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

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
memory safetyfuzzing or regression evidencesigning or wallet path
AI analysis · Informational 18/100

This commit is a large feature update for the Cake Wallet app that adds the ability to hide (archive) cryptocurrency accounts, customize account cards, and reorganize wallet settings. It is primarily a user-interface and data-management change. There is no direct evidence in the commit that it fixes a security vulnerability; it looks like a normal product feature release.

Security candidatechore: add new images for robinhood (#3689)by David Adegoke · 098e1ea0 · Oct 7, 2026 · 2 filesMessage 90 · StrongInformational 15Details
Commit message · David Adegoke

chore: add new images for robinhood (#3689)

* fix: add new images and fix integration tests

* fix: round robinhood network icon and align card background.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only replaces two Robinhood-themed image files (SVG graphics) with updated versions. It changes the visual design, dimensions, and colors of icons and a card background. There is no code change, no executable logic, and no security-relevant behavior.

Security candidatefix: add new images and fix integration tests (#3679)by David Adegoke · ad93901a · Oct 5, 2026 · 17 filesMessage 80 · StrongInformational 15Details
Commit message · David Adegoke

fix: add new images and fix integration tests (#3679)

80/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a routine product update for the Cake Wallet app. It swaps in new Robinhood-themed icons and card backgrounds, adjusts a color gradient, adds Robinhood to integration-test wallet lists, fixes a QR-code image reference to point at the new Robinhood QR asset, and tweaks how stablecoins are filtered in the currency picker. There is no code change that introduces a security vulnerability.

Security candidateAdd Robinhood Chain (#3398)by David Adegoke · 046e57c5 · Oct 4, 2026 · 143 filesMessage 76 · AdequateLow 35Details
Commit message · David Adegoke

Add Robinhood Chain (#3398)

* fix android CI

* feat: Add Robinhood Chain, all major flows done. minor issue now is our providers don't support it yet as its still pretty early, two weeks from launch

* feat: Add Robinhood Chain, all major flows done. minor issue now is our providers don't support it yet as its still pretty early, two weeks from launch

* Cleanup

* auto-reformat

* fix ui issue and contact listing for tokens

* fix: missing icons and crash for fee priority in settings

* chore: cleanup

* fixes from feedbacks

* fix: review issues and sync to latest dev
feat: switch history api to etherscan, add history toggle to privacy settings, exclude robETH from exchange pickers, skip tokens discovery for chains that moralis hasn't indexed, add tests

* fix: address Robinhood review comments

* fix: show Solana token icons in history

* fix: address review comments and default Robinhood to PublicNode

* fix: revert filter and refuse unmapped networks in provider

---------

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

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet path
AI analysis · Low 35/100

This commit adds support for a new blockchain, "Robinhood Chain" (chain ID 4663), to the Cake Wallet app. It is a large feature patch that wires the new chain into wallet creation, sending, receiving, exchange providers, transaction history, settings, and UI assets. There is no direct evidence in the commit of a security vulnerability, but the size and breadth of the change introduce ordinary implementation risks typical of adding a new EVM chain.

Security candidatecw-1683-prepare-zano-removal (#3668)by malik1004x · 86616811 · Oct 3, 2026 · 12 filesMessage 76 · AdequateInformational 23Details
Commit message · malik1004x

cw-1683-prepare-zano-removal (#3668)

* wip zano removal

* add zano removal popup

* constantly show popup if user keeps using deprecated wallet

* add confirmation before viewing seed

* fix viewed check

* prevent wallet staying open after seed backup

* Update lib/entities/default_settings_migration.dart

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

* add passphrase

* make popup scrollable

* delete deprecated seeds when wallet is deleted

* encrypt seeds

* also deprecate decred

* remove decred from available types

* remove backup logic

* showArrow: false,

* Remove deprecated wallet seeds deletion

Removed deprecated wallet seeds deletion from delete method.

---------

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

This commit prepares Cake Wallet to remove support for Zano and Decred wallets. It adds a new database table to store encrypted seed phrases for wallets that are being deprecated, shows warning popups to users so they back up their seeds, and stops new Zano/Decred wallets from being created. It also fixes a minor cleanup bug where a cached Zano wallet might not be closed before deletion. There is no direct evidence in the commit of an exploitable security vulnerability; the changes are primarily user-facing deprecation and data-preservation work.

Security candidateCw 1551 quick bitcoin wallet sync (#3446)by Serhii · d7ebf428 · Oct 2, 2026 · 84 filesMessage 76 · AdequateLow 33Details
Commit message · Serhii

Cw 1551 quick bitcoin wallet sync (#3446)

* add Wallet Accounts page and integrate UI

* account model refactor

* add walletInfoAccount table and API

* add WalletAccountList API

* add multi-account support for Electrum wallets

* add Bitcoin lightning card and card style handling

* refine account filtering and card selection

* update current account balance on wallet changes

* update configure.dar

* Use named parameters for card design

* Add Bitcoin account handling and refactor lookup

* refactor dashboard

* refactor cards UI and account balance handling

* Improve Bitcoin account selection and balances

* restrict unspent coin usage to current account

* filter transactions by current Bitcoin account

* refactor electrum wallet

* refactor address generation

* add accountIndex to address fetch logic

* Update configure.dart

* reload transactions on Bitcoin account change

* restore multiple BTC accounts and improve fetch

* show account balance with in btc

* track account index in Bitcoin transactions

* discover btc BIP39 accounts during restore

* fix account switching and card ordering bugs

* fix card customizer

* limit account name length in modal

* update BTC account list balance display

* auto-reformat

* formating fix

* skip HD map validation

* fix 0 balance issue

* minor fix

* quick bitcoin wallet sync

* restore shuffle change output

* restore address lookup fix

* Update electrum.dart

* remove account customizer

* Merge branch 'CW-1142-Add-accounts-feature-to-BTC' into CW-1551-Quick-Bitcoin-Wallet-Sync

* probe only segwit in account discovery

* add account discovery limit and tracking

* Improve Electrum sync account handling [skip ci]

* remove legacy monero account and address list UI

* rework BTC account balance refres

* avoid unnecessary BTC account reloads

* refactor account header in addresses page

* fix blank popup when editing an account

* fix: dedupe UTXO balance

* minor fix

* add Bitcoin current account API

* Apply batched suggestions from code review [skip ci]

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

* address PR review comments [skip ci]

* remove account customizer and fix accounts init

* restrict extra BTC accounts to SegWit

* add BTC multi-account toggle

* Fix BTC sync gating and account balance update

* minor fix

* Update electrum_wallet.dart

* store selected account on WalletInfo

* Refine wallet account reset visibility

* refactor BTC address prep and move accounts page

* refactor account stack and customizer routing

* migrate legacy Lightning card styles

* unify dashboard account change state

* fix account routing and Electrum balances

* fix account setup and wallet cards UI

* disable Bitcoin Accounts for all hardware

* merge conflicts fix

* minor fixes

* update cards_view [skip ci]

* reverted cards view update [skip ci]

* fix asset name

* moved the transaction filtering into the electrum wallet

* localization

* disable accounts for watch-only wallets

* fix: stop card render from switching the wallet account

* fix: restore Lightning transactions in tx history

* minor fix

* fix: skip duplicate legacy address generation [skip ci]

* fix: correct account balance/design mismatch bugs

* addressing review comments

---------

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
secret or key materialsigning boundarysigning or wallet path
AI analysis · Low 33/100

This is a large feature commit that adds multi-account support for Bitcoin wallets in Cake Wallet, along with a 'quick sync' optimization. It changes how addresses, transactions, balances, and unspent coins are tracked per account. The changes are mostly architectural, but they touch sensitive wallet logic such as key derivation, transaction selection, balance calculation, and address discovery. There is no explicit vendor statement that this is a security fix, and no CVE or independent researcher attribution is present in the commit materials.

Security candidateMerge pull request #3658 from cake-tech/integration-test-fixesby David Adegoke · bc302f0e · Sep 27, 2026 · 3 filesMessage 83 · StrongInformational 16Details
Commit message · David Adegoke

Merge pull request #3658 from cake-tech/integration-test-fixes

fix: flaky integration test runs on the CI emulator

83/100 · StrongMessage clarity
✓ Specific, 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
authentication pathmerge-commit duplicate discount
AI analysis · Informational 16/100

This commit fixes flaky integration tests in the project's automated CI pipeline and makes a small UI cleanup change in the app's authentication screen. It does not appear to fix a security vulnerability. The auth-page change replaces a direct 'dismiss' call on notification bars with a safer helper that checks whether the bar is actually showing before trying to dismiss it, preventing a possible crash or visual glitch during PIN entry.

Security candidatefix: handle flushbar dismissalby Blazebrain · 88a7e72c · Sep 27, 2026 · 2 filesMessage 47 · ThinInformational 23Details
Commit message · Blazebrain

fix: handle flushbar dismissal

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 23/100

This commit fixes how the app dismisses on-screen notification banners (called 'flushbars') during login. Previously, the code tried to dismiss a banner even when it wasn't currently shown, which could cause the app to crash or behave oddly. The new helper checks whether the banner is actually visible before dismissing it, and removes it from the navigation stack if it isn't. The change is a stability fix rather than a security vulnerability.

Security candidateIntegration tests (#3477)by David Adegoke · dfa51657 · Sep 23, 2026 · 137 filesMessage 93 · StrongLow 26Details
Commit message · David Adegoke

Integration tests (#3477)

* fix android CI

* feat: Add integration test harness and new-ui test keys

This change:
- Adds a BaseRobot with bounded waits to replace hard sleeps in integration tests
- Adds AppLauncher, TestConfig and TestWallets as the core test harness
- Adds onboarding flows composing the existing onboarding robots
- Adds robots for the new dashboard, home page and lightning username page
- Adds a tier0 onboarding create suite targeting the new UI
- Applies the declared navbar action keys that were never attached to the InkWell
- Fixes AlertWithOneAction dropping its buttonKey since the alert redesign
- Adds stable ValueKeys to the home page action row, wallet name, top bar and sync bar
- Makes the legacy tap and text entry helpers wait for widgets instead of sleeping

* fix: Test secrets drift and integration test runner parameterization

This change:
- Adds missing test wallet seed and receive address entries to the secrets generator
- Fixes trailing space typos in two secret key names
- Adds bloc_test to pubspec_base.yaml so pubspec regeneration keeps it
- Parameterizes the integration test runner with suite dir, tier, platform and device knobs
- Fixes the runner aborting on first failure and misaligning durations after retries
- Adds adb data reset so Android suites start from a fresh install

* feat: Android emulator integration test workflows for dev PRs

This change:
- Adds a reusable integration test workflow building the app with prebuilt native deps and running the suites on an Android emulator
- Adds the PR gate workflow triggering fund-free tier0 suites on pull requests into dev
- Fixes the old workflow discarding the test runner exit code so failures now fail the job
- Removes the disabled automated integration test workflow on the stale flutter image
- Removes the commit-message gated Linux desktop test steps, unit tests stay
- Removes the vestigial emulator config from the reusable build workflow

* feat: Revive fund-free integration test suites for the new UI

This change:
- Adds tier0 suites for restore, seed confirmation, wallet switching, receive address, settings navigation and the show keys auth gate
- Adds tier1 suites for sync status, swap quotes and transaction history running non-blocking on PRs
- Adds robots for the settings, receive, swap and send sheets
- Adds auth, wallet switching and restore flows
- Applies widget keys to settings rows through their route names, they were declared but never attached
- Adds keys to the swap amount fields, send inputs, confirm swiper and history tiles
- Adds an integrationTest wrapper containing background async app errors that are not test failures
- Makes taps wait out running route transitions before hitting the screen
- Adds a watchdog to the test runner so a wedged driver fails bounded instead of hanging
- Removes the old UI suites, robots, helpers and the stale widget_test counter template

* chore: Add integration testing docs and suite template

This change:
- Adds docs/INTEGRATION_TESTS.md covering the architecture, local runs, tier rules and the flakiness playbook
- Adds a copy-paste suite template teammates start new feature tests from

* feat: Manual funds integration test workflow with funded-chain auto-discovery

This change:
- Adds a funds suite sending a real self transaction on every funded chain
- Adds a funds suite creating a real swap and broadcasting its deposit
- Discovers funded chains from the funded wallet seeds map, adding a seed to the secret adds the chain
- Adds the manual workflow dispatched from the Actions tab with flow, chain and recording inputs
- Gates the run behind the funds-tests environment and posts the result to slack
- Keeps funded seeds out of PR builds, the checked in seed map is empty

* fix: Harden integration test harness from review findings

This change:
- Fixes body failures being swallowed by the guarded test zone, failing suites hung until the watchdog instead of failing fast
- Fixes multi chain CHAINS dispatch values being split apart by the define forwarding
- Fixes the swap limits wait timing out on pairs without a provider minimum
- Makes unknown chain names in CHAINS fail with a readable message
- Keys favorite token rows by index, duplicate token symbols crashed on duplicate keys
- Guards the recording encryption so a keyserver flake cannot eat the test result
- Removes the dead security and backup robot and corrects the screenshot claim in the docs

* chore: Hold two funded seeds per chain in the funded wallets map

This change:
- Changes the funded wallet seeds map to a list of seeds per chain
- Keeps the first seed as the primary for sends and swaps, the second is reserved for cross wallet scenarios

* feat: Try each funded wallet per chain until one has a balance

This change:
- Adds a funds flow restoring a chain's funded wallets in turn and using the first with a spendable balance
- Treats a wallet that finishes syncing while still empty as drained so the next seed gets its turn quickly
- Fails a chain with a top up message when every funded wallet of that chain is empty

* reformat integration test related files

* fix: Run the integration test emulator on the kvm capable runner

This change:
- Moves the test job to the linux-amd64 runner the old emulator workflow targeted, the android builders have no /dev/kvm
- Exposes /dev/kvm through a docker device flag instead of a volume, a bind mount materializes a directory when the host node is missing
- Fails the kvm check in seconds with a clear error instead of waiting out the emulator boot timeout

* fix: Queue the integration test job on the live android runner pool

This change:
- Moves the job back to the android runner labels, no runner carries the old linux-amd64 label anymore so the job queued forever
- Keeps the kvm device flag and check so a host without kvm fails immediately with a clear error

* feat: Run the integration test gate on github hosted runners

This change:
- Moves the test job to ubuntu-latest which has working kvm, the self-hosted android builders do not expose /dev/kvm yet
- Runs directly on the vm since the cake container image does not fit hosted disk, flutter is pinned through the flutter action
- Adds rust android targets for the breez cargokit build and java 17 for gradle
- Keeps the prebuilt native deps from the ghcr docker cache, they pull fine on hosted docker
- Adds pub, gradle and flutter caching plus a disk cleanup step
- Keeps every input, the runner script, tier1 soft run, recording and artifacts unchanged

* fix: Install flutter from the same source as the ci container image

This change:
- Clones the flutter 3.41.9 tag directly like the container image instead of using the release archive
- The archive ships a stricter dart that rejects the checked in mweb ffi bindings, the tag clone compiles them
- Caches the cloned sdk between runs

* fix: Regenerate the mweb ffi bindings with the workflow dart

This change:
- Regenerates cw_mweb/lib/generated_bindings.g.dart after the deps step, the docker deps builder generates it with an older dart whose ffigen output the current compiler rejects

* fix: Pin ffigen so fresh resolutions generate compliant mweb bindings

This change:
- Pins ffigen to ^20.1.1 in cw_mweb, the unconstrained dependency resolved to 7.1.0 on fresh checkouts
- Old ffigen emits ffi classes without the base or final modifiers the current dart compiler requires

* fix: Restore the pinned cw_mweb pubspec before regenerating bindings

This change:
- Restores cw_mweb/pubspec.yaml after the deps step, the deps image rsync clobbers it with the stale unpinned copy so the ffigen pin never applied
- Wipes the rsynced pubspec.lock and .dart_tool so pub resolves the pinned ffigen fresh
- Asserts the regenerated bindings carry class modifiers so a bad generation fails in seconds
- Skips the libclang install when it is already present, apt spent fourteen minutes on it

* fix: Run the emulator test logic from a file, the action splits script lines

This change:
- Moves the whole emulator script into a file written before the emulator step, the action executes every script line as a separate sh command so multi line logic broke with a syntax error
- Passes the action a single line script invoking that file with bash

* fix: Give the ci emulator a real phone profile

This change:
- Sets the avd to the pixel 5 profile, the default 320x640 skin cannot fit the seed word grid so every wallet creation suite failed its seed display checks
- Caps tier0 attempts at ten minutes, two failing suites at the thirty minute worst case blew the job timeout

* fix: Wait for pages on the ci emulator instead of asserting immediately

This change:
- Makes the legacy page assertion poll for the page, the wallet keys page arrives after the ci emulator finishes unlocking the wallet so both auth gated suites failed on a race
- Raises the tier0 attempt timeout, the first attempt for each suite compiles that target's kernel and was being killed then passing on retry
- Raises the job timeout to fit the per suite compiles

* fix: Recover from driver attach failures instead of burning the timeout

This change:
- Detects attempts where the flutter driver never attached to the app and retries them without spending the real retry, restarting adb first
- Lowers the ci attempt timeout back to ten minutes, every passing attempt finishes within four so a longer cap only makes an attach failure cost more

* fix: Bound the adb recovery and give up when the driver never attaches

This change:
- Bounds every adb call in the recovery path, adb wait-for-device blocks forever when the emulator is gone and silently ate a whole ci job
- Aborts the suite when adb cannot be brought back instead of retrying against a dead device
- Stops the run after a few driver attach failures, an environment that never attaches will not fix itself
- Dumps logcat after every failed attempt so a failure to start the app leaves evidence behind

* fix: Stop the runner failing when every suite passes

This change:
- Assigns the result arrays empty instead of only declaring them, set -u treats a declared but never assigned array as unbound so the summary died on the first run where nothing failed

* fix: Make the ci build cacheable and keep tier results when the runner dies

This change:
- Splits the flutter and pub caches into restore and save steps, actions/cache only saves when the whole job succeeds so they were never written and every run paid for a cold build
- Lets setup-gradle write its cache, it is read only on branches other than the default one
- Caps the gradle heap before the test phase, the six gigabyte daemon plus the emulator left the runner too little to stay alive
- Runs tier0 and tier1 as separate emulator steps so each uploads its logs before the next can take the runner down
- Logs memory and disk around each tier
- Documents how ci runs the suites and the two environment quirks that only bite there

* fix: token decimals defaulting to zero and breaking amount parsing in solana

(cherry picked from commit c220bbb46df9468faf9a8967cb0ef672af7cc664)

* fix: Install the test error handler after the app boots and drain benign errors

This change:
- Installs the test error handler after main() instead of before it, the app replaces FlutterError.onError while booting so the handler installed earlier never ran
- Replaces the app's async error handler during tests, it returns at its first await without recording anything so the framework asserted instead of reporting the real error
- Drains background errors the app tolerates at runtime from the wait loops, anything unrecognised still fails the test where it happened
- Collects the tolerated categories in one place, layout and semantics assertions from debug builds plus the transient network failures exception_handler.dart already ignores

* fix: Import FlutterExceptionHandler from foundation so the test build compiles

This change:
- Imports package:flutter/foundation.dart in the launcher, material.dart only re-exports Brightness and UniqueKey from foundation so FlutterExceptionHandler was not in scope
- Drops the material.dart import, every symbol the launcher uses comes from foundation

* chore: Drop the funds-tests environment from the funds workflow and docs

This change:
- Removes the environment input from the funds workflow, we no longer use a funds-tests GitHub environment so passing it would only auto create an unprotected one on the next dispatch
- Says plainly in the docs that nothing gates the dispatch, the doc still claimed the run waits for environment approval
- Names write_funds_secrets as the one thing keeping funded seeds out of a PR build, that used to be backed by environment scoping too

* chore: Trim the integration test comments down to the ones that carry weight

This change:
- Drops the doc comment sitting on top of every robot primitive, flow and config getter, they restated the method name and nothing else
- Collapses the multi paragraph docstrings on the launcher, the error drain and the funded wallet lookup into the one or two lines that actually explain why the code is shaped that way
- Removes the file and class header paragraphs, the funded wallets stub keeps a short note because an empty map needs one
- Keeps the notes worth having, the chain quirks in the onboarding flow, the route transition tap, the dust thresholds, the void attempt handling in the runner

* chore: Fold the components folder into core and clear out the leftover comments

This change:
- Moves common_test_cases.dart into core, the components folder was down to that one file after common_test_constants.dart went
- Drops six methods from it that nothing calls, dragUntilVisible alone was 95 lines of scroll logic with no caller
- Removes the comments narrating the line below them across the older robots, "Drag to the left" above a moveBy and "Confirmation for buttons 1-9" above the loop
- Deletes the commented out body of takeScreenshots and says instead that it does nothing, all fifteen callers have been no-ops
- Notes in the docs that new robots extend BaseRobot while the older ones still carry a CommonTestCases

* chore: Clear out pending items

* refactor: Move the onboarding robots onto BaseRobot and drop the sleeps

This change:
- Deletes common_test_cases.dart, the sixteen robots that held a CommonTestCases now extend BaseRobot like the newer ones do
- Moves the primitives those robots needed onto BaseRobot with the same behaviour, isSpecificPage, hasType, hasValueKey, hasText, hasTextAtLeastOnce and swipePage
- Renames each robot's page check to isDisplayed so every robot answers the same question the same way
- Removes the twenty six defaultSleepTime calls, every one of them sat in front of an action that already waits for what it needs
- Waits for the view model to move to the next word in seed verification instead of sleeping a second and hoping, and fails with a message when it does not
- Settles after opening a tab on the wallet keys page, the assertions there read the tree straight after the tap
- Drops the fifteen takeScreenshots calls, the method's body has been commented out the whole time so none of them did anything
- Formats the three files dart format was still rewriting

* fix: Wait out the navigation the removed sleeps used to cover

This change:
- Settles after a page mounts in isSpecificPage, the route being replaced stays in the tree while it animates out and assertions on text were matching both screens, seed_confirmation_test failed on finding two "Verify Seed" widgets
- Settles after the last pin digit, the gate sends itself away and returning early landed the caller's next navigation on a locked navigator, wallet_switching_test failed on the !_debugLocked assertion

Both are places where waiting for a widget to exist is not the same as waiting for the app to
be idle, which is what the sleeps were quietly doing.

* fix: Recognise every way a flutter drive attach fails and give tier1 a retry

This change:
- Matches the other wordings flutter drive uses when the driver never attaches, we had only the connect one and missed the isolate initialise, the service disappeared and the driver extension variants
- Gives tier1 the same single retry tier0 has, running it with none meant a driver that never attached was reported as a failing test

Two of the three tier1 failures on the last run were attaches that never happened, neither
of them reached any test code.

* fix: Sync status test watched the wrong status class, history scroll had no guard

This change:
- Accepts SyncronizingSyncStatus in the sync status suite, cw_core spells it without the h and it is a separate class from SyncingSyncStatus, so chains reporting it sat out the full three minute timeout and then failed saying the wallet never synced while printing Synchronizing
- Waits for the home scroll view before handing it to scrollUntilVisible, which calls single on the finder every drag and reported a missing scroll view as a bare Bad state: No element
- Skips the scroll entirely when the history tiles are already on screen

* fix: Test the transaction history the way the screen actually works

The suite looked for history tiles on the home page and scrolled for more when it found
none, which could never pass. The home page renders the history under a tab, and for a
wallet with tokens the assets tab is the one selected first, so the history section was
never built. It also shows a three item preview, itemsShort caps it at
shortHistoryLength, and everything else sits behind the All button in a modal.

This change:
- Opens the history tab before looking for tiles, wallets with no assets tab render the history with no tab bar at all and skip that step
- Asserts the preview never renders more than the three the view model hands it, instead of scrolling for tiles that were never coming
- Opens the All button and checks the full list in the modal, which nothing covered before
- Adds keys for the tab items, the All button, the single tab history bar and the modal root

* fix: Stop the runner wiping a real wallet install and document what CI does that the docs did not

Following app_config.sh and then running the tests locally clears com.cakewallet.cake_wallet
between every suite, which is a developer's own wallets. CI never hits this because the
workflow renames the app afterwards, a step that only existed in the workflow.

This change:
- Refuses to clear a package that is not named for testing, with the rename command in the message
- Adds that rename to the local prerequisites, next to the reason it matters
- Spells out the assets/images vector pass, compile_graphics.sh does not cover that folder and those vec files are neither committed nor ignored, so a fresh checkout fails on the welcome screen
- Notes that a second Gradle daemon from Android Studio deadlocks the build

* test: Make the tier0 and tier1 assertions check what they claim to

An audit of every robot against the screen it drives turned up assertions that pass without
telling you anything, the same shape as the transaction history suite looking for tiles on a
tab it never opened.

This change:
- Reads the receive address off the screen instead of the view model, the view model holding the right address says nothing about what the user is told to send to, and reads both the chunked and the plain render because only handling the first comes back empty
- Verifies a restored wallet knows the address its seed derives, restoring the wrong wallet from a correct seed used to look the same as success, and this found two stale addresses in the secrets
- Replaces the sync bar check, the key it asserted sits on a widget that renders for every status including none, so it was true whenever the home page was up
- Requires the All transaction view to render more than the home preview, it could not tell the two apart before
- Fails the keys page check when a wallet type matches none of its branches instead of passing having verified nothing

* refactor: Remove outdated items from integration tests

* test: Wait for the wallet to actually change instead of pumping a fixed half second

Tapping a wallet row does nothing when that wallet is already open, and the load runs behind
a progress overlay, so a tap that went nowhere looked the same as a successful switch.

This change:
- Waits for the app store to report the wallet before returning, and fails with a message when it never does

* test: Open wallet groups before looking for a wallet by name

Wallets that share a seed are listed as children of their group's tile and are not on screen
while it is closed, so switching to one would time out looking for a name that is only
rendered once the group is opened. Single seed wallets carry their own name as the tile
title, which is why this has not come up yet.

This change:
- Opens the group tiles when the wallet is not already on screen

* chore: Keep the receive address widget diff to the key it needed

A formatter pass rewrote the whole file, quotes, body style and trailing commas, for what was
a one line addition. Restored the original shape so the diff shows only the key.

* chore: Drop trailing whitespace left by the comment cleanup

* test: Cover the send screen refusing what it cannot send

Nothing covered the send screen, which is the one place in the app where getting it wrong
costs the user money. The property worth holding is that the swiper, the point of no return,
is only ever offered for a transaction the wallet actually built.

This change:
- Adds a tier0 suite driving an empty form, an address the chain cannot parse, and a well formed address on a wallet that has never held anything, and requires that none of the three ever produce a swiper
- Waits for the swiper and requires it not to arrive rather than checking once, the screen passes through syncing, building and failed states on the way and any of them can be the one you catch
- Notes in the docs that a merge from dev leaves the generated chain proxies and the assets/images vec files behind, which has broken the local build three times now

* test: Add send and swap dry runs and a flows mode that never spends

The funds suites were all or nothing: the only way to find out whether a funded wallet still
works was to spend from it. Almost everything worth checking happens before the swipe, the
wallet finds its balance, prices the fee and builds a transaction, or the provider returns a
live quote, and none of that costs anything.

This change:
- Adds a send dry run that stops at the swiper, reaching it means the transaction was really built
- Adds a swap dry run that stops before the swap button, creating a trade registers an order with the provider even though no funds move, so it goes no further than the quote
- Adds a dry-run value to FLOWS that runs both and neither of the spending suites, and makes it the default so a mis-click cannot send anything

* test: Cover a wallet name that is already taken being refused

Two wallets answering to the same name is how someone ends up sending from the wrong one, and
nothing checked that the form stops it.

This change:
- Adds a tier0 suite that creates a wallet, starts a second one and gives it the same name, and requires the form to refuse it and stay put
- Splits the walk to the naming form out of createAdditionalWalletFromWalletList so a suite can stop there instead of going through with the wallet

* test: Cover a seed the wallet cannot parse restoring nothing

Restoring from a seed the wallet does not understand either fails outright or, worse, derives
some other wallet the user has no keys for. The restore button is disabled until the words
check out and nothing checked that.

This change:
- Adds a tier0 suite that types twelve words outside the wordlist, presses restore, and requires the form to stay put
- Follows it with the real seed in the same run, so the refusal above cannot pass just because the form restores nothing for any seed at all
- Splits the walk to the restore form out of restoreFirstWalletFromSeed so a suite can stop there

* refactor: Make spending its own switch instead of a value hidden in flows

flows says which flow to run, so folding a dry-run value into it made the dropdown answer two
questions at once and buried the one that matters.

This change:
- Adds a spend input, off by default, and gates the broadcasting suites on it
- Puts flows back to all, send or swap
- Runs the dry runs whenever their flow is picked, they cost nothing either way

* chore: cleanup minor issues

* test: Cover one seed backing wallets on two chains

Wallet groups had no coverage at all, and the part that would break quietly is the seed: a
group member that derived its own seed instead of sharing one looks identical from the wallet
list. It is also the only way a wallet ends up inside a collapsed group tile, which is the
path switchToWallet handles and nothing exercised.

This change:
- Adds a tier0 suite that creates a solana wallet, adds an ethereum wallet to its seed, and requires both to report the same seed
- Switches back to the first afterwards, which only works by opening the group it now sits in
- Adds the flow for it, a child wallet skips the seed and verification screens for a page explaining it shares one, so it cannot reuse the normal creation steps
- Adds the one key the group page was missing, its next button

* test: Cover changing the pin replacing the one that unlocks the wallet

Nothing checked that changing the pin actually takes. Watching the setup screen close proves
nothing, the only evidence is the new pin opening something the old one guarded.

This change:
- Adds a tier0 suite that changes the pin and then unlocks the seed and keys page with the new one
- Goes through the pin gate on the way in, so it also covers the current pin being required before the change is allowed

* test: Cover changing the language, and make settings rows and pickers addressable

Writing this turned up two things in the app rather than the test.

Only ListItemRegularRow was given its keyValue as a widget key. Toggles, checkboxes,
dropdowns and selectors all took the same keyValue and dropped it, so every settings control
that is not a plain navigation row could not be found at all.

Picker named three item types and gave everything else an empty string, so a picker over
plain values, the language list among them, rendered every row with the same key.

This change:
- Passes keyValue through as a key for the other four row types
- Falls back to the item itself for the picker name, so each row is distinct
- Adds a tier0 suite that changes the language and requires the row to show the new one

* test: Cover switching the node the wallet talks to

Which node a wallet is pointed at decides what it sees, and a switch that quietly does not
take leaves someone on a node they believe they left. Nothing covered it.

This change:
- Adds a tier1 suite that reads the current node, switches to another one, confirms, and requires the wallet to be pointed somewhere new
- tier1 rather than tier0 because opening the page speed tests every node against the network

* test: Cover the address book keeping the address it was given

Pasting an address once and trusting it afterwards is the whole point of an address book, so
an entry that comes back changed is a way to lose money quietly. Nothing covered it.

This change:
- Adds a tier0 suite that saves a contact through the form and requires the stored address to match what was typed
- Checks the saved record rather than the rows, the list filters what it shows by the currency in play so a contact can be saved and correctly not on screen
- Adds keys for the add button, the name field, the currency picker, the address field and save

* fix: Key picker rows on a name that does not change with the language

Enumerable items fell through to toString, which is translated for some of them, so the
same row carried a different key depending on the language in use.

* test: Cover the fiat currency setting, transaction details and sending to a contact

This change:
- Adds a suite for turning the fiat api off and on, which is what decides whether the
currency setting is offered at all, then changes the currency through it
- Adds a suite that taps a transaction and checks the details that open belong to it
- Adds a suite that saves a contact and picks it from the send screen
- Adds a suite for restoring a 25 word monero seed, which takes a seed type and a restore
height the polyseed path never asks for
- Keys the address book button on the send screen so a test can reach it
- Lets SUITE_DIR take a single suite file, for iterating on one test
- Lists every suite and what it proves in the integration tests doc

* test: Cover renaming and deleting a wallet

This change:
- Adds a suite for renaming a wallet, including the refusal when the name is already held
by another wallet
- Adds a suite for deleting a wallet, checking it leaves storage and not only the list
- Keys the edit button in the wallet list and the name field, the two buttons and both
dialogs on the wallet edit page, none of which could be reached from a test before
- Fixes the wallets list robot, which looked for a single Wallets title even though the
navbar carries the same word, and looked for wallet names across the whole tree even
though every dashboard tab stays mounted in an IndexedStack

* ci: Report every integration test run to slack

This change:
- Posts a report to slack on every run, naming each tier's counts, duration and any suite
that failed, with the full list of what passed in a reply on the same message
- Adds a SUMMARY_FILE knob to the runner, which writes what it counted in a form the
report can be built from rather than parsing the run log
- Skips with a notice when SLACK_APP_TOKEN or SLACK_TESTS_CHANNEL is missing, and never
fails the gate when slack is unreachable
- Leaves the funds workflow alone, the new slack_notify input defaults to off

* chore: Removing unneeded items

* ci: Say which slack scope was missing when a report is rejected

A rejection carries the scope it wanted in a field of its own, and dropping it left the
warning saying missing_scope without saying what to go and add.

* ci: Report funds runs to the tests channel and say when slack refuses them

This change:
- Sends the funds report to SLACK_TESTS_CHANNEL, so both test workflows land in one place
and the apk channel is left to builds
- Checks the slack response, the post was going out unchecked so a rejected report looked
like a delivered one
- Builds the message from the environment instead of interpolating workflow inputs into
the shell, a quote in a dispatch input was enough to break the payload

* ci: Give the test reports their own slack app

Uploading apks and reporting test results are different jobs with different scopes, and
the name on a message is how anyone in the channel tells which one sent it. Both test
workflows now post through SLACK_TESTS_TOKEN, which only needs chat:write, and the apk
uploads keep SLACK_APP_TOKEN and its file scopes.

* fix: Restore the swap amount key and say when a suite never ran

The AnyPay redesign moved the deposit amount field into SwapAmountBox and it lost the key
the swap suite enters an amount through, so that suite could no longer reach it. Both
amount fields are keyed now, deposit and receive.

This change also:
- Records whether a failed suite failed on its own or because the driver never attached,
which is what happened to send_validation_test in run 31364715120 where the suite never
actually ran
- Rebuilds the slack report out of blocks, so the status is a heading, the tiers sit in
their own fields, failures name their reason and the run is a button rather than a bare
url

* perf: End an attempt early when the driver cannot attach

flutter drive says it is struggling to attach within about a minute and then, when it is
really wedged, sits there until TEST_TIMEOUT kills it. Run 31364715120 lost 20 minutes to
two attempts doing exactly that.

This change:
- Watches the attempt log and ends the attempt VOID_GRACE seconds after the driver first
reports trouble, 120 by default, so the retry starts on a fresh app instead of waiting
out the remaining eight minutes
- Starts that clock at the first complaint rather than at the attempt, since the attempt
spends its first minute building and installing
- Moves the marker list into one variable, the watchdog and the after the fact check were
going to drift apart otherwise

* perf: Drop the driver grace to 60s and take the whole drive down with it

Measured against run 31364715120: the 19 attempts that attached did so in under a second,
while the two that never attached had the warning out at 5 seconds. 60 leaves a wide
margin over a healthy attach on a runner that was already running slow, and saves another
minute on each dead attempt.

Ending the attempt now walks the process tree rather than signalling the wrapper. On linux
the drive runs under timeout, and a KILL to that cannot be forwarded, so the drive would
have been left holding the device just as the retry went looking for it.

* trigger another test run

* Triggering another run, its been green so far

* fix: Wait for the wallet to be ready before tapping send in the funds suites

The send button is disabled until isReadyForSend, which wants a synced wallet, but the
funds flow moves on as soon as a balance appears. Every funded chain was therefore tapping
a disabled button and then waiting ninety seconds for a confirm sheet that could never
open. The robot now waits on the same value the screen gates on, so a wallet that never
syncs says so instead of looking like a missing widget.

* test: Make a funds send failure say what went wrong and stop it spreading

A send that never reaches the confirm sheet was reported as a missing ConfirmSwiper, which
says nothing about the cause. It now reports the state of whichever sheet is up, what the
wallet holds, and the build error when the chain rejected the transaction.

Recovery between chains was a single pop, so the first chain to fail left the app somewhere
the next chain's restore could not start from and every chain after it failed too. It now
unwinds until the home page is back and stops the suite if it cannot get there.

* test: full testing of all the funded tests and fix issues that came up with them

* fix: update sync key to fix sync test

* fix: out of space error

* fix: integration test review issues

* fix: merge conflicts and update test suites

* fix: false test passes and add funded wallet passphrases
chore: remove unused integration test robot methods
feat: save integration test screenshots on Android
feat: pick the swap pair for the funds dispatch

* fix: Keep the runner output on the step log through a file descriptor

* fix: timeout because of runner crash

* test: handle new seed ui flow and fix hang for runner

* fix: emulator teardown not rendering succesfully
feat: use currency picker for selecting swap options for funded run selected swap currency

* test: add key for compact dot key for sync and link to robot

* minor fixes

* test: review fixes for integration tests

93/100 · StrongMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialaccess controldefensive validationseed or entropy pathsigning or wallet pathauthentication path
AI analysis · Low 26/100

This is a large commit that adds and reorganizes automated integration tests for the Cake Wallet app. Most of the changes are test code, CI workflow files, and small app-side widget key additions so tests can find on-screen elements. There is one minor production bug fix buried in the history: a Solana token-decimals default was corrected so amounts parse correctly. The commit does not appear to introduce a security vulnerability; if anything it improves quality assurance by adding many regression tests and hardening CI behavior.

Security candidatecharts (#3162)by malik1004x · b88fbf32 · Sep 22, 2026 · 94 filesMessage 49 · ThinInformational 22Details
Commit message · malik1004x

charts (#3162)

* charts (wip)

* charts (wip)

* wip

* add asset grid

* split files

* logic wip

* proper getPrices logic

* viewmodel (wip)

* charts

* remove unused import

* remove restricted import...?

* fix background gradient when scrolling

* add safeguards for broken db

* save new pin on removal

* add safeguards for concurrency

* add haptic feedback

* fix haptic feedback

* fix fiat ticker

* reduce chart padding

* add line touch indicator

* improve touch target size on range selector

* add date/time display when viewing past amount

* merge

* remove iconSvgPath reference

* merge

* fix state for date display

* merge

* auto-reformat

* only load charts when page is opened

* merge

* reformat and apply lints

* refactor to use `Money` instead of storing amount in `String`

* add slop comment

* fix exception on division by zero

* ci

* workaround toDouble being removed

* disable strict parsing and rounding

* fix abs()

* use new currency picker sheet

* safeguard for max flutter-supported decimals

* fix amount precision

* adjust to new buy/sell

* Update lib/new-ui/pages/charts_page.dart

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

* adjust buy/sell di

* replace -> ignore

* reformat

---------

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

49/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference! Too few words to establish purpose
Why it was queued
access controlcryptography-sensitive path
AI analysis · Informational 22/100

This commit adds a new cryptocurrency price-charts feature to the Cake Wallet app. It introduces screens, data models, a price API client, local database tables to cache prices, and related UI assets. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a normal feature addition. A few code-quality items (such as unimplemented error handling for some token types and network calls carrying an API key) are visible but do not by themselves prove an exploitable flaw.

Security candidateremove old ui (#3629)by malik1004x · d38c7481 · Sep 22, 2026 · 155 filesMessage 59 · ThinInformational 18Details
Commit message · malik1004x

remove old ui (#3629)

* remove old ui

* remove imports to nonexistent files

* remove old buy/sell

* remove unreachable pages

* readd Routes.exchange

* remove broken di

59/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 18/100

This is a large cleanup commit that removes the old user interface code from the Cake Wallet app and switches the app to use only the new UI. It deletes many old screens, view models, fonts, and related dependency-injection registrations. There is no direct security fix here; it is ordinary maintenance that reduces code size and removes unused/commented-out functionality such as the Yat emoji-id integration and old buy/sell/exchange pages. Because so much code is removed, there is a small risk that something useful was accidentally deleted or that a route now points to a missing page, but the diff itself does not show an exploitable vulnerability.

Security candidateCw 1624 trezor passphrase on trezor device instead of app (#3601)by Konstantin Ullrich · 98f58c28 · Sep 18, 2026 · 50 filesMessage 81 · StrongLow 26Details
Commit message · Konstantin Ullrich

Cw 1624 trezor passphrase on trezor device instead of app (#3601)

* feat: add support for Trezor device settings configuration and `AwaitingSettings` state in pairing flow

* fix ugly widgets

* trezor options ui

* feat: add support for Trezor on device passphrases

* chore: bump trezor_flutter deps

* fix: remove unused subtitle property in proceed_on_device_sheet [skip ci]

* chore: update trezor_flutter dependency to latest commit [skip ci]

* fix: set restore height and store wallet during initialization steps

---------

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

This commit adds a new option for Trezor hardware wallet users to enter their passphrase directly on the Trezor device instead of typing it into the Cake Wallet app. It also updates the pairing flow to ask users about auto-connect and passphrase settings before finishing setup. The change is a feature improvement for hardware wallet usability and appears intended to reduce exposure of the passphrase to the app. There is no clear security vulnerability in the diff, but the commit is partial: it depends on an updated external Trezor library whose full behavior is not shown, and it removes some old passphrase-handling code while adding new session logic.