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 2 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 queuedfix(firo): fill spark memo from payment URI messageby sneurlax · 60a6112d · Oct 4, 2026 · 2 filesMessage 85 · StrongInformational 19Details
Commit message · sneurlax

fix(firo): fill spark memo from payment URI message

Scanning or pasting a firo: URI only ever applied the message param to
the local note. firo-qt treats message as the spark memo when the
recipient is a spark address, so do the same in both send views.

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

This commit fixes a small user-experience bug in Stack Wallet for Firo cryptocurrency. When a user scanned or pasted a firo: payment link containing a message, the app previously put that message only in the local private note field. Now, if the recipient is a Spark privacy address, the message is also placed in the Spark memo field, matching how the official Firo desktop wallet (firo-qt) behaves. This is a feature-parity fix, not a security patch.

Security candidatefix: ignore a failed build after cancelby Cyrix126 · 6a58f42a · Sep 29, 2026 · 10 filesMessage 57 · ThinInformational 23Details
Commit message · Cyrix126

fix: ignore a failed build after cancel

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 pathboot or update path
AI analysis · Informational 23/100

This commit fixes a UI bug in Stack Wallet where cancelling a transaction build could cause the app to try to close a dialog that was already gone, leading to a crash or confusing error screen. The fix moves a 'wasCancelled' flag outside the try-block so it remains visible in the catch-block, and then skips popping the dialog if the user cancelled. It is a stability/UX fix, not a cryptographic or funds-theft issue.

AI review queuedfix: close the building dialog once on cancelby Cyrix126 · dd0d2d58 · Sep 29, 2026 · 2 filesMessage 57 · ThinInformational 18Details
Commit message · Cyrix126

fix: close the building dialog once on cancel

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

This commit fixes a small UI bug in a cryptocurrency wallet app. Previously, pressing Cancel on a 'building transaction' dialog could close the dialog twice, which might cause a harmless crash or visual glitch. The fix moves the dialog-closing action into the cancel callback so it happens exactly once.

AI review queuedfix: add missing QR scan button to desktop token send viewsby Cyrix126 · 9854a51f · Sep 26, 2026 · 2 filesMessage 62 · AdequateInformational 19Details
Commit message · Cyrix126

fix: add missing QR scan button to desktop token send views

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

This commit simply adds a missing QR-code scan button to two desktop token-send screens in the Stack Wallet app. It is a user-interface fix, not a security patch. There is no indication it fixes a vulnerability.

AI review queuedMerge pull request #1452 from levoncrypto/masternode-operator-rewardby Julian · 7d9cba12 · Sep 25, 2026 · 2 filesMessage 73 · AdequateLow 30Details
Commit message · Julian

Merge pull request #1452 from levoncrypto/masternode-operator-reward

remove operator reward option from masternode registration

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 30/100

This commit removes the user-facing 'operator reward' field from the Firo masternode registration screen and hard-codes that value to zero in the wallet logic. It is a feature removal rather than a fix for an active security flaw, but it does close off a potential input-validation and transaction-construction risk surface.

AI review queuedMerge branch 'staging' into masternode-operator-rewardby Julian · e88cb980 · Sep 25, 2026 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Julian

Merge branch 'staging' into masternode-operator-reward

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

This commit changes how a Firo cryptocurrency wallet picks a special 'owner address' when setting up a masternode. Previously, the wallet only made sure the owner address was different from the collateral address. Now it also checks that the owner address is different from the payout address. This prevents the same address from being accidentally reused for two different roles, which could reduce privacy or cause bookkeeping problems. There is no direct evidence in the commit that this fixes an active security vulnerability, but it is a defensive improvement.

AI review queuedMerge pull request #1453 from levoncrypto/masternode-payout-uiby Julian · fb70bcca · Sep 25, 2026 · 1 fileMessage 58 · ThinLow 42Details
Commit message · Julian

Merge pull request #1453 from levoncrypto/masternode-payout-ui

