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 43 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 queuedMerge pull request #1498 from cypherstack/pr1479/fixby Julian · 3c757a6e · Nov 3, 2026 · 2 filesMessage 58 · ThinModerate 62Details
Commit message · Julian

Merge pull request #1498 from cypherstack/pr1479/fix

fix merge order screwup

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

This commit fixes a privacy bug in Stack Wallet's Ethereum support. Previously, if a user turned Tor on or off while the wallet was still using an already-created network connection, later Ethereum traffic could accidentally use the wrong route—potentially sending sensitive RPC requests outside Tor after the user enabled it, or through Tor after the user disabled it. The patch wraps each Ethereum connection in a guard that refuses to send any further request if the Tor setting has changed since the connection was created, forcing the next operation to build a fresh connection under the current preference. It also adds tests proving the behavior.

AI review queuedMerge pull request #1496 from cypherstack/pr1479/eth-client-tor-changeby Julian · cf26d6d0 · Nov 3, 2026 · 2 filesMessage 73 · AdequateLow 47Details
Commit message · Julian

Merge pull request #1496 from cypherstack/pr1479/eth-client-tor-change

Fail ETH RPCs when the Tor preference changed after the client was built

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

This commit fixes a privacy issue in Stack Wallet's Ethereum support. Previously, if a user turned Tor on or off while the wallet was running, some Ethereum network requests could still use the old connection method, potentially exposing the user's real IP address or sending traffic outside Tor. The fix makes the wallet refuse to send such requests once the Tor setting changes, so the next request creates a fresh connection matching the current preference. The change includes tests proving the behavior.

AI review queuedfix(desktop qr): scale large camera frames down before scanningby sneurlax · f515c604 · Oct 31, 2026 · 3 filesMessage 85 · StrongInformational 15Details
Commit message · sneurlax

fix(desktop qr): scale large camera frames down before scanning

Camera frames are now scaled to fit 1280 px before scanning, which keeps
decoding fast when a camera hands back a large frame. Before the Windows
scanner read frames from the preview, a USB webcam there returned
3264x2448 photos even at the medium preset, which took 2-3 s per frame
to decode and scan on an older laptop. Windows preview captures now use
the same 1280 px cap. Files from Select file are still scanned at full
size.

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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a performance improvement, not a security fix. It makes QR code scanning faster on desktop by shrinking very large camera frames (for example, 3264x2448 images from a Windows webcam) down to 1280 pixels before trying to decode them. Previously, huge frames could take 2-3 seconds per frame to scan. There is no indication this change addresses a security vulnerability.

AI review queuedfix(desktop qr): decode QR images of any PNG bit depth from Select fileby sneurlax · cec03d5d · Oct 31, 2026 · 3 filesMessage 95 · StrongLow 32Details
Commit message · sneurlax

fix(desktop qr): decode QR images of any PNG bit depth from Select file

Image.convert(numChannels: 4) keeps the source format, so a 1-bit PNG
(Python qrcode's default output) stayed bit-packed and getBytes returned a
quarter of the bytes RGBLuminanceSource reads. It threw a RangeError, which
was swallowed and reported as "No QR code found". 16-bit PNGs failed the same
way. Convert to 8-bit RGBA, build 0xAARRGGBB pixels explicitly, and
composite transparency onto white. Move the decode into
utilities/qr_image_decoder.dart with tests for 1-bit, 8-bit gray, palette,
16-bit, RGB, RGBA, transparent and JPEG input.

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 32/100

This commit fixes a bug in Stack Wallet's desktop QR code scanner that prevented users from importing QR codes saved as certain types of PNG files (especially small 1-bit black-and-white ones, like those produced by Python's qrcode library). The old code misread the raw image bytes, causing the scanner to silently report 'No QR code found.' The fix converts all incoming images to a standard 8-bit RGBA format before decoding, and adds automated tests for many image formats.

AI review queuedMigrate the Fact0rn default node to allow Torby sneurlax · 82b494ad · Oct 28, 2026 · 3 filesMessage 78 · AdequateLow 25Details
Commit message · sneurlax

Migrate the Fact0rn default node to allow Tor

updateDefaults keeps the saved node's tor and clearnet flags, so existing
installs kept the old clearnet-only Fact0rn default even though it now
allows Tor. With Tor turned on that node is rejected and Fact0rn cannot
refresh or pass the node test.

Add a one-time migration that enables Tor on the saved Fact0rn default
node. Only a node that still matches the old shipped default on every
field the user can edit (host, port, name, SSL, failover, login, clearnet
only) is touched, so a node the user customised keeps its settings.
Clearnet stays enabled, so nothing changes with Tor off, and later
choices are left alone.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Low 25/100

