You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bitcoin v26.2 merge introduced stricter fee validation that causes multiple wallet functional tests to fail. The tests create transactions that don't meet DigiByte's fee requirements, causing mempool rejection and transaction broadcast failures.
126
+
127
+
### Root Cause
128
+
Related to BUG-001 (fee enforcement), the stricter validation from Bitcoin v26.2 exposes the fee calculation inconsistencies in DigiByte. Tests expect transactions to be accepted but they're rejected due to:
129
+
1. Fee amounts exceeding `-maxtxfee` limits
130
+
2. Transactions not meeting minimum fee requirements
131
+
3.`testmempoolaccept` returning `allowed: false` for valid-looking transactions
132
+
133
+
### Symptoms
134
+
-`wallet_fundrawtransaction.py`: testmempoolaccept failures in external inputs test
135
+
-`wallet_send.py`: `AssertionError: not(False == True)` at mempool acceptance checks
136
+
-`wallet_sendall.py`: JSONRPC errors in transaction creation
137
+
-`wallet_fundrawtransaction.py --legacy-wallet`: "Fee exceeds maximum configured by user"
138
+
-`wallet_bumpfee.py`: "min relay fee not met" (4380 sats < 177000 sats required), transactions not mining
139
+
-`wallet_create_tx.py`: "Fee exceeds maximum configured by user" even with high maxtxfee
140
+
-`wallet_groups.py`: Balance expectations fail (4.29 DGB vs 215 DGB expected) due to fee consumption
141
+
142
+
### Fix Required
143
+
```cpp
144
+
// Two-pronged approach needed:
145
+
// 1. Fix underlying fee calculation in BUG-001
146
+
// 2. Update test expectations for DigiByte fee structure
147
+
148
+
// In tests, may need to:
149
+
// - Increase -maxtxfee from 10.0 to higher value
150
+
// - Adjust expected fee amounts in assertions
151
+
// - Account for DigiByte's 100x fee multiplier in test logic
0 commit comments