Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This commit fixes a bug in the Cake Wallet Litecoin wallet where, when renaming a wallet, stored MWEB (a privacy feature for Litecoin) transaction records were being copied to a new storage box by reusing the exact same object references. …
Data migration now clones objects instead of sharing referencesPrevents potential state corruption when renaming Litecoin walletsNo explicit input validation or cryptographic change present
This is a routine update to the project's automated iOS build pipeline. It changes which Apple computer (runner) and Xcode version are used to compile and upload the iPhone app, so the app meets Apple's upcoming App Store requirement to us…
This commit is a routine mix of small fixes and test-tool updates. It makes a UI key more specific to avoid list-item conflicts, adds a safety check before showing a post-transaction popup, updates a test helper to match new app settings, …
Flutter BuildContext used across async gap now guarded by context.mountedNo explicit security keywords, CVE references, or advisory links in commit or titleChanges are split across UI, test tooling, and fixture scripts with no coherent security theme
This is a large accessibility and test-automation improvement for the Cake Wallet Flutter app. It adds stable identifiers to buttons, text fields, lists, and dialogs so screen readers and automated UI tests can find them. The patch also re…
Removed user-data interpolation from accessibility identifiers (tx ids, wallet names, seed words, addresses)Added stable, index-based or enum-based semantics identifiers across UI componentsAdded custom lints and CI workflow to prevent future user-data interpolation in test keys
This commit adds three new automated testing pipelines for the Cake Wallet mobile app: one for Android, one for iOS, and a weekly overnight test. These are explicitly marked as 'reply-only' experiments, meaning a failure will not block rel…
New CI/CD pipeline handling wallet seed phrases and API keysUse of `NO_REPLY` / `continue-on-error: true` to avoid blocking mergesExplicit mitigation: avoids `npx` on macOS to prevent environment-variable leakage via process title
This is a large cleanup of how the app labels its on-screen buttons and fields for automated testing and accessibility tools. Previously, many test labels were accidentally built from private user data such as wallet names, transaction IDs…
Accessibility identifiers derived from PII/sensitive data (wallet names, transaction IDs, seed words, addresses) are replaced with static or index-based identifiersNew custom lint rule no_string_interpolation_in_test_key blocks string interpolation in test keys except for int indexes and enum .nameNew custom lint rule require_test_key_semantics_identifier ensures framework interactive widgets with _key keys expose a Semantics identifier
This is a very large code refactor of the cryptocurrency swap/exchange feature in Cake Wallet. It rewrites how exchange rates are fetched, how trades are created and tracked, and how trade history is stored in the local database. The commi…
Large-scale rewrite of trade creation, rate fetching, and status monitoringDatabase schema migration for Trade table with data reconstruction from old columnsNew amount parsing helper (Money.safeParse) and exchange-rate math (ExchangeRate.fromAmounts)
This commit expands Cake Wallet's Lightning Bitcoin feature so it works across multiple Bitcoin accounts instead of being locked to the primary account only. It also fixes address selection so the app picks an unused Segwit address that be…
Account isolation logic changed: Lightning and Segwit address selection now account-awarePrevious code could return a Segwit address from a different account than the one currently selectedRemoval of hard-coded account index checks suggests prior account-boundary assumptions were too restrictive
This commit is a large internal refactor of how Bitcoin-style wallets in Cake Wallet store and derive account keys. It replaces scattered maps of HD keys with a single shared 'ElectrumAccounts' model, initializes those keys earlier during …
Refactor of BIP32 HD key derivation and account key storage across multiple coin modulesWallet keys view model now exposes master xPrv and xPub instead of per-account private keyChange in how legacy change HDs are identified, with a new regression test for Litecoin MWEB change addresses
This commit deletes four leftover Android Java files that were no longer used. The app's namespace was already fixed to 'com.cakewallet.cake_wallet', so these old copies of the main activity and application class under different package na…
This commit fixes visual layout bugs in the Cake Wallet mobile app where long Tamil translations were being drawn off-screen or clipped. It also fixes a broken unit test by adding a missing mock object. There is no security vulnerability h…
This commit adds new language translations (Bengali, Marathi, Tamil, Telugu), fixes Hindi translations, and introduces automated tools to check translation quality. It also makes a small formatting fix so cryptocurrency amounts display wit…
No changes to cryptographic, authentication, networking, or storage codeNo permission changes or new entitlementsNo changes to dependency versions or external URL endpoints
This commit is a routine user-interface redesign for the Cake Wallet app. It adds a new 'More Actions' menu (a floating plus button), moves Contacts and Buy/Sell options into that menu, and introduces first-time explainer pop-ups for gift …
No security-relevant code changes identifiedUI-only refactor with no new network, storage, or crypto logicNew URL launch to cakepay.com in gift card explainer uses standard url_launcher external application mode
This commit improves accessibility for screen-reader users. It adds spoken labels to buttons that were previously unlabeled, announces which cryptocurrency each wallet holds, removes a duplicate invisible tap target, and makes the currentl…
This commit improves screen-reader accessibility in the Cake Wallet mobile app. It makes settings switches announce their name (e.g., 'Auto generate addresses, switch, off') and makes choice options like 'Enabled / Tor only / Disabled' tel…
This commit makes small GitHub workflow and documentation tweaks. It adds read-only permissions to four pull-request check workflows, deletes an already-commented-out lint workflow, and updates a Windows installer filename and release note…
Workflow least-privilege hardening: four PR workflows now declare read-only repository permissionsRemoval of an inactive lint workflow that contained commented-out build steps and external download commandsDocumentation-only update for Windows installer filename and release history
This commit is a routine version bump and changelog update for the Cake Wallet/Monero.com v6.5.4 release candidate. It updates translated changelog text, version/build numbers across Android, iOS, Linux, and macOS, and makes minor UI fixes…
This commit fixes a bug in how Cake Wallet signs Bitcoin-style messages. Previously, the app could not correctly sign messages with 'change addresses' (a special type of address used when sending leftover funds back to yourself). The fix m…
Refactor centralizes address validation and derivation-path construction for hardware signingChange addresses are now included in address lookup, fixing a functional signing bugTaproot and MWEB addresses are explicitly rejected for message signing
This commit fixes a bug in Cake Wallet's Bitcoin message signing. Previously, if a user chose a silent payment address (a newer privacy-focused Bitcoin address type), the app would still sign the message using the wallet's main key. That s…
Cryptographic signature produced for a different identifier than the one presented to the userSilent fallback to main wallet key when selected address cannot be derivedMessage signing bypass for silent payment / unheld addresses
This commit is a straightforward user-interface performance fix. It wraps each tab of the app's main dashboard in a Flutter widget called TickerMode, which pauses animations in tabs that are not currently visible. Before the change, a load…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityStrip EVM chain id from QR scanned into swap receive address (#3756)by claude[bot] · 1772b762 · Oct 24, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · claude[bot]
Strip EVM chain id from QR scanned into swap receive address (#3756)
The swap receive address QR scanner assigned the raw URI path, so an EIP-681 QR like ethereum:0x...@1 left "@1" on the address. Parse the scanned URI with PaymentRequest.fromUri, the same parser the exchange card already uses, so the chain id is removed.
2caafc677 dropped the method signature line in cw_core/lib/lnurl.dart, leaving its body directly inside `class LNURL`. cw_core no longer parses, so mobx_codegen fails ("90:5: Expected a class member") and every app, unit_tests and internal-build CI job on dev and open PRs goes red.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
98/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 20/100
This commit fixes a simple Dart programming mistake where a method declaration line was accidentally deleted, causing the app code to fail compilation. It restores the missing line so the method works again. There is no security issue here—just a build break on the development branch.
AI review queuedfix: convert decoded JSON list instead of casting in solana_signAllTransactions (#3671)by KShot · 03f27548 · Oct 22, 2026 · 1 fileMessage 93 · StrongLow 37Details
Commit message · KShot
fix: convert decoded JSON list instead of casting in solana_signAllTransactions (#3671)
params['transactions'] arrives as decoded JSON (List<dynamic>), so the hard cast 'as List<String>' threw a TypeError on every solana_signAllTransactions request, which the handler mapped to MALFORMED_REQUEST_PARAMS after the user had already approved. Convert with List<String>.from(... as List<dynamic>) instead — the same pattern already used for decoded JSON in lib/buy/buy_quote.dart. Malformed (non-string) elements still throw inside the same try block, so invalid requests are still rejected as malformed.
Fixes #3659
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 37/100
This commit fixes a bug in Cake Wallet's Solana WalletConnect feature. When a user approved signing multiple Solana transactions, the app incorrectly tried to force the incoming transaction list into a specific Dart type (List<String>), but the data arrived as a generic decoded JSON list (List<dynamic>). This caused a TypeError every time, which the app then reported to the connected dApp as 'MALFORMED_REQUEST_PARAMS' even though the user had already approved. The fix safely converts the list to the expected string type instead of hard-casting it, restoring normal functionality for multi-transaction signing requests.
AI review queuedfeat: add unit tests CI workflow (#3640)by David Adegoke · 49b48988 · Oct 22, 2026 · 12 filesMessage 98 · StrongInformational 15Details
Commit message · David Adegoke
feat: add unit tests CI workflow (#3640)
* feat: add unit tests CI workflow
* fix: update workflow to pull prebuilt dependencies and handle cache misses
* fix: update unit tests job to the new ci and fix the red tests
---------
Co-authored-by: Omar <omarh.ismail1@gmail.com>
98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a new automated unit-test workflow to the project's GitHub Actions CI pipeline and fixes several existing tests that were failing. It also makes a small UI improvement (adding a 'truncateLabel' option for settings rows) and updates a secrets-import helper to include Bitcoin configuration. There is no security-relevant change here.
AI review queuedmiscellaneousby Omar · 2caafc67 · Oct 22, 2026 · 4 filesMessage 18 · OpaqueInformational 18Details
Commit message · Omar
miscellaneous
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100
This commit is mostly housekeeping. It adds documentation showing users how to verify that downloaded Cake Wallet files are genuine, updates the README to point to that guide, expands .gitignore to avoid accidentally committing signing secrets, and adds a 10-second timeout to a Lightning/lnurl network request so the app won't hang forever if a server is slow or missing.
Lower-priorityRename Moonpay Cash App payment method to Cash App Pay (#3748)by Seth For Privacy · 75eee6ba · Oct 21, 2026 · 1 fileMessage 58 · ThinTriage 0Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedWallet picker follow-ups to #3717 (#3729)by Omar Hatem · aaaea05e · Oct 21, 2026 · 7 filesMessage 76 · AdequateLow 48Details
Commit message · Omar Hatem
Wallet picker follow-ups to #3717 (#3729)
* fix(address-book): wallet picker follow-ups to #3717
- addressForBuy now skips hiddenAddresses, like the receive page's own address selection. Every swap hides its refund address, so on the Lightning/Silent Payments page the picker's on-chain "Active" entry (from #3717) could be that refund address. Buy-provider payouts stop landing on hidden addresses too. - The picker decided "active" with name.contains('Active'), but the name is localized first ("Aktiv", "Activo", ...), so BTC/LTC wallets were missing from it in every language but English. WalletContact now carries the raw address-map label and the filter matches on that. - On the Silent Payments page the SP address is marked active again, next to the on-chain one. The picker offers SP addresses only when the caller opts in; the send page does for software Bitcoin wallets. Hardware/air-gapped senders can't build SP outputs, and swap or Lightning-withdraw inputs never opt in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(address-book): trim comments; gate SP picker on hasSilentPaymentsScanning
Bugbot: wallets restored from an xpub have no hardwareWalletType, so they were offered Silent Payments addresses they can't pay.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(address-book): offer SegWit instead of Silent Payments/MWEB in wallet picker
Reverts the Silent Payments opt-in. A Bitcoin wallet on its Silent Payments or Lightning page, and a Litecoin wallet on its MWEB page, now expose a plain SegWit address as 'Active', so every sender gets an address it can pay.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(litecoin): use addressForBuy for the MWEB page's address-book entry
Litecoin's addressForBuy now returns a regular address on the MWEB page, so the buy flow and other wallets' address books both get an address every sender can pay.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(address-book): offer a Litecoin wallet's MWEB address when it's on the MWEB page
A user who left wallet A on MWEB expects other wallets to send to that MWEB address. Litecoin's addressForBuy still returns a regular address there, so the buy flow is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(bitcoin): drop the unneeded Litecoin activeAddress parameter
Litecoin only has P2WPKH and MWEB pages, so its active address is always `address`. electrum_wallet_addresses.dart is back to dev's version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 48/100
This commit fixes address-selection bugs in Cake Wallet's address book and wallet picker. Before the fix, the app could suggest Bitcoin/Litecoin addresses that the sending wallet couldn't actually pay (for example, a hidden swap refund address, a Silent Payments address for a hardware wallet, or a Litecoin MWEB address). It also relied on the English word 'Active' in a translated name, so non-English users saw fewer wallets. The patch makes the picker choose only plain, broadly-supported addresses for buy/exchange flows and uses an untranslated label to decide which address is active.
Lower-prioritymake model_generator less annoying (#3745)by malik1004x · 970e47a5 · Oct 20, 2026 · 1 fileMessage 53 · ThinTriage 0Details
Commit message · malik1004x
make model_generator less annoying (#3745)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Security candidatefix: make the wallet-access 2FA step non-dismissable (CW-1711) (#3742)by Seth For Privacy · 5aec35b4 · Oct 20, 2026 · 1 fileMessage 93 · StrongModerate 51Details
Commit message · Seth For Privacy
fix: make the wallet-access 2FA step non-dismissable (CW-1711) (#3742)
* fix: make the wallet-access 2FA step non-dismissable
TotpAuthCodePage ignored isClosable since the New Design rewrite (#2797): the back arrow was always shown and popped the route. On the resume lock that returned to the app without the TOTP code; on cold start it left a black screen. The Android back gesture could pop it too.
Hide the back arrow and block pops with PopScope when isClosable is false.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the 2FA page title when the back arrow is hidden
Without a leading button ModalTopBar's row has no height and clips the title.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access control
AI analysis · Moderate 51/100
This commit fixes a bug in Cake Wallet's two-factor authentication (2FA) screen. Previously, when the app required a 2FA code to unlock the wallet, users could bypass that requirement by pressing the back arrow or using Android's back gesture. The fix removes the back arrow and blocks the back gesture when the screen is meant to be mandatory, so the wallet cannot be accessed without entering the 2FA code.
AI review queuedCW-1509: Add BTCMap.org to apps (#3715)by Patrick · 75fa8961 · Oct 20, 2026 · 33 filesMessage 68 · AdequateInformational 20Details
Commit message · Patrick
CW-1509: Add BTCMap.org to apps (#3715)
* add BTCMap.org to apps
* launch btcmap.org/apps instead of btcmap.org
* localize btcmap subtitle
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 20/100
This commit adds a new promotional tile called "BTC Map" to the app's dashboard. Tapping it opens the website btcmap.org/apps in the phone's external browser. It also adds translated subtitle text for the new tile in many languages. There is no security vulnerability visible in the change.
AI review queuedclearer error when restoring unavailable wallet from qr (#3743)by malik1004x · c579e50e · Oct 20, 2026 · 1 fileMessage 58 · ThinLow 32Details
Commit message · malik1004x
clearer error when restoring unavailable wallet from qr (#3743)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 32/100
This commit adds a clearer error message when a user tries to restore a wallet type that is not available in the current app. It prevents confusing behavior by throwing a specific exception early in the QR-code restore process, rather than letting the restore proceed with an unsupported wallet type.
AI review queuedupdate translation :3by Omar · d4739e47 · Oct 19, 2026 · 30 filesMessage 28 · OpaqueInformational 15Details
Commit message · Omar
update translation :3
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit only updates translated text strings in the app. It adds or rewrites a user-facing message explaining that the Zano cryptocurrency will be removed from Cake Wallet in a future version because of maintenance burden. There are no code, logic, or security changes.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityfix: zip slip in backup (#3710)by cyan · e0d2ba25 · Oct 19, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · cyan
fix: zip slip in backup (#3710)
65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityShow significant decimals for low-value token prices in charts (#3712)by claude[bot] · 4f792ca4 · Oct 19, 2026 · 4 filesMessage 81 · StrongTriage 0Details
Commit message · claude[bot]
Show significant decimals for low-value token prices in charts (#3712)
* Show significant decimals for low-value token prices in charts
Chart prices were always formatted with 2 decimals, so low-value tokens such as SHIB showed 0.00. Values below 1 now get enough decimals to show two significant digits (e.g. 0.000012); everything that already rendered with 2 decimals is unchanged. UI formatting only.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tRHpox4mz8ZttHqrSgKzz
* Move chart low-value formatting into Money.toStringWithPrecision
Replace the chart-only extension with an optional meaningfulDecimals param on Money.toStringWithPrecision: for non-zero values below 1 it shows that many digits after the leading fraction zeros (max 12 fraction digits). Without the param, output is unchanged. The chart crosshair now formats the touched point's Money instead of the double y value.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tRHpox4mz8ZttHqrSgKzz
* Throw when meaningfulDecimals is combined with useBaseUnit
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tRHpox4mz8ZttHqrSgKzz
---------
Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: malik1004x <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
Security candidatefix out of bounds index in card customizer (#3733)by malik1004x · 71cd9cf6 · Oct 19, 2026 · 1 fileMessage 58 · ThinInformational 22Details
Commit message · malik1004x
fix out of bounds index in card customizer (#3733)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Informational 22/100
This commit fixes a UI bug in Cake Wallet's card customizer. Previously, when picking a card color, the app could compute an index that pointed past the end of the available color list, which could cause a crash or display glitch. The fix uses the actual filtered color list when computing the selected index and falls back to the first color instead of an invalid position.
Security candidatefix: honor Require PIN after timeout on resume (CW-1707) (#3726)by Seth For Privacy · d665e308 · Oct 19, 2026 · 3 filesMessage 98 · StrongModerate 59Details
Commit message · Seth For Privacy
fix: honor Require PIN after timeout on resume (CW-1707) (#3726)
* fix: honor Require PIN after timeout when returning from background (CW-1707)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: ignore stale requireAuth result once the app is backgrounded again
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: ask for the PIN when the last auth time can't be read (CW-1707)
On Android the secure storage read can throw: a value that fails to decrypt comes back as a PlatformException. requireAuth() let that escape, so the resume handler never set _requestAuth and the app came back without the PIN. Return true instead, so every caller asks for the PIN when the timeout can't be checked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: arm Require PIN after lock in the session a wallet is created or restored (CW-1709) (#3736)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Omar <omarh.ismail1@gmail.com>
98/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Moderate 59/100
This commit fixes a bug in Cake Wallet where the app could resume from the background without asking for the PIN, even when the user had turned on 'Require PIN after timeout.' In some cases, especially on Android, a secure-storage read error could silently prevent the lock screen from appearing. The patch makes the app ask for the PIN whenever the last-auth time cannot be read, and it also tightens the lifecycle handling so the PIN prompt is honored when returning from the background after a wallet is created or restored.
* iOS only, display why keychain failed to get the read key of PIN
* offer app reset if restored from icloud backup and the keychain data is missing
* fix review comments
88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
authentication path
AI analysis · Low 33/100
This commit improves how Cake Wallet handles a specific iOS situation: when a user restores their phone from an iCloud backup, the app data comes back but the iOS Keychain (which stores the PIN and wallet passwords) does not. Previously the app could silently fail or behave oddly. Now it detects the missing keychain, explains the situation to the user, and offers to wipe the unusable local wallets so the user can restore them with their recovery phrases. It is a defensive UX and error-handling improvement, not an attack vulnerability.
Lower-priorityfix: authenticate to github.com (#3739)by cyan · 843fc29e · Oct 19, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · cyan
fix: authenticate to github.com (#3739)
65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Security candidatefix: open external links outside the app so the PIN lock can show (#3737)by Seth For Privacy · f80ac4df · Oct 19, 2026 · 9 filesMessage 93 · StrongModerate 64Details
Commit message · Seth For Privacy
fix: open external links outside the app so the PIN lock can show (#3737)
Links opened with the default launch mode use SFSafariViewController on iOS. While it covers Flutter no lifecycle events reach Dart, so returning from the background showed the browser without asking for the PIN.
Refs GHSA-329m-5v92-587r, CW-1707
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlsigning or wallet path
AI analysis · Moderate 64/100
This update changes how the app opens web links so they launch in the device's regular browser instead of an embedded browser sheet. The problem was that on iOS the embedded sheet (SFSafariViewController) hid the app from normal background/foreground events, so when a user returned from viewing a link the wallet reappeared without asking for the PIN. That could let someone with brief physical access to an unlocked phone browse back to the wallet without re-entering the PIN. The patch forces links to open externally, restoring the normal app lifecycle and letting the PIN lock screen appear.
AI review queueduse on-chain address in wallet picker (#3717)by Patrick · df6051b5 · Oct 18, 2026 · 1 fileMessage 53 · ThinInformational 23Details
Commit message · Patrick
use on-chain address in wallet picker (#3717)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100
This commit changes how Cake Wallet picks which Bitcoin-style address to display as 'Active' in the wallet picker. Previously, the app always used the main on-chain address, even when the user was on a Lightning or Silent Payments address page. Now, for Lightning and Silent Payments pages, it uses the on-chain address associated with those features, and passes that chosen address into the address-type labeling logic. This is a UI/UX consistency fix rather than a cryptographic or network security change. It could affect what address a user sees or copies, but there is no direct evidence it enables theft or unauthorized transactions.
buy.cakepay.com no longer resolves; the macOS Cake Pay tile opened it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cake pay): link terms to cakepay.com/terms
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
Security candidatevalidate swaptrade networks against /get-coins (#3724)by Patrick · 4ef592e4 · Oct 16, 2026 · 3 filesMessage 81 · StrongModerate 58Details
Commit message · Patrick
validate swaptrade networks against /get-coins (#3724)
* validate swaptrade networks against /get-coins
* fix swaptrade order status decoding + error handling
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Moderate 58/100
This commit changes how Cake Wallet's SwapTrade exchange integration validates which cryptocurrencies and networks are supported. Instead of relying on a hardcoded internal list of network names, it now fetches the supported coins and networks from the SwapTrade API at runtime and validates the user's chosen currency/network against that live list. It also improves error handling and fixes how trade statuses are decoded. The change reduces the risk of sending funds on an unsupported or mismatched blockchain network (which can cause loss of funds), but the commit itself is a defensive correctness fix rather than a confirmed vulnerability patch.
Lower-priorityfix navbar index calculation (#3718)by malik1004x · 017f734f · Oct 16, 2026 · 1 fileMessage 53 · ThinTriage 0Details
Commit message · malik1004x
fix navbar index calculation (#3718)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityfix(coin-control): show Blockchair in Litecoin explorer label (#3725)by Seth For Privacy · 17cbe273 · Oct 15, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · Seth For Privacy
fix(coin-control): show Blockchair in Litecoin explorer label (#3725)
PR #3705 switched Litecoin unspent-coin explorer links to Blockchair, but the row subtitle still said "View Transaction on Earlyordies.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