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…
Merge pull request #1469 from Cyrix126/building_dialog_cancel
fix: mobile, canceling a transaction build closes an extra view
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Informational 24/100
This commit fixes a mobile UI bug where pressing Cancel on a 'building transaction' dialog accidentally closed one too many screens. The fix moves the responsibility for closing the dialog into each screen's cancel handler, and prevents error dialogs from appearing after the user has already cancelled. It is a user-experience bug fix, not a security vulnerability.
AI review queuedMerge branch 'staging' into building_dialog_cancelby Julian · 0485b166 · Oct 8, 2026 · 6 filesMessage 50 · ThinInformational 20Details
Commit message · Julian
Merge branch 'staging' into building_dialog_cancel
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This commit is a routine merge from the project's staging branch into a feature branch. The visible code changes fix small UI/UX bugs in Stack Wallet's send screens: clearing an internal address-validation cache when the form is reset, making desktop fee estimates fetch only once (and retry after a failure), and adding QR-code scan buttons to two desktop token send pages. There is no direct evidence in the commit that these were security vulnerabilities, and the commit message does not describe security relevance.
AI review queuedMerge pull request #1468 from Cyrix126/desktop_fee_form_refetchby Julian · 62432946 · Oct 8, 2026 · 2 filesMessage 58 · ThinInformational 17Details
Commit message · Julian
Merge pull request #1468 from Cyrix126/desktop_fee_form_refetch
Desktop fee form refetch
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit fixes a desktop wallet bug where the send-fee form would repeatedly re-fetch fee estimates on every screen rebuild, wasting resources and possibly flickering. It now caches the fee estimate and only retries if the previous fetch failed. There is no indication this is a security fix.
AI review queuedMerge branch 'staging' into desktop_fee_form_refetchby Julian · 8a72c82f · Oct 8, 2026 · 4 filesMessage 50 · ThinInformational 17Details
Commit message · Julian
Merge branch 'staging' into desktop_fee_form_refetch
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit merges a feature branch into another work-in-progress branch. It adds QR-code scanning buttons to two desktop token send screens and resets an internal address-validation state variable when the send form is cleared. There is no direct evidence in the commit that these changes fix a security vulnerability; they appear to be normal UI/UX improvements and state cleanup.
AI review queuedMerge pull request #1467 from Cyrix126/clear_send_form_validityby Julian · d3383b4e · Oct 8, 2026 · 2 filesMessage 73 · AdequateLow 32Details
Commit message · Julian
Merge pull request #1467 from Cyrix126/clear_send_form_validity
fix: reset the address validity when clearing the send form
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 32/100
This change fixes a UI state bug in the cryptocurrency wallet's send form. When a user clears the send form, the app now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing an old address as valid after the user cleared it, which might confuse someone into thinking a new or empty address is acceptable. There is no direct evidence in the commit of funds being stolen or a remote attack.
AI review queuedMerge branch 'staging' into clear_send_form_validityby Julian · 22560a59 · Oct 8, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Julian
Merge branch 'staging' into clear_send_form_validity
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a QR code scanner button to two desktop cryptocurrency send forms. It is a straightforward user-interface feature addition with no apparent security relevance.
AI review queuedMerge pull request #1466 from Cyrix126/desktop_token_qr_buttonby Julian · 47f6d369 · Oct 8, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · Julian
Merge pull request #1466 from Cyrix126/desktop_token_qr_button
fix: add missing QR scan button to desktop token send views
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This commit adds a missing QR code scan button to two desktop token send screens in the Stack Wallet app. It is a straightforward user-interface fix that restores a feature already present on mobile and other send views; there is no indication it fixes a security vulnerability.
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is purely a code-formatting cleanup. It changes line breaks and indentation in four user-interface files so the code is easier to read, but it does not change what the app actually does. There is no security relevance.
AI review queuedstyle: formattingby Cyrix126 · 09ed5441 · Oct 8, 2026 · 4 filesMessage 18 · OpaqueInformational 15Details
Commit message · Cyrix126
style: formatting
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 contains only cosmetic code formatting changes—adjusting line breaks and indentation in four files. There are no functional changes, no bug fixes, and no security-related modifications.
AI review queuedfix: stop estimating the desktop fee for a zero amountby Cyrix126 · 90c91bde · Oct 7, 2026 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · Cyrix126
fix: stop estimating the desktop fee for a zero amount
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 23/100
This commit fixes a UI bug in the desktop version of Stack Wallet where the send amount could be lost while the app was trying to estimate transaction fees. The fix keeps the amount 'alive' in memory so fee estimation does not accidentally reset it to zero. There is no direct evidence this is a security vulnerability, but it could cause user confusion or failed transactions.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 32/100
This commit updates the Stack Wallet app so that when a single payment is broken into multiple cryptocurrency transactions, the user sees a clear warning on the confirmation screen. It also changes the app's internal record-keeping to handle multiple transaction IDs (txids) instead of assuming there is always just one. The main risk being addressed is that a user might accidentally send a split payment to a vendor or exchange that only credits single-transaction payments, leading to lost or miscredited funds.
AI review queuedfix: stop refetching the desktop fee rates on every rebuildby Cyrix126 · a1ca9292 · Oct 7, 2026 · 2 filesMessage 62 · AdequateInformational 18Details
Commit message · Cyrix126
fix: stop refetching the desktop fee rates on every rebuild
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit fixes a performance bug in the desktop version of Stack Wallet where the app repeatedly re-fetched Bitcoin-style fee rates every time the on-screen fee form rebuilt. The change caches the fee result and only fetches again if the previous attempt failed. It is primarily a reliability/efficiency improvement, not a security fix.
AI review queuedfix: reset the address validity when clearing the send formby Cyrix126 · 43dd0477 · Oct 6, 2026 · 2 filesMessage 62 · AdequateLow 34Details
Commit message · Cyrix126
fix: reset the address validity when clearing the send form
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 a UI state bug in Stack Wallet's send form. When a user clears the send form, the wallet now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing an old address as valid after the user cleared it, which might confuse someone into thinking a new or empty address is ready to send to.
Merge pull request #1450 from Ez3kiel-dev/fix/xelis-integration
fix(xelis): restore wallet integration with XWF
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 35/100
This is a large feature/fix merge that restores and rewrites the Xelis (XEL) cryptocurrency integration in Stack Wallet. It swaps the old hand-rolled Xelis code for a new generated native interface (XWF), adds wallet restore/backup support, improves send-flow safety by cancelling prepared transactions when the user leaves the confirmation screen, and adds many integration tests. There is no direct evidence in the commit of an active security vulnerability being patched; the changes look like a substantial integration repair with several defensive-hardening improvements.
Security candidateMerge branch 'staging' into fix/xelis-integrationby Julian · b0e5d35a · Oct 6, 2026 · 78 filesMessage 45 · ThinLow 32Details
Commit message · Julian
Merge branch 'staging' into fix/xelis-integration
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Low 32/100
This commit is a large merge that mainly adds integration tests for a desktop 'forgot password' reset feature and makes supporting code changes to safely shut down background database workers during that reset. It also removes a large set of older mobile integration tests and updates linting rules. The security-relevant part is the reset flow: when a desktop user forgets their password, the app can delete all local wallet data and quit. The new tests verify that the deletion really happens, that sensitive files are removed, that backups and certain other files are kept, and that the app handles failures safely without leaving data behind.
AI review queuedMerge pull request #1361 from cypherstack/fix/305-multiline-transaction-notesby Julian · 5172e63e · Oct 5, 2026 · 3 filesMessage 73 · AdequateInformational 19Details
Commit message · Julian
Merge pull request #1361 from cypherstack/fix/305-multiline-transaction-notes
fix: support multiple lines in transaction note editing
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit lets users type multi-line notes when editing transaction and trade notes, and fixes the desktop layout so long notes scroll instead of breaking the screen. It also swaps the old `mounted` check for the newer `context.mounted` pattern. There is no security issue here; it is a straightforward user-interface improvement with added tests.
Monero payment URIs can list several recipients, e.g. `monero:A;B?tx_amount=1;2&recipient_name=x;y`. Parse these into PaymentUriData.recipients, requiring one amount (and, when given, one name) per address. Callers opt in with allowMultipleRecipients, so screens that handle a single address reject these URIs rather than dropping recipients.
Monero wallets now report supportsMultiRecipient. On their mobile and desktop send screens, "Add recipient" or a multi-recipient URI replaces the address field with the Recipient forms started for FROST, one per recipient, which can be added to and removed. A multi-recipient URI scanned or pasted into one of those forms asks before replacing all the recipients. A multi-recipient URI rejected for its amounts clears the previous recipient and amount, so Preview can't send them instead. The amount field shows their total, and removing all but one recipient returns to the normal form. The transaction has one output per recipient, and the confirmation screen lists each recipient with its name and amount.
The Recipient form now: - shows the payment request's name for its address, and flags an invalid address; - fills in the address, amount, and name from a pasted payment request, as it did from a scanned one; - scans with the desktop QR code scanner on desktop; - keeps its amount, rather than the number typed, when the display unit changes, which otherwise read e.g. 1000 mXMR as 1000 XMR. The send screens' amount field does the same, keeping any Xelis send all. Recipient forms are kept per wallet, so recipients entered for one wallet never appear in another wallet's form.
prepareSend no longer treats a multi-recipient total equal to the whole balance as sending the whole balance, which it then rejected for multiple recipients; the fee has to fit in the balance as for any other amount.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100
This commit adds support for Monero payment URIs that contain multiple recipients, such as a single QR code or link that pays several people at once. It also fixes a related display bug where changing the currency unit (for example from XMR to milli-XMR) would misread the typed number. The changes are a feature addition with some defensive hardening, not a patch for an active security vulnerability.
Security candidateMerge branch 'staging' into fix/305-multiline-transaction-notesby Julian · 21491edb · Oct 5, 2026 · 75 filesMessage 50 · ThinLow 32Details
Commit message · Julian
Merge branch 'staging' into fix/305-multiline-transaction-notes
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Low 32/100
This commit is a large merge that mainly removes old integration tests and adds new desktop 'forgot password' reset tests. It also adds a safe-shutdown path for background Firo cache workers and databases. The changes look like defensive hardening for a data-wipe feature rather than an active security vulnerability. There is no clear exploit or malicious change in the diff, but the merge is broad and the actual production reset logic is only partially visible, so we cannot fully verify it is safe.
Merge pull request #1455 from cypherstack/fix/desktop-pw-reset
fix(desktop): desktop forgot password flow and app startup process re…
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Moderate 57/100
This commit fixes the desktop "forgot password" reset flow in Stack Wallet. It adds integration tests that verify the app can securely wipe its own data when a user forgets the desktop password, and it updates the Firo cache worker to close cleanly during that wipe. The change is defensive: it makes sure databases and background workers shut down before files are deleted, so leftover data or crashed workers do not leave sensitive information behind.
AI review queuedMerge branch 'staging' into fix/desktop-pw-resetby Julian · d9b5cc02 · Oct 5, 2026 · 23 filesMessage 45 · ThinLow 37Details
Commit message · Julian
Merge branch 'staging' into fix/desktop-pw-reset
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
This commit is a large merge that mainly adds a new 'prove you own a Spark address' feature to the Stack Wallet app, plus some related fixes. It also updates a dependency that handles SOCKS5 proxy connections and changes how the app decides whether it is running on a desktop or phone. The changes look like ordinary feature work rather than an obvious security patch, but a few areas could affect security: the new ownership-proof code uses private keys, the proxy library upgrade could change how Tor/proxy traffic is routed, and the desktop-detection refactor changes platform assumptions across the app.
AI review queuedMerge pull request #1439 from navidR/dev/navidr/spark-name-verificationby Julian · a5411a50 · Oct 5, 2026 · 16 filesMessage 83 · StrongLow 34Details
Commit message · Julian
Merge pull request #1439 from navidR/dev/navidr/spark-name-verification
Spark Names: add ownership proof generation
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit adds a new feature to Stack Wallet that lets users prove they own a Spark (privacy) address by generating a cryptographic ownership proof. It also improves the sign/verify screens so view-only wallets can still verify proofs, and it fixes message handling so pasted or typed messages keep their exact spaces and line breaks instead of being silently trimmed. The changes are mostly new feature code plus hardening of the UI around message integrity.
AI review queuedMerge branch 'staging' into dev/navidr/spark-name-verificationby Julian · 92955848 · Oct 5, 2026 · 7 filesMessage 60 · AdequateLow 39Details
Commit message · Julian
Merge branch 'staging' into dev/navidr/spark-name-verification
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 39/100
This commit merges several changes into a development branch. The most notable security-relevant change is a fix for how the Trocador exchange service routes traffic: it now automatically uses Tor (an anonymity network) when the user has Tor enabled, instead of callers hardcoding non-Tor connections. Previously, exchange calls always used the regular internet even if Tor was turned on, which could leak a user's IP address and trading activity to Trocador. The commit also updates the SOCKS5 proxy library and adds a test to verify that proxy requests correctly send hostnames (including .onion addresses) to the SOCKS server. Separately, it adds a small UI convenience: when paying a Spark private address, a payment message is auto-filled into the memo field, matching Firo-QT's behavior.
Spark: add address ownership proof signing and verification
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · Informational 24/100
This commit adds a new feature to Stack Wallet that lets Spark (Firo privacy) address owners prove they control an address, and lets others verify that proof. It also fixes a few related UI issues: view-only wallets can now only verify (not sign) Spark proofs, pasted messages keep exact spaces/newlines instead of being trimmed, and the signing/verification screens scroll properly on desktop. There is no direct evidence in the commit that this fixes an active security vulnerability; it reads as a feature addition with some hardening improvements.
AI review queuedMerge branch 'staging' into feat/trocador-onionby Julian · a0a72593 · Oct 5, 2026 · 2 filesMessage 45 · ThinInformational 20Details
Commit message · Julian
Merge branch 'staging' into feat/trocador-onion
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This commit adds a small convenience feature in Stack Wallet: when a user scans or opens a Firo payment QR code that contains a 'message' field and the payment address is a Spark privacy address, the wallet now automatically copies that message into the Spark memo field. Spark memos are like short notes attached to private Firo transactions. The change is a user-experience improvement to match how the official Firo desktop wallet (firo-qt) behaves. There is no obvious security bug in the code itself, but it does involve handling untrusted payment data and trusting a third-party address-validation helper.
AI review queuedMerge pull request #1463 from cypherstack/fix/firo-uri-message-to-spark-memoby Julian · 48d10009 · Oct 5, 2026 · 2 filesMessage 73 · AdequateInformational 19Details
Commit message · Julian
Merge pull request #1463 from cypherstack/fix/firo-uri-message-to-spark-memo
Firo: fill spark memo from payment URI message
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit fixes a small user-experience gap in the Stack Wallet app for Firo cryptocurrency users. When someone scans or opens a Firo payment link (URI) that includes a message and the payment is going to a Spark privacy address, the app now correctly copies that message into the Spark memo field. Previously, the message was apparently ignored for Spark addresses. There is no indication this is a security vulnerability; it is a feature-completion/fix for wallet behavior matching the official Firo wallet (firo-qt).