SW
← All projectsStack Wallet

Stack Wallet

Actively maintained multi-coin self-custody wallet with Monero support and on-device keys.

MoneroPrivacy protocolsSoftware walletsNormal
Repository coverage

1166 commits in the local evidence base

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.

376security candidates450second-pass queue826AI analyses
104commits · 30 days
161commits · 60 days
472commits · 180 days
945commits · 365 days
Backfill bands
Sep 27 → Mar 31404 seen73 candidatesComplete
Mar 31 → Jul 29463 seen238 candidatesComplete
Jul 29 → Aug 2887 seen8 candidatesComplete
Aug 28 → Sep 2753 seen6 candidatesComplete
Commit communication

Does the history explain itself?

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
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Julian24159176246
sneurlax380170270163
kroplabeskidu333176
slopbot9k1628163
Navid Rahimi1017154
julian347112269044
Dan Miller841525053
Cyrix12618414049
Reuben Yap20318052
julian-CStack222049
levoncrypto24121043
cassandras-lies413048
Analysis record

Published AI watches

Last scanned 48 minutes ago

Moderate 57 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1528 from cypherstack/fix/taproot-input-sequence

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
05b0ad33by Julian+1−11 file
No security note in commit
Low 35 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1541 from cypherstack/rotate-receiving-address-types

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
01be23d6by Julian+1288−210 files
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1537 from cypherstack/fix/simplex-current-receiving-address

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
f41c799eby sneurlax+239−593 files
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Test the Buy form's Choose from Stack flow in the real app

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…

ba44e64cby slopbot9k+1022−27 files
No security note in commit
Moderate 52 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Rotate used receiving addresses on every derivation path

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…

Address reuse mitigationPrivacy improvementWallet receive-address rotation
8998a949by slopbot9k+243−02 files
Vendor flagged security relevance
Low 36 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1529 from cypherstack/fix/electrs-vanished-tx

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
1d319093by Julian+4−31 file
No security note in commit
Informational 12 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1505 from cypherstack/repro-dnix-packages

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
9c89083fby Julian+4431−69337 files
No security note in commit
Moderate 61 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge branch 'staging' into repro-dnix-packages

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
e517d08eby Julian+7700−164556 files
No security note in commit
Moderate 61 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1510 from cypherstack/electrum-client-per-wallet-refactor

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
a7d86094by Julian+7700−164556 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Stop describing a certificate approval as a pin

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…

4b88ce9aby slopbot9k+3−32 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Format the view-only restore view

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.

6d56c42bby slopbot9k+8−91 file
No security note in commit
Low 33 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge remote-tracking branch 'upstream/staging' into electrumx-per-wallet

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
16b06913by slopbot9k+3251−249339 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1511 from Cyrix126/share_send_fee_logic

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
40c9a054by Julian+3176−249237 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1509 from cypherstack/feat/monero-signing

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 …

7659bc86by Julian+75−13 files
No security note in commit
Informational 17 AI analysisMessage 90 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

feat(xmr): sign and verify messages

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
6c49e3ceby sneurlax+75−13 files
No security note in commit
Low 43 AI analysisMessage 86 · Strong
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Drop vanished unconfirmed txs on electrs too

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
a31b28b6by sneurlax+4−31 file
No security note in commit
Informational 17 AI analysisMessage 58 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1506 from cypherstack/fix/sol-add-token-new-wallet

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
ed3f1cd0by Julian+241−1014 files
No security note in commit
Informational 22 AI analysisMessage 73 · Adequate
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Merge pull request #1483 from cypherstack/fix/eth-add-token-new-wallet

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)
213c6b0cby Julian+171−552 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Format Solana wallet picker changes for the current Dart SDK

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…

e93f0521by sneurlax+78−1012 files
No security note in commit
Informational 18 AI analysisMessage 50 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

Fix Ethereum picker empty state during wallet registration

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…

a729e6d5by sneurlax+139−122 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateclearly show delivery country as requiredby julian · de3538d7 · Jul 8, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · julian

clearly show delivery country as required

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit simply changes a form field label from 'Delivery country' to 'Delivery country (Required)' in the app's shopping/payment flow. It is a user-interface wording change with no security relevance.

Security candidateadd incl VAT info where requestedby julian · e526fb0b · Jul 8, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · julian

add incl VAT info where requested

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit simply adds the text '(incl. VAT)' next to displayed prices in two shopping-related screens. It is a cosmetic/user-interface label change with no security relevance.

Security candidatevat rate can actually be a decimal which was not what the docs specifiedby julian · 3b500730 · Jul 8, 2026 · 2 filesMessage 50 · ThinInformational 19Details
Commit message · julian

vat rate can actually be a decimal which was not what the docs specified

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 19/100