pick owner address distinct from payout

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 42/100

This change updates the Firo wallet's masternode owner address selection so that the chosen owner address is different from both the collateral address and the payout address. Previously, the code only ensured the owner address differed from the collateral address. The change appears to prevent a configuration where the owner, collateral, and payout addresses overlap, which could cause issues with masternode registration or rewards. There is no direct evidence in the commit that this fixes an active security vulnerability, but address reuse or overlap in masternode operations can have privacy and operational risks.

Security candidateMerge branch 'staging' into masternode-payout-uiby Julian · 1324e37a · Sep 25, 2026 · 20 filesMessage 45 · ThinInformational 19Details
Commit message · Julian

Merge branch 'staging' into masternode-payout-ui

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit is a routine feature merge that adds support for a new Ethereum token called rsFIRO across several app variants. It updates token lists, adds an icon, and includes a database migration so existing users automatically see the new token. There is no indication this change fixes a security vulnerability or introduces a known dangerous behavior.

Security candidateMerge branch 'staging' into masternode-operator-rewardby Julian · 8cc81383 · Sep 25, 2026 · 28 filesMessage 50 · ThinInformational 19Details
Commit message · Julian

Merge branch 'staging' into masternode-operator-reward

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit is a routine feature merge that adds support for a new Ethereum token called rsFIRO, updates some app configuration scripts, refreshes a privacy-related Git dependency, and fills in missing API-key placeholders for exchange integrations. There is no direct evidence in the diff of a security vulnerability, malicious code, or a fix for a disclosed security issue. The changes are mostly product/configuration plumbing.

Security candidateMerge pull request #1448 from reubenyap/codex/rsfiro-app-configby Julian · 6203aeae · Sep 25, 2026 · 20 filesMessage 73 · AdequateInformational 19Details
Commit message · Julian

Merge pull request #1448 from reubenyap/codex/rsfiro-app-config

feat: add rsFIRO with configurable Ethereum token defaults

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 19/100

This commit adds support for a new Ethereum token called rsFIRO and makes the list of default Ethereum tokens configurable for each app flavor (Stack Wallet, Stack Duo, Campfire). It also includes a database migration so existing users get rsFIRO added automatically. There is no obvious security vulnerability in the changes, but the migration logic has a subtle edge case that could, in theory, affect token data consistency.

AI review queuedallow owner address to equal voting addressby levoncrypto · 19add823 · Sep 25, 2026 · 1 fileMessage 45 · ThinInformational 24Details
Commit message · levoncrypto

allow owner address to equal voting address

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

This small change relaxes a wallet rule for the Firo cryptocurrency. Previously, when setting up a masternode-like service, the wallet required the 'owner address' to be different from the 'voting address'. Now it allows them to be the same. The change itself does not look like a typical security bug; it is more likely a feature or bug-fix for valid user setups. However, because it removes a deliberate separation between two addresses, it could slightly weaken privacy or governance separation in some configurations. There is no evidence in the commit of a vulnerability, exploit, or security disclosure.

AI review queuedpick owner address distinct from payout and voting addressesby levoncrypto · 86b9ec97 · Sep 25, 2026 · 1 fileMessage 50 · ThinModerate 59Details
Commit message · levoncrypto

pick owner address distinct from payout and voting addresses

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 · Moderate 59/100

This change fixes how Stack Wallet picks a special 'owner address' for Firo masternode-related operations. Previously, the wallet only made sure the owner address was different from the collateral address. Now it also ensures it differs from the payout and voting addresses. Using the same address for multiple roles could weaken privacy or cause operational problems in how the wallet tracks funds and masternode rewards.

AI review queuedassets: clean rsFIRO SVGs with svgcleanerby Reuben Yap · 570e3e2a · Sep 24, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Reuben Yap

