Author: David A. Harding 2020-04-22 20:28:13
Published on: 2020-04-22T20:28:13+00:00
In a discussion about implementing a reject message with an extension that returns the transaction IDs of any conflicts, Antoine Riard raised concerns that an attacker could create a local conflict in the mempool. However, Dave countered that a mempool is not necessary to send a transaction and suggested opening connections to random Bitcoin nodes directly, which is what a lite client would do. If the pinned transaction is in the mempools of a significant number of Bitcoin nodes, it should take just a few random connections to find one of those nodes, learn about the conflict, and download the pinned transaction. Alternatively, Dave suggested finding another way to poll a significant number of people with mempools, such as BIP35 mempool messages or reusing the payment hash in a bunch of 1 msat probes to LN nodes who opt-in to scanning their bitcoind's mempools for a corresponding preimage.
Updated on: 2023-06-14T00:39:19.081851+00:00