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 queuedremove unused parsing functionsby Julian · 5dd9fdb8 · Aug 26, 2026 · 1 fileMessage 35 · OpaqueInformational 12Details
Commit message · Julian
remove unused parsing functions
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100
This commit simply deletes two unused helper functions that converted numbers between different locale formats (for example, swapping commas and periods used as decimal separators). Because the functions were not being used anywhere in the app, removing them does not change app behavior and does not fix or introduce a security issue.
AI review queuedreset desktop fee rate type state providerby Julian · c4f0cb35 · Aug 26, 2026 · 1 fileMessage 45 · ThinModerate 50Details
Commit message · Julian
reset desktop fee rate type state provider
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 50/100
This commit fixes a state-carryover bug in the desktop version of Stack Wallet. A global fee-rate setting was not being reset when a user opened a new send form, so a custom fee chosen in one wallet could silently carry over to another wallet's send form. If the user did not notice, a transaction could be sent with an unexpected (possibly very low or very high) custom fee. The patch resets the fee type to 'average' each time the desktop send form is initialized.
AI review queuedfix(search): respect locale and coin precisionby Julian · d8efa9af · Aug 26, 2026 · 7 filesMessage 57 · ThinInformational 17Details
Commit message · Julian
fix(search): respect locale and coin precision
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit fixes how the wallet's search and filter features interpret typed-in amounts. Previously, the app assumed everyone uses a dot (.) as the decimal separator and parsed amounts in a way that could misread or silently mishandle values for some currencies. Now it respects the user's locale (e.g., comma for German) and uses the coin's own precision rules. There is no direct evidence this was a security vulnerability, but incorrect amount parsing in a wallet can lead to users selecting wrong coins or filters, so it is treated as a correctness/reliability fix rather than an exploit.
AI review queued- editable locale-aware text for mobile and desktop send flows - parse scanned payment amounts canonically, preserve values across locale changes, validate nonce text, and keep displayed fees separate from editable controller textby Julian · 62d0508c · Aug 26, 2026 · 9 filesMessage 73 · AdequateLow 47Details
Commit message · Julian
- editable locale-aware text for mobile and desktop send flows - parse scanned payment amounts canonically, preserve values across locale changes, validate nonce text, and keep displayed fees separate from editable controller text
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 47/100
This commit is a hardening and bug-fix patch for Stack Wallet's send screens. It changes how payment amounts are entered, parsed, and displayed so the wallet respects the user's locale (for example, comma vs. period as a decimal separator) without losing or misinterpreting values. It also stops using formatted fee strings for internal calculations, instead keeping fees as raw numeric Amount objects, and adds validation for Ethereum transaction nonces so only whole numbers are accepted. The changes reduce the chance that a user accidentally sends the wrong amount because the app misread a pasted QR-code amount or a locale-formatted number.
AI review queued- Treat maxFeePerGas as the total protocol cap for presets and custom fees. Validate it against base and priority fees, and use the same cap and gas limit for transaction construction and maximum-fee estimates.by Julian · 83f71a54 · Aug 26, 2026 · 10 filesMessage 65 · AdequateModerate 60Details
Commit message · Julian
- Treat maxFeePerGas as the total protocol cap for presets and custom fees. Validate it against base and priority fees, and use the same cap and gas limit for transaction construction and maximum-fee estimates.
- Localize custom fee input and reject malformed gas limits.
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This commit fixes how Stack Wallet handles Ethereum transaction fees. Previously, the app appears to have treated 'max base fee' and 'priority fee' as separate fields, which could let users set a priority fee higher than the total fee cap or set a total cap too low to cover the network's base fee. The patch makes the 'max fee per gas' the hard total cap, validates that the priority fee fits inside it, and uses the same cap and gas limit both when building the transaction and when showing the maximum possible fee. It also improves input validation so malformed gas limits are rejected and fee numbers are properly localized for different languages.
AI review queuedStandardize localized input:by Julian · 865fd824 · Aug 26, 2026 · 20 filesMessage 58 · ThinModerate 61Details
Commit message · Julian
Standardize localized input:
- Explicit editable and canonical parsers, strict ASCII amount formatting, locale relocalization, and isolated IME recovery
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 61/100
This commit rewrites how the Stack Wallet app handles typed-in money amounts. It makes the rules for what counts as a valid amount much stricter: only digits and the user's locale-specific decimal separator are allowed, grouping characters (like commas in 1,000) are rejected, and the code now keeps a separate 'canonical' parser for trusted sources like QR codes. The change also adds recovery logic for on-screen keyboards that compose characters in unusual ways, so the app doesn't get stuck with an unparseable amount. The main risk is that a user could previously enter an amount that the app misread by a factor of 1,000 (for example, treating '1.000' as one thousand instead of one), which could lead to sending far more cryptocurrency than intended.
AI review queuedupdate NSPhotoLibraryUsageDescription stringby Julian · 0f6c54fa · Aug 24, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Julian
update NSPhotoLibraryUsageDescription string
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 only rewords the iOS permission message shown to users when the app requests access to the photo library. It changes a generic 'Photo Library Access Warning' into a clearer explanation that the app only reads images the user selects (for example, a QR code photo) and does not access the library automatically. There is no code change that alters what the app actually does or fixes a security flaw.
AI review queuedupdate NSPhotoLibraryUsageDescription stringby Julian · f920c360 · Aug 24, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Julian
update NSPhotoLibraryUsageDescription string
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 only rewords the iOS permission message shown to users when the app wants to access photos. It changes a generic 'Photo Library Access Warning' to a clearer explanation that the app only reads images the user selects (for example, a QR code photo) and will not access the photo library automatically. There is no code change that alters what the app actually does or fixes a security flaw.
AI review queuedreplace deprecated share callby Julian · dafffe88 · Aug 22, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Julian
replace deprecated share call
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 simply swaps an old, deprecated 'Share' button function for the newer 'SharePlus' package equivalent in the PayNym screen. It is a routine maintenance/dependency update with no visible security change.
AI review queuedsome dependency clean upby Julian · 24668572 · Aug 19, 2026 · 6 filesMessage 28 · OpaqueInformational 18Details
Commit message · Julian
some dependency clean up
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit updates several third-party software libraries (dependencies) and adjusts the code that shares QR-code images so it uses the newer library's API. It is a routine maintenance/cleanup change. There is no direct evidence in the commit that it fixes a security vulnerability, but keeping dependencies up to date can remove known bugs in older library versions.
AI review queuedrefactor electrumx based coin transaction building and fee calculationby Julian · d00afa71 · Aug 19, 2026 · 5 filesMessage 50 · ThinLow 33Details
Commit message · Julian
refactor electrumx based coin transaction building and fee calculation
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 33/100
This commit refactors how Stack Wallet builds Bitcoin-like transactions and calculates fees. It introduces a new fee planner that handles three modes: normal fixed-amount sends, 'subtract fee from amount' (the recipient gets slightly less so the sender doesn't need extra funds for the fee), and sweep/all sends. The change consolidates previously scattered fee logic into one place and adds unit tests. It is a code-quality and feature refactor; there is no direct evidence in the commit that it fixes a known security vulnerability, but any change to transaction-fee logic can affect whether users accidentally overpay, underpay, or create invalid transactions.
AI review queuedfix custom fee ui state drift on mobileby Julian · a8ca183a · Aug 18, 2026 · 9 filesMessage 45 · ThinLow 30Details
Commit message · Julian
fix custom fee ui state drift on mobile
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 30/100
This commit fixes a UI bug in Stack Wallet where the custom/preset fee selection could get out of sync between the fee picker and the actual transaction being built. Previously, whether a custom fee was active was tracked in a separate local variable that could drift from the shared state provider. The patch makes the send flow read the fee mode directly from the shared state provider at the moment the transaction is prepared, and adds a helper that only supplies a custom fee value when custom mode is actually selected. The risk is that a user might have a preset fee selected while the app still uses an old custom fee value, or vice versa, leading to an unexpected transaction fee.
AI review queuedmemo/extraid swap supportby Julian · 09ac90fe · Aug 18, 2026 · 16 filesMessage 35 · OpaqueLow 34Details
Commit message · Julian
memo/extraid swap support
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 34/100
This commit adds support for 'memos' or 'destination tags' when swapping cryptocurrencies through third-party exchange providers. Some coins (like XRP, XLM, ATOM, etc.) require these extra identifiers so the receiving platform knows which customer account should get the funds. Previously, the wallet always sent these fields as empty/null, which could cause swapped funds to be lost or misattributed when sent to an exchange or custodial address that requires a memo. The change also parses memos from scanned QR payment URIs and shows input fields only when the chosen currency commonly needs one.
AI review queuedformattingby Julian · f2325147 · Aug 17, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Julian
formatting
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-formatting cleanup in a single Dart file that builds the QR-code generation screen. It rewraps long lines, adjusts indentation, and replaces a deprecated SVG color property with a newer colorFilter property. No security-sensitive logic, permissions, or data handling changed.
AI review queuedtighten up DPS persistenceby Julian · 898c56d2 · Aug 16, 2026 · 2 filesMessage 35 · OpaqueModerate 57Details
Commit message · Julian
tighten up DPS persistence
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 57/100
This commit hardens how Stack Wallet stores the desktop password 'key blob' on disk. It prevents creating a new password blob when one already exists, verifies writes actually landed, makes password changes more atomic, and lets the app recover when the stored version number doesn't match the blob. The changes reduce the risk of ending up with a corrupt or mismatched password state that could lock a user out or leave an old password usable unexpectedly.
AI review queuedfix autobackup locationby Julian · 6541cdcc · Aug 16, 2026 · 1 fileMessage 28 · OpaqueInformational 19Details
Commit message · Julian
fix autobackup location
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 19/100
This is a one-line bug fix in a mobile/desktop cryptocurrency wallet's auto-backup screen. The developer changed which folder path is recorded as the backup destination: previously the code saved the user's original picked path, and now it saves a computed 'pathToSave' variable. Without more context we cannot tell whether this fixes a security problem or merely a functional/UI bug, but it could affect where sensitive backup files are written.
AI review queuedadd extra check to nano interface account info parsingby Julian · 0fde946a · Aug 16, 2026 · 2 filesMessage 50 · ThinLow 45Details
Commit message · Julian
add extra check to nano interface account info parsing
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 45/100
This commit tightens how Stack Wallet parses account information for Nano cryptocurrency sends. Previously, if the Nano node returned an error or a malformed balance, the code could crash or behave unpredictably. Now it explicitly checks for error responses and invalid balance values before continuing. This is a defensive hardening fix that prevents bad node responses from causing app crashes or incorrect send calculations.
AI review queuedfix nanswap networksby Julian · 24d58009 · Aug 16, 2026 · 3 filesMessage 28 · OpaqueLow 33Details
Commit message · Julian
fix nanswap networks
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 33/100
This commit fixes a network-labeling bug in the Nanswap cryptocurrency exchange integration. Before the fix, the code sometimes mixed up the currency/network a user was supposed to send in with the one they would receive out. That could mislead users into depositing funds on the wrong blockchain or network, which in the worst case could mean lost or stuck funds. The patch adds helper getters so the correct network is always chosen, and adds a unit test to confirm the behavior.
AI review queuedensure frost wallet data is fully deleted on wallet deleteby Julian · 1c85b97a · Aug 16, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · Julian
ensure frost wallet data is fully deleted on wallet delete
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 59/100
This commit fixes a cleanup bug in Stack Wallet: when a user deleted a FROST (multi-signature) Bitcoin wallet, the app was leaving behind sensitive key material and configuration data in secure storage and the local database. The patch now explicitly deletes those leftover FROST records during wallet deletion, reducing the risk that a deleted wallet's secrets could be recovered or reused later.
AI review queuedfix node backup restoresby Julian · f8c2bb12 · Aug 15, 2026 · 3 filesMessage 28 · OpaqueLow 30Details
Commit message · Julian
fix node backup restores
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 30/100
This commit fixes how Stack Wallet restores saved cryptocurrency node settings from backups. Previously, the restore code assumed fields like SSL, Tor, and primary-node flags were stored in specific formats (sometimes text, sometimes true/false) and could misread or drop values, potentially restoring a node with the wrong security/privacy settings. The patch introduces a single, tested helper that consistently interprets those fields across old and new backup formats, and also preserves a previously-missing 'node API secret' field during restore.
AI review queuedfix btc frost priceby Julian · 9685de56 · Aug 15, 2026 · 2 filesMessage 28 · OpaqueInformational 17Details
Commit message · Julian
fix btc frost price
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 17/100
This commit fixes a bug in how the Stack Wallet app fetches cryptocurrency prices from CoinGecko. Previously, the app tried to match coins by their display name (e.g., 'Bitcoin'), which caused 'Bitcoin Frost' to be missed because its name differs. The change now matches coins by their unique CoinGecko ID instead, so both regular Bitcoin and Bitcoin Frost get correct price data. There is no security vulnerability here—it's a functional bug fix for price display accuracy.
AI review queuedfix swap rate sortingby Julian · f9182524 · Aug 15, 2026 · 2 filesMessage 28 · OpaqueInformational 24Details
Commit message · Julian
fix swap rate sorting
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 24/100
This commit fixes a bug in how Stack Wallet sorts cryptocurrency exchange rate estimates. Previously, the sorting logic was broken: it could place failed/null estimates incorrectly and did not reliably show the best (highest) rate first. The fix ensures better rates appear at the top and failed providers are pushed to the bottom. It is a UI/ordering bug, not a direct theft-of-funds vulnerability, but it could mislead a user into picking a worse exchange rate.
AI review queuedtighten up amount parsingby Julian · f32a921e · Aug 15, 2026 · 5 filesMessage 35 · OpaqueModerate 51Details
Commit message · Julian
tighten up amount parsing
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 51/100
This commit tightens how the wallet parses amounts typed or pasted by users. It now rejects strings that contain plus/minus signs or hidden whitespace characters (like tabs and newlines), and it turns on 'strict' parsing in more places so that spaces inside an amount are not silently ignored. The change is defensive: it reduces the chance that a cleverly crafted amount string could be misread, potentially leading to a wrong payment amount or an unexpected transaction.
AI review queuedhandle zero restore chain heightby Julian · e0dbdb8f · Aug 14, 2026 · 4 filesMessage 45 · ThinInformational 19Details
Commit message · Julian
handle zero restore chain height
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 19/100
This commit fixes a simple math bug that could occur when a cryptocurrency wallet tries to show how far along a restore/sync is, but the current blockchain height is reported as zero. Previously, dividing by zero could produce an invalid result (infinity or 'not a number'). The change makes the progress show 0% until a real chain height is known. It is a robustness fix, not a security vulnerability that an attacker can exploit.
✓ 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 42/100
This commit adds a safety check to prevent a Bitcoin PayNym notification transaction from being built using only Taproot (BIP86) inputs. The new code throws an error if the first input is Taproot, while allowing mixed or non-Taproot inputs. PayNym notification transactions have specific protocol requirements, and using an all-Taproot input set could lead to an invalid or incompatible notification that another wallet might not recognize, potentially causing loss of privacy or failed payments. The change is defensive and includes a unit test.