This commit fixes a data-type mismatch in how the app reads VAT (sales tax) rates from a partner service. The code previously expected whole-number percentages like 19, but the service can actually send decimal values like 19.5. The change lets the app store and handle those decimal rates correctly. There is no direct evidence this is a security fix; it reads as a routine bug fix for incorrect parsing that could cause display or calculation errors.

Security candidatehack fix bad http urls from apiby julian · f8fa726a · Jul 8, 2026 · 1 fileMessage 25 · OpaqueLow 38Details
Commit message · julian

hack fix bad http urls from api

25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 38/100

This commit changes how the app handles package tracking links from a shopping partner API. Previously, the app took whatever text the API returned and treated it as a link. Now, if the text doesn't already start with 'http://' or 'https://', the app automatically adds 'https://' in front. This is a quick fix to prevent broken or unsafe links, but it doesn't fully validate that the resulting string is a real, safe URL.

Security candidateflagby julian · 976bd6be · Jul 8, 2026 · 1 fileMessage 0 · OpaqueLow 44Details
Commit message · julian

flag

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 44/100

A single-line change flips a third-party shopping integration from sandbox/test mode to live/production mode. This is a configuration change rather than a traditional code vulnerability, but it moves real user transactions and partner secrets from a safe test environment to the live service. If the rest of the app is not ready for production, this could expose real payment or order data, charge real money, or leak the partner secret through production traffic.

AI review queuedFix Spark Name registration formatby Reuben Yap · ca52f39c · Jul 3, 2026 · 3 filesMessage 45 · ThinLow 31Details
Commit message · Reuben Yap

Fix Spark Name registration format

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 31/100

This commit fixes the way Spark Name registration data is embedded in blockchain transactions. Spark Names are human-readable aliases (like a username) tied to a privacy address. The previous code likely sent the registration fee to a plain address without attaching the required extra metadata, which could cause the name registration to fail or be recorded incorrectly. The patch adds the proper script format, including the name and Spark address, so the Firo network can recognize and process the registration. It also switches the underlying Spark mobile library from Cypher Stack's fork to the official Firoorg repository.

Security candidateshow request shipping tracking links if availableby julian · 70981e89 · Jun 26, 2026 · 3 filesMessage 45 · ThinInformational 21Details
Commit message · julian

show request shipping tracking links if available

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 21/100

This commit adds a feature that displays shipping tracking links on a purchase ticket detail page. When a user taps a link, the app tries to open it in an external browser. The change is mostly a normal UI feature, but it does accept tracking-link strings from ticket data and pass them directly to the phone's URL opener. That creates a small risk if a malicious or compromised server sends a harmful link, because the app will try to open whatever it receives without visible filtering.

Security candidatefeat(shopinbit): split tracking linksby sneurlax · 1b9d2818 · Jun 26, 2026 · 1 fileMessage 57 · ThinInformational 18Details
Commit message · sneurlax

feat(shopinbit): split tracking links

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 18/100

This commit is a routine feature improvement for the ShopinBit integration in Stack Wallet. It changes how package tracking links are handled: instead of storing one raw string that may contain several URLs crammed together with commas, pipes, or semicolons, the code now splits that string into a clean list of individual tracking URLs. It also turns empty strings from the server into null values so the rest of the app doesn't treat an empty value as a real link. There is no security fix here and nothing that looks like a vulnerability.

Security candidaterefactor(shopinbit): parse ticket messages with the html packageby sneurlax · ad6cde62 · Jun 26, 2026 · 3 filesMessage 62 · AdequateLow 37Details
Commit message · sneurlax

refactor(shopinbit): parse ticket messages with the html package

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 37/100

This commit replaces a custom-built HTML parser in Stack Wallet's ShopinBit ticket-message feature with the well-known 'html' package. The old code parsed HTML by hand using string scanning and regular expressions, which is a common source of security bugs (for example, tricking the parser into treating malicious code as harmless text or vice versa). The new code uses a dedicated HTML parser that is more robust against malformed or adversarial input. The change is a defensive refactor; there is no direct evidence in the commit that an actual attack was found or exploited.

Security candidatefix(shopinbit): handle ticket message mediaby sneurlax · 71d8a86f · Jun 26, 2026 · 4 filesMessage 57 · ThinLow 37Details
Commit message · sneurlax

fix(shopinbit): handle ticket message media

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 · Low 37/100

This update improves how Stack Wallet's ShopInBit support-chat feature handles images and file attachments. It replaces an older inline-base64-only image renderer with a safer parser that also supports server-hosted attachments, adds request timeouts so background polling can't get stuck forever, and skips malformed messages instead of crashing the whole chat. The code also adds path-traversal checks on attachment URLs so a malicious link can't trick the app into requesting unintended server paths using the user's own login token.