This commit fixes a bug where the Fact0rn cryptocurrency default node in Stack Wallet stayed set to 'clearnet only' even after the app shipped a new default that supports Tor. For users who turned on Tor, the wallet could no longer connect to that node, so Fact0rn balances would not refresh and the node health test would fail. The patch adds a one-time database migration that flips Tor support on for the default Fact0rn node, but only if the user has not customized it. It is a connectivity/usability fix, not a vulnerability that lets an attacker steal funds or run code.

AI review queuedfix(openalias): drop the resolved alias when the recipient field changesby sneurlax · eb9d88da · Oct 28, 2026 · 3 filesMessage 85 · StrongLow 36Details
Commit message · sneurlax

fix(openalias): drop the resolved alias when the recipient field changes

Clearing the field and typing the same alias again reused the old
lookup. Every change of the address now drops a lookup for another
alias, so the cleared field ends it.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 36/100

This commit fixes a bug in Stack Wallet's OpenAlias lookup for cryptocurrency sending. Previously, if a user cleared the recipient field and retyped the same alias, the wallet reused the old address lookup instead of fetching it again. The fix now drops the cached lookup whenever the recipient text changes, ensuring a fresh lookup occurs. This is a correctness and potential security fix because a stale or attacker-controlled alias resolution could be reused when the user expected a new lookup.

AI review queuedfix(openalias): expire a resolved alias with its TTLby sneurlax · b1366075 · Oct 28, 2026 · 5 filesMessage 85 · StrongModerate 60Details
Commit message · sneurlax

fix(openalias): expire a resolved alias with its TTL

A repeated Preview or Add recipient reused the cached address for as
long as the form lived, so a later send could pay an address the
recipient had since replaced. Reuse now ends with the answer's TTL,
capped at an hour.

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

This commit fixes a bug in Stack Wallet where an OpenAlias recipient address (for example, an email-like alias that resolves to a crypto address) could be reused indefinitely once it was first looked up. If the recipient later changed their address, the wallet might still send funds to the old, cached address. The fix makes the cached address expire after the time-to-live (TTL) returned by the OpenAlias lookup, capped at one hour, so the wallet will re-resolve the alias before sending if the cached answer is stale.

AI review queuedfix(openalias): keep the alias when a preview is repeatedby sneurlax · 9a5c8f07 · Oct 26, 2026 · 3 filesMessage 62 · AdequateLow 36Details
Commit message · sneurlax

fix(openalias): keep the alias when a preview is repeated

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

This commit fixes a bug in Stack Wallet's send flow when using OpenAlias (human-readable addresses like alice@example.com that resolve to crypto addresses). Previously, after previewing a transaction, the app replaced the alias with the resolved crypto address in the input field. If the user went back and previewed again, the app would try to re-resolve the now-plain address as if it were an alias, or lose track of the original alias. The fix keeps the alias visible to the user while internally using the resolved address for the transaction, and caches the resolution so repeated previews don't trigger unnecessary or incorrect lookups. There is no direct evidence this was exploitable for theft, but address/alias confusion in a wallet send flow is a sensitive area.

AI review queuedrefactor(openalias): share the lookup between the send viewsby sneurlax · 2ce39bf4 · Oct 26, 2026 · 4 filesMessage 62 · AdequateInformational 17Details
Commit message · sneurlax

refactor(openalias): share the lookup between the 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 17/100

This commit is a code cleanup that moves the OpenAlias lookup logic into a shared service so both the mobile and desktop send screens use the same implementation. There is no direct evidence in the commit that it fixes a security vulnerability; it appears to be a refactoring change with added unit tests.

AI review queuedFormat Tor templateby slopbot9k · 6cb1d36c · Oct 26, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · slopbot9k

Format Tor template

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit adds a single blank line to a code template file. It is purely a formatting change with no functional or security impact.

AI review queuedmulti recipient ui fixesby Julian · 0b8c3f39 · Oct 13, 2026 · 8 filesMessage 28 · OpaqueLow 40Details
Commit message · Julian

multi recipient ui fixes

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

This commit fixes UI bugs in Stack Wallet's multi-recipient send screen. The changes make payment-request names display more safely (so a malicious name can't be confused with a trusted contact label), ensure payment-request messages are actually used, and add several 'mounted' checks to prevent crashes when a user navigates away during QR scanning or clipboard access. The patch is defensive and improves security posture, but it is a partial UI fix rather than a complete elimination of all related risks.

AI review queuedMerge pull request #1459 from waozixyz/monero-multi-recipient-uriby Julian · 83bb15f8 · Oct 13, 2026 · 12 filesMessage 73 · AdequateLow 32Details
Commit message · Julian