assets: clean rsFIRO SVGs with svgcleaner

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 simply runs a cleanup tool on three SVG image files used for the rsFIRO cryptocurrency icon. It removes unnecessary formatting and metadata from the image files without changing their visual appearance. There is no security relevance.

AI review queuedMerge staging and keep the upstream CI workflowby Reuben Yap · 2dbadce6 · Sep 24, 2026 · 10 filesMessage 45 · ThinInformational 18Details
Commit message · Reuben Yap

Merge staging and keep the upstream CI workflow

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

This commit is a routine merge from a staging branch that mostly tidies up build scripts and CI. The only user-visible change is that the Firo wallet now groups 'revoked' and 'banned' masternodes together under a single red 'banned' label, instead of showing them as two separate statuses. It also updates a privacy-related internal dependency and makes sure empty API key templates are created automatically during builds and tests. There is no obvious security vulnerability in the diff itself.

AI review queuedremove operator reward option from masternode registrationby levoncrypto · 77ea7c04 · Sep 23, 2026 · 2 filesMessage 50 · ThinInformational 23Details
Commit message · levoncrypto

remove operator reward option from masternode registration

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

This commit removes the user-facing 'operator reward' field from the Firo masternode registration screen and hard-codes that value to 0. The change simplifies the form and prevents users from entering an operator reward percentage. There is no direct evidence in the commit that this fixes an active security vulnerability, but it does eliminate a potential source of user error or misuse in how masternodes are registered.

AI review queuedclean up and fix ciby Julian · abae853a · Sep 23, 2026 · 6 filesMessage 38 · OpaqueInformational 13Details
Commit message · Julian

clean up and fix ci

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 13/100

This commit is routine build and continuous-integration housekeeping. It adds missing placeholder API key entries for several exchange partners (including Trocador) to test and prebuild scripts, removes some stale gitignore entries, and fixes a minor string formatting issue in an error message. There is no indication of a security vulnerability being fixed.

AI review queuedMerge pull request #1451 from levoncrypto/masternode-statusby Julian · 2a92caba · Sep 23, 2026 · 2 filesMessage 73 · AdequateInformational 19Details
Commit message · Julian

Merge pull request #1451 from levoncrypto/masternode-status

use ACTIVE/BANNED masternode statuses, revoked masternodes are banned

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit simplifies how the Stack Wallet app displays Firo masternode status. Previously, the app distinguished between masternodes that were 'banned' and those that were 'revoked'. Now both conditions are shown as 'BANNED' with a red color. This is a user-interface labeling change; it does not appear to alter wallet security, transaction handling, or private keys.

AI review queueduse ACTIVE/BANNED masternode statuses, revoked masternodes are bannedby levoncrypto · 3d724b93 · Sep 23, 2026 · 2 filesMessage 50 · ThinInformational 16Details
Commit message · levoncrypto

use ACTIVE/BANNED masternode statuses, revoked masternodes are banned

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

This commit simplifies how the Stack Wallet app labels Firo masternodes. Previously, the app distinguished between 'banned' and 'revoked' masternodes, showing banned ones in orange and revoked ones in red. Now both states are treated as 'banned' and shown in red. This is a UI/status-label change; it does not appear to alter how transactions are signed, validated, or how funds are handled.

AI review queuedMerge branch 'staging' into codex/rsfiro-app-configby Reuben Yap · fee7936d · Sep 23, 2026 · 2 filesMessage 50 · ThinInformational 20Details
Commit message · Reuben Yap

Merge branch 'staging' into codex/rsfiro-app-config

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

This commit is a routine merge that improves how the Stack Wallet app displays Firo masternode status. Previously, a masternode was shown as simply 'ACTIVE' or 'REVOKED' based only on whether it had been revoked. Now it can also show 'BANNED' when the masternode has been banned for misbehavior (a 'poseBanHeight' value other than -1). The colors in the UI were also updated so banned nodes appear orange instead of green or red. There is no indication this fixes a security vulnerability; it is a user-interface accuracy improvement.

