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…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedupdate mocksby Julian · ea722de8 · Aug 14, 2026 · 6 filesMessage 18 · OpaqueInformational 15Details
Commit message · Julian
update mocks
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 15/100
This commit only updates automatically generated test mock files so they match a new method signature for a network health-check ('ping') call. No real application code, user data, or wallet security behavior changed. It is a routine test-maintenance change with no security relevance.
AI review queuedfix sorting to match commentby Julian · e1354a89 · Aug 14, 2026 · 2 filesMessage 45 · ThinLow 34Details
Commit message · Julian
fix sorting to match comment
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 · Low 34/100
This commit fixes a sorting bug in how the wallet chooses which coins (UTXOs) to use when sending a BIP47/Paynym notification transaction. The code's comment said taproot coins should be used last and the oldest non-taproot coins first, but the actual sort was doing the opposite for age (newest first). The fix makes the code match the comment. Because notification transactions are special (they reveal a payment code to the recipient), using the wrong coin order could cause the wallet to select a taproot coin when a non-taproot one was available, potentially breaking notification parsing for the receiver or causing the wallet to fall back to a less desirable coin selection.
AI review queuedclean up epicbox/http/https checkby Julian · 598898ae · Aug 14, 2026 · 2 filesMessage 45 · ThinLow 29Details
Commit message · Julian
clean up epicbox/http/https check
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 · Low 29/100
This commit fixes a logic bug in how Stack Wallet decides whether to use an Epicbox server or an HTTP/HTTPS receiver when sending Epic Cash transactions. The old code used OR instead of AND when checking for HTTP/HTTPS prefixes, which meant every receiver address was treated as needing an Epicbox check. The new code cleanly separates the two paths and adds a unit test to confirm HTTP/HTTPS addresses bypass Epicbox while email-style Epicbox addresses use it.
AI review queuedfix mweb fee providerby Julian · 9cd17dbd · Aug 14, 2026 · 1 fileMessage 28 · OpaqueLow 26Details
Commit message · Julian
fix mweb fee provider
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 26/100
This commit fixes a small but meaningful mix-up in the mobile wallet's send screen. The code was reading the desktop fee-rate setting when preparing a Litecoin MWEB (privacy) transaction, instead of reading the mobile fee-rate setting. If the two settings differ, the user could end up paying an unexpected fee, or the transaction might not be built with the fee they actually selected on their phone. There is no direct evidence in the commit of funds being stolen or a remote attacker being able to exploit this.
AI review queuedfix exchange refund gatingby Julian · 3b57511d · Aug 14, 2026 · 1 fileMessage 35 · OpaqueModerate 50Details
Commit message · Julian
fix exchange refund gating
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 50/100
This commit fixes a single-character bug in the Stack Wallet exchange flow. A double negation (!!) was accidentally used where a single negation (!) was intended. The bug caused the app to require a refund address even from exchanges that do not support one, which could block legitimate transactions. The fix changes the logic so that a refund address is only required when the exchange actually supports it. There is no direct evidence in the commit that this was a security vulnerability, but a mis-gated refund flow could in theory lead to user confusion or funds being sent to an unsupported/invalid refund path.
AI review queuedfix checkTrades early returnby Julian · c6f639c8 · Aug 14, 2026 · 1 fileMessage 35 · OpaqueLow 33Details
Commit message · Julian
fix checkTrades early return
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 33/100
This commit fixes a bug in the wallet's notification service where checking one trade could accidentally stop all remaining trade checks. The function now correctly continues to the next trade instead of returning early. It also makes the trade-check function properly asynchronous so the periodic timer doesn't wait on it. This is a reliability/bug-fix change with minor security relevance: a stuck or failing trade check could have delayed or suppressed status updates for other trades, potentially hiding problems from the user.
AI review queuedensure marked used UTXOs do not get included in frost txnby Julian · f372d522 · Aug 14, 2026 · 1 fileMessage 50 · ThinModerate 58Details
Commit message · Julian
ensure marked used UTXOs do not get included in frost txn
50/100 · ThinMessage clarity
✓ Specific, 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 · Moderate 58/100
This commit fixes a bug in Stack Wallet's Bitcoin FROST wallet where coins that had already been spent (marked as 'used') could still be selected for new transactions. This could cause the wallet to attempt to spend the same coin twice, leading to failed or invalid transactions. The fix adds a filter to exclude any UTXOs that are marked as used or have an unclear used status.
✓ 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 20/100
This commit fixes a UI bug in Stack Wallet's desktop FROST wallet key popup. The previous version accidentally displayed the current FROST keys/config in the section meant to show the previous generation's keys/config. The patch corrects which data is shown in each section and adds a widget test to verify the fix. There is no direct evidence in the commit that this was a security vulnerability, but mislabeling sensitive key material could confuse users.
AI review queuedfix mwc first blockby Julian · 0e56467c · Aug 14, 2026 · 1 fileMessage 28 · OpaqueInformational 17Details
Commit message · Julian
fix mwc first block
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit changes a single constant used to estimate the first block time for the Mimblewimblecoin (MWC) cryptocurrency when restoring a wallet from a date. The old value was too early, which could cause wallet restores to scan blocks that did not exist yet. The new value is later and more accurate. There is no direct security vulnerability here; it is a correctness fix that may affect user experience and restore accuracy.
✓ 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 · Moderate 59/100
This commit fixes how Stack Wallet's desktop app parses token amounts for Solana tokens and other tokens. Previously, the app used simple string replacement for commas and periods, which could misinterpret numbers depending on the user's locale. For example, in some countries '1,000' means one thousand, while in others it means one. The fix uses locale-aware parsing and rejects inputs containing plus, minus, or space characters. The change also affects how displayed amounts are formatted, using the token's own decimal places instead of the coin's.
AI review queuedfix possible nano send amount bugby Julian · 00a81912 · Aug 14, 2026 · 2 filesMessage 45 · ThinModerate 56Details
Commit message · Julian
fix possible nano send amount bug
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 · Moderate 56/100
This commit fixes a bug in how Stack Wallet prepares Nano cryptocurrency sends. Previously, the app calculated the remaining balance after a send using a locally cached balance, which could be outdated. It now fetches the live balance from the network and explicitly checks that the user has enough funds. If the cached balance was higher than the real balance, the old code could have created an invalid or over-spending transaction.
AI review queuedflatpak: add :create to data-dir filesystem grants so first-run persistsby Dan Miller · 5e411341 · Aug 13, 2026 · 3 filesMessage 50 · ThinInformational 18Details
Commit message · Dan Miller
flatpak: add :create to data-dir filesystem grants so first-run persists
50/100 · ThinMessage clarity
✓ Specific, 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 change updates three Flatpak app permission files so the apps can create their own data folders (like ~/.stackwallet) on first launch. Previously, the apps could only access those folders if they already existed, which could cause first-run setup to fail. The change is a sandbox permission tweak, not a fix for a code vulnerability.
AI review queuedeth fees update/fixby Julian · 3af51469 · Aug 12, 2026 · 3 filesMessage 28 · OpaqueLow 41Details
Commit message · Julian
eth fees update/fix
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 41/100
This commit changes how Ethereum transaction fees are calculated in Stack Wallet. Previously, the wallet set the maximum base fee equal to the current network base fee, which could cause transactions to fail if network fees rose even slightly. The fix doubles the maximum base fee for preset fee options to give transactions more headroom. It also removes a check that prevented the priority fee from exceeding the maximum base fee. The commit adds extra logging for fee values but does not otherwise change security-sensitive code.
AI review queuedfiro temp SISTby Julian · 8f849d6b · Aug 12, 2026 · 8 filesMessage 8 · OpaqueLow 30Details
Commit message · Julian
firo temp SIST
8/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 30/100
This commit changes how the Stack Wallet mobile app handles private Firo (Spark) transactions. It temporarily blocks sending private Firo funds to exchange addresses, and rewrites the internal logic for preparing and broadcasting Spark spends so that each transaction uses only a single Spark coin input. It also adds a new planner that can split one payment across multiple single-input transactions when needed. The change appears to be a defensive measure rather than a fix for an active exploit, but it touches sensitive transaction-building code and removes some previously available functionality.
AI review queuedmaybeby Julian · c6a23088 · Aug 1, 2026 · 1 fileMessage 0 · OpaqueInformational 22Details
Commit message · Julian
maybe
0/100 · OpaqueMessage clarity
! 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 22/100
This commit changes how transaction fees are calculated for a specific type of Litecoin transaction called 'mwebPegIn' (Mimblewimble peg-in). Previously, the fee was estimated once and the transaction was built. Now, for mwebPegIn transactions, it loops: builds the transaction, checks the actual fee based on the final transaction size, and rebuilds if the fee is too low. This is a bug fix to ensure users pay the correct network fee and their transactions don't get stuck or fail. There is no clear security vulnerability here; it appears to be a correctness/reliability improvement.
AI review queuedclean up remaining pointlessnessby julian · 07398235 · Jul 31, 2026 · 1 fileMessage 35 · OpaqueLow 27Details
Commit message · julian
clean up remaining pointlessness
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 27/100
This commit removes two blocks of code that added an API key to outgoing requests for a cryptocurrency exchange integration called CypherGoat. The commit message calls this 'pointlessness,' suggesting the API key was unused or unnecessary. There is no direct evidence in the commit that this fixes a security vulnerability, but sending API keys when they are not needed can slightly increase exposure risk if those requests or logs are intercepted.
! 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 18/100
This commit is a minor cleanup: it swaps two ordinary print statements for Flutter's debugPrint (which only shows in debug builds), removes a leftover debug print of a transaction map, and stops sending an API key in requests to the CypherGoat exchange service. The API-key removal is the only change with any security angle, but the diff does not show what the key was, how it was stored, or whether it was sensitive. There is no evidence of an active vulnerability being fixed.
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 21/100
This commit updates a database migration in the Stack Wallet app. It bumps the database version from 2 to 3 and changes the upgrade logic so that, when upgrading from any version below 3, two tables related to a 'Shop in Bit' feature are deleted and recreated, plus an app notifications table is created. The commit message and code comment state this is needed to 'recreate sib tables correctly.' There is no explicit mention of a security issue in the commit or supplied references. The main risk is that deleting and recreating tables during migration could cause data loss if the tables already contained user data, but the developer comment claims the feature was not used before this point. No independent security disclosure or vendor security advisory was provided.
AI review queuedcyphergoat related tweaksby Julian · 903aac9d · Jul 30, 2026 · 10 filesMessage 35 · OpaqueInformational 22Details
Commit message · Julian
cyphergoat related tweaks
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 22/100
This commit makes several small adjustments to the CypherGoat exchange integration in Stack Wallet. It adds a new 'other' field to trade records to store a tracking URL, makes some CypherGoat API response fields optional instead of required, filters out some competing exchange providers from CypherGoat rate quotes, and fixes a minor error-message formatting bug. There is no clear security vulnerability being patched, and the commit message does not describe any security relevance.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply adds three identical SVG image files for a new exchange partner icon named 'cyphergoat' to the project's asset folders. It is a routine asset-only change with no code modifications and no apparent security relevance.
✓ 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 15/100
This commit only updates the .gitignore file to ignore the android/build/ directory. It is a routine repository hygiene change with no security relevance.
✓ 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 · Low 31/100
This commit fixes how Stack Wallet handles Firo masternode collateral UTXOs. Previously, the wallet could auto-freeze a UTXO, the user could deliberately unfreeze it, and then a later sync would re-freeze it automatically. The patch prevents that automatic re-freezing once a user has unfrozen a UTXO, while still allowing a first-time auto-freeze when masternode collateral is newly detected. It also improves the labels shown to users when collateral is detected with certainty versus only suspected. The pubspec.lock changes update unrelated dependencies and are not directly security-relevant.
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 20/100
This commit is a UI refactor for the masternode feature in Stack Wallet. It removes a hard-coded note-based detection system for masternode collateral transactions and instead lets the user explicitly start the masternode registration flow from the masternode screen. It also fixes a couple of small UI bugs, such as showing the wrong error message text in slatepack/slate failure dialogs and properly formatting pre-filled amounts in the desktop send form. There is no obvious security vulnerability introduced, but the change removes a large block of auto-detection logic that previously tried to identify 1000-FIRO self-sends as collateral.
AI review queuedcyphergoat: use Decimal for money values, error instead of default on missing fieldsby 4rkal · 26e0a0cb · Jul 27, 2026 · 5 filesMessage 50 · ThinLow 44Details
Commit message · 4rkal
cyphergoat: use Decimal for money values, error instead of default on missing fields
50/100 · ThinMessage clarity
✓ Specific, 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 · Low 44/100
This commit hardens how Stack Wallet's CypherGoat exchange integration handles API responses. It replaces imprecise floating-point math with exact decimal arithmetic for money amounts, and stops silently substituting default values (like 0 or empty strings) when expected fields are missing. Instead, the app now throws a clear error if required fields are absent or malformed. This reduces the risk of incorrect trade amounts being shown or accepted, and makes the app fail more safely if the exchange server sends an unexpected or malformed response.
✓ 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 commit finishes adding support for a new cryptocurrency exchange partner called LetsExchange to the Stack Wallet app. It adds the exchange's logo, wires up its name in currency lookup and trade-detail screens, adds its API credentials placeholders to build scripts, removes its response bodies from debug logs, and excludes it from a Trocador aggregator filter. There is no security fix or vulnerability visible in the changes.