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

fix custom fee ui state drift on mobile

Public commit record

What the developer wrote

Authored by Julian

45/100 · Thin
fix custom fee ui state drift on mobile
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a UI bug in Stack Wallet where the custom/preset fee selection could get out of sync between the fee picker and the actual transaction being built. Previously, whether a custom fee was active was tracked in a separate local variable that could drift from the shared state provider. The patch makes the send flow read the fee mode directly from the shared state provider at the moment the transaction is prepared, and adds a helper that only supplies a custom fee value when custom mode is actually selected. The risk is that a user might have a preset fee selected while the app still uses an old custom fee value, or vice versa, leading to an unexpected transaction fee.

Recommended action

Review the updated send flows to confirm the provider state is always refreshed before transaction preparation and that no other send paths still rely on the removed local custom-fee flags. Consider adding integration tests that switch between preset and custom fees and verify the prepared TxData.feeRateType and satsPerVByte values match the UI selection.

Security signals we found

01

UI state drift between fee picker and transaction preparation

02

Inconsistent custom/preset fee selection could lead to unintended transaction fees

03

Removal of parallel local state in favor of single source of truth (Riverpod provider)

04

New helper enforces that custom fee value is only passed when custom mode is active

Risk score

Why this scored 30/100

Our methodology →
Potential impact 8/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 6/15
Confidence 6/10
Evidence quality 3/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.