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 #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.
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.
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.
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.
Security candidateMerge branch 'staging' into fix/eth-add-token-new-walletby Julian · fbc7a683 · Nov 10, 2026 · 151 filesMessage 50 · ThinLow 45Details
Commit message · Julian
Merge branch 'staging' into fix/eth-add-token-new-wallet
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 45/100
This is a large merge commit that brings in many changes, most of which are defensive hardening and testing rather than a single obvious vulnerability fix. The most user-visible security improvements are: network images (token icons, exchange logos, card images) now route through the app's Tor-aware HTTP client instead of going directly over clearnet; Firo's Spark anonymity-set cache gets safer reset/recovery logic to avoid corrupting privacy data; and new integration tests verify that wallet creation actually produces recoverable seeds and addresses. There is also a database migration that enables Tor for the Fact0rn default node. The commit does not describe a specific CVE or credit an external researcher, and the diff is too broad to treat as a focused security patch.
Security candidatePin camera_linux to cypherstack/camera-linux mainby sneurlax · 3f81beb7 · Nov 6, 2026 · 2 filesMessage 45 · ThinInformational 13Details
Commit message · sneurlax
Pin camera_linux to cypherstack/camera-linux main
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 13/100
This commit changes which external camera plugin source Stack Wallet uses. It switches from a personal developer's copy (sneurlax/camera-linux) to the project's own organization copy (cypherstack/camera-linux) and updates to a newer commit. This is a supply-chain/maintenance change, not a code fix. There is no direct evidence in the commit that it fixes a security vulnerability, but pinning dependencies to an organization-controlled repository is generally a good hygiene practice that reduces future supply-chain risk.
This commit adds a startup warning in Stack Wallet's desktop versions. If a required native library file is missing or blocked by antivirus software, the app now shows a one-time dialog explaining which wallets are affected and why. It does not change how wallets open or fix any underlying vulnerability; it only improves user-facing error reporting.
Security candidateMerge branch 'staging' into fix/native-library-check-hybridby sneurlax · 945b09e0 · Nov 5, 2026 · 90 filesMessage 50 · ThinLow 32Details
Commit message · sneurlax
Merge branch 'staging' into fix/native-library-check-hybrid
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Low 32/100
This is a large merge commit that mostly adds automated wallet-creation integration tests and fixes several UI/data-handling bugs. The changes do not appear to introduce a deliberate backdoor or remote exploit. The most security-relevant fixes are: (1) Firo's Spark coin cache is now reset in a safer, crash-recoverable way instead of deleting rows while another process might be reading them; (2) the exchange form no longer uses predictable UUIDs to decide which price request to display, replacing them with a simpler object-token that should reduce race-condition bugs; (3) several send/confirm screens now treat an empty amount as null/zero rather than a real zero amount, which could prevent accidental dust or zero-value transactions; and (4) a debug print statement that leaked the correct recovery-phrase word during onboarding was removed. There are also many test-only files and formatting changes.
Merge pull request #1501 from cypherstack/various-patches
Various patches
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
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Low 38/100
This is a large routine merge of bug fixes and test additions for the Stack Wallet cryptocurrency app. The visible code changes fix UI glitches, make Firo's privacy cache reset more reliable, clean up exchange-rate refresh logic, and add a new suite of wallet-creation integration tests. None of the changes appear to introduce a security vulnerability; several look like defensive hardening against race conditions and stale data.
Merge pull request #1502 from cypherstack/chore/update-mobile-app-privacy
chore: update mobile_app_privacy pin
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
access controlmerge-commit duplicate discount
AI analysis · Low 30/100
This commit only updates a Git dependency pin for a private Cypher Stack package called mobile_app_privacy from one commit hash to another. The actual code changes in the referenced repository are not visible in this diff, so we cannot determine what security relevance, if any, the new pin has. It is a routine dependency bump unless the underlying package update fixes a privacy or security issue.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 6/100
This commit only updates a Git dependency pin (a reference to another repository) for a package called mobile_app_privacy. The actual code changes in that package are not shown, and no security relevance is stated. On its own, this commit does not reveal any vulnerability or security fix.
Security candidateMerge branch 'staging' into fix/desktop-address-book-chooserby Julian · d13b7b54 · Nov 3, 2026 · 45 filesMessage 50 · ThinModerate 63Details
Commit message · Julian
Merge branch 'staging' into fix/desktop-address-book-chooser
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 pathauthentication pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Moderate 63/100
This large merge commit mostly hardens privacy and fixes amount-input bugs. It routes remote images through Tor when the user has Tor enabled, switches several coins (Fact0rn, Ethereum, Nano) to support Tor, and rewrites amount parsing so changing currency units or locales does not accidentally alter the value being sent. It also migrates existing Fact0rn default nodes to allow Tor while leaving user-customised nodes untouched, and stops Ethereum/Stellar node tests from silently bypassing the Tor proxy.
Merge pull request #1494 from cypherstack/pr1479/eth-transport-controls
Let ETH nodes choose Tor or clearnet
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
cryptography-sensitive pathsigning or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Low 47/100
This update improves privacy and security in Stack Wallet by making network image downloads and Ethereum/Stellar node connections respect the user's Tor setting. Previously, Ethereum could not route through Tor and several image loaders always used the regular internet, potentially exposing user activity. The patch also enables Tor by default for the Fact0rn coin's built-in node and lets users choose Tor/clearnet/both for Ethereum nodes. It is a defensive privacy fix rather than a remote exploit.
Security candidatefix(desktop qr): scan Windows camera frames from the preview in memoryby sneurlax · a04c7814 · Nov 2, 2026 · 4 filesMessage 100 · StrongHigh 74Details
Commit message · sneurlax
fix(desktop qr): scan Windows camera frames from the preview in memory
camera_windows' takePicture() always saves a JPEG in the user's Pictures folder. Deleting it afterwards still puts a QR code, which may hold a seed or private key, on disk, where OneDrive sync, file recovery or the indexer can pick it up. Show the live preview texture instead and capture it in memory with RepaintBoundary.toImage(), at the camera's own resolution capped at 1280 px. camera_windows mirrors its preview, so the capture is flipped back before decoding. Drop the capture cleanup code and its test.
Errors are drawn over the preview rather than replacing it, so capture keeps running and the error clears when frames come back. Blank frames (nothing drawn yet, or a covered lens) are logged once and skipped with the usual delay, and a spinner shows until the first frame arrives.
Tested on Windows 11 with a USB webcam under Impeller and Skia: preview captures are 640x480, two QR codes (one about 260 characters) scan in the add-node view, and nothing is written to Pictures.
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
secret or key material
AI analysis · High 74/100
This commit fixes a privacy/security bug in Stack Wallet's Windows QR scanner. Previously, every time the app scanned a QR code on Windows, it called the camera plugin's takePicture(), which permanently saved a JPEG of the QR code (which could contain a wallet seed or private key) to the user's Pictures folder. Even deleting the file afterward left a window where OneDrive, search indexing, file recovery tools, or other software could access it. The fix captures the live camera preview directly in memory, scans it without writing anything to disk, and adds tests for the new in-memory frame handling.
Merge pull request #1476 from cypherstack/fix/recipient-locale-change
Fix recipient amounts being cleared on locale changes
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 pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 33/100
This commit fixes a UI bug in Stack Wallet where changing the app's language/locale or the amount unit (like switching from full coins to milli-coins) would accidentally clear or alter the recipient's entered amount. The fix separates 'display updates' from actual user input so the wallet keeps the intended payment amount while only reformatting how it looks. It also adds many automated tests to prevent the bug from returning.
Security candidateMerge branch 'staging' into fix/recipient-locale-changeby Julian · 6fb054b1 · Nov 2, 2026 · 30 filesMessage 50 · ThinModerate 61Details
Commit message · Julian
Merge branch 'staging' into fix/recipient-locale-change
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 pathmerge-commit duplicate discount
AI analysis · Moderate 61/100
This commit is a large merge that adds two main security features to Stack Wallet: OpenAlias support (letting users type human-readable aliases like alice@example.com instead of long crypto addresses) and stronger verification of transaction data received from ElectrumX servers. The server-verification changes are defensive: they make the wallet check raw transaction bytes and signatures before trusting sizes or coin values, which helps protect against a malicious or compromised server lying about balances or transaction sizes. The OpenAlias feature introduces new network lookups that, if mishandled, could leak which addresses a user is paying, but the code routes them through Tor when enabled and blocks them in Incognito mode.
Merge pull request #1456 from cypherstack/feat/openalias
Add OpenAlias for Monero sends
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
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 31/100
This commit adds OpenAlias support for Monero sends in Stack Wallet. OpenAlias lets users type a human-readable alias (like alice@example.com) instead of a long crypto address; the wallet then looks up the corresponding Monero address via DNS. The change introduces a new lookup service, wires it into the mobile and desktop send flows, and shows the resolved alias on the confirmation screen. It also adds many tests. There is no direct evidence in the commit of a security vulnerability, but any DNS-based alias system introduces new trust and privacy considerations.
Security candidateMerge branch 'staging' into feat/openaliasby Julian · ad1efd57 · Oct 30, 2026 · 15 filesMessage 45 · ThinModerate 64Details
Commit message · Julian
Merge branch 'staging' into feat/openalias
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 64/100
This commit adds a defensive security feature to Stack Wallet that verifies transactions and coin values received from ElectrumX servers before trusting them. It protects against a malicious or compromised server lying about transaction sizes, coin values, or transaction contents. The wallet now fetches raw transaction bytes, checks they hash to the expected transaction ID, verifies the wallet's own signatures, and for older P2PKH coins cross-checks the parent transaction to confirm the amount. Unverified transactions are dropped and unverified coins are blocked from spending. The commit also fixes RBF (Replace-By-Fee) fee calculations to use verified sizes and follow Bitcoin's replacement fee rules.
Merge pull request #1480 from cypherstack/verify-inputs
verify legacy inputs
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
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · High 75/100
This commit adds cryptographic verification to stop a malicious or compromised ElectrumX server from lying to the wallet. Before this change, the wallet trusted the server for transaction sizes, UTXO values, and unconfirmed transaction details. A dishonest server could trick the user into overpaying fees, accepting fake payments, or trying to spend coins that do not exist. The patch makes the wallet fetch raw transaction bytes, check that they hash to the claimed transaction ID, verify that the wallet itself signed the inputs, and, for older P2PKH coins, confirm the spent amounts against the parent transaction. If verification fails, the wallet drops or blocks the suspicious transaction or coin.
✓ Subject identifies a change✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · High 80/100
This commit adds cryptographic checks that make sure transaction data coming from ElectrumX servers really was signed by the user's wallet and matches the amounts the wallet expects. Before this change, a malicious or buggy server could lie about a coin's value, a pending transaction's size, or even invent a fake spend that the wallet would trust. The fix verifies raw transaction bytes, checks signatures, and for older 'legacy' P2PKH inputs it also fetches and checks the parent transaction to confirm the amount. If verification fails, the wallet now blocks the coin or drops the unverified transaction instead of using it.
Merge remote-tracking branch 'github-cs-check/feat/openalias' into feat/openalias
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 pathmerge-commit duplicate discount
AI analysis · Low 27/100
This commit is mostly routine maintenance: updating Rust compiler versions, refreshing third-party library references, switching block-explorer URLs, and adding a Linux packaging helper that removes an executable-stack flag from bundled wallet libraries. The most security-relevant change is the new helper script, which prevents modern Linux from rejecting (or potentially mishandling) certain native libraries. There is no clear vulnerability being fixed, no vendor security disclosure, and no independent researcher credited.
Security candidateMerge branch 'staging' into feat/openaliasby Julian · f9e48dd5 · Oct 29, 2026 · 14 filesMessage 45 · ThinInformational 23Details
Commit message · Julian
Merge branch 'staging' into feat/openalias
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 23/100
This merge commit mostly updates build tooling, Rust compiler versions, Flutter plugin wiring, and block-explorer URLs. The most security-relevant change is a new Linux release script that removes the executable-stack flag from bundled wallet libraries and refuses to ship any other library that still requests one. This is a hardening/fix for a deployment issue where modern Linux systems could reject or warn about those libraries. There are no obvious malicious code changes or direct exploit patches visible in the diff.