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

Fix mweb fee override propagation

Public commit record

What the developer wrote

Authored by Hector Chu

45/100 · Thin
Fix mweb fee override propagation
✓ 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 bug where a user-specified custom fee amount was not being passed along when building Mimblewimble (MWEB) transactions in the Stack Wallet app. Without the fix, the wallet could ignore the user's fee choice and use a default or calculated fee instead, potentially leading to unexpected transaction costs or failed transactions.

Recommended action

Review the MWEB transaction builder to confirm overrideFeeAmount is now consumed correctly end-to-end, and add regression tests covering custom fee scenarios for MWEB sends. Verify no other fee-related parameters are similarly dropped in adjacent code paths.

Security signals we found

01

Fee override parameter not propagated to MWEB transaction builder

02

Potential user-expected fee mismatch in privacy-focused MWEB transactions

03

Single-line omission fix with no broader refactoring

Risk score

Why this scored 46/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 7/15
Affected reach 10/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.