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…
chore(shopinbit): address review on car-research finalize
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
authentication path
AI analysis · Informational 23/100
This commit makes two small code cleanups in a car-research payment flow. One change removes a manual timer cancellation and relies on the caller to cancel it, which could in theory lead to a timer continuing to run briefly if the caller doesn't always do so. The other change replaces a safe integer parser (which throws a clear error on bad input) with a stricter parser that throws a less informative error. Neither change is obviously a security fix, and the commit message frames them as routine review follow-up rather than a security issue.
fix(shopinbit): require remaining required fields across models
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
authentication path
AI analysis · Low 26/100
This commit tightens how the Stack Wallet app reads data from its ShopInBit partner service. Previously, several fields were treated as optional and replaced with safe defaults (empty strings, false, current time) when missing. Now the code requires those fields to be present and correctly typed. This is a defensive correctness fix: it makes the app fail earlier and more visibly if the server sends unexpected or malformed data, rather than silently continuing with placeholder values. There is no direct evidence this fixes an active security vulnerability, but it reduces the risk of logic errors or misleading UI state caused by missing fields.
fix(shopinbit): surface parse errors for required ticket fields
and cleaning
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
authentication path
AI analysis · Low 29/100
This commit changes how the Stack Wallet app parses data from its ShopInBit partner service. Previously, missing or malformed fields were silently replaced with empty strings, zero, or the current date/time. Now the app throws visible errors instead. That is generally a good defensive change, but it removes some safety comments and fallback behavior for unknown ticket states, and it makes parsing stricter. The patch is small and appears aimed at surfacing bugs rather than introducing a vulnerability, but it is only a partial hardening of the parsing layer.
fix(shopinbit): keep car-research expiresAt null on parse failure
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
authentication path
AI analysis · Low 35/100
This commit fixes a bug in the Stack Wallet app's integration with ShopinBit's car-research service. Previously, if the invoice expiration date was missing or unreadable, the app would silently replace it with the current time, making a brand-new invoice look like it had already expired. Now the app keeps the expiration date as 'unknown' instead of guessing. This is a correctness and user-experience fix, not a remote code execution or theft vulnerability.
Security candidatefix(shopinbit): treat an empty 2xx body as an errorby sneurlax · 0d54cd92 · Jun 10, 2026 · 1 fileMessage 62 · AdequateLow 44Details
Commit message · sneurlax
fix(shopinbit): treat an empty 2xx body as an error
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
authentication path
AI analysis · Low 44/100
This commit fixes a bug in the Stack Wallet app's integration with ShopInBit. Previously, if the server returned a successful HTTP response with an empty body, the app would pretend it received valid data and create fake placeholder objects (for example, a support ticket with ID 0). Now the app correctly treats an empty successful response as an error instead. This is a defensive fix that prevents the app from acting on fabricated data, which could confuse users or lead to incorrect app behavior.
Security candidatefix(shopinbit): recover car-research invoices within the +24h graceby sneurlax · c5f20015 · Jun 10, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · sneurlax
fix(shopinbit): recover car-research invoices within the +24h grace
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
authentication path
AI analysis · Informational 18/100
This commit fixes a business-logic bug in Stack Wallet's ShopinBit ticket screen. Previously, car-research invoices that had expired but were still within a 24-hour grace period were incorrectly treated as unpayable, so users could not resume or recover them. The change extends the payable check from the original expiration time to 24 hours after expiration, matching the documented spec. There is no direct security signal in the diff itself.
Security candidatefix(shopinbit): re-authenticate once on HTTP 401by sneurlax · 85e8b394 · Jun 10, 2026 · 1 fileMessage 57 · ThinInformational 22Details
Commit message · sneurlax
fix(shopinbit): re-authenticate once on HTTP 401
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 22/100
This commit fixes a bug in the Stack Wallet app's integration with ShopInBit. Previously, if the app's login token expired while making a request, the app would simply fail. Now, when it receives an HTTP 401 'unauthorized' error, it automatically refreshes the token once and retries the request. This is a routine reliability fix rather than a security vulnerability patch.
Security candidatefix(shopinbit): regenerate expired invoice via PUT ?retry=trueby sneurlax · d1457a08 · Jun 10, 2026 · 2 filesMessage 62 · AdequateInformational 18Details
Commit message · sneurlax
fix(shopinbit): regenerate expired invoice via PUT ?retry=true
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
authentication path
AI analysis · Informational 18/100
This commit fixes a small integration bug in the Stack Wallet app's ShopInBit payment feature. Previously, when a user tried to refresh an expired invoice, the app called the server without the required retry=true flag. The fix adds that flag so the server regenerates the invoice instead of returning an error. There is no direct evidence this is a security vulnerability; it appears to be a normal bug fix for a broken user flow.
Security candidatechore(shopinbit): clean up merge lintsby sneurlax · 716c6e33 · Jun 10, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · sneurlax
chore(shopinbit): clean up merge lints
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100
This is a routine code cleanup commit. It removes one unused import and fixes a Dart lint warning by replacing an unnecessary null-assertion operator with a direct property access. There is no security-relevant change.
Security candidatefix: race condition when refreshing all shopinbit tickets when not all tickets use the same customer key. Probably introduces bugs elsewhere now though...by julian · b9b104fd · Jun 10, 2026 · 12 filesMessage 62 · AdequateLow 35Details
Commit message · julian
fix: race condition when refreshing all shopinbit tickets when not all tickets use the same customer key. Probably introduces bugs elsewhere now though...
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
authentication path
AI analysis · Low 35/100
This commit fixes a race condition in the Stack Wallet app's ShopinBit feature. Previously, the app stored one shared 'customer key' on the API client object. When refreshing multiple tickets that belonged to different customer keys, one ticket's key could overwrite another's mid-refresh, causing requests to be sent with the wrong key. The fix passes the correct customer key alongside each individual request instead of relying on shared state. The commit message notes the fix may introduce other bugs elsewhere.
Security candidaterefactor(shopinbit): drop the single-flight ticket/invoice fetch wrappersby sneurlax · f01dc8c3 · Jun 10, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
refactor(shopinbit): drop the single-flight ticket/invoice fetch wrappers
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
authentication path
AI analysis · Informational 15/100
This commit removes a small performance optimization in the Stack Wallet app's ShopInBit service. Previously, if multiple parts of the app tried to fetch the same ticket list or car-research invoice list at the same time, they would share one network request. After this change, each call goes straight to the API independently. There is no security fix or vulnerability here—it's a straightforward code simplification that may slightly increase API traffic.
Security candidatefix(shopinbit): drop the by-customer car ticket fallbackby sneurlax · 77461f13 · Jun 10, 2026 · 3 filesMessage 62 · AdequateInformational 22Details
Commit message · sneurlax
fix(shopinbit): drop the by-customer car ticket fallback
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
authentication path
AI analysis · Informational 22/100
This commit removes a fallback mechanism in Stack Wallet's ShopInBit car-research payment flow. Previously, if the server didn't immediately provide the real customer-support ticket ID, the app would try to guess it by listing all tickets associated with the customer and picking the newest one that wasn't already known. That fallback is now deleted; the app simply waits for the server to supply the real ticket ID directly. The change is described as a functional fix, not a security fix, but removing a heuristic that touches other customer tickets reduces the risk of accidentally opening or acting on the wrong ticket.
Security candidaterefactor(shopinbit): consolidate poll backoff into the clientby sneurlax · 090ab331 · Jun 10, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
refactor(shopinbit): consolidate poll backoff into the client
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
authentication path
AI analysis · Informational 15/100
This commit is a simple code cleanup: it moves the same retry-backoff calculation used by three different screens into one shared helper inside the ShopInBit client. There is no change in behavior, no bug fix, and no security improvement or regression.
Security candidatefix(shopinbit): migrate car research flow to API v1.0.6by sneurlax · fb6ea0c2 · Jun 10, 2026 · 5 filesMessage 77 · AdequateInformational 16Details
Commit message · sneurlax
fix(shopinbit): migrate car research flow to API v1.0.6
docs(shopinbit): tighten car research v1.0.6 comments
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
authentication path
AI analysis · Informational 16/100
This commit updates the Stack Wallet app's 'ShopinBit car research' feature to work with a newer version of the partner API (v1.0.6). It mainly changes how the app checks whether a customer has paid the car-research fee and how it finds the resulting support ticket. The old code relied on a separate 'log payment' API call that is being removed; the new code reads the payment/ticket status directly from a status endpoint. There is no obvious security bug being fixed, but the change removes a workaround where payment confirmation was partly driven by the client calling a logging endpoint.
Security candidatefeat(shopinbit): after payment, nav back to specific request if knownby sneurlax · 25541dd3 · Jun 4, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
feat(shopinbit): after payment, nav back to specific request if known
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
authentication path
AI analysis · Informational 15/100
This commit changes the post-payment navigation in the ShopInBit feature of Stack Wallet. After a user pays, the app now tries to return them to the specific purchase request they came from, instead of always sending them to the general requests list. There is no security issue visible in this change.
fix(shopinbit): combine by-customer and car-invoice fetches
getTicketsByCustomer and getCurrentCarResearchInvoices were the two read paths left outside the completer-based dedup that already guards _refreshRef, so overlapping refreshes (tickets view racing a post-action refresh, or refreshAll racing adoptRealCarTicket) each fired their own request. Wrap both in the same in-flight combined pattern and route callers through it.
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
authentication path
AI analysis · Informational 19/100
This change is a performance fix, not a security fix. It prevents the wallet's ShopInBit ticket screen from making duplicate API calls when several refreshes happen at the same time. The code now shares one in-flight request among callers instead of firing multiple identical requests. There is no evidence in the commit of a vulnerability being patched.
Security candidatefix(shopinbit): back off pollers on error and pause when backgroundedby sneurlax · 5ebb52c2 · Jun 4, 2026 · 3 filesMessage 85 · StrongLow 37Details
Commit message · sneurlax
fix(shopinbit): back off pollers on error and pause when backgrounded
The payment, car-research, and ticket-detail views polled on fixed 15s/30s timers that kept firing at full rate even when a request failed, so a 429 just got ignored and re-provoked. Switch each to a self-scheduling timer that doubles its interval on failure (capped at 120s) and resets on success, and pause polling while the app is backgrounded via WidgetsBindingObserver. Previously swallowed poll errors are now logged.
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
authentication path
AI analysis · Low 37/100
This commit fixes a bug in Stack Wallet's ShopInBit feature where the app kept asking the server for updates every 15 or 30 seconds, even when the server was already saying 'slow down' (HTTP 429) or the request failed. The fix adds a backoff that doubles the wait time after failures, pauses polling when the app is in the background, and starts logging errors that were previously silently ignored. It is a defensive hardening change, not an active vulnerability being exploited.
Security candidatefix(shopinbit): back off the real-car-ticket adoption retriesby sneurlax · 5caf4095 · Jun 4, 2026 · 1 fileMessage 62 · AdequateInformational 19Details
Commit message · sneurlax
fix(shopinbit): back off the real-car-ticket adoption retries
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
authentication path
AI analysis · Informational 19/100
This change adjusts how the app waits for a car-purchase ticket to become available. Instead of asking the server every 3 seconds for 36 seconds (12 tries), it now asks fewer times and waits longer between each try. This is a reliability and politeness fix that reduces unnecessary load on the server and the user's device; it does not appear to be a security patch.
Security candidatefix(shopinbit): retry 429s with backoff at the request chokepointby sneurlax · 99345336 · Jun 4, 2026 · 2 filesMessage 85 · StrongLow 29Details
Commit message · sneurlax
fix(shopinbit): retry 429s with backoff at the request chokepoint
All ShopinBit requests funnel through _send, which treated 429 like any other error and let callers re-fire immediately. Add 429-aware retry there: respect a server Retry-After when present, else exponential backoff with jitter, capped at 30s. Widen the http Response to carry headers so Retry-After is readable.
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
authentication path
AI analysis · Low 29/100
This commit fixes a reliability issue in the Stack Wallet app's integration with ShopinBit. Previously, when the ShopinBit server was overwhelmed and returned a '429 Too Many Requests' error, the app would immediately give up and let the caller retry right away, potentially hammering the server even harder. Now, the app automatically waits and retries up to three times, respecting the server's 'Retry-After' instruction or using a sensible backoff delay. This is a defensive improvement that reduces accidental denial-of-service behavior and improves request success rates under load.
Security candidatefeat(shopinbit): show a QR code for manual crypto paymentsby sneurlax · 2b4d0cbc · Jun 2, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
feat(shopinbit): show a QR code for manual crypto payments
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
authentication path
AI analysis · Informational 15/100
This commit adds a QR code display to a payment screen so users can scan an address with another wallet app instead of copying and pasting it. There is no security issue visible in the change.
Security candidatefix(shopinbit): don't tear down the payment dialog when opening Send fromby sneurlax · 0a387bda · Jun 2, 2026 · 2 filesMessage 62 · AdequateInformational 17Details
Commit message · sneurlax
fix(shopinbit): don't tear down the payment dialog when opening Send from
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
authentication path
AI analysis · Informational 17/100
This commit fixes a user-experience bug in the Stack Wallet app's ShopInBit payment flow on desktop. Previously, opening the 'send from' wallet dialog would close the entire payment dialog, so after sending funds the user was dumped back at the Services page instead of returning to the payment view. The change keeps the payment dialog open underneath the send dialog. There is no security vulnerability here—just a navigation/UI behavior fix.
Security candidatefix(shopinbit): retry the real car ticket longer, offer a My Requests shortcutby sneurlax · a10633a2 · Jun 2, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax
fix(shopinbit): retry the real car ticket longer, offer a My Requests shortcut
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
authentication path
AI analysis · Informational 15/100
This commit is a routine user-experience improvement for a cryptocurrency wallet's car-research payment flow. It makes the app wait a bit longer for a backend ticket to appear and adds a 'My Requests' shortcut button so users don't have to navigate manually. There is no security-relevant change in the diff.
Security candidatefix: log previously-swallowed errors in ShopinBit and CakePay flowsby sneurlax · d911bfd2 · Jun 2, 2026 · 7 filesMessage 62 · AdequateInformational 20Details
Commit message · sneurlax
fix: log previously-swallowed errors in ShopinBit and CakePay flows
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
authentication path
AI analysis · Informational 20/100
This commit only adds logging to error paths in the ShopinBit and CakePay shopping/payment flows. It does not change how errors are handled or fix any underlying bug; it simply records details that were previously silently ignored. There is no direct security fix here, but better logging can help developers detect and diagnose future problems.
Security candidatefix(shopinbit): stop polling a ticket once it reaches a terminal stateby sneurlax · f6babb46 · Jun 2, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · sneurlax
fix(shopinbit): stop polling a ticket once it reaches a terminal state
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
authentication path
AI analysis · Informational 18/100
This commit fixes a minor behavior bug in the Stack Wallet app's ShopInBit ticket screen. Previously, the app kept checking (polling) a support or order ticket every 30 seconds even after the ticket was already closed, merged, or refunded. The change makes the app stop polling once the ticket reaches a final, unchangeable state. This is mainly a resource/battery/network efficiency fix, not a security fix.
Security candidatefix(shopinbit): open the real car ticket after the research fee, not the receiptby sneurlax · a5b8a4b3 · Jun 2, 2026 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · sneurlax
fix(shopinbit): open the real car ticket after the research fee, not the receipt
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
authentication path
AI analysis · Informational 23/100
This commit fixes a bug in the Stack Wallet app's ShopInBit car-research payment flow. Previously, after a customer paid the research fee, the app tried to open the wrong ticket (a partner-only fee receipt that the customer cannot view), which could leave the user stuck or confused. The fix adds logic to find and open the actual customer-facing car-research ticket instead, with retries and a clearer message if it isn't ready yet.