From 50cede3f5a4d4fbfbb7c420b94e661a6a159bced Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Tue, 26 Mar 2019 16:40:58 -0400 Subject: [mempool] Allow one extra single-ancestor transaction per package This implements the proposed policy change from [1], which allows certain classes of contract protocols involving revocation punishments to use CPFP. Note that some such use-cases may still want some form of one-deep package relay, though even this alone may greatly simplify some lightning fee negotiation. [1] https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-November/016518.html --- src/validation.h | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/validation.h') diff --git a/src/validation.h b/src/validation.h index 638229952d..a72ed3c580 100644 --- a/src/validation.h +++ b/src/validation.h @@ -63,6 +63,12 @@ static const unsigned int DEFAULT_ANCESTOR_SIZE_LIMIT = 101; static const unsigned int DEFAULT_DESCENDANT_LIMIT = 25; /** Default for -limitdescendantsize, maximum kilobytes of in-mempool descendants */ static const unsigned int DEFAULT_DESCENDANT_SIZE_LIMIT = 101; +/** + * An extra transaction can be added to a package, as long as it only has one + * ancestor and is no larger than this. Not really any reason to make this + * configurable as it doesn't materially change DoS parameters. + */ +static const unsigned int EXTRA_DESCENDANT_TX_SIZE_LIMIT = 10000; /** Default for -mempoolexpiry, expiration time for mempool transactions in hours */ static const unsigned int DEFAULT_MEMPOOL_EXPIRY = 336; /** Maximum kilobytes for transactions to store for processing during reorg */ -- cgit v1.2.3