Security candidatefix(shopinbit): await clipboard write in car-research copy addressby sneurlax · 5130e665 · Jun 26, 2026 · 1 fileMessage 62 · AdequateInformational 16Details
Commit message · sneurlax

fix(shopinbit): await clipboard write in car-research copy address

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 16/100

This is a small UI reliability fix in a cryptocurrency wallet's car-research payment screen. The developer made the 'copy address to clipboard' function wait for the clipboard write to complete before showing a confirmation message, and added a check to avoid using a screen that may have been closed during the operation. It is a routine correctness improvement, not a security fix for an exploitable vulnerability.

Security candidatefix(shopinbit): show payment QR in a dialog instead of a bottom sheetby sneurlax · a9e9eb73 · Jun 26, 2026 · 2 filesMessage 85 · StrongInformational 15Details
Commit message · sneurlax

fix(shopinbit): show payment QR in a dialog instead of a bottom sheet

fix(shopinbit): align payment QR copy icon with Stack's native style
fix(shopinbit): await clipboard write in payment QR dialog

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 15/100

This commit is a routine user-interface polish for the ShopinBit payment flow. It changes how a QR-code payment screen is displayed (from a bottom sheet to a dialog), updates a copy icon to match the app's style, and makes the clipboard copy operation wait for completion before showing a confirmation message. There is no security-relevant change.

Security candidatefix(shopinbit): pop payment loading overlay on the root navigatorby sneurlax · c7c38ab1 · Jun 26, 2026 · 1 fileMessage 85 · StrongInformational 17Details
Commit message · sneurlax

fix(shopinbit): pop payment loading overlay on the root navigator

fix(ui): make showLoading dismissal robust against nesting and unmount
fix(shopinbit): solve payment overlay soft-lock without touching showLoading

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 17/100

This commit fixes a UI bug in the Stack Wallet app's ShopinBit payment screen. A loading overlay that appears while refreshing or checking an invoice could get stuck (a 'soft-lock') because it was being shown on a nested navigator instead of the root one. The fix tells the overlay to display on the root navigator so it can be properly dismissed, preventing users from getting stuck on a frozen payment screen.

Security candidatefix(shopinbit): remove "recommendations" travel optionby sneurlax · 18b42d59 · Jun 23, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · sneurlax

fix(shopinbit): remove "recommendations" travel option

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 'I need recommendations' checkbox from a travel booking form inside the Stack Wallet app. Users must now type a destination city instead of asking for recommendations. There is no security issue visible in the code change.

Security candidatefix(shopinbit): dumb hacked check for first and last nameby julian · 2c229d73 · Jun 23, 2026 · 1 fileMessage 62 · AdequateInformational 23Details
Commit message · julian

fix(shopinbit): dumb hacked check for first and last name

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 tightens the shipping/billing name validation in the ShopInBit feature of Stack Wallet. Previously, any non-empty name was accepted; now the name must contain at least two whitespace-separated words (e.g., a first and last name). The change is a client-side form check and does not appear to fix a security vulnerability. It is more likely a business-rule or partner-compliance fix to prevent incomplete names from being submitted to the ShopInBit service. There is no evidence in the commit or supplied references of a security issue, exploit, or disclosure.

Security candidatefix(shopinbit): WIP/not fully tested: add state/province where requiredby julian · 1232ed88 · Jun 23, 2026 · 13 filesMessage 52 · ThinInformational 19Details
Commit message · julian

fix(shopinbit): WIP/not fully tested: add state/province where required

52/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
authentication path
AI analysis · Informational 19/100

This commit is a work-in-progress feature update for the ShopinBit integration inside Stack Wallet. It adds the ability to collect and send a U.S. state or Canadian province/territory when required for delivery or billing addresses. It is not a security patch; it is a functional change to address form handling and API request data. There is no indication in the commit that it fixes a vulnerability, leak, or exploit.

Security candidatefix(shopinbit): car fee viewby julian · 7a56c671 · Jun 23, 2026 · 7 filesMessage 57 · ThinInformational 16Details
Commit message · julian

fix(shopinbit): car fee view

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 16/100

This commit is a UI refactor for the ShopinBit 'car fee' checkout screen. It removes a separate delivery-address form and instead reuses the country already chosen earlier in the request flow, displaying it as read-only billing-country information. The change also splits the country field into a human-readable name plus an ISO code. There is no obvious security bug being fixed; it looks like a normal feature cleanup to reduce duplicated input and prevent inconsistent country data.

Security candidatefix(shopinbit): desktop first run dialogby julian · 5c7f7717 · Jun 23, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · julian

fix(shopinbit): desktop first run dialog

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 commit is a routine UI tweak for the desktop version of a feature called ShopinBit. It changes the width of a first-run information dialog, removes a Cancel button, adjusts spacing, and indents bullet points. There is nothing here related to security.

