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…
Scope cached ShopinBit attachments by customer key
TorAwareNetworkImage keys its cache on the url alone, so an attachment path fetched under one customer key would be served from cache to a later customer key without an authenticated request. Add an optional cacheScope that is part of the key, and pass the ShopinBit customer key there. The bearer token stays out of the key so a refreshed token does not refetch.
The key is captured together with the request response rather than read from the widget when building the image: FutureBuilder keeps showing the previous snapshot while a new future is pending, and that snapshot must not be paired with a later customer's scope.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Moderate 60/100
This commit fixes a privacy bug in Stack Wallet's image caching. When the app showed customer support attachments from ShopinBit, it cached images using only the web address. Because the same attachment path can return different files for different customers, a later customer could briefly see another customer's cached image without a fresh permission check. The patch adds a 'customer key' to the cache key so each customer's images stay separate, and it makes sure the key is tied to the actual downloaded response rather than the on-screen widget state.
The recipient now carries a required ttl, so the test fakes pass one.
Resolved with `flutter pub get` against the ~/.pub-cache git mirror of github.com/cypherstack/cs_openalias fetched from the local checkout; the URL resolves once that SHA is on GitHub.
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
access control
AI analysis · Informational 19/100
This commit updates a dependency (cs_openalias) to a newer pinned version and adjusts automated tests to match a new requirement that every recipient record must include a 'time-to-live' (TTL) duration. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine dependency pin and test update.
The attachment images were fetched from a query-auth URL carrying the token and customer key. Now that they go through the HTTP wrapper, which logs failed requests, and dart:io puts the request URL in its exceptions, those credentials could end up in the log file.
Fetch the plain URL with the Authorization and External-Customer-Key headers instead. TorAwareNetworkImage takes the headers but keeps keying the image cache on the URL alone, so a re-mounted attachment still comes from the cache.
client.dart wasn't formatted on staging, so its diff includes one formatting change.
73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
access controlcredential or privilege stateauthentication path
AI analysis · Moderate 60/100
This commit fixes a privacy/credential-leak issue in Stack Wallet's ShopinBit support-ticket feature. Previously, image attachments were downloaded using a URL that contained the user's secret access token and customer key as visible query parameters. Because the app's HTTP wrapper logs failed requests and Dart's networking exceptions include the full URL, those secret credentials could have been written to log files on the device. The patch switches to sending the credentials as HTTP headers instead, so the URL stays plain and the sensitive values are not embedded in it. A new test confirms the image loader accepts headers but still caches images by URL alone.
Security candidateMark Nano, Banano and Fact0rn as Tor-ready, proxy Stellar node testby kroplabeskidu · 6d56032a · Oct 27, 2026 · 3 filesMessage 83 · StrongLow 48Details
Commit message · kroplabeskidu
Mark Nano, Banano and Fact0rn as Tor-ready, proxy Stellar node test
Nano and Banano already send every request through Tor, and Fact0rn uses the regular ElectrumX client, so they only needed the torSupport flag.
The Stellar node test proxied its first request but then created a StellarSDK with the default client, so the follow-up ledger query went out directly.
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
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 48/100
This commit fixes a privacy leak in the Stellar wallet connection test and marks three cryptocurrencies (Nano, Banano, and Fact0rn) as supporting Tor. Previously, when testing a Stellar node, the first request went through the Tor proxy, but a follow-up request to check the ledger height was sent directly over the regular internet, potentially exposing the user's IP address and the node they were connecting to. The commit also correctly notes that Nano, Banano, and Fact0rn already supported Tor routing in practice, so their flags were updated to reflect that.
Security candidateAdd Tor support for Ethereumby kroplabeskidu · d4381fb3 · Oct 27, 2026 · 5 filesMessage 78 · AdequateLow 38Details
Commit message · kroplabeskidu
Add Tor support for Ethereum
web3dart was handed a plain http Client, so ETH and ERC-20 RPC could not use Tor and the coin was flagged as not Tor-ready. Give it an IOClient wrapping a SOCKS5-proxied HttpClient instead, the same way Solana does it, and do the same for the node connection test.
Also add the usual node tor/clearnet mismatch check and set torSupport.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 38/100
This commit adds Tor privacy support for Ethereum in Stack Wallet. Previously, Ethereum RPC traffic always traveled over the regular internet (clearnet), even when the user turned on Tor, because the underlying library used a plain HTTP client. The patch routes Ethereum traffic through the Tor SOCKS5 proxy when Tor is enabled, and adds a check that warns if the selected node conflicts with the user's Tor setting. It also adds tests to confirm the proxying works.
Security candidateLoad remote images over Tor when it is enabledby kroplabeskidu · 0059f656 · Oct 27, 2026 · 13 filesMessage 68 · AdequateHigh 71Details
Commit message · kroplabeskidu
Load remote images over Tor when it is enabled
Image.network and SvgPicture.network use their own HTTP clients and ignore the Tor setting, so token logos, exchange and coin logos, CakePay card images, ShopinBit attachments and theme previews were fetched directly even in Tor mode.
Add TorAwareNetworkImage and TorAwareSvgNetworkLoader, which go through the app's HTTP wrapper, and use them at all call sites.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathauthentication path
AI analysis · High 71/100
This commit fixes a privacy leak in Stack Wallet. When users turned on Tor mode to hide their internet traffic, the app was still loading remote images—such as token logos, exchange icons, gift-card pictures, and theme previews—directly over the normal internet, bypassing Tor. The change adds new image loaders that route these image requests through the app's Tor-aware HTTP client, and replaces all direct image loading calls across the wallet's user interface.
chore(deps): pin cs_openalias 6c9376e and dnssec_resolver b33d6a2
cs_openalias 6c9376e re-exports isOpenAliasApplication, so the application test imports the facade and openalias is no longer a dev dependency; the dependency_overrides entry stays until the package is published. dnssec_resolver b33d6a2 reports a missing record only for a secure denial, refuses SHA-1-only delegations and backs off its native polling. openalias 46d8402 and doh_transport 7211549 are unchanged.
Resolved with `flutter pub get` against the ~/.pub-cache git mirrors of github.com/cypherstack/<pkg>, each fetched from the local checkout (`git -C ~/.pub-cache/git/cache/<pkg>-<hash> fetch <checkout> +main:refs/local/main`); the URLs resolve once those SHAs are on GitHub.
95/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
Why it was queued
access controlsigning or wallet path
AI analysis · Low 25/100
This commit updates two internal library dependencies to newer pinned versions. The newer versions are described as tightening DNS security checks (refusing older SHA-1-only delegations and handling missing DNS records more safely) and removing a development-only dependency from the wallet's build. There is no direct evidence in the commit of an exploitable vulnerability in the wallet itself, but the dependency bumps are framed as security-hardening.
Merge pull request #1475 from slopbot9k/rust-1.99.1
Require Rust 1.99.1 and pin the plugin releases built with it
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
access controlmerge-commit duplicate discount
AI analysis · Informational 12/100
This commit updates the Rust compiler version used to build the wallet from 1.89.0 to 1.99.1 across build scripts, documentation, and dependency references. It also switches some third-party plugin references to newer commits or forks maintained by the same team, and updates prebuilt binary download URLs and SHA256 hashes. A small code change removes a `disable()` call before stopping the Tor service. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine toolchain and dependency refresh.
Security candidateMerge branch 'staging' into rust-1.99.1by Julian · c7ef7391 · Oct 26, 2026 · 8 filesMessage 45 · ThinLow 33Details
Commit message · Julian
Merge branch 'staging' into rust-1.99.1
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 · Low 33/100
This commit is a routine merge that mostly improves how Stack Wallet's Linux release packages are built. The main change adds a build-time script that strips an unsafe 'executable stack' flag from three cryptocurrency wallet libraries (Monero, Wownero, Salvium) so modern Linux systems will load them. It also updates Dogecoin and Litecoin block-explorer URLs from an old domain to a new one. There is no evidence in the commit of an active security vulnerability being exploited, but the executable-stack flag is a genuine hardening concern for Linux binaries.
fix: point Dogecoin and Litecoin default explorer links at sochain.com
68/100 · AdequateMessage clarity
✓ 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 · Informational 23/100
This commit simply updates the default web links used to view Dogecoin and Litecoin transactions. The old links pointed to chain.so, which now redirects to sochain.com; the new links go directly to sochain.com. There is no code vulnerability or user-data risk visible in the change itself.
Security candidatefix: point Dogecoin and Litecoin default explorer links at sochain.comby Atif Nazir · 4642939c · Oct 24, 2026 · 2 filesMessage 85 · StrongInformational 17Details
Commit message · Atif Nazir
fix: point Dogecoin and Litecoin default explorer links at sochain.com
chain.so explorer links now reach the transaction page only after two redirects (chain.so/tx/DOGE/<txid> -> sochain.com/tx/DOGE/<txid> -> sochain.com/doge/tx/<txid>). Use the current form directly for mainnet and testnet.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 17/100
This commit simply updates the default web links used to look up Dogecoin and Litecoin transactions. The old chain.so URLs now redirect twice before showing the transaction, so the developer pointed the wallet directly at the new sochain.com address format. It is a routine maintenance change to keep the 'View on block explorer' feature working smoothly.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is a large batch of new and updated automated tests for the send-money screens in Stack Wallet. It checks that fee estimates are displayed correctly, that users can pick custom fees, and that fees update when balances or sync status change. There are no changes to the actual wallet app code that users run—only test code.
Security candidaterefactor: share the send fee logic across platformsby Cyrix126 · f9ec2c3e · Oct 16, 2026 · 24 filesMessage 62 · AdequateInformational 11Details
Commit message · Cyrix126
refactor: share the send fee logic across platforms
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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 11/100
This commit is a code cleanup that moves fee-calculation logic out of several send screens into a single shared module. It does not change what the app does; it only reorganizes how fee estimates are computed and displayed across mobile and desktop. There is no indication this introduces a security vulnerability.
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.
✓ 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.
✓ 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.
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.
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.
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.
✓ 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 pathboot or update path
AI analysis · Informational 23/100
This commit fixes a UI bug in Stack Wallet where cancelling a transaction build could cause the app to try to close a dialog that was already gone, leading to a crash or confusing error screen. The fix moves a 'wasCancelled' flag outside the try-block so it remains visible in the catch-block, and then skips popping the dialog if the user cancelled. It is a stability/UX fix, not a cryptographic or funds-theft issue.
✓ 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 · Informational 19/100
This commit is a routine feature merge that adds support for a new Ethereum token called rsFIRO across several app variants. It updates token lists, adds an icon, and includes a database migration so existing users automatically see the new token. There is no indication this change fixes a security vulnerability or introduces a known dangerous behavior.
Merge branch 'staging' into masternode-operator-reward
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 · Informational 19/100
This commit is a routine feature merge that adds support for a new Ethereum token called rsFIRO, updates some app configuration scripts, refreshes a privacy-related Git dependency, and fills in missing API-key placeholders for exchange integrations. There is no direct evidence in the diff of a security vulnerability, malicious code, or a fix for a disclosed security issue. The changes are mostly product/configuration plumbing.
Merge pull request #1448 from reubenyap/codex/rsfiro-app-config
feat: add rsFIRO with configurable Ethereum token defaults
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 · Informational 19/100
This commit adds support for a new Ethereum token called rsFIRO and makes the list of default Ethereum tokens configurable for each app flavor (Stack Wallet, Stack Duo, Campfire). It also includes a database migration so existing users get rsFIRO added automatically. There is no obvious security vulnerability in the changes, but the migration logic has a subtle edge case that could, in theory, affect token data consistency.