From d33cdbd0777700f4fc488d54b90a8795d2c33639 Mon Sep 17 00:00:00 2001 From: Greg Sanders Date: Fri, 5 Jan 2024 12:56:42 -0500 Subject: [PATCH] give cluster mempool rationale --- bip-ephemeralanchors.mediawiki | 1 + 1 file changed, 1 insertion(+) diff --git a/bip-ephemeralanchors.mediawiki b/bip-ephemeralanchors.mediawiki index bd0187acb7..7ae519307b 100644 --- a/bip-ephemeralanchors.mediawiki +++ b/bip-ephemeralanchors.mediawiki @@ -50,6 +50,7 @@ desired: * It does not solve many-party contract pinning, such as a three-party payment channel * It does not solve batched payments pinning if the service is unable to double-spend its own inputs. For example, an exchange may require strict separation between client funds and fee funds for security reasons. * In two-party smart contracts, all but two outputs must be relative-timelocked, which interferes with tooling such as [https://bitcoin.sipa.be/miniscript/ Miniscript] and smart contract composition such as making an output that is directly deposited into another smart contract or any wallet with standard address types. +* Perhaps most importantly, it is incompatible with future improvements to the mempool, particularly [https://github.com/bitcoin/bitcoin/issues/27677 Cluster Mempools]. This proposal gives a standard way to create a 0-fee "parent" transaction which can be fee-bumped by any wallet by introducing a special 0-value anchor output