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.
AI review queuedadd paddingby Robert Malikowski · 90cbf677 · Jul 13, 2026 · 5 filesMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
add padding
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine UI polish: it adds bottom padding to a transaction history list and renames an internal counter from 'enabledProviders' to 'enabledProvidersCount' to make the code clearer. There is no security change.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 44/100
This commit fixes two bugs in Cake Wallet's exchange flow. First, when creating a trade record for the NEAR Intents exchange provider, the app was accidentally recording the 'from' currency as both the source and destination currency. Second, the code that checks whether the user's wallet can send funds for a trade was refactored to return error strings instead of throwing exceptions, and logging of those errors was moved to the caller. The first fix is a real functional bug that could mislead users about what they are receiving in a trade. The second is mostly a code-quality and reliability improvement.
✓ 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 20/100
This commit wraps a lightning balance lookup in a try/catch so that if the lookup fails, the app logs an error instead of crashing or throwing an unhandled exception. It is a defensive reliability fix; there is no direct evidence it fixes an exploitable security vulnerability.
AI review queuedImprove how wallets are renamed. (#3352)by Omar Hatem · 00088502 · Jul 12, 2026 · 16 filesMessage 76 · AdequateLow 32Details
Commit message · Omar Hatem
Improve how wallets are renamed. (#3352)
* Improve how wallets are renamed. affected wallets (Electrum-like) (BTC, LTC, BCH, Doge)
* more improvements also added Solana, Tron, EVM
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 32/100
This commit refactors how Cake Wallet renames cryptocurrency wallets. Previously, each wallet type had its own rename code that opened the wallet, copied specific files, and deleted the old directory. The new code centralizes the file-copying logic and makes the process more consistent across Bitcoin-like coins, Litecoin, Bitcoin Cash, Dogecoin, EVM chains, Solana, and Tron. The change appears to be a code-quality and reliability improvement rather than an obvious security fix, but it does address some risky patterns in the old rename implementation—such as deleting the old wallet directory before confirming the new one is valid, and not checking whether the destination wallet already exists.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit changes the source of a software dependency (ledger-usb-plus) from a third-party developer's repository to Cake Wallet's own fork, and updates which version is used. The stated reason is to fix Android CI (continuous integration). There is no direct evidence in the commit that this is a security fix, but switching dependency sources can carry supply-chain security implications that are worth reviewing.
AI review queuedfix styling on new wallet type selection (#3392)by malik1004x · f4b17e33 · Jul 10, 2026 · 1 fileMessage 53 · ThinInformational 15Details
Commit message · malik1004x
fix styling on new wallet type selection (#3392)
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 15/100
This commit is a purely cosmetic UI fix for the wallet type selection screen in the Cake Wallet app. It wraps a list container in a rounded clipping widget, slightly increases row height from 48 to 50 pixels, and adjusts indentation. There is no security-relevant change.
payjoin: exclude 0-conf inputs from receiver candidates (#3389)
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 48/100
This change stops Payjoin transactions from using unconfirmed (0-confirmation) coins as inputs when the wallet is acting as the receiver in a Payjoin swap. Before the fix, the receiver could accidentally propose or sign a Payjoin that relied on coins that had not yet been mined into a block. Such coins can disappear, be double-spent, or get replaced, which could cause the Payjoin to fail, be invalid, or expose the receiver to loss or confusion. The fix adds an optional 'confirmed only' filter and turns it on for Payjoin receiver candidate inputs.
AI review queuedfeat: harden spam detection for solana and evm (#3322)by David Adegoke · a7073df4 · Jul 10, 2026 · 5 filesMessage 93 · StrongModerate 51Details
Commit message · David Adegoke
feat: harden spam detection for solana and evm (#3322)
* feat: harden spam detection for solana and evm
* fix: guard scam/impersonator tokens from auto-enabling on EVM and Solana
* feat: enhance token property validation for scam detection
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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 51/100
This commit strengthens the wallet's automatic detection and handling of scam, spam, and impersonator tokens on Ethereum-compatible (EVM) chains and Solana. It adds checks for suspicious names/symbols (e.g., fake 'ETH', 'SOL', 'USDC', or tokens with 'airdrop', 'claim', URLs), prevents auto-enabling tokens that look like well-known coins but aren't verified, and uses Moralis API data such as price, value, verified-contract status, and security score to decide whether a discovered token should be shown as enabled. It also re-runs a one-time cleanup on existing tokens to reclassify any previously missed scams. There is no direct exploit fixed in the diff; rather, it is a defensive hardening change against social-engineering/token-spam attacks.
AI review queuedif input transactions are not all fetched correctly or had a failure,… (#3353)by Omar Hatem · 910a5cd9 · Jul 8, 2026 · 3 filesMessage 81 · StrongLow 34Details
Commit message · Omar Hatem
if input transactions are not all fetched correctly or had a failure,… (#3353)
* if input transactions are not all fetched correctly or had a failure, still parse the transaction correctly instead of skipping it
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit changes how Cake Wallet handles Bitcoin transactions when it cannot fetch all of their 'input' transaction data from the Electrum server. Previously, such transactions were skipped entirely and not shown in the wallet. Now they are still parsed and displayed, but with a warning ('Transaction has missing data') and a null fee. The change also makes the list of input transactions nullable and adds null checks in fee-calculation and replace-by-fee code paths, throwing errors if input data is missing there. This is primarily a robustness/usability fix, but it touches transaction parsing and fee logic, which are security-sensitive areas.
✓ Descriptive subject✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 39/100
This is a large code refactor of Cake Wallet's address resolver feature, which turns human-readable names (like Twitter handles, ENS domains, or email-style addresses) into cryptocurrency addresses. The change reorganizes existing lookup logic into a cleaner provider/service pattern and adds new address sources such as Nostr, BIP353, and Zcash names. It is primarily a structural rewrite rather than an obvious security fix, but because it touches many parts of how the app decides where to send money, any bugs in the new resolver could lead to payments going to the wrong address.
AI review queuedfeat: add lightning preimage to transaction detailsby Konstantin Ullrich · 6cb31493 · Jul 6, 2026 · 3 filesMessage 62 · AdequateInformational 18Details
Commit message · Konstantin Ullrich
feat: add lightning preimage to transaction details
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit adds a new piece of information—the Lightning Network payment preimage—to the transaction details screen. The preimage is a proof that a Lightning payment completed, and it is already stored in the wallet's existing payment data. The change simply displays it to the user, similar to showing a receipt number. There is no indication it introduces a security vulnerability.
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 21/100
This commit contains three small, unrelated fixes. One adds a safety catch around a Lightning wallet disconnect call so the app doesn't crash if disconnect fails. Another trims spaces and trailing currency text from amount inputs before converting them to numbers, which could prevent user input errors or unexpected parsing. The third is an Italian translation correction for the word 'change'. There is no clear security vulnerability being patched.
AI review queuedbetter error msgby Robert Malikowski · c3545b13 · Jul 3, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Robert Malikowski
better error msg
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply changes an error message shown to users when no cryptocurrency exchange provider can create a quote. Instead of a generic failure message, the app now tells the user which specific cryptocurrency could not be quoted. There is no security issue here.
AI review queuedwrap HistoryTopBar in Observerby Robert Malikowski · 47431246 · Jul 3, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Robert Malikowski
wrap HistoryTopBar in Observer
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine Flutter UI fix. It wraps a top bar widget in an 'Observer' so the interface automatically updates when the underlying app state changes. There is no security relevance visible in the change.
AI review queuedlayout fixby Robert Malikowski · 7b17459e · Jul 3, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
layout fix
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This is a minor user-interface layout fix. It swaps which corner of a history page header is rounded based on a setting, reduces vertical padding slightly, and only shows a divider line when the bottom is not rounded. There is no security relevance visible in the change.
AI review queuedfix decimals exceptionby Robert Malikowski · 72b0844f · Jul 3, 2026 · 1 fileMessage 28 · OpaqueInformational 23Details
Commit message · Robert Malikowski
fix decimals exception
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 23/100
This is a small bug-fix patch in Cake Wallet's buy/sell cryptocurrency screen. It rounds the calculated crypto amount to the correct number of decimal places before converting it into a Money object. Without the fix, certain exchange rates or fiat amounts could produce a value with too many decimal places, causing a 'decimals exception' (an app crash or error). The change is defensive and improves reliability, but it does not appear to be a security vulnerability on its own.
AI review queuedlayout fixby Robert Malikowski · 1af6ab00 · Jul 3, 2026 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
layout fix
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a purely cosmetic UI layout fix. It adds a rounded-bottom toggle to a history top bar widget and adjusts padding so the bar looks correct when there are no items below it. There is no security relevance.
AI review queuedreformatby Robert Malikowski · 1f4054d6 · Jul 3, 2026 · 7 filesMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
reformat
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is purely a code reformatting (whitespace and indentation cleanup) across seven user-interface files. It does not change app behavior, fix a bug, or alter security logic. The only non-whitespace change is a minor adjustment to the exception handler's debug-mode ignore condition, which is also a low-risk formatting/condition restructuring with no security impact.
AI review queuednew buy/sellby Robert Malikowski · 72c28991 · Jul 3, 2026 · 25 filesMessage 28 · OpaqueInformational 15Details
Commit message · Robert Malikowski
new buy/sell
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit is a routine feature update that redesigns the buy/sell cryptocurrency flow in the Cake Wallet app. It adds new screens for selecting amounts, providers, payment methods, confirming trades, and redirecting to third-party payment services. It also updates icons and translations. There is no clear security vulnerability in the code changes themselves, but the commit touches code that handles financial transactions and redirects to external providers, which is always a sensitive area.
AI review queuedfix evm decimals in historyby Robert Malikowski · bfeae1ec · Jul 1, 2026 · 1 fileMessage 45 · ThinInformational 18Details
Commit message · Robert Malikowski
fix evm decimals in history
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit fixes how many decimal places are shown for EVM (Ethereum-compatible) token amounts in the transaction history screen. Previously, the app likely showed the wrong number of decimals, making token amounts appear much larger or smaller than they actually are. This is a user-interface bug, not a way to steal funds or attack the wallet.
AI review queuedfix date format in tx detailsby Robert Malikowski · 46cda778 · Jul 1, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Robert Malikowski
fix date format in tx details
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a tiny UI fix that changes how the date is displayed on a transaction details screen. It swaps one date-formatting helper for another so the date appears in the user's chosen language. There is no security issue visible in the change.
AI review queuedwipby Robert Malikowski · afbc6db0 · Jul 1, 2026 · 6 filesMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
wip
0/100 · OpaqueMessage clarity
! Generic or placeholder subject! Too few words to establish purpose! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a work-in-progress (WIP) refactor of the buy/sell cryptocurrency flow in the Cake Wallet app. It restructures how the buy/sell mode is passed through the dependency injection system, replaces some UI placeholders, and adds a new custom amount input widget. There is no indication of a security fix or vulnerability being addressed.
AI review queuedwipby Robert Malikowski · a2a05002 · Jul 1, 2026 · 5 filesMessage 0 · OpaqueInformational 18Details
Commit message · Robert Malikowski
wip
0/100 · OpaqueMessage clarity
! Generic or placeholder subject! Too few words to establish purpose! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100
This commit is a routine work-in-progress UI feature for buying and selling cryptocurrency inside the Cake Wallet app. It adds a new screen where users can pick preset fiat amounts (like $50, $100, $500) or enter a custom amount. There is nothing in the changes that fixes a security bug, opens a vulnerability, or handles sensitive data in a risky way. It is normal product development code.
AI review queuedwipby Robert Malikowski · 0c469f20 · Jun 30, 2026 · 4 filesMessage 0 · OpaqueInformational 15Details
Commit message · Robert Malikowski
wip
0/100 · OpaqueMessage clarity
! Generic or placeholder subject! Too few words to establish purpose! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a work-in-progress (WIP) UI change for Cake Wallet. It adds a new buy/sell amount page, wires it into the app's dependency injection system, and connects a selector modal so users can open the new page. There is nothing in the code that touches security-sensitive behavior such as sending funds, storing keys, handling passwords, or network requests. It is purely user-interface scaffolding.
AI review queuednew buy/sell flow (wip)by Robert Malikowski · 5264eed6 · Jun 30, 2026 · 5 filesMessage 18 · OpaqueInformational 15Details
Commit message · Robert Malikowski
new buy/sell flow (wip)
18/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine user-interface work-in-progress change. It adds a new bottom-sheet modal that lets users choose between buying or selling cryptocurrency, adds two new icon images, and updates the English text strings. There is no security-relevant change in the code.