search

WalletWasabi / WalletWasabi

Open-source, non-custodial, privacy preserving Bitcoin wallet for Windows, Linux, and Mac.
https://wasabiwallet.io
MIT License
2.15k stars 499 forks source link

Mempool min fee not met #13442

Open Kruwed opened 3 weeks ago

Kruwed commented 3 weeks ago

I tried to send a transaction at 2 sats/vbyte and it failed, increasing it to 3 worked:

2024-09-21 xx:xx:50.167 [1] INFOTransactionBroadcaster.BroadcastCoreAsync (133)Trying to broadcast transaction with random node (::ffff:127.0.0.1):xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2024-09-21 xx:xx:50.168 [1] INFOTransactionBroadcaster.BroadcastCoreAsync (133)Trying to broadcast transaction with random node (::ffff:127.0.0.1):xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2024-09-21 xx:xx:50.169 [1] INFOTransactionBroadcaster.BroadcastCoreAsync (133)Trying to broadcast transaction with random node (::ffff:127.0.0.1):xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2024-09-21 xx:xx:50.169 [1] INFOTransactionBroadcaster.BroadcastCoreAsync (133)Trying to broadcast transaction with random node (::ffff:127.0.0.1):xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2024-09-21 xx:xx:50.173 [1] INFOTransactionBroadcaster.BroadcastCoreAsync (133)Trying to broadcast transaction with random node (::ffff:127.0.0.1):xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2024-09-21 xx:xx:57.187 [1] INFOTransactionBroadcaster.BroadcastError (238)Failed to broadcast transaction: Timed out to broadcast to [::ffff:127.0.0.1]:37150 node. 2024-09-21 xx:xx:57.188 [1] INFOTransactionBroadcaster.BroadcastError (238)Failed to broadcast transaction: Timed out to broadcast to [::ffff:127.0.0.1]:37150 node. 2024-09-21 xx:xx:57.188 [1] INFOTransactionBroadcaster.BroadcastError (238)Failed to broadcast transaction: Timed out to broadcast to [::ffff:127.0.0.1]:37150 node. 2024-09-21 xx:xx:57.188 [1] INFOTransactionBroadcaster.BroadcastError (238)Failed to broadcast transaction: Timed out to broadcast to [::ffff:127.0.0.1]:37150 node. 2024-09-21 xx:xx:57.188 [1] INFOTransactionBroadcaster.BroadcastError (238)Failed to broadcast transaction: Timed out to broadcast to [::ffff:127.0.0.1]:37150 node. 2024-09-21 xx:xx:57.190 [1] INFOTransactionBroadcaster.BroadcastAsync (68)Trying to broadcast transaction via backend API:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. 2024-09-21 xx:xx:58.770 [1] INFOTransactionBroadcaster.BroadcastError (238)Failed to broadcast transaction: Bad Request mempool min fee not met, 220 < 250. 2024-09-21 09:58:58.779 [1] ERRORTransactionPreviewViewModel.OnConfirmAsync (412)System.InvalidOperationException: Error while sending transaction. at WalletWasabi.Blockchain.TransactionBroadcasting.TransactionBroadcaster.SendTransactionAsync(SmartTransaction tx) at WalletWasabi.Fluent.ViewModels.Wallets.Send.TransactionPreviewViewModel.SendTransactionAsync(SmartTransaction transaction) at WalletWasabi.Fluent.ViewModels.Wallets.Send.TransactionPreviewViewModel.OnConfirmAsync()

v2.2.1.0 Windows 10

lontivero commented 3 weeks ago

The error makes sense. You have broadcasted a transaction which pays less than the minimum. Did this happen in mainnet? How did you selected the fee rate?

Kruwed commented 3 weeks ago

The error makes sense. You have broadcasted a transaction which pays less than the minimum. Did this happen in mainnet? How did you selected the fee rate?

Yes, it happens on mainnet often when 2 sats/vbyte is selected. I'm not sure why, but mempool.space shows the purge limit is 2.01+ sat/vbyte when there's consistently room in most blocks for transactions between 1.8 sat/vbyte and 2 sat/vbyte:

image

turbolay commented 3 weeks ago

Sorry to ask for a precision but have you changed the fee rate suggested by Wasabi or was it the fee rate suggested?

Kruwed commented 3 weeks ago

Sorry to ask for a precision but have you changed the fee rate suggested by Wasabi or was it the fee rate suggested?

It's likely I adjusted the fee rate lower than the original suggestion of 3 or 4. I'll pay closer attention next time to see what conditions the problem is reproduced under.

turbolay commented 3 weeks ago

I faced this problem with the fee suggested by Wasabi.

lontivero commented 3 weeks ago

We have to use decimals for fee rates instead of integers. I think it can be done backward compatible.