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
473commits · 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 34 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.

AI review queuedflatpak: add :create to data-dir filesystem grants so first-run persistsby Dan Miller · 5e411341 · Aug 13, 2026 · 3 filesMessage 50 · ThinInformational 18Details
Commit message · Dan Miller

flatpak: add :create to data-dir filesystem grants so first-run persists

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This change updates three Flatpak app permission files so the apps can create their own data folders (like ~/.stackwallet) on first launch. Previously, the apps could only access those folders if they already existed, which could cause first-run setup to fail. The change is a sandbox permission tweak, not a fix for a code vulnerability.

AI review queuedeth fees update/fixby Julian · 3af51469 · Aug 12, 2026 · 3 filesMessage 28 · OpaqueLow 41Details
Commit message · Julian

eth fees update/fix

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 41/100

This commit changes how Ethereum transaction fees are calculated in Stack Wallet. Previously, the wallet set the maximum base fee equal to the current network base fee, which could cause transactions to fail if network fees rose even slightly. The fix doubles the maximum base fee for preset fee options to give transactions more headroom. It also removes a check that prevented the priority fee from exceeding the maximum base fee. The commit adds extra logging for fee values but does not otherwise change security-sensitive code.

AI review queuedfiro temp SISTby Julian · 8f849d6b · Aug 12, 2026 · 8 filesMessage 8 · OpaqueLow 30Details
Commit message · Julian

firo temp SIST

8/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 30/100

This commit changes how the Stack Wallet mobile app handles private Firo (Spark) transactions. It temporarily blocks sending private Firo funds to exchange addresses, and rewrites the internal logic for preparing and broadcasting Spark spends so that each transaction uses only a single Spark coin input. It also adds a new planner that can split one payment across multiple single-input transactions when needed. The change appears to be a defensive measure rather than a fix for an active exploit, but it touches sensitive transaction-building code and removes some previously available functionality.

AI review queuedmaybeby Julian · c6a23088 · Aug 1, 2026 · 1 fileMessage 0 · OpaqueInformational 22Details
Commit message · Julian

maybe

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 22/100

This commit changes how transaction fees are calculated for a specific type of Litecoin transaction called 'mwebPegIn' (Mimblewimble peg-in). Previously, the fee was estimated once and the transaction was built. Now, for mwebPegIn transactions, it loops: builds the transaction, checks the actual fee based on the final transaction size, and rebuilds if the fee is too low. This is a bug fix to ensure users pay the correct network fee and their transactions don't get stuck or fail. There is no clear security vulnerability here; it appears to be a correctness/reliability improvement.

AI review queuedclean up remaining pointlessnessby julian · 07398235 · Jul 31, 2026 · 1 fileMessage 35 · OpaqueLow 27Details
Commit message · julian

clean up remaining pointlessness

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 27/100

This commit removes two blocks of code that added an API key to outgoing requests for a cryptocurrency exchange integration called CypherGoat. The commit message calls this 'pointlessness,' suggesting the API key was unused or unnecessary. There is no direct evidence in the commit that this fixes a security vulnerability, but sending API keys when they are not needed can slightly increase exposure risk if those requests or logs are intercepted.

AI review queuedclean upby julian · ade42baa · Jul 31, 2026 · 3 filesMessage 0 · OpaqueInformational 18Details
Commit message · julian

clean up

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit is a minor cleanup: it swaps two ordinary print statements for Flutter's debugPrint (which only shows in debug builds), removes a leftover debug print of a transaction map, and stops sending an API key in requests to the CypherGoat exchange service. The API-key removal is the only change with any security angle, but the diff does not show what the key was, how it was stored, or whether it was sensitive. There is no evidence of an active vulnerability being fixed.

AI review queuedrecreate sib tables correctlyby julian · be28a7a5 · Jul 31, 2026 · 1 fileMessage 35 · OpaqueInformational 21Details
Commit message · julian

recreate sib tables correctly

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 21/100

This commit updates a database migration in the Stack Wallet app. It bumps the database version from 2 to 3 and changes the upgrade logic so that, when upgrading from any version below 3, two tables related to a 'Shop in Bit' feature are deleted and recreated, plus an app notifications table is created. The commit message and code comment state this is needed to 'recreate sib tables correctly.' There is no explicit mention of a security issue in the commit or supplied references. The main risk is that deleting and recreating tables during migration could cause data loss if the tables already contained user data, but the developer comment claims the feature was not used before this point. No independent security disclosure or vendor security advisory was provided.

AI review queuedcyphergoat related tweaksby Julian · 903aac9d · Jul 30, 2026 · 10 filesMessage 35 · OpaqueInformational 22Details
Commit message · Julian

cyphergoat related tweaks

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 22/100

