From dave at dtrt.org Wed Apr 22 20:28:13 2020 From: dave at dtrt.org (David A. Harding) Date: Wed, 22 Apr 2020 16:28:13 -0400 Subject: [Lightning-dev] [bitcoin-dev] RBF Pinning with Counterparties and Competing Interest In-Reply-To: References: <20200422182454.3y3foxxhiovokovp@ganymede> Message-ID: <20200422202813.oadvvn4j3oe7geq6@ganymede> On Wed, Apr 22, 2020 at 03:03:29PM -0400, Antoine Riard wrote: > > In that case, would it be worth re-implementing something like a BIP61 > reject message but with an extension that returns the txids of any > conflicts? > > That's an interesting idea, but an attacker can create a local conflict in > your mempool You don't need a mempool to send a transaction. You can just open connections to random Bitcoin nodes directly and try sending your transaction. That's what a lite client is going to do anyway. If the pinned transaction is in the mempools of a significant number of Bitcoin nodes, then it should take just a few random connections to find one of those nodes, learn about the conflict, and download the pinned transaction. If that's not acceptable, you could find some other way to poll a significant number of people with mempools, e.g. 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. -Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: