AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 52 Monero

Rotate used receiving addresses on every derivation path

Public commit record

What the developer wrote

Authored by slopbot9k

73/100 · Adequate
Rotate used receiving addresses on every derivation path

A refresh only checked the current receiving address of the wallet's
main address type for history. A used address on any other supported
derivation path stayed the latest one, so the Receive view's other
address tabs and the Buy form's BIP84 fallback kept handing out an
address that already had transactions.

Once the main address is settled, the refresh now also checks the
latest saved receiving address of each other supported derivation path
and saves the next one while it has history.

Left alone:
- paths with no saved receiving address
- view-only wallets, whose single path the main check already covers
- wallets with address reuse enabled
- paths that share the main address type (bch44, eCash44), since saved
addresses are looked up by address type
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

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 generated addresses for other address types (such as older SegWit or legacy addresses), the wallet would keep showing those addresses in its Receive screen and Buy form even after they had already received payments. Reusing addresses is bad for privacy because it lets anyone see all your transactions on that address. The fix makes the wallet check every supported address type and automatically generate a fresh, unused receiving address for each one.

Recommended action

Users should update to a build containing this commit. No immediate key rotation is required, but users who previously received funds on reused secondary addresses should be aware that those address histories are public on-chain. Developers should verify that `supportedDerivationPathTypes` is correctly populated for each currency and that address types sharing the main type (e.g., bch44/eCash44) are handled elsewhere if needed.

Security signals we found

01

Address reuse mitigation

02

Privacy improvement

03

Wallet receive-address rotation

04

ElectrumX transaction-history check

05

Test coverage added for multi-path rotation

Risk score

Why this scored 52/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 10/15
Affected reach 10/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.