pull down to refresh
Miners are of tertiary importance here (if any). The setting is applied by node runners and affects nodes in the first place.
reply
What use is it to learn about transactions that never get confirmed?
reply
The assumption that a transaction would have never got confirmed is incorrect.
reply
Prove it by showing me a single block whose tail end is composed of transactions paying less than minRelayTxFeerate.
reply
List of them: https://blockchair.com/bitcoin/transactions?s=time(desc)&q=fee(0..98),is_coinbase(false)#f=hash,block_id,input_count,output_count,time,output_total,output_total_usd,fee_usd,fee,is_coinbase
Example of such a transaction: https://blockchair.com/bitcoin/transaction/49a0efc983b19038cb5aa80008d7b9f7690dfb80de84a55f7aabce9d3137f2fa
I am not sure I see the point of doing this while miners apparently do not consider including transactions below the minimum transaction relay feerate of 1 ṩ/vB: we do see a bunch of transactions with feerates below 1 ṩ/vB bumbling around in mempools that accept them, but as far as I am aware, no miner has included any significant amount of them in blocks even if their blocks then were not full.
As long as there are no miners including them, you are just wasting bandwidth.