Author: Greg Sanders 2022-10-19 13:22:08
Published on: 2022-10-19T13:22:08+00:00
A group of individuals were discussing V3 transactions and pinning attacks. Greg Sanders suggested a solution called "Ephemeral Anchors", which involves marking an output as an anchor that must be spent within a V3 package with a 0-fee parent transaction. This method simplifies mempool reasoning and allows anyone to bump the transaction without any transaction key material. The Lightning Carve-out is superseded by this logic, allowing for robust multi-party fee bumping. However, there are concerns about whether allowing non-zero value in ephemeral outputs would open up MEV concerns and how SIGHASH_GROUP like constructs would work.Gloria proposed a solution for ln-penalty, reducing the number of anchors per commitment transaction to 1 and each version of the commitment transaction has a unique party's key on it worked around the problem. Antoine Riard suggested that package relay should be included in addition to package RBF, otherwise if Lightning transactions are still relayed one by one, the version of the commitment transaction won't replace the counterparties's commitments sleeping in network mempools. If non-zero value is allowed in ephemeral outputs, it could modify the incentives games of the channels counterparties.
Updated on: 2023-06-16T01:57:38.176299+00:00