Broadcasting fails with min relay fee not met or mempool min fee not met. The transaction never reached the network, so your coins have not moved.
Why nodes reject it
Every node enforces a minimum relay fee rate in sat/vB. When its mempool is full, it evicts the cheapest transactions and temporarily raises its own minimum, which produces the second message. Nodes expose the current figure through getmempoolinfo, and mempool explorers show it too.
Fix
- Check current fee rates in a mempool explorer (choosing a sat/vB rate).
- Rebuild the transaction above the current mempool minimum, with headroom.
- Enable RBF so you can bump the fee later.
- Broadcast and confirm the hash appears in the mempool.
Estimate the total with the Bitcoin fee calculator.
Sometimes only one broadcasting service rejects the transaction while others accept it, because each node has its own settings and current mempool minimum. Check the hash in an explorer before rebuilding; if every node refuses, the rate is genuinely too low for current conditions.
Wallet fee estimates follow recent blocks and may lag during a spike, so avoid the “economy” rate for payments with a deadline.
Paying a swap order
An order such as BTC to USDT waits one hour for payment. If you may not make it, create a new order first and never pay an expired one. If a late payment confirms anyway, contact support with the order number and hash.
FAQ
Did I lose BTC after this error?
No. The transaction was not accepted, so nothing moved.
What fee rate avoids it?
One above the current mempool minimum, with headroom; check an explorer right before sending.