[bitcoin-dev] Bitcoin Contracting Primitives WG 1st Meeting, Tuesday 15 Nov. 18:00 UTC

2022-10-31 Thread Antoine Riard via bitcoin-dev
Hi list, After I have been asked offline the exact date when those meetings were actually starting, I'm proposing Tuesday 15th November at 18:00 UTC, i.e 2 weeks from now. Thinking about a monthly frequency for now (from my experience attending dlcspecs/lighnting specs meetings/core dev meetings

Re: [bitcoin-dev] On mempool policy consistency

2022-10-31 Thread Peter Todd via bitcoin-dev
On Mon, Oct 31, 2022 at 06:21:08PM +0100, yancy via bitcoin-dev wrote: > > Protocol Devs, > > After reading through this email thread and BIP125, I'm curious if non-rbf > nodes will relay full-rbf transactions and vice versa. That is to say, if > only one non-rbf node exists on the network,

Re: [bitcoin-dev] On mempool policy consistency

2022-10-31 Thread yancy via bitcoin-dev
Protocol Devs, After reading through this email thread and BIP125, I'm curious if non-rbf nodes will relay full-rbf transactions and vice versa. That is to say, if only one non-rbf node exists on the network, however, every other node implements full-rbf, will the transaction still be

Re: [bitcoin-dev] On mempool policy consistency

2022-10-31 Thread Greg Sanders via bitcoin-dev
Thanks for your full thoughts Suhas, The idea of V3 is that we're currently leaving fees on the table by allowing use-cases to be pinned, not that we like Lightning and we think miners should stop being profit maximizing somehow to enable safer/better layer 2 systems. If someone wants to bump

Re: [bitcoin-dev] On mempool policy consistency

2022-10-31 Thread Suhas Daftuar via bitcoin-dev
AJ, Thanks for the thoughtful post. I think your observations about how we view mempool policy in the Bitcoin Core project, and how that seems to be changing in the discussions around `-mempoolfullrbf`, are on-point and provide a helpful baseline for considering future policy changes. For a long