pull down to refresh

You’d think everyone wants their Bitcoin transaction confirmed as fast as possible, right? But in practice, there’s a growing range of users who are totally fine waiting hours, days—or even indefinitely. And that’s a key reason why we now have a fee-diverse mempool.
Here’s why someone might intentionally send a low-fee tx and just… wait:
  1. It’s not urgent. Batched withdrawals, UTXO consolidations, or low-priority internal txs don’t need fast settlement. Confirmation “eventually” is good enough.
  2. They’re broke. In some places, even 5 sats/vB is a lot. People time txs for low-fee windows or hope for a mempool clear-out.
  3. It’s a test. Some folks send dust amounts just to observe behavior, track fee dynamics, or educate others. Confirmation is optional.
  4. RBF safety net. They start low and replace later if needed. No harm in trying the cheap route first.
  5. Automation or protocol-driven behavior. Some setups broadcast low-fee txs as part of scheduled tasks or automated flows—confirmation just isn’t time-sensitive.
  6. Adversarial tactics. Sometimes it’s meant to stay stuck (e.g. mempool pinning).
When enough of these transactions float around, we get a mempool that includes both 1 sat/vB txs and 100 sat/vB ones. That fee diversity affects relay behavior, compact block reconstruction, miner incentives, and more.
So yeah some people are willing to wait forever. And that changes the dynamics for all of us.
0 sats \ 0 replies \ @senf 19h
Way too many people pay for urgency they don't need. Why pay 100 sat/vbyte for a transaction that's going to sit in your cold storage for the next 10 years? Who cares if it confirms next month instead of next block? My slowest transaction took about nine weeks.
reply