[SECURITY] data carrier transactions (OP_RETURN outputs) should not be relayed by default so that mempools are not overcrowded with non-transfer transactions #27032

issue GregTonoski opened this issue on February 3, 2023

GregTonoski commented at 10:16 AM on February 3, 2023: none

By default, (big e.g. 4MB, full block size) data carrier transactions should not be relayed in order not to fill the default 300MB capacity of mempool with fewer than 100 transactions and give space/priority to standard (non-data carrier, transfer) transactions.

Expected behavior datacarrier parameter is set to false by default (if not set in bitcoin.conf otherwise)

Actual behavior

datacarrier=0 must be set in bitcoin.conf in order not to relay data carrier transactions like for example: 0301e0480b374b32851a9462db29dc19fe830a7f7d7a88b81612b9d42099c0ae

To reproduce

Just run Bitcoin Core without modifying default settings.

System information

Bitcoin Core 24.0.1.
GregTonoski added the label Bug on Feb 3, 2023
MarcoFalke commented at 10:49 AM on February 3, 2023: member

The transaction you are referring to is already non-standard and was not relayed by Bitcoin Core by default. Bitcoin Core policy and policy changes have no effect if miners ignore them.

If you have more bitcoin questions and/or support requests, please use Bitcoin StackExchange or the #bitcoin IRC channel on Libera Chat.
MarcoFalke closed this on Feb 3, 2023
MarcoFalke removed the label Bug on Feb 3, 2023
GregTonoski commented at 10:56 AM on February 3, 2023: none

Thanks for the clarification.
MarcoFalke deleted a comment on Feb 4, 2023
MarcoFalke locked this on Feb 4, 2023

Contributors