AI review queuedci: format touched files and reuse test key stubsby Reuben Yap · 015a8011 · Sep 23, 2026 · 5 filesMessage 67 · AdequateInformational 15Details
Commit message · Reuben Yap

ci: format touched files and reuse test key stubs

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is purely cosmetic and CI-related. It reformats several Dart UI files to match the project's code style and removes a redundant fallback block in the GitHub Actions test workflow that wrote empty placeholder API keys when real keys were not supplied. There is no functional change to app behavior or security-sensitive logic.

AI review queuedfeat: load rsFIRO icons from per-app asset sourcesby Reuben Yap · 4bf55f6a · Sep 23, 2026 · 8 filesMessage 62 · AdequateInformational 15Details
Commit message · Reuben Yap

feat: load rsFIRO icons from per-app asset sources

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

This commit simply swaps the source of the rsFIRO token icon from a network-downloaded image to a local SVG file bundled inside the app. It is a cosmetic/user-interface change with no security implications.

Security candidatefeat: generate per-app Ethereum token defaultsby Reuben Yap · 82f9fa6d · Sep 23, 2026 · 9 filesMessage 57 · ThinInformational 19Details
Commit message · Reuben Yap

feat: generate per-app Ethereum token defaults

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

This commit reorganizes how Stack Wallet and its related apps choose which Ethereum tokens appear by default. It does not fix a security bug and does not introduce an obvious vulnerability. The main change is moving the default token list from a single shared file into per-app configuration scripts, and adding a new rsFIRO token for the Campfire app. The token contract addresses shown in the diff match well-known public Ethereum addresses, so there is no direct evidence of malicious token substitution.

AI review queuedMerge pull request #1449 from levoncrypto/masternode-uiby Julian · c95cd3e7 · Sep 22, 2026 · 2 filesMessage 58 · ThinInformational 18Details
Commit message · Julian

Merge pull request #1449 from levoncrypto/masternode-ui

Fix masternode status

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit fixes the masternode status display in the Firo wallet. Previously, the UI only showed a masternode as either 'ACTIVE' or 'REVOKED' based on a single check. Now it correctly distinguishes three states: active, banned, and revoked. This is a user-interface bug fix with no apparent security impact.

AI review queuedFix masternode statusby levoncrypto · 852c4df1 · Sep 22, 2026 · 2 filesMessage 28 · OpaqueInformational 19Details
Commit message · levoncrypto

Fix masternode status

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

This commit fixes how the app displays the status of Firo masternodes. Previously, a masternode was shown as either 'ACTIVE' or 'REVOKED' based only on whether it had been revoked. Now it also recognizes a 'BANNED' state (when the node has been banned for misbehavior). This is a UI/accuracy improvement, not a security vulnerability fix.

Security candidateMerge pull request #1437 from cypherstack/julian/various-fixes-contdby Julian · ae6a439d · Sep 19, 2026 · 234 filesMessage 58 · ThinLow 44Details
Commit message · Julian

Merge pull request #1437 from cypherstack/julian/various-fixes-contd

Julian/various fixes contd

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Low 44/100

This is a very large routine merge of 'various fixes' for the Stack Wallet Flutter app. The visible changes mostly update build tooling (Flutter 3.47.2, Android Gradle Plugin 9, Go/Rust versions), switch several crypto plugins from Git submodules to native-assets/prebuilt builds, reformat code, regenerate Isar database schema files, and fix a handful of UI/amount-handling bugs. There is no explicit security disclosure in the commit message or diff, and no single clearly exploitable vulnerability is introduced. The most security-relevant code-level changes are hardening touches: Android secure-storage options now disable reset-on-error and enable backup migration, ElectrumX ping now returns false on timeout instead of throwing, and MWEB peg-out UTXOs now enforce an extra maturity check before being considered spendable. However, the patch is huge (234 files, thousands of lines changed), so a complete security review is not possible from the supplied excerpt alone.