Re: Call for reconfiguration of nodes to relay transactions with fee-rates <1 sat/vb

I forget to mention it earlier, but there's at least 3 call to reduce default minrelayfee value in past.
https://github.com/bitcoin/bitcoin/issues/14012
https://gnusha.org/pi/bitcoindev/CAGHFe1BXdTkPZn4r_KTxYoz0sqcMsV830dm5JTTFURxDezBnDQ@mail.gmail.com/
https://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-07-05-19.22.log.html#l-24

Quote from: Greg Tonoski on January 31, 2025, 11:32:20 AM

For spam protection, there is the

Code:

datacarrier=0

which is much more effective. Also, there is the (OP_FALSE OP_IF) filter bugfix implemented in Bitcoin Knots.

If both of them become default on many nodes, spammer will resort to use old technique (using 20-byte public key on address) which is worse on long term due to unprunable UTXO. IMO only making OP_FALSE OP_IF ... OP_ENDIF as non-standard is good compromise.

Quote from: d5000 on January 31, 2025, 12:11:09 PM

And it seems the datacarrier option isn't used enough to deter Ordinals who have grown again a bit in the past 2 months.

Ordinals use Taproot redeem script. So i think you actually meant Runes, which use OP_RETURN.