Merge pull request #1459 from waozixyz/monero-multi-recipient-uri

Support multi-recipient Monero payment URIs

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

This commit adds support for Monero payment links that can specify multiple recipients at once, such as splitting a bill. It updates the wallet's send screen, confirmation screen, and address parsing logic so users can scan or paste a single Monero URI and pay several addresses in one transaction. The change is a feature addition, not a bug fix, and the code includes validation and tests for malformed URIs.

AI review queuedMerge branch 'staging' into building_dialog_cancelby Julian · 0485b166 · Oct 8, 2026 · 6 filesMessage 50 · ThinInformational 20Details
Commit message · Julian

Merge branch 'staging' into building_dialog_cancel

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 from the project's staging branch into a feature branch. The visible code changes fix small UI/UX bugs in Stack Wallet's send screens: clearing an internal address-validation cache when the form is reset, making desktop fee estimates fetch only once (and retry after a failure), and adding QR-code scan buttons to two desktop token send pages. There is no direct evidence in the commit that these were security vulnerabilities, and the commit message does not describe security relevance.

AI review queuedMerge pull request #1468 from Cyrix126/desktop_fee_form_refetchby Julian · 62432946 · Oct 8, 2026 · 2 filesMessage 58 · ThinInformational 17Details
Commit message · Julian

Merge pull request #1468 from Cyrix126/desktop_fee_form_refetch

Desktop fee form refetch

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

This commit fixes a desktop wallet bug where the send-fee form would repeatedly re-fetch fee estimates on every screen rebuild, wasting resources and possibly flickering. It now caches the fee estimate and only retries if the previous fetch failed. There is no indication this is a security fix.

AI review queuedMerge branch 'staging' into desktop_fee_form_refetchby Julian · 8a72c82f · Oct 8, 2026 · 4 filesMessage 50 · ThinInformational 17Details
Commit message · Julian

Merge branch 'staging' into desktop_fee_form_refetch

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

This commit merges a feature branch into another work-in-progress branch. It adds QR-code scanning buttons to two desktop token send screens and resets an internal address-validation state variable when the send form is cleared. There is no direct evidence in the commit that these changes fix a security vulnerability; they appear to be normal UI/UX improvements and state cleanup.

AI review queuedMerge pull request #1467 from Cyrix126/clear_send_form_validityby Julian · d3383b4e · Oct 8, 2026 · 2 filesMessage 73 · AdequateLow 32Details
Commit message · Julian

Merge pull request #1467 from Cyrix126/clear_send_form_validity

fix: reset the address validity when clearing the send form

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

This change fixes a UI state bug in the cryptocurrency wallet's send form. When a user clears the send form, the app now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing an old address as valid after the user cleared it, which might confuse someone into thinking a new or empty address is acceptable. There is no direct evidence in the commit of funds being stolen or a remote attack.

AI review queuedMerge branch 'staging' into clear_send_form_validityby Julian · 22560a59 · Oct 8, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Julian

Merge branch 'staging' into clear_send_form_validity

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

This commit adds a QR code scanner button to two desktop cryptocurrency send forms. It is a straightforward user-interface feature addition with no apparent security relevance.

AI review queuedMerge pull request #1466 from Cyrix126/desktop_token_qr_buttonby Julian · 47f6d369 · Oct 8, 2026 · 2 filesMessage 73 · AdequateInformational 20Details
Commit message · Julian

Merge pull request #1466 from Cyrix126/desktop_token_qr_button

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

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

This commit adds a missing QR code scan button to two desktop token send screens in the Stack Wallet app. It is a straightforward user-interface fix that restores a feature already present on mobile and other send views; there is no indication it fixes a security vulnerability.

AI review queuedstyle: formattingby Cyrix126 · 09ed5441 · Oct 8, 2026 · 4 filesMessage 18 · OpaqueInformational 15Details
Commit message · Cyrix126

style: formatting

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 15/100

This commit contains only cosmetic code formatting changes—adjusting line breaks and indentation in four files. There are no functional changes, no bug fixes, and no security-related modifications.

AI review queuedfix: stop estimating the desktop fee for a zero amountby Cyrix126 · 90c91bde · Oct 7, 2026 · 2 filesMessage 62 · AdequateInformational 23Details
Commit message · Cyrix126

fix: stop estimating the desktop fee for a zero amount

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

This commit fixes a UI bug in the desktop version of Stack Wallet where the send amount could be lost while the app was trying to estimate transaction fees. The fix keeps the amount 'alive' in memory so fee estimation does not accidentally reset it to zero. There is no direct evidence this is a security vulnerability, but it could cause user confusion or failed transactions.

