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.
52/100 average clarity
61Strong · 80–100
359Adequate · 60–79
549Thin · 40–59
197Opaque · 0–39
33security candidates with opaque commit messaging
This commit fixes a bug in how Taproot (a modern Bitcoin-style transaction format) inputs were being built. Previously, the 'sequence number'—a field that controls things like time-locks and replacement rules—was being dropped for Taproot …
Missing nSequence preservation for Taproot key-path inputsBehavioral divergence between Taproot and other input types in the same switchPotential for unintended transaction semantics (RBF, timelocks) due to default sequence value
This commit changes how Stack Wallet picks and updates Bitcoin receiving addresses. It makes the wallet rotate (advance to a fresh address) not just on its main address type, but also on other supported address types when they have transac…
Address rotation logic added for non-main derivation pathsView-only Taproot wallet explicitly rejected in Buy flow to avoid deriving addresses without private key materialNew test coverage for address reuse and rotation across BIP44/BIP84/BIP86 paths
This change fixes how Stack Wallet picks a Bitcoin receiving address when a user buys crypto through Simplex. Previously, the app could generate a fresh address every time instead of reusing the same one, which could cause funds sent to an…
Address reuse / derivation index stability for fiat-to-crypto buy flowRace-condition protection via mutex for address generationRemoval of direct Isar query from UI layer in favor of wallet abstraction
This commit adds automated integration and widget tests for the 'Buy' form's 'Choose from Stack' feature in a cryptocurrency wallet app. It does not change production code, fix bugs, or alter security behavior. It only verifies that the ex…
This commit fixes a privacy and usability bug in Stack Wallet. Previously, when the wallet refreshed its transaction history, it only checked whether the main receiving address (for example, a Taproot address) had been used. If you had gen…
This update fixes how Stack Wallet detects Bitcoin transactions that have disappeared from the memory pool (unconfirmed transactions). Previously, the wallet only recognized a specific error message format used by some server software. Now…
Error-handling robustness improvementData consistency fix for local transaction databaseServer-backend compatibility broadening
This is a large build-system refactor for a cryptocurrency wallet app. It replaces an older manual native-library build process with a new 'dnix' system that can either build libraries from source or download verified prebuilt binaries. Th…
Build system refactor only: no application runtime code changedNew verification step check_native_overrides.dart added to CI and local configure flowPrebuilt binaries are now verified against package dnix.lock hashes instead of app-level manifest URLs
This is a large merge commit that rewrites how the wallet connects to Electrum servers. The main security-relevant changes are: each wallet now owns its own Electrum connection instead of sharing one global client; the app learns to rememb…
Per-wallet Electrum connection ownership replaces shared singleton, reducing cross-wallet state contaminationTrusted TLS certificate pinning per node (host/port/SSL) addedCertificate approval UI with SHA-256 fingerprint display and forget action
This is a large refactor of how the Stack Wallet app connects to Electrum servers. Previously, all wallets of the same coin shared one global Electrum connection, which could leak wallet activity across wallets and made it hard to cleanly …
Shared Electrum client manager removed; per-wallet client isolation addedTLS certificate pinning/trust-on-first-use support added for Electrum nodesPer-request timeouts added instead of single global timeout
This commit only rewords comments and a test name. It changes the phrase 'approval pins the certificate' to 'approval accepts the certificate' and clarifies that only untrusted certificates reach the custom check. There is no code behavior…
This commit is purely a code-formatting cleanup in a single Dart file. It rewraps a few lines of navigation and theme code to match the project's style guide. There are no functional changes, no bug fixes, and no security relevance.
This is a large merge commit that refactors how transaction fees are calculated and displayed across Stack Wallet's send screens. It replaces duplicated fee-calculation code in many send views with a shared set of providers and helper widg…
Refactor of transaction-fee estimation logic across send flowsRemoval of duplicated fee-calculation code and session cachesIntroduction of shared fee providers and reusable UI helpers
This is a large code refactor that moves fee-calculation logic out of individual send screens into shared providers and helper classes. The goal is to make the send fee UI behave consistently across mobile, desktop, token, and Solana token…
Refactor of transaction fee estimation and selection UI across all send flowsConsolidation of wallet-specific fee logic (Cryptonote priorities, Firo Spark/public/OP_RETURN, Solana token fallback, Ethereum custom EIP-1559) into shared providersRemoval of per-view fee caches and timers; replacement with shared debounce/focus-loss retry logic
This commit adds a new feature to Stack Wallet that lets Monero (XMR) users cryptographically sign messages with their wallet address and verify signatures from others. It is a routine feature addition, not a security fix or vulnerability …
This commit adds a new feature to Stack Wallet that lets Monero wallet users cryptographically sign messages with their wallet keys and verify signatures from others. It is a routine feature implementation, not a security fix. There is no …
Feature addition, not a patch or fixView-only wallets are explicitly blocked from signingEmpty signature result from underlying library is treated as failure
This commit fixes a bug where Stack Wallet could not clean up old unconfirmed transactions when connected to electrs servers. The wallet checks whether a transaction still exists on the server; it previously only recognized ElectrumX/Fulcr…
Error-message parsing used for transaction lifecycle decisionWallet state desynchronization due to backend-specific error handlingRBF/replaced transaction cleanup failure
This commit fixes a user-interface bug in Stack Wallet's Solana token-add flow. Previously, when a user created a new Solana wallet while trying to add a Solana token, the wallet picker could see the newly created wallet in the database be…
No cryptographic or signing code changedNo network or RPC behavior changedNo authentication, authorization, or permission logic changed
This commit fixes a UI crash in Stack Wallet that could occur when adding an Ethereum token right after creating a new Ethereum wallet. The problem was a timing mismatch: the new wallet's basic info was saved to the database before the wal…
Crash/DoS in wallet picker UI due to inconsistent wallet registration stateRace condition between database persistence and in-memory provider registrationUI state derived from one provider (all wallet info) without checking another provider (registered wallets)
This commit only reformats Dart code to match the project's current Dart SDK style rules. It changes whitespace, line breaks, and import grouping in two wallet-related UI files. There are no functional changes, no security fixes, and no be…
This commit fixes a UI bug in Stack Wallet's Ethereum token-add flow. During wallet creation, the app briefly knew about a new Ethereum wallet before the wallet was fully registered, causing the token picker to show an empty or broken list…
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 18/100
This commit is a routine feature improvement for the ShopinBit integration in Stack Wallet. It changes how package tracking links are handled: instead of storing one raw string that may contain several URLs crammed together with commas, pipes, or semicolons, the code now splits that string into a clean list of individual tracking URLs. It also turns empty strings from the server into null values so the rest of the app doesn't treat an empty value as a real link. There is no security fix here and nothing that looks like a vulnerability.
Security candidaterefactor(shopinbit): parse ticket messages with the html packageby sneurlax · ad6cde62 · Jun 26, 2026 · 3 filesMessage 62 · AdequateLow 37Details
Commit message · sneurlax
refactor(shopinbit): parse ticket messages with the html package
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
authentication path
AI analysis · Low 37/100
This commit replaces a custom-built HTML parser in Stack Wallet's ShopinBit ticket-message feature with the well-known 'html' package. The old code parsed HTML by hand using string scanning and regular expressions, which is a common source of security bugs (for example, tricking the parser into treating malicious code as harmless text or vice versa). The new code uses a dedicated HTML parser that is more robust against malformed or adversarial input. The change is a defensive refactor; there is no direct evidence in the commit that an actual attack was found or exploited.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 37/100
This update improves how Stack Wallet's ShopInBit support-chat feature handles images and file attachments. It replaces an older inline-base64-only image renderer with a safer parser that also supports server-hosted attachments, adds request timeouts so background polling can't get stuck forever, and skips malformed messages instead of crashing the whole chat. The code also adds path-traversal checks on attachment URLs so a malicious link can't trick the app into requesting unintended server paths using the user's own login token.
fix(shopinbit): await clipboard write in car-research copy address
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
authentication path
AI analysis · Informational 16/100
This is a small UI reliability fix in a cryptocurrency wallet's car-research payment screen. The developer made the 'copy address to clipboard' function wait for the clipboard write to complete before showing a confirmation message, and added a check to avoid using a screen that may have been closed during the operation. It is a routine correctness improvement, not a security fix for an exploitable vulnerability.
Security candidatefix(shopinbit): show payment QR in a dialog instead of a bottom sheetby sneurlax · a9e9eb73 · Jun 26, 2026 · 2 filesMessage 85 · StrongInformational 15Details
Commit message · sneurlax
fix(shopinbit): show payment QR in a dialog instead of a bottom sheet
fix(shopinbit): align payment QR copy icon with Stack's native style fix(shopinbit): await clipboard write in payment QR dialog
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit is a routine user-interface polish for the ShopinBit payment flow. It changes how a QR-code payment screen is displayed (from a bottom sheet to a dialog), updates a copy icon to match the app's style, and makes the clipboard copy operation wait for completion before showing a confirmation message. There is no security-relevant change.
Security candidatefix(shopinbit): pop payment loading overlay on the root navigatorby sneurlax · c7c38ab1 · Jun 26, 2026 · 1 fileMessage 85 · StrongInformational 17Details
Commit message · sneurlax
fix(shopinbit): pop payment loading overlay on the root navigator
fix(ui): make showLoading dismissal robust against nesting and unmount fix(shopinbit): solve payment overlay soft-lock without touching showLoading
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Informational 17/100
This commit fixes a UI bug in the Stack Wallet app's ShopinBit payment screen. A loading overlay that appears while refreshing or checking an invoice could get stuck (a 'soft-lock') because it was being shown on a nested navigator instead of the root one. The fix tells the overlay to display on the root navigator so it can be properly dismissed, preventing users from getting stuck on a frozen payment screen.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit removes a 'I need recommendations' checkbox from a travel booking form inside the Stack Wallet app. Users must now type a destination city instead of asking for recommendations. There is no security issue visible in the code change.
Security candidatefix(shopinbit): dumb hacked check for first and last nameby julian · 2c229d73 · Jun 23, 2026 · 1 fileMessage 62 · AdequateInformational 23Details
Commit message · julian
fix(shopinbit): dumb hacked check for first and last name
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
authentication path
AI analysis · Informational 23/100
This commit tightens the shipping/billing name validation in the ShopInBit feature of Stack Wallet. Previously, any non-empty name was accepted; now the name must contain at least two whitespace-separated words (e.g., a first and last name). The change is a client-side form check and does not appear to fix a security vulnerability. It is more likely a business-rule or partner-compliance fix to prevent incomplete names from being submitted to the ShopInBit service. There is no evidence in the commit or supplied references of a security issue, exploit, or disclosure.
fix(shopinbit): WIP/not fully tested: add state/province where required
52/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
authentication path
AI analysis · Informational 19/100
This commit is a work-in-progress feature update for the ShopinBit integration inside Stack Wallet. It adds the ability to collect and send a U.S. state or Canadian province/territory when required for delivery or billing addresses. It is not a security patch; it is a functional change to address form handling and API request data. There is no indication in the commit that it fixes a vulnerability, leak, or exploit.
Security candidatefix(shopinbit): car fee viewby julian · 7a56c671 · Jun 23, 2026 · 7 filesMessage 57 · ThinInformational 16Details
Commit message · julian
fix(shopinbit): car fee view
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 16/100
This commit is a UI refactor for the ShopinBit 'car fee' checkout screen. It removes a separate delivery-address form and instead reuses the country already chosen earlier in the request flow, displaying it as read-only billing-country information. The change also splits the country field into a human-readable name plus an ISO code. There is no obvious security bug being fixed; it looks like a normal feature cleanup to reduce duplicated input and prevent inconsistent country data.
Security candidatefix(shopinbit): desktop first run dialogby julian · 5c7f7717 · Jun 23, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · julian
fix(shopinbit): desktop first run dialog
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This commit is a routine UI tweak for the desktop version of a feature called ShopinBit. It changes the width of a first-run information dialog, removes a Cancel button, adjusts spacing, and indents bullet points. There is nothing here related to security.
Security candidatefeat(shopinbit): keep polling ticket state & messages of terminal ticketsby sneurlax · 6da8d2fe · Jun 19, 2026 · 2 filesMessage 62 · AdequateInformational 16Details
Commit message · sneurlax
feat(shopinbit): keep polling ticket state & messages of terminal tickets
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
authentication path
AI analysis · Informational 16/100
This commit changes the Stack Wallet app so it keeps checking (polling) the status of certain ShopInBit support tickets even after they are in a final, unchangeable state. Previously, the app stopped polling once a ticket was closed, merged, or refunded. The change removes those stop conditions. On its own, this is a behavior change rather than a direct security flaw, but it could slightly increase network traffic, battery use, and the number of API calls made to the ShopInBit server. There is no evidence in the commit that this fixes a security vulnerability or that it introduces one.
This reverts commit d00a101abc0bb8da416fa6f81027584f12a4e7b3.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
authentication path
AI analysis · Low 26/100
This commit flips a single setting in the Stack Wallet app so that its built-in ShopInBit shopping feature talks to a test/sandbox environment instead of the real production service. The change is explicitly marked with a TODO saying it must be set to false for production. Using sandbox mode in a production release could mean users see fake/test data, make payments that don't result in real orders, or interact with a less secure/test server. However, the diff alone does not prove this change was ever shipped to users, and the commit message only says it is reverting an earlier change that disabled the sandbox.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 45/100
This commit changes a third-party shopping integration from 'sandbox' (test) mode to live mode. The developer left a note earlier saying it should be set to false in production. The change itself is a normal production toggle, but because it involves real money/purchases and secret API credentials, it is worth reviewing whether this was released safely and whether any test-only behavior or weaker security settings were carried over accidentally.
Security candidateSwitch default Tezos node to tezos.stackwallet.com which doesn't support /header/shell, so getChainHeight calls /header instead, which also contains level.by Dan Miller · 3c5e7918 · Jun 17, 2026 · 2 filesMessage 50 · ThinInformational 19Details
Commit message · Dan Miller
Switch default Tezos node to tezos.stackwallet.com which doesn't support /header/shell, so getChainHeight calls /header instead, which also contains level.
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 19/100
This commit changes the default Tezos blockchain server used by Stack Wallet from a public Tezos node to Stack Wallet's own node, and adjusts the API endpoint used to check the latest block height. There is no direct evidence in the commit of a security vulnerability, but running wallet traffic through a single party-controlled node and changing the data source for chain state can carry trust and reliability risks.
Security candidateChange fact0rn explorer address from non-working one.by Dan Miller · a421c789 · Jun 12, 2026 · 1 fileMessage 50 · ThinInformational 19Details
Commit message · Dan Miller
Change fact0rn explorer address from non-working one.
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 19/100
This commit simply swaps the default web address used to look up Fact0rn transactions in Stack Wallet. The old explorer (factexplorer.io) was reportedly not working, so the developer reverted to the official explorer.fact0rn.io. There is no code change that handles private keys, balances, or network connections differently. At most, users who click a transaction link may now land on a working website instead of a broken one.
Security candidateUpdate URL for default fact0rn electrumx server.by Dan Miller · ddd18dca · Jun 12, 2026 · 1 fileMessage 45 · ThinInformational 13Details
Commit message · Dan Miller
Update URL for default fact0rn electrumx server.
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 13/100
This commit simply swaps the default server address used by the Stack Wallet app for the Fact0rn cryptocurrency from one Project Factor server (electrumx1) to another (electrumx2). It is a routine infrastructure update. There is no direct evidence in the commit that this fixes a security vulnerability, but changing default servers can be relevant to trust and availability.
Security candidatefix: reduce pointless API callsby julian · a8e74ffe · Jun 11, 2026 · 1 fileMessage 57 · ThinInformational 18Details
Commit message · julian
fix: reduce pointless API calls
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 18/100
This change alters how a wallet feature called ShopInBit refreshes support-ticket details. Previously it fired three API calls at once; now it first checks ticket status and skips the other two calls if the server returns a 403 'permission denied' response. The stated goal is simply to reduce unnecessary network traffic. There is no direct evidence in the commit that this fixes a security vulnerability, but it does reduce the amount of ticket-related data the app requests when the user is no longer authorized to view a ticket.
Security candidatefix: API was updated to show ticket type so we can now filter receipts outby julian · 7dbea236 · Jun 11, 2026 · 2 filesMessage 62 · AdequateInformational 16Details
Commit message · julian
fix: API was updated to show ticket type so we can now filter receipts out
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
authentication path
AI analysis · Informational 16/100
This commit updates the wallet's integration with a third-party shopping service. The service's API now labels certain records as 'receipts', and the wallet now skips those records when refreshing ticket data. This appears to be a correctness or data-handling fix rather than a security vulnerability. There is no indication it fixes an exploit or protects user funds directly.
Security candidatefix: ensure ticket gets stored on car invoice polling ticket created/foundby julian · a1ccc0cd · Jun 11, 2026 · 1 fileMessage 62 · AdequateInformational 16Details
Commit message · julian
fix: ensure ticket gets stored on car invoice polling ticket created/found
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
authentication path
AI analysis · Informational 16/100
This commit fixes a data-handling bug in a car-research invoice payment screen. Previously, when the app polled the server for invoice status and discovered a newly created support ticket, it did not save that ticket to the local database. The patch adds logic to fetch the full ticket details from the server and store a minimal local record so the rest of the app can see and update it later. There is no indication this is a security vulnerability; it appears to be a functional bug fix.
chore: ensure expected field parsing fails ungracefully
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
authentication path
AI analysis · Low 26/100
This commit changes how a wallet app parses invoice data from a partner service. Previously, missing or malformed date/number fields were handled gracefully by returning null or skipping them. Now, those same missing or malformed fields will cause the parsing to crash with an exception. The commit title says this ungraceful failure is intentional. This is a defensive change: it makes the app fail loudly instead of silently accepting bad data, which can prevent subtle bugs or misuse. However, it is not a typical security patch and could in theory be abused if an attacker can feed malformed JSON to the app to trigger a crash (denial of service).
Security candidatefix(shopinbit): remove unused customerKey field from ApiResponseby sneurlax · 2f8328e4 · Jun 11, 2026 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
fix(shopinbit): remove unused customerKey field from ApiResponse
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
authentication path
AI analysis · Informational 15/100
This commit removes an unused field called customerKey from a data structure used when the app talks to the ShopInBit service. There is no security fix here; it is a small cleanup that deletes dead code.
fix(shopinbit): remove pointless mounted check and verbose comments
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
authentication path
AI analysis · Informational 12/100
This commit removes a safety check and some explanatory comments from a Flutter screen that shows a fallback dialog when a car purchase ticket takes too long to appear. The removed 'mounted' check ensured the screen still existed before showing a dialog. On its own, this change does not create a security issue; it is a minor code-cleanup change that slightly increases the theoretical risk of a harmless UI crash if the screen is closed at exactly the wrong moment.
Security candidatefix(shopinbit): only mark car research complete once the ticket existsby sneurlax · 6b7d9bcb · Jun 11, 2026 · 1 fileMessage 62 · AdequateInformational 16Details
Commit message · sneurlax
fix(shopinbit): only mark car research complete once the ticket exists
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
authentication path
AI analysis · Informational 16/100
This commit fixes a UI timing bug in a cryptocurrency wallet's car-research payment flow. Previously, the app could mark the payment as 'complete' and try to open the order details before the backend ticket actually existed, which could briefly show the wrong screen or a fallback. Now it waits until the real ticket ID is available before marking the flow complete. There is no direct evidence this is a security vulnerability.
fix(shopinbit): handle no_payment_required as fully covered
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
authentication path
AI analysis · Informational 21/100
This commit fixes a UI/workflow bug in Stack Wallet's ShopInBit integration. When an order is fully covered by a voucher or store credit, the payment status becomes 'no_payment_required' and the invoice has no payment addresses. Previously the app treated this as a failed payment load and blocked the user; now it shows a 'fully covered' screen and lets the user continue. It is a functional bug fix rather than a security vulnerability.