This commit makes several small adjustments to the CypherGoat exchange integration in Stack Wallet. It adds a new 'other' field to trade records to store a tracking URL, makes some CypherGoat API response fields optional instead of required, filters out some competing exchange providers from CypherGoat rate quotes, and fixes a minor error-message formatting bug. There is no clear security vulnerability being patched, and the commit message does not describe any security relevance.

AI review queuedadd cg svg iconby julian · 1df7c3f9 · Jul 30, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · julian

add cg svg icon

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply adds three identical SVG image files for a new exchange partner icon named 'cyphergoat' to the project's asset folders. It is a routine asset-only change with no code modifications and no apparent security relevance.

AI review queuedgitignore updateby julian · 10d1fc8d · Jul 30, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · julian

gitignore update

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates the .gitignore file to ignore the android/build/ directory. It is a routine repository hygiene change with no security relevance.

AI review queuedfix masternode utxo freeze handlingby Julian · 7f6e685a · Jul 30, 2026 · 4 filesMessage 45 · ThinLow 31Details
Commit message · Julian

fix masternode utxo freeze handling

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 how Stack Wallet handles Firo masternode collateral UTXOs. Previously, the wallet could auto-freeze a UTXO, the user could deliberately unfreeze it, and then a later sync would re-freeze it automatically. The patch prevents that automatic re-freezing once a user has unfrozen a UTXO, while still allowing a first-time auto-freeze when masternode collateral is newly detected. It also improves the labels shown to users when collateral is detected with certainty versus only suspected. The pubspec.lock changes update unrelated dependencies and are not directly security-relevant.

Security candidatesib: remove full service arrangementby julian · 84436b7e · Jul 30, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · julian

sib: remove full service arrangement

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 removes one travel booking option ('Full Service') from a list of choices in the Stack Wallet app's ShopinBit travel form. It is a routine product or UI change, not a security fix.

AI review queuedMasternode UI fixby levoncrypto · 81888179 · Jul 28, 2026 · 11 filesMessage 28 · OpaqueInformational 20Details
Commit message · levoncrypto

Masternode UI fix

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit is a UI refactor for the masternode feature in Stack Wallet. It removes a hard-coded note-based detection system for masternode collateral transactions and instead lets the user explicitly start the masternode registration flow from the masternode screen. It also fixes a couple of small UI bugs, such as showing the wrong error message text in slatepack/slate failure dialogs and properly formatting pre-filled amounts in the desktop send form. There is no obvious security vulnerability introduced, but the change removes a large block of auto-detection logic that previously tried to identify 1000-FIRO self-sends as collateral.

AI review queuedcyphergoat: use Decimal for money values, error instead of default on missing fieldsby 4rkal · 26e0a0cb · Jul 27, 2026 · 5 filesMessage 50 · ThinLow 44Details
Commit message · 4rkal

cyphergoat: use Decimal for money values, error instead of default on missing fields

50/100 · ThinMessage clarity
✓ Specific, 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 44/100

This commit hardens how Stack Wallet's CypherGoat exchange integration handles API responses. It replaces imprecise floating-point math with exact decimal arithmetic for money amounts, and stops silently substituting default values (like 0 or empty strings) when expected fields are missing. Instead, the app now throws a clear error if required fields are absent or malformed. This reduces the risk of incorrect trade amounts being shown or accepted, and makes the app fail more safely if the exchange server sends an unexpected or malformed response.

Security candidateupdate for sib 1.0.7by Julian · 283a3678 · Jul 27, 2026 · 6 filesMessage 38 · OpaqueInformational 23Details
Commit message · Julian

update for sib 1.0.7

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 23/100

This commit updates the Stack Wallet app's ShopInBit payment flow to support a new version of the ShopInBit backend API (1.0.7). It mainly adds handling for expired and underpaid invoices, allowing users to refresh or retry invoices instead of being stuck. There is no clear security vulnerability in the diff itself; it appears to be a feature/bug-fix update for payment recovery.

Security candidatesib: fix key iconby julian · a8568469 · Jul 24, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · julian

sib: fix key icon

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit is a purely cosmetic UI fix for a key icon in the ShopInBit settings screen. It wraps the existing SVG key icon in a rounded grey container and applies a black color filter. There is no security relevance in the code change.

Security candidatesib: more fixes and clean upby julian · d213b222 · Jul 23, 2026 · 7 filesMessage 45 · ThinInformational 19Details
Commit message · julian

sib: more fixes and clean up

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

This commit updates the Stack Wallet app's integration with the ShopInBit service. It mainly adds a new 'delivery state/province' field to order requests, normalizes how US states and Canadian provinces are displayed, and fixes a small UI spacing issue. There is no clear security problem here; it looks like routine feature cleanup to make address information more complete and consistent.

Security candidateunreviewedby Julian · 40c4ac5b · Jul 23, 2026 · 6 filesMessage 0 · OpaqueInformational 24Details
Commit message · Julian

unreviewed

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 · Informational 24/100