AI review queuedfix: stop refetching the desktop fee rates on every rebuildby Cyrix126 · a1ca9292 · Oct 7, 2026 · 2 filesMessage 62 · AdequateInformational 18Details
Commit message · Cyrix126

fix: stop refetching the desktop fee rates on every rebuild

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

This commit fixes a performance bug in the desktop version of Stack Wallet where the app repeatedly re-fetched Bitcoin-style fee rates every time the on-screen fee form rebuilt. The change caches the fee result and only fetches again if the previous attempt failed. It is primarily a reliability/efficiency improvement, not a security fix.

AI review queuedfix: reset the address validity when clearing the send formby Cyrix126 · 43dd0477 · Oct 6, 2026 · 2 filesMessage 62 · AdequateLow 34Details
Commit message · Cyrix126

fix: reset the address validity when clearing the send form

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

This commit fixes a UI state bug in Stack Wallet's send form. When a user clears the send form, the wallet now also resets whether the entered address is considered valid. Without this fix, the form could incorrectly keep showing an old address as valid after the user cleared it, which might confuse someone into thinking a new or empty address is ready to send to.

AI review queuedMerge pull request #1361 from cypherstack/fix/305-multiline-transaction-notesby Julian · 5172e63e · Oct 5, 2026 · 3 filesMessage 73 · AdequateInformational 19Details
Commit message · Julian

Merge pull request #1361 from cypherstack/fix/305-multiline-transaction-notes

fix: support multiple lines in transaction note editing

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 lets users type multi-line notes when editing transaction and trade notes, and fixes the desktop layout so long notes scroll instead of breaking the screen. It also swaps the old `mounted` check for the newer `context.mounted` pattern. There is no security issue here; it is a straightforward user-interface improvement with added tests.

AI review queuedSupport multi-recipient Monero payment URIsby Waozi · 81b0f4dc · Oct 5, 2026 · 12 filesMessage 80 · StrongLow 29Details
Commit message · Waozi

Support multi-recipient Monero payment URIs

Monero payment URIs can list several recipients, e.g.
`monero:A;B?tx_amount=1;2&recipient_name=x;y`. Parse these into
PaymentUriData.recipients, requiring one amount (and, when given, one
name) per address. Callers opt in with allowMultipleRecipients, so screens
that handle a single address reject these URIs rather than dropping
recipients.

Monero wallets now report supportsMultiRecipient. On their mobile and
desktop send screens, "Add recipient" or a multi-recipient URI replaces
the address field with the Recipient forms started for FROST, one per
recipient, which can be added to and removed. A multi-recipient URI
scanned or pasted into one of those forms asks before replacing all the
recipients. A multi-recipient URI rejected for its amounts clears the
previous recipient and amount, so Preview can't send them instead. The
amount field shows their total, and removing all but one recipient
returns to the normal form. The transaction has one output per
recipient, and the confirmation screen lists each recipient with its
name and amount.

The Recipient form now:
- shows the payment request's name for its address, and flags an
invalid address;
- fills in the address, amount, and name from a pasted payment request,
as it did from a scanned one;
- scans with the desktop QR code scanner on desktop;
- keeps its amount, rather than the number typed, when the display unit
changes, which otherwise read e.g. 1000 mXMR as 1000 XMR. The send
screens' amount field does the same, keeping any Xelis send all.
Recipient forms are kept per wallet, so recipients entered for one
wallet never appear in another wallet's form.

prepareSend no longer treats a multi-recipient total equal to the whole
balance as sending the whole balance, which it then rejected for
multiple recipients; the fee has to fit in the balance as for any other
amount.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit adds support for Monero payment URIs that contain multiple recipients, such as a single QR code or link that pays several people at once. It also fixes a related display bug where changing the currency unit (for example from XMR to milli-XMR) would misread the typed number. The changes are a feature addition with some defensive hardening, not a patch for an active security vulnerability.

AI review queuedMerge branch 'staging' into fix/desktop-pw-resetby Julian · d9b5cc02 · Oct 5, 2026 · 23 filesMessage 45 · ThinLow 37Details
Commit message · Julian

Merge branch 'staging' into fix/desktop-pw-reset

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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 37/100

This commit is a large merge that mainly adds a new 'prove you own a Spark address' feature to the Stack Wallet app, plus some related fixes. It also updates a dependency that handles SOCKS5 proxy connections and changes how the app decides whether it is running on a desktop or phone. The changes look like ordinary feature work rather than an obvious security patch, but a few areas could affect security: the new ownership-proof code uses private keys, the proxy library upgrade could change how Tor/proxy traffic is routed, and the desktop-detection refactor changes platform assumptions across the app.