AI review queuedfix: wrong app feature flag usedby julian · a6a72c17 · Jun 22, 2026 · 1 fileMessage 57 · ThinInformational 16Details
Commit message · julian

fix: wrong app feature flag used

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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100

A single-line fix changes which app feature flag controls whether a 'Gift cards' button appears in the wallet screen. The old code checked a flag named 'shopinBit' but should have checked 'cakePay'. This is almost certainly a UI/functional bug rather than a security vulnerability, but it could affect whether users see or can access a third-party gift-card service integration.

Security candidatefeat(shopinbit): keep polling ticket state & messages of terminal ticketsby sneurlax · 6da8d2fe · Jun 19, 2026 · 2 filesMessage 62 · AdequateInformational 16Details
Commit message · sneurlax

feat(shopinbit): keep polling ticket state & messages of terminal tickets

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 16/100

This commit changes the Stack Wallet app so it keeps checking (polling) the status of certain ShopInBit support tickets even after they are in a final, unchangeable state. Previously, the app stopped polling once a ticket was closed, merged, or refunded. The change removes those stop conditions. On its own, this is a behavior change rather than a direct security flaw, but it could slightly increase network traffic, battery use, and the number of API calls made to the ShopInBit server. There is no evidence in the commit that this fixes a security vulnerability or that it introduces one.

Security candidateRevert "chore: disable shopinbit sandbox"by julian · 72cff2bf · Jun 18, 2026 · 1 fileMessage 60 · AdequateLow 26Details
Commit message · julian

Revert "chore: disable shopinbit sandbox"

This reverts commit d00a101abc0bb8da416fa6f81027584f12a4e7b3.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
authentication path
AI analysis · Low 26/100

This commit flips a single setting in the Stack Wallet app so that its built-in ShopInBit shopping feature talks to a test/sandbox environment instead of the real production service. The change is explicitly marked with a TODO saying it must be set to false for production. Using sandbox mode in a production release could mean users see fake/test data, make payments that don't result in real orders, or interact with a less secure/test server. However, the diff alone does not prove this change was ever shipped to users, and the commit message only says it is reverting an earlier change that disabled the sandbox.

Security candidatechore: disable shopinbit sandboxby julian · d00a101a · Jun 18, 2026 · 1 fileMessage 47 · ThinLow 45Details
Commit message · julian

chore: disable shopinbit sandbox

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 45/100

This commit changes a third-party shopping integration from 'sandbox' (test) mode to live mode. The developer left a note earlier saying it should be set to false in production. The change itself is a normal production toggle, but because it involves real money/purchases and secret API credentials, it is worth reviewing whether this was released safely and whether any test-only behavior or weaker security settings were carried over accidentally.

Security candidateSwitch default Tezos node to tezos.stackwallet.com which doesn't support /header/shell, so getChainHeight calls /header instead, which also contains level.by Dan Miller · 3c5e7918 · Jun 17, 2026 · 2 filesMessage 50 · ThinInformational 19Details
Commit message · Dan Miller

Switch default Tezos node to tezos.stackwallet.com which doesn't support /header/shell, so getChainHeight calls /header instead, which also contains level.

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 path
AI analysis · Informational 19/100

This commit changes the default Tezos blockchain server used by Stack Wallet from a public Tezos node to Stack Wallet's own node, and adjusts the API endpoint used to check the latest block height. There is no direct evidence in the commit of a security vulnerability, but running wallet traffic through a single party-controlled node and changing the data source for chain state can carry trust and reliability risks.

AI review queuedfix(firo): temporarily disable masternode management until its fixedby julian · 2cc98629 · Jun 17, 2026 · 2 filesMessage 62 · AdequateInformational 12Details
Commit message · julian

fix(firo): temporarily disable masternode management until its fixed

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit simply hides the 'Masternodes' menu option for Firo wallets in both mobile and desktop versions of Stack Wallet. The underlying masternode management code is not removed or changed, only the user-facing button that opens it is commented out. The commit message says this is a temporary disablement 'until its fixed,' but gives no details about what is broken or whether it is security-related.

AI review queuedfix(firo): wip masternode ui fixing and cleanupby julian · 476bc108 · Jun 17, 2026 · 2 filesMessage 37 · OpaqueInformational 16Details
Commit message · julian

fix(firo): wip masternode ui fixing and cleanup

37/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 16/100

This commit tidies up the Firo masternode creation screen. It adds a button-lock so pressing 'Create Masternode' repeatedly doesn't fire multiple times, wraps long-running balance checks in loading spinners, and replaces several hand-built confirmation dialogs with a single reusable dialog widget. There is no obvious security vulnerability being fixed here; it reads as a routine UI polish and bug-fix change.