This commit is a large UI refactor of the Stack Wallet 'ShopInBit' payment flow. It extracts duplicated payment-method selection and QR-code dialogs into a shared widget, fixes some navigation bugs after a payment is sent, and tightens the USDT Ethereum-address detection. There is no obvious new security vulnerability in the diff, but the change is substantial and unreviewed, so it could contain subtle bugs.

Security candidateUpdate Spark Mobile wrapper pinby Reuben Yap · a9d36e11 · Jul 23, 2026 · 2 filesMessage 45 · ThinLow 32Details
Commit message · Reuben Yap

Update Spark Mobile wrapper pin

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Low 32/100

This commit changes which version of the 'Spark Mobile' cryptographic library Stack Wallet uses. It switches from the official Firo project repository to a fork maintained by Cypher Stack (the same company that makes Stack Wallet) and updates the pinned commit hash. The change itself does not show any vulnerability in the code, but it is a supply-chain-style update: the wallet now depends on a different copy of a library that handles sensitive private-key and transaction operations for the Firo cryptocurrency. Without knowing what changed between the two commit hashes, we cannot say whether this makes users safer or less safe.

Security candidatesib: (delivery) state parsing fix and loading message changedby julian · e6265ae6 · Jul 23, 2026 · 2 filesMessage 50 · ThinInformational 18Details
Commit message · julian

sib: (delivery) state parsing fix and loading message changed

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

This commit fixes a small parsing bug in the Stack Wallet app's ShopInBit feature. The app reads a 'state/province' line from a support ticket message. Previously it only looked for lines starting with 'Delivery state:', but now it also accepts 'State:'. A user-facing loading message was also reworded from 'Updating available countries' to 'Checking available countries'. There is no clear security relevance in the change itself.

AI review queuedclean up remaining letsexchange integration itemsby julian · b76c068d · Jul 20, 2026 · 10 filesMessage 45 · ThinInformational 15Details
Commit message · julian

clean up remaining letsexchange integration items

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

This commit finishes adding support for a new cryptocurrency exchange partner called LetsExchange to the Stack Wallet app. It adds the exchange's logo, wires up its name in currency lookup and trade-detail screens, adds its API credentials placeholders to build scripts, removes its response bodies from debug logs, and excludes it from a Trocador aggregator filter. There is no security fix or vulnerability visible in the changes.

AI review queuedRestore Spark Name fee script sizingby Reuben Yap · 1579f8ee · Jul 16, 2026 · 2 filesMessage 45 · ThinLow 42Details
Commit message · Reuben Yap

Restore Spark Name fee script sizing

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

This commit fixes how the Stack Wallet calculates the size of a special 'Spark Name' fee script when building cryptocurrency transactions. Previously, the wallet appears to have used a fixed estimate (noProofNameTxData!.size) and did not account for the extra bytes added by embedding the Spark Name data into the output script. The patch now measures the actual increase in script size and adds that delta to the transaction size used for fee estimation. If left unfixed, transactions with Spark Names could have had fees that did not cover the real transaction size, potentially causing the transaction to be rejected, delayed, or underpaid.

AI review queuedTest Spark Name character validationby Reuben Yap · 2bff96e5 · Jul 16, 2026 · 1 fileMessage 55 · ThinInformational 12Details
Commit message · Reuben Yap

Test Spark Name character validation

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds a new automated test that checks whether a regular expression correctly accepts or rejects certain Spark Name characters (hyphens/periods vs underscores). It does not change any production wallet code, fix a bug, or alter behavior users would see.

AI review queuedReject invalid Spark Name charactersby Reuben Yap · f2d474d9 · Jul 16, 2026 · 4 filesMessage 45 · ThinLow 45Details
Commit message · Reuben Yap

Reject invalid Spark Name characters

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

This commit updates the Stack Wallet app to use a newer version of the underlying Spark library and changes how 'Spark Name' registration fees are calculated. The title says it rejects invalid Spark Name characters, but the actual code diff mainly removes a manual size adjustment for the special name-tag output and updates a dependency. The security relevance is not clearly spelled out in the commit itself, and the change appears to be a partial fix or cleanup rather than a complete, self-contained security patch.

AI review queuedFix Spark Name registration fee sizingby Reuben Yap · 4f3534de · Jul 16, 2026 · 2 filesMessage 45 · ThinLow 44Details
Commit message · Reuben Yap

Fix Spark Name registration fee sizing

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

This commit fixes how the Stack Wallet calculates transaction fees for a feature called Spark Name registration. Previously, the wallet did not correctly account for the extra data added to the transaction when registering a Spark Name, and it also treated name-registration payments like ordinary 'send all' transactions. The fix ensures the fee is sized properly and that the miner fee is never subtracted from the amount being sent for a name registration. In practical terms, before the fix a user registering a Spark Name might have paid an unexpectedly low fee, causing the transaction to be rejected or delayed by the network, or the wallet might have tried to subtract the fee from the registration amount, potentially sending less than intended.