pull down to refresh

0 sats \ 5 replies \ @gregtonoski OP 31 Jan \ on: Call for nodes reconfiguration: minrelaytxfee=0.00000001 bitcoin_Mining
As a side note, consider also setting incrementalrelayfee=0 instead of the default 3000 in order to relay replacement transactions which fee-rates don't change.
write
preview
this territory is moderated
0 sats \ 4 replies \ @Murch 31 Jan
Imagine every node operator adopts that policy. What sort of consequences would you expect of making it free to send any amount of data to all bitcoin nodes?
reply
0 sats \ 3 replies \ @gregtonoski OP 31 Jan
It wouldn't cause "it free to send any amount of data to all bitcoin nodes". Let's not exaggerate.
reply
0 sats \ 2 replies \ @Murch 31 Jan
Accepting replacements that do not pay a higher feerate than the original means that the sender paid nothing for the relay of additional data.
reply
0 sats \ 1 reply \ @gregtonoski OP 31 Jan
That's not true. It means that the sender paid for the extra bytes at the same fee-rate.
reply
0 sats \ 0 replies \ @Murch 11h
Let’s say I send a 200 vbyte transaction with a fee of 200 sats. Then I get to send a replacement for that transaction that is also 200 vbytes and pays 200 sats.
How much did my second transaction increase the available fees in the mempool? Zilch.
Ergo, the relay of my second transaction was free, and I can repeat that until one of my transactions gets confirmed.
reply