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 queuedfeat(shopinbit): add ShopInBit More menu item on mobileby sneurlax · 0582da4a · Apr 6, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
feat(shopinbit): add ShopInBit More menu item on mobile
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 15/100
This commit simply adds a new 'Services' menu item to the bottom navigation bar in the mobile wallet view. It lets users open an existing screen called ServicesView. There is no security-relevant change in the code shown.
✓ 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 deletes the pubspec.lock file, which is Dart/Flutter's record of exact dependency versions used to build the app. Removing it does not change any application code or fix a security bug. It is a routine project-maintenance change, though it means future builds will resolve dependency versions from pubspec.yaml rather than using pinned versions.
AI review queuedfeat(paynym): add isTaproot param to getPaymentCode and enable on claimby sneurlax · c648781b · Apr 6, 2026 · 2 filesMessage 62 · AdequateInformational 20Details
Commit message · sneurlax
feat(paynym): add isTaproot param to getPaymentCode and enable on claim
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 20/100
This commit updates the Paynym (BIP47 reusable payment code) claim flow in Stack Wallet so that newly claimed payment codes advertise both SegWit and Taproot support. Previously the claim screen requested a non-SegWit payment code; now it requests a code with both feature bits set. The wallet's payment-code generator also gains a new optional `isTaproot` flag. This is a feature/correctness change rather than a clear security fix, but enabling the right address-type flags can affect which addresses are derived when other wallets pay you, so it has mild security/reliability relevance.
AI review queuedTODO: merge https://github.com/cypherstack/bip47/pull/9 and update to mainby sneurlax · 783dbded · Apr 6, 2026 · 1 fileMessage 38 · OpaqueLow 25Details
Commit message · sneurlax
TODO: merge https://github.com/cypherstack/bip47/pull/9 and update to main
38/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100
This commit changes a dependency reference in a build template from the project's official BIP47 repository to a personal fork owned by a user named 'sneurlax'. The commit message says this is a temporary TODO step to merge a pull request. On its own, this is a supply-chain risk signal: it points the build to code outside the project's normal trusted source, but the diff does not show what changed in that fork or whether the fork contains malicious or vulnerable code.
feat(paynym): add P2TR (taproot) payment address support
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 12/100
This commit adds support for Bitcoin Taproot (P2TR) addresses to the Paynym feature in Stack Wallet. Paynyms are reusable payment codes that let users receive payments without sharing a new address each time. The change extends the existing support for legacy and SegWit addresses to also handle Taproot addresses, and refactors the code to choose address types more cleanly. There is no indication in the commit that this fixes a security vulnerability.
fix(paynym): handle taproot inputs in notification tx parsing/building
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 · Low 44/100
This commit fixes how Stack Wallet handles Bitcoin PayNym notification transactions when the wallet has taproot-style coins. PayNym notification transactions need the sender's raw public key to set up a private payment channel. Taproot inputs hide that raw public key, so the previous code could crash or fail to parse/build notifications when taproot coins were selected. The fix avoids picking taproot coins for notification transactions and gracefully returns null instead of crashing when a taproot input is encountered during parsing.
AI review queuedfix(desktop): Show Create Masternode page as dialogby narekgeghamyan0 · 1480494c · Mar 31, 2026 · 1 fileMessage 62 · AdequateInformational 19Details
Commit message · narekgeghamyan0
fix(desktop): Show Create Masternode page as dialog
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 19/100
This commit changes how the 'Create Masternode' screen appears on desktop computers. Previously it was pushed as a full page after confirming a transaction; now it is shown as a popup dialog on desktop, while mobile behavior stays the same. It also adds a safety check that the screen context is still valid before showing the dialog. There is no clear security problem here—this looks like a normal user-interface fix.
AI review queuedfix(particl): override bitcoindart in order to resolve dependency issueby sneurlax · 4958bfd3 · Mar 24, 2026 · 2 filesMessage 89 · StrongLow 26Details
Commit message · sneurlax
fix(particl): override bitcoindart in order to resolve dependency issue
had to `sudo apt-get install -y lld-18` tho
89/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
Why it was queued
second-pass: broader security terminology
AI analysis · Low 26/100
This commit updates the Stack Wallet app's package dependencies and adds an override so that a specific Bitcoin-related library (bitcoindart) is pinned to a CypherStack-controlled version. The stated reason is to fix a dependency conflict introduced by another package (bip47). The change itself is a build/dependency configuration update, not a code-level security fix. There is no direct evidence in the commit that this resolves a vulnerability, only that it resolves a dependency issue.
AI review queuedFix Firo masternode registration to use external collateral instead of redundantly re-sending 1000 FIROby Navid Rahimi · 1069b40b · Mar 15, 2026 · 7 filesMessage 50 · ThinHigh 70Details
Commit message · Navid Rahimi
Fix Firo masternode registration to use external collateral instead of redundantly re-sending 1000 FIRO
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 · High 70/100
This commit fixes a bug in Stack Wallet's Firo masternode registration feature. Previously, the wallet would redundantly send another 1000 FIRO inside the registration transaction itself, using that new output as collateral. The updated code instead uses an existing 1000 FIRO unspent output (UTXO) in the wallet as collateral, which is the correct behavior for Firo masternodes. The change also adds checks that the collateral exists, is confirmed, is exactly 1000 FIRO, and is signed with the correct private key. This prevents users from accidentally spending an extra 1000 FIRO and makes the registration compatible with standard Firo masternode requirements.
AI review queuedfeat: use token ticker in confirm send dialog if it's availableby sneurlax · 6fca0f15 · Mar 3, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
feat: use token ticker in confirm send dialog if it's available
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 15/100
This commit is a minor user-interface improvement. It changes the transaction confirmation screen so that when sending a token, the token's short name (ticker) is shown in the desktop send-authorization widget instead of falling back to the main coin name. There is no security-relevant change visible in the code.
AI review queuedfeat: add ordinal spend warning to confirm transaction viewby sneurlax · e673f614 · Mar 3, 2026 · 1 fileMessage 62 · AdequateInformational 19Details
Commit message · sneurlax
feat: add ordinal spend warning to confirm transaction view
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 19/100
This commit adds a warning message shown to users when they are about to spend a Bitcoin UTXO that contains an ordinal inscription. It is a user-interface safety feature, not a fix for a code vulnerability. It helps prevent users from accidentally spending or losing valuable or meaningful inscription assets.
AI review queuedfeat: never peg ordinals into MWEBby sneurlax · 1e5cf6e2 · Mar 3, 2026 · 1 fileMessage 57 · ThinModerate 59Details
Commit message · sneurlax
feat: never peg ordinals into MWEB
it destroys them
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 · Moderate 59/100
This update prevents a user's wallet from accidentally sending special Bitcoin assets called 'ordinals' into a privacy feature called MWEB. Ordinals are unique digital items stored on Bitcoin, and sending them into MWEB would permanently destroy them. The change filters out any UTXOs (chunks of Bitcoin) that carry ordinals before they can be pegged into MWEB.
AI review queuedfeat: add prepareOrdinalSend to ordinals interfaceby sneurlax · 63aa9ef2 · Mar 3, 2026 · 1 fileMessage 62 · AdequateInformational 16Details
Commit message · sneurlax
feat: add prepareOrdinalSend to ordinals interface
w a single input send-all
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 16/100
This commit adds a new helper function for sending Bitcoin ordinals (special NFT-like assets). It builds a transaction that spends only the single ordinal coin and sends it to a recipient. The change temporarily unblocks a 'blocked' ordinal UTXO so the wallet's coin selection will accept it, then re-blocks it afterward. There is no obvious security bug in the diff, but the code touches sensitive areas: coin control, blocked UTXO state, fee handling, and ordinal preservation. The safety of the function depends heavily on whether the underlying prepareSend correctly handles a single-input send-all and does not accidentally add extra inputs or change outputs that could split or lose the ordinal.
AI review queuedfix: check isOnline before offlineMode in Xelis exit()by sneurlax · 00b95a0e · Mar 1, 2026 · 1 fileMessage 62 · AdequateLow 30Details
Commit message · sneurlax
fix: check isOnline before offlineMode in Xelis exit()
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 · Low 30/100
This is a small, defensive bug fix in the Xelis cryptocurrency wallet's shutdown code. Before the change, the wallet always tried to put itself into 'offline mode' when exiting, even if it was already offline. After the change, it first checks whether the wallet is actually online and only then switches to offline mode. The main risk is avoiding unnecessary or incorrect state changes during shutdown, which could potentially cause crashes, resource leaks, or confusion in wallet state. There is no direct evidence of a security vulnerability being exploited.
AI review queuedfix: temp input script index in particl buildTransactionby sneurlax · 933d2686 · Mar 1, 2026 · 1 fileMessage 42 · ThinLow 41Details
Commit message · sneurlax
fix: temp input script index in particl buildTransaction
42/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 41/100
This commit fixes a small but meaningful bug in how Stack Wallet builds Particl cryptocurrency transactions. The code was accidentally reading the script signature from the first input for every input, instead of reading the correct one for each input. That could corrupt the transaction data the wallet stores or signs, potentially causing invalid transactions, failed sends, or in the worst case a security issue if the wrong data is signed. The fix changes one index from 'first input' to 'current input'.
AI review queuedfix: witness field parsing in particl updateTransactionsby sneurlax · 42e8cec0 · Mar 1, 2026 · 1 fileMessage 62 · AdequateLow 34Details
Commit message · sneurlax
fix: witness field parsing in particl updateTransactions
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 · Low 34/100
This commit fixes how the Particl wallet reads transaction input data, specifically the 'witness' field, by switching to a dedicated parser instead of manually pulling fields. The change suggests the previous code may have misread or mishandled witness data, which could cause incorrect transaction details, failed transactions, or wallet display errors for Particl users. There is no claim in the commit that this is a security fix, and no independent security analysis is supplied.
AI review queuedfix: checkBlockUTXO only checking the specific UTXO outputby sneurlax · 8b82eb1c · Mar 1, 2026 · 1 fileMessage 62 · AdequateLow 40Details
Commit message · sneurlax
fix: checkBlockUTXO only checking the specific UTXO output
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 · Low 40/100
This commit fixes a bug in how Stack Wallet checks whether a Particl coin can be spent. Previously, the wallet looked at every output in the entire transaction to decide if a single coin (UTXO) was blocked. If any unrelated output in the same transaction was a blind/confidential/data/staking output, the wallet would wrongly mark the user's spendable coin as blocked too. Now it only checks the specific output that actually belongs to the coin in question. This is a correctness fix that could prevent coins from being incorrectly frozen or hidden from the user, but it does not appear to be a direct theft or remote-code-execution vulnerability.
AI review queuedfix: ordinals by looking up tx info directlyby sneurlax · dd8be539 · Mar 1, 2026 · 4 filesMessage 80 · StrongLow 35Details
Commit message · sneurlax
fix: ordinals by looking up tx info directly
TODO: remove (comment?) dead code litescribe_api.dart, litescribe_response.dart, address_inscription_response.dart are now orphaned
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100
This commit changes how the Stack Wallet app detects Litecoin Ordinals (a type of digital collectible). Instead of asking a third-party service (litescribe.io) which inscriptions belong to a wallet address, the app now asks its own ord-litecoin.stackwallet.com server directly about each transaction output. The change removes a heuristic that blocked small outputs as 'possible ordinals' only when an address-level check passed, and instead checks each output directly. There is no clear security bug being fixed, but the commit does switch data sources and removes some protective logic around small-value outputs.
AI review queueddelete custom epicbox impl and some other minimal working changesby julian · aa20a549 · Feb 4, 2026 · 8 filesMessage 50 · ThinInformational 18Details
Commit message · julian
delete custom epicbox impl and some other minimal working changes
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 commit removes a custom Epicbox server implementation from the Stack Wallet app and switches the UI to use a built-in list of default Epicbox servers. It also adds delete buttons for custom servers and changes how default servers are stored. There is no clear security fix here; it looks like a feature refactor or cleanup that may have minor side effects on how server settings are saved and restored.
AI review queuedfeat: add mobile epicbox server mgmt uiby sneurlax · 03eb5861 · Feb 4, 2026 · 5 filesMessage 57 · ThinInformational 16Details
Commit message · sneurlax
feat: add mobile epicbox server mgmt ui
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 16/100
This commit adds a new mobile screen for managing 'Epicbox' servers used by Epic Cash wallets. It lets users add, edit, and pick custom server addresses. The change is a feature addition; there is no direct evidence in the commit that it fixes a security bug or introduces a clear vulnerability, but it does expose network endpoint configuration to the user and performs live connection tests from the app.
AI review queuedclean up txv2by julian · d2f99c98 · Feb 3, 2026 · 1 fileMessage 28 · OpaqueInformational 16Details
Commit message · julian
clean up txv2
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 16/100
This commit tidies up a Dart file that decides what text label to show for cryptocurrency transactions (for example, 'Received', 'Sending', or 'Cancelled'). It removes a large block of duplicated code and changes the logic that decides when a transaction is 'waiting for sender' or 'waiting for receiver' so it also considers whether an optional on-chain note is present. The change is a code cleanup with a small logic adjustment; there is no direct evidence it fixes a security vulnerability.
AI review queuedfix address orderby julian · be51789f · Feb 3, 2026 · 1 fileMessage 28 · OpaqueLow 29Details
Commit message · julian
fix address order
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 29/100
This commit fixes a likely data-labeling bug in the Epic Cash wallet code. The previous code assigned the sender's address to a transaction output (money received) and the recipient's address to a transaction input (money spent). The swap corrects this so outputs are labeled with the recipient's address and inputs with the sender's address. This is primarily a correctness/display issue rather than a direct theft vulnerability, but it could mislead users or downstream features about where funds came from or went.
AI review queuedaccount for on chain note in messagesby julian · b4600e13 · Feb 3, 2026 · 1 fileMessage 45 · ThinInformational 17Details
Commit message · julian
account for on chain note in messages
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 17/100
This commit fixes a small logic bug in how Stack Wallet displays the status of certain transactions. Previously, the app did not count an optional on-chain note as one of the messages, so it could show the wrong status label (for example, saying it is still waiting for the sender when it should already be waiting for confirmations). There is no sign this can be used to steal funds or attack users; it is mainly a user-interface correctness fix.
AI review queuedupdate epic when epic box is changed receiving addressby julian · 4e7ac9e2 · Feb 3, 2026 · 2 filesMessage 50 · ThinLow 31Details
Commit message · julian
update epic when epic box is changed receiving address
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 31/100
This commit changes how Stack Wallet handles Epic Cash receiving addresses when the Epic Box server (a messaging relay for this privacy coin) is changed. It removes some default servers, renames others, and adds logic to regenerate and store the wallet's receiving address whenever the Epic Box configuration changes. The change appears to be a bug fix to keep the wallet's displayed address in sync with the active relay server, rather than a security vulnerability fix.
AI review queueddo not say on chain note is optionalby julian · 8a67326f · Feb 3, 2026 · 2 filesMessage 45 · ThinInformational 16Details
Commit message · julian
do not say on chain note is optional
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 16/100
This commit simply removes the word "(optional)" from two on-screen labels in the Stack Wallet app. The labels now say "On chain Note" instead of "On chain Note (optional)". There is no code behavior change, no security fix, and no vulnerability being addressed. It is a minor user-interface wording update.