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 queuedMerge pull request #1528 from cypherstack/fix/taproot-input-sequenceby Julian · 05b0ad33 · Nov 20, 2026 · 1 fileMessage 73 · AdequateModerate 57Details
Commit message · Julian
Merge pull request #1528 from cypherstack/fix/taproot-input-sequence
Preserve input sequence for Taproot key-path spends
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 · Moderate 57/100
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 key-path spends and silently reset to a default value. That could break intended transaction behavior such as time-locked refunds or Replace-By-Fee (RBF), and in some wallet designs could even make a transaction spendable under different conditions than the user expected. The fix simply passes the intended sequence number through when creating the Taproot input.
Lower-priorityMerge pull request #1532 from CumpsD/fix/exchange-currency-icon-casingby Julian · 43660486 · Nov 20, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Julian
Merge pull request #1532 from CumpsD/fix/exchange-currency-icon-casing
fix(exchange): load the currency icon by file type and per selection
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
merge-commit duplicate discount
Lower-priorityfix(exchange): load the currency icon by file type and per selectionby David Cumps · 0df864fd · Nov 19, 2026 · 2 filesMessage 97 · StrongTriage 0Details
Commit message · David Cumps
fix(exchange): load the currency icon by file type and per selection
The exchange amount field loaded every remote currency icon as an SVG, so PNG icons (Wizard Swap, Exolix) failed to decode. Because the widget was reused and VectorGraphic keeps its last picture when a load fails, the previous currency's icon stayed visible, e.g. Monero's icon next to ETH. Load .svg URLs with the SVG loader and anything else as an image, keyed by URL so a new selection never reuses the previous icon.
97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityMerge pull request #1536 from cypherstack/linux-cmake-install-bug-fixby Julian · 05c33bd7 · Nov 19, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Julian
Merge pull request #1536 from cypherstack/linux-cmake-install-bug-fix
Keep Linux Flutter installs inside the build bundle
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI review queuedMerge pull request #1541 from cypherstack/rotate-receiving-address-typesby Julian · 01be23d6 · Nov 18, 2026 · 10 filesMessage 58 · ThinLow 35Details
Commit message · Julian
Merge pull request #1541 from cypherstack/rotate-receiving-address-types
Rotate receiving address types
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 · Low 35/100
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 transaction history. It also changes the 'Buy' flow so that if a user selects a Taproot-only view-only wallet, the app shows a warning and refuses to use it, because that wallet type cannot derive the non-Taproot address the Buy partner requires. The change is primarily a privacy/usability improvement, but it touches address-derivation and transaction-scanning logic.
Merge pull request #1537 from cypherstack/fix/simplex-current-receiving-address
fix(buy): persist and reuse Simplex BIP84 receiving address
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 29/100
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 earlier address to be harder to track or link. The patch makes the app persist and reuse a single BIP84 (SegWit) receiving address, and adds a lock so multiple simultaneous calls don't create duplicate addresses.
AI review queuedTest the Buy form's Choose from Stack flow in the real appby slopbot9k · ba44e64c · Nov 17, 2026 · 7 filesMessage 83 · StrongInformational 15Details
Commit message · slopbot9k
Test the Buy form's Choose from Stack flow in the real app
Nothing ran the Buy form's "Choose from Stack" end to end: that a Taproot wallet gets a saved BIP84 address, that a used address is replaced after a refresh, or that a view only Taproot wallet is turned away with a dialog.
integration_test/buy_flow runs those scenarios against the real desktop app, one launch per file. Bitcoin wallets talk to a fake ElectrumX server on a loopback port and the app's HTTP requests are refused, so a run needs no network. Wallets come from the public BIP test mnemonic, which makes every expected address a known value.
A widget test covers the dialog on the mobile and the desktop layout, where the form sits under different navigators.
TestUI gains an optional report prefix so these tests can reuse it. The wallet creation output is unchanged.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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 existing feature works correctly for different wallet types (Taproot, restored, view-only) and shows the right dialog when a wallet cannot be used.
Lower-prioritySay why a view only Taproot wallet cannot be chosen to buyby slopbot9k · 5613ee21 · Nov 17, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · slopbot9k
Say why a view only Taproot wallet cannot be chosen to buy
Choosing a view only Taproot wallet in the Buy form did nothing. The form asks the wallet for a BIP84 address because Taproot addresses are not allowed, a view only wallet cannot derive one, and the error was swallowed. The address field kept its previous value with no message.
The form now shows a dialog for that case and leaves the address field as it was.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI review queuedRotate used receiving addresses on every derivation pathby slopbot9k · 8998a949 · Nov 17, 2026 · 2 filesMessage 73 · AdequateModerate 52Details
Commit message · slopbot9k
Rotate used receiving addresses on every derivation path
A refresh only checked the current receiving address of the wallet's main address type for history. A used address on any other supported derivation path stayed the latest one, so the Receive view's other address tabs and the Buy form's BIP84 fallback kept handing out an address that already had transactions.
Once the main address is settled, the refresh now also checks the latest saved receiving address of each other supported derivation path and saves the next one while it has history.
Left alone: - paths with no saved receiving address - view-only wallets, whose single path the main check already covers - wallets with address reuse enabled - paths that share the main address type (bch44, eCash44), since saved addresses are looked up by address type
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 52/100
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 generated addresses for other address types (such as older SegWit or legacy addresses), the wallet would keep showing those addresses in its Receive screen and Buy form even after they had already received payments. Reusing addresses is bad for privacy because it lets anyone see all your transactions on that address. The fix makes the wallet check every supported address type and automatically generate a fresh, unused receiving address for each one.
AI review queuedMerge pull request #1529 from cypherstack/fix/electrs-vanished-txby Julian · 1d319093 · Nov 16, 2026 · 1 fileMessage 73 · AdequateLow 36Details
Commit message · Julian
Merge pull request #1529 from cypherstack/fix/electrs-vanished-tx
Recognize vanished unconfirmed transactions on electrs
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 36/100
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 it recognizes the same message across more server types, including electrs. Without this fix, the wallet could fail to clean up transactions that no longer exist, potentially leaving stale or misleading transaction records.
Lower-priorityMerge pull request #1531 from CumpsD/fix/trade-details-duplicate-tickerby Julian · 3e91bcd7 · Nov 16, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Julian
Merge pull request #1531 from CumpsD/fix/trade-details-duplicate-ticker
fix(exchange): show the pay-in ticker once in trade details
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
merge-commit duplicate discount
Lower-priorityfix(exchange): show the pay-in ticker once in trade detailsby David Cumps · 0b3dc5bd · Nov 15, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · David Cumps
fix(exchange): show the pay-in ticker once in trade details
The header formatted known coins with pAmountFormatter, which already appends the display unit, and then appended the ticker again ("-0.02000000 BTC BTC", or "-2,000,000 sats BTC" in sats). Append the ticker only in the fallback for coins the app does not know.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritystyle: dart format trade_details_view.dartby David Cumps · d3ffc339 · Nov 15, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · David Cumps
style: dart format trade_details_view.dart
Formatting only, no logic change. The file predates the Dart 3.13 bump (2dc2473be), and the CI format check covers every changed file in full.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Merge pull request #1505 from cypherstack/repro-dnix-packages
Repro dnix packages
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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. The change also updates CI workflows, Docker images, documentation, and adds many tests. There is nothing in the commit that obviously introduces a security vulnerability; it appears to be a maintainability and reproducibility improvement.
Lower-prioritySplit the build docs into an overview and per-host guidesby slopbot9k · 207ac93d · Nov 13, 2026 · 6 filesMessage 83 · StrongTriage 0Details
Commit message · slopbot9k
Split the build docs into an overview and per-host guides
docs/building.md now covers how a build works, source builds and prebuilts, the configuration options and troubleshooting, and links to a step-by-step guide for each host: docs/building/linux.md, docs/building/macos.md and docs/building/windows.md. Native library details (pinning and verification, local overrides and checkouts, when native hooks run, Xcode pins and CI images) move to docs/building/native-libraries.md, and test instructions to docs/building/testing.md. The macOS guide now says that only dnix's source builds of its four packages need Xcode 27.0 (27A266a), installed under /Applications without being selected; the app builds with your usual Xcode, and building the whole app with 27.0 is optional.
Validation: a script checked that every relative link and heading anchor in the six files resolves under GitHub's heading slugs, and that all 17 code blocks and 14 URLs from the old docs/building.md are still present; git diff --check passed. Apart from a prebuilt macOS configuration on an Apple Silicon Mac, the documented commands were not rerun for this change.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationdocumentation-only discount
Lower-priorityCheck Go for Stack Wallet's MWEB builds on every platformby slopbot9k · cd16799f · Nov 13, 2026 · 3 filesMessage 83 · StrongTriage 0Details
Commit message · slopbot9k
Check Go for Stack Wallet's MWEB builds on every platform
flutter_mwebd's hook builds Stack Wallet's MWEB library with the host's Go for Android, iOS, Linux and macOS during flutter build, run and test, but the preflight only checked the Windows route. Require Go 1.24.1 or newer on the Flutter host for those targets in both modes, matching the go.mod of the mwebd-wrapper commit that flutter_mwebd 0.0.1-pre.12 builds. The Windows WSL check now also requires Go 1.24.0 or newer, from mwebd v0.1.19's go.mod, so an old Go there fails before configuration changes files instead of partway through. Document both minimums.
Validation: build_input, native_build_config, configure_native_assets, build_environment, windows_secp_build and xcode_setup tests pass on macOS; native_dependency_contract fails only its app-package metadata test, which needs the app's flutter pub get. The new tests fail when the host Go check, the version comparison or the WSL version check is removed. Dart analysis with the repo lints, formatting and git diff --check passed. On an Apple Silicon Mac with Go 1.27.3 the preflight passes, and with a fake Go 1.22.2 first on PATH it reports the old version. Nothing was run on Windows or on a Linux host.
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedMerge branch 'staging' into repro-dnix-packagesby Julian · e517d08e · Nov 13, 2026 · 56 filesMessage 45 · ThinModerate 61Details
Commit message · Julian
Merge branch 'staging' into repro-dnix-packages
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
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 remember a specific TLS certificate for each node and will only trust that certificate for that exact host/port/SSL combination; and there are fixes for connection leaks during cancelled wallet restores. The commit also adds many tests for failover, certificate pinning, and Tor routing. It looks like a defensive hardening patch rather than a fix for a single known exploit.
AI review queuedMerge pull request #1510 from cypherstack/electrum-client-per-wallet-refactorby Julian · a7d86094 · Nov 13, 2026 · 56 filesMessage 58 · ThinModerate 61Details
Commit message · Julian
Merge pull request #1510 from cypherstack/electrum-client-per-wallet-refactor
Electrum client per wallet refactor
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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 close connections. The change gives each wallet its own Electrum client, adds per-request timeouts, improves failover logic, and introduces a way to pin a specific TLS certificate for a node instead of blindly trusting any certificate. It also fixes several lifecycle bugs where restore/cancel flows could leave connections open. The commit is defensive in nature and does not appear to introduce a new vulnerability, but because it is large and touches certificate handling, it warrants careful review.
Security candidateStop describing a certificate approval as a pinby slopbot9k · 4b88ce9a · Nov 13, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · slopbot9k
Stop describing a certificate approval as a pin
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 15/100
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 change.
AI review queuedFormat the view-only restore viewby slopbot9k · 6d56c42b · Nov 12, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · slopbot9k
Format the view-only restore view
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 15/100
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.
Merge remote-tracking branch 'upstream/staging' into electrumx-per-wallet
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Low 33/100
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 widgets. The change is primarily a code-quality/feature refactor; there is no direct evidence in the commit message or diff that it fixes a specific security vulnerability. However, because fee handling touches how much users pay and how transactions are built, any bug in the refactor could affect user funds or transaction reliability.
Merge pull request #1511 from Cyrix126/share_send_fee_logic
refactor: share the send fee logic across send's 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
cryptography-sensitive pathsigning or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Low 34/100
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 sends. The diff itself is mostly cleanup and consolidation; it does not obviously add or remove security checks, but any refactor touching transaction-fee handling deserves a careful look because mistakes here could affect how much fee a user pays or whether a transaction is constructed correctly.
Merge pull request #1509 from cypherstack/feat/monero-signing
feat(xmr): sign and verify messages
68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100
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 patch.
Security candidatefeat(xmr): sign and verify messagesby sneurlax · 6c49e3ce · Nov 10, 2026 · 3 filesMessage 90 · StrongInformational 17Details
Commit message · sneurlax
feat(xmr): sign and verify messages
Implement SignVerifyInterface on LibMoneroWallet so Monero wallets get the existing Sign / Verify view. cs_monero 4.0.0 already wraps MONERO_Wallet_signMessage and MONERO_Wallet_verifySignedMessage, so this only forwards them through CsMoneroInterface.
Signatures are wallet2 SigV2 spend-key signatures for the chosen primary address or subaddress, compatible with monero-wallet-cli/rpc sign and verify. wallet2 returns an empty string instead of throwing when signing fails, so treat that as an error. View-only wallets cannot sign.
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundaryprivacy or spend-authorization protocolsigning or wallet path
AI analysis · Informational 17/100
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 indication in the commit that it addresses a vulnerability or security incident.
AI review queuedDrop vanished unconfirmed txs on electrs tooby sneurlax · a31b28b6 · Nov 10, 2026 · 1 fileMessage 86 · StrongLow 43Details
Commit message · sneurlax
Drop vanished unconfirmed txs on electrs too
updateTransactions re-fetches stored unconfirmed txs and deletes the ones the server no longer has, but it recognised that only by ElectrumX's exact wording ("daemon error: DaemonError({'code': -5, ..."). electrs passes bitcoind's message through unwrapped, so a replaced or dropped tx was never deleted and every later refresh failed: one RBF bump left a wallet on an electrs server unable to sync. Match bitcoind's message alone, as ElectrumXClient.request already does.
Related to #1411 (electrs servers). Covered by rbf_cpfp_test.dart against electrs in the Bitcoin regtest tests (feat/regtest).
86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 43/100
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/Fulcrum's specific error wording and ignored electrs' simpler error message. As a result, a replaced or dropped transaction stayed in the wallet and blocked future refreshes, leaving the wallet unable to sync. The fix makes the check look for the simpler message that all server types share.