Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 809A0C002D for ; Tue, 6 Dec 2022 04:48:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 5A37E81443 for ; Tue, 6 Dec 2022 04:48:22 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 5A37E81443 Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=AAsJ3CTI X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -0.099 X-Spam-Level: X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, PDS_OTHER_BAD_TLD=1.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-ykBD5Mou92 for ; Tue, 6 Dec 2022 04:48:20 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 5F7D781430 Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) by smtp1.osuosl.org (Postfix) with ESMTPS id 5F7D781430 for ; Tue, 6 Dec 2022 04:48:20 +0000 (UTC) Received: by mail-pg1-x530.google.com with SMTP id h33so12345742pgm.9 for ; Mon, 05 Dec 2022 20:48:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NcAhthgaRENJvBpMlOw6JYW/tIsFApJjhm3Ya0ajUdQ=; b=AAsJ3CTIakmSuGN/TVyHLaYRp7pj2E+wUvbXsKqzDEQBD9jsiuyOXsonvJo2TwhehS KHnPduXZEBpE3CIY3Ljx91GJ/2T3U+FiwNbuk7yk42dtygDQapIcHN24jC1+qB8f1kBb Bzm4hFE+w11olFGk0lQRf/7pjMlQKZCE4XGLerhxsXfblVNZ1RcZdCQgl6WG3Y1HSepX zk5OSqcrVZYrfn75dMepz8bNrfhb308QSShpBo5M0Ni7kvq+1m0uJ9tPbEMss/Q5H9XN EylGKbhUJoJJlsM51IGa0g0dIO2DkEOSWLdCjTmDEm/KNsUWIk6xELzPF34QroiZdXCt On4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NcAhthgaRENJvBpMlOw6JYW/tIsFApJjhm3Ya0ajUdQ=; b=NuV8nMXjG/y0AvfgR77dnf3W3e3dPVyegsv2IbDia4WYpxYuN4CRLVyCidWqgVX//4 dZOyrEVWqKaTdJImtrhZkHdESGA2Qtt8cbyGyNiyRjBMOfxm0UysnedXD+vntzDH2SU0 t1D+hcEeLi3VtKotVPi+MLlwv1NKAZLRS+3I8EiIiGuGEUcIEoYxJktdKqYuQro2ZQEL +jYJJbsniSnxjAKkA9Wt5RSNQNIGGgG1hFHPeNpW65Ltsz897zgGxisYBiuWb+zr+TKb b00w8ykh5rbAVeqOABk/rCM6fDF85x24JoRvgsekWQpDEjhboSPWRORXAsUXJ9Kx911t Xe2A== X-Gm-Message-State: ANoB5pnI4chZZt7dqmMer0l0bd6p5V1GHxFkWrDwamd0pgk6PAlQJ/po BJgVu4ZR26/QjLRpI0cyBGo8K6qVEsMjZsSw2nM= X-Google-Smtp-Source: AA0mqf5Z1Dm0+1Ret/oF5Uo1Ysor4paeuUohI3gpDQjy8f7pS8CaEhNTV+RAj3F5ue4fkMXBktF8/bxTJQR/QpY6l38= X-Received: by 2002:a63:3113:0:b0:478:99c3:7cf9 with SMTP id x19-20020a633113000000b0047899c37cf9mr13253288pgx.616.1670302099619; Mon, 05 Dec 2022 20:48:19 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: El_Hoy Date: Tue, 6 Dec 2022 01:48:07 -0300 Message-ID: To: Erik Aronesty , Michael Folkson , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000050c4cf05ef218374" X-Mailman-Approved-At: Tue, 06 Dec 2022 12:13:39 +0000 Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2022 04:48:22 -0000 --00000000000050c4cf05ef218374 Content-Type: text/plain; charset="UTF-8" On Mon, Dec 5, 2022 at 3:58 PM Erik Aronesty via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > note: if it was possible to enforce this, we wouldn't need proof of work > at all. since it isn't possible, proof of work is strictly necessary. > If making empty statements were enough to convince people, we would not need to give good arguments to back our claims. Proof of work is "strictly necessary" to build blocks that are accepted by the consensus rules, that are enforced by the validation nodes that propagate those blocks. If there are multiple valid blocks that are generated close enough and some of them propagate faster than the others, then validation nodes add some economic incentive against certain practices. Miners will obviously choose what validation nodes enforce or they will lose money. On Mon, Dec 5, 2022 at 3:58 PM Michael Folkson via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > > Daniel Lipshitz has been working on BSV apparently [0] so I guess anything > is possible with him.(...) > -- > Michael Folkson You are apparently making an Ad Hominem attack [1] so I guess your comment is not serious. Thanks for the context anyway. [1]: https://en.wikipedia.org/wiki/Ad_hominem --- Eloy > On Mon, Dec 5, 2022 at 9:53 AM Rijndael via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > >> Good morning, >> >> That sounds like a very dangerous mode of operation. You can already hand >> a transaction to a miner privately. I hand a transaction to a miner with >> some reasonable fee, and then I go and broadcast a different transaction >> with a minimal fee that spends the same inputs. The whole network >> (including the miner I handed the tx to) could all be running with a strict >> first-seen mempool policy, but we can still have a situation where the >> miner creates a block with a different transaction from what you see in >> your mempool. If anytime this happens, the nodes running your proposed rule >> drop the block, then anyone can fork those nodes off the network whenever >> they want. >> >> Even outside of adversarial settings, Bitcoin doesn't (and doesn't >> attempt to) promise consistency across mempools. Making a consensus rule >> that enforces mempool consistency is a recipe for (unintended?) >> chainsplits. >> >> - rijndael >> >> >> On 12/5/22 7:20 AM, El_Hoy via bitcoin-dev wrote: >> >> The only option I see against the attack Peter Todd is doing to opt-in >> RBF and 0Conf bitcoin usage is working on a bitcoin core implementation >> that stops propagation of full-rbf replaced blocks. Running multiple of >> such nodes on the network will add a risk to miners that enable full-rbf >> that would work as an incentive against that. >> >> Obviously that would require adding an option on bitcoin core (that is >> not technically but politically difficult to implement as Petter Todd >> already have commit access to the main repository). >> >> That said, a sufficiently incentivized actor (like Daniel Lipshitz or >> Muun wallet developers) could work on a fork and run several nodes with >> such functionality. As far as I understand the percolation model, with 10 >> to 20 nodes running such a rule would create a significant risk for >> full-rbf miners. >> >> Regards. >> >> --- Eloy >> >> >> On Tue, Nov 15, 2022 at 11:43 AM Peter Todd via bitcoin-dev < >> bitcoin-dev@lists.linuxfoundation.org> wrote: >> >>> On Tue, Nov 15, 2022 at 03:36:08PM +1000, Anthony Towns via bitcoin-dev >>> wrote: >>> > On Tue, Nov 08, 2022 at 01:16:13PM -0500, Peter Todd via bitcoin-dev >>> wrote: >>> > > FYI I've gotten a few hundred dollars worth of donations to this >>> effort, and >>> > > have raised the reward to about 0.02 BTC, or $400 USD at current >>> prices. >>> > >>> > Seems like this has been mostly claimed (0.014btc / $235, 9238sat/vb): >>> >>> I'm turning it back on when (if) the mempool settles down. I've got more >>> than >>> enough donations to give another run at it (the majority was donated >>> privately >>> FWIW). There's a risk of the mempool filling up again of course; hard to >>> avoid >>> that. >>> >>> Right now of course it's really easy to double spend with the obvious >>> low-fee/high-fee method as the min relay fee keeps shifting. >>> >>> > >>> https://mempool.space/tx/397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11fc2be29d934d69138c >>> > >>> > The block it was claimed in seems to have been about an hour after the >>> > default mempool filled up: >>> > >>> > https://twitter.com/murchandamus/status/1592274621977477120 >>> > >>> > That block actually seems to have included two >>> > alice.btc.calendar.opentimestamps.org txs, the other paying $7.88 >>> > (309sat/vb): >>> > >>> > >>> https://mempool.space/tx/ba9670109a6551458d5e1e23600c7bf2dc094894abdf59fe7aa020ccfead07cf >>> >>> The second is because I turned down the full-rbf reward to more normal >>> fee >>> levels. There's also another full-rbf double-spend from the Bob >>> calendar, along >>> the same lines: >>> 7e76b351009326a574f3120164dbbe6d85e07e04a7bbdc40f0277fcb008d2cd2 >>> >>> I double-spent the txin of the high fee tx that got mined. But I >>> mistakenly had >>> RBF enabled in that double-spend, so while it propagated initially, I >>> believe >>> it was replaced when something (someone?) rebroadcast the high-fee >>> 397dcb tx. >>> >>> > Timeline (utc) to me looks like: >>> > >>> > - 13:12 - block 763148 is mined: last one that had a min fee < >>> 1.5sat/vb >>> > - 13:33 - >>> f503868c64d454c472859b793f3ee7cdc8f519c64f8b1748d8040cd8ce6dc6e1 >>> > is announced and propogates widely (1.2sat/vb) >>> > - 18:42 - >>> 746daab9bcc331be313818658b4a502bb4f3370a691fd90015fabcd7759e0944 >>> > is announced and propogates widely (1.2sat/vb) >>> > - 21:52 - ba967010 tx is announced and propogates widely, since >>> > conflicting tx 746daab9 has been removed from default >>> > mempools >>> > - 21:53 - murch tweets about default mempool filling up >>> > - 22:03 - 397dcbe4 tx is announced and propogates widely, since >>> > conflicting tx f503868 has already been removed from default >>> > mempools >>> >>> Is that 22:03 time for 397 from your node's logs? It was originally >>> announced >>> hours earlier. From one of my full-rbf nodes: >>> >>> 2022-11-14T14:08:37Z [mempool] replacing tx >>> 764867062b67fea61810c3858d587da83a28290545e882935a32285028084317 with >>> 397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11fc2be29d934d69138c for >>> 0.00468 additional fees, -1 delta bytes >>> >>> > - 22:35 - block 763189 is mined >>> > - 22:39 - block 763190 is mined >>> > - 23:11 - block 763191 is mined >>> > - 23:17 - block 763192 is mined including 397dcbe4 >>> > >>> > miningpool.observer reports both 397dcbe4 and ba967010 as missing in >>> the >>> > first three blocks, and gives similar mempool ages for those txs to >>> what >>> > my logs report: >>> > >>> > >>> https://miningpool.observer/template-and-block/0000000000000000000436aba59d8430061e0e50592215f7f263bfb1073ccac7 >>> > >>> https://miningpool.observer/template-and-block/00000000000000000005600404792bacfd8a164d2fe9843766afb2bfbd937309 >>> > >>> https://miningpool.observer/template-and-block/00000000000000000004a3073f58c9eae40f251ea7aeaeac870daeac4b238fd1 >>> > >>> > That presumably means those pools (AntPool twice and "unknown") are >>> > running with large mempools that didn't kept the earlier 1.2sat/vb txs. >>> >>> To be clear, you think that AntPool and that other exchange is running >>> with a >>> larger than normal max mempool size limit? You mean those miners *did* >>> keep the >>> earlier 1.2sat/vb tx? >>> >>> > The txs were mined by Foundry: >>> > >>> > >>> https://miningpool.observer/template-and-block/00000000000000000001382a226aedac822de80309cca2bf1253b35d4f8144f5 >>> > >>> > This seems to be pretty good evidence that we currently don't have any >>> > significant hashrate mining with fullrbf policies (<0.5% if there was a >>> > high fee replacement available prior to every block having been mined), >>> > despite the bounty having been collected. >>> >>> Oh, we can put much lower bounds on that. I've been running OTS >>> calendars with >>> full-rbf replacements for a few months without clear evidence of a >>> full-rbf >>> replacement. While there was good reason to think some miners were >>> mining >>> full-rbf before a few years back, they probably didn't bother to reapply >>> their >>> patches each upgrade. `mempoolfullrbf=1` is much simpler to use. >>> >>> -- >>> https://petertodd.org 'peter'[:-1]@petertodd.org >>> _______________________________________________ >>> bitcoin-dev mailing list >>> bitcoin-dev@lists.linuxfoundation.org >>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>> >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >> > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --00000000000050c4cf05ef218374 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon, Dec 5, 2022 at 3:58 PM Erik Aronesty via bitcoin-dev <= ;bitcoin-dev@lists= .linuxfoundation.org> wrote:
note: if it was possible=C2=A0to enforce this, we = wouldn't need proof of work at all.=C2=A0 =C2=A0since it isn't poss= ible, proof of work is strictly necessary.

If making empty statements were enough to convince people,= we would not need to give good arguments to back our claims. Proof of work= is "strictly necessary" to build blocks that are accepted by the= consensus rules, that are enforced by the validation nodes that propagate = those blocks. If there are multiple valid blocks that are generated close e= nough and some of them propagate faster than the others, then validation no= des add some economic incentive against certain practices. Miners will obvi= ously choose what validation nodes enforce or they will lose money.<= /span>

On Mon, Dec 5, 2022 at 3:58 PM Micha= el Folkson via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
=

Daniel Lipshitz has been working on BSV apparently [0] so I guess anything is=20 possible with him.(...)
--Michael Folkson
=20

You are apparently making an Ad Hominem a= ttack [1] so I guess your comment is not serious. Thanks for the context an= yway.

--- Eloy

<= /div>

On Mon, Dec 5, 2022 at 9:5= 3 AM Rijndael via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org= > wrote:
=20 =20

Good morning,

That sounds like a very dangerous mode of operation. You can already hand a transaction to a miner privately. I hand a transaction to a miner with some reasonable fee, and then I go and broadcast a different transaction with a minimal fee that spends the same inputs. The whole network (including the miner I handed the tx to) could all be running with a strict first-seen mempool policy, but we can still have a situation where the miner creates a block with a different transaction from what you see in your mempool. If anytime this happens, the nodes running your proposed rule drop the block, then anyone can fork those nodes off the network whenever they want.

Even outside of adversarial settings, Bitcoin doesn't (and doesn't attempt to) promise consistency across mempools. Making a consensus rule that enforces mempool consistency is a recipe for (unintended?) chainsplits.

- rijndael


On 12/5/22 7:20 AM, El_Hoy via bitcoin-dev wrote:
=20
The only option I see against the attack Peter Todd is doing to opt-in RBF and 0Conf bitcoin usage is working on a bitcoin core implementation that stops propagation of full-rbf replaced blocks. Running multiple of such nodes on the network will add a risk to miners that enable full-rbf that would work as an incentive against that.

Obviously that would require adding an option on bitcoin core (that is not technically but politically difficult to implement as Petter Todd already have commit access to the main repository).

That said, a sufficiently incentivized actor (like Daniel Lipshitz or Muun wallet developers) could work on a fork and run several nodes with such functionality. As far as I understand the percolation model, with 10 to 20 nodes running such a rule would create a significant risk for full-rbf miners.

Regards.

---=C2=A0 Eloy


On Tue, Nov 15, 2022 at 11:43 AM Peter Todd via bitcoin-dev <bitcoin-dev@lists.linuxfoundati= on.org> wrote:
On Tue, Nov 15, 2022 at 03:36:08PM +1000, Anthony Towns via bitcoin-dev wrote:
> On Tue, Nov 08, 2022 at 01:16:13PM -0500, Peter Todd via bitcoin-dev wrote:
> > FYI I've gotten a few hundred dollars worth of donations to this effort, and
> > have raised the reward to about 0.02 BTC, or $400 USD at current prices.
>
> Seems like this has been mostly claimed (0.014btc / $235, 9238sat/vb):

I'm turning it back on when (if) the mempool settles down. I've got more than
enough donations to give another run at it (the majority was donated privately
FWIW). There's a risk of the mempool filling up again of course; hard to avoid
that.

Right now of course it's really easy to double spend with the obvious
low-fee/high-fee method as the min relay fee keeps shifting.

> https://mempool.space/tx/397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11= fc2be29d934d69138c
>
> The block it was claimed in seems to have been about an hour after the
> default mempool filled up:
>
> https://twitter.com/murcha= ndamus/status/1592274621977477120
>
> That block actually seems to have included two
> alice.btc.calendar.opentimestamps.org txs, the other paying $7.88
> (309sat/vb):
>
> https://mempool.space/tx/ba9670109a6551458d5e1e23600c7bf2dc094894abdf59= fe7aa020ccfead07cf

The second is because I turned down the full-rbf reward to more normal fee
levels. There's also another full-rbf double-spend from the Bob calendar, along
the same lines: 7e76b351009326a574f3120164dbbe6d85e07e04a7bbdc40f0277fcb008d2cd2<= br>
I double-spent the txin of the high fee tx that got mined. But I mistakenly had
RBF enabled in that double-spend, so while it propagated initially, I believe
it was replaced when something (someone?) rebroadcast the high-fee 397dcb tx.

> Timeline (utc) to me looks like:
>
>=C2=A0 - 13:12 - block 763148 is mined: last one that had a m= in fee < 1.5sat/vb
>=C2=A0 - 13:33 - f503868c64d454c472859b793f3ee7cdc8f519c64f8b1748d8040cd8ce6dc6e1<= br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is announced and pr= opogates widely (1.2sat/vb)
>=C2=A0 - 18:42 - 746daab9bcc331be313818658b4a502bb4f3370a691fd90015fabcd7759e0944<= br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is announced and pr= opogates widely (1.2sat/vb)
>=C2=A0 - 21:52 - ba967010 tx is announced and propogates widely, since
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 conflicting tx 746d= aab9 has been removed from default
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 mempools
>=C2=A0 - 21:53 - murch tweets about default mempool filling u= p
>=C2=A0 - 22:03 - 397dcbe4 tx is announced and propogates widely, since
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 conflicting tx f503= 868 has already been removed from default
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 mempools

Is that 22:03 time for 397 from your node's logs? It was originally announced
hours earlier. From one of my full-rbf nodes:

=C2=A0 =C2=A0 2022-11-14T14:08:37Z [mempool] replacing tx 764867062b67fea61810c3858d587da83a28290545e882935a32285028084317 with 397dcbe4e95ec40616e3dfc4ff8ffa158d2e72020b7d11fc2be29d934d69138c for 0.00468 additional fees, -1 delta bytes

>=C2=A0 - 22:35 - block 763189 is mined
>=C2=A0 - 22:39 - block 763190 is mined
>=C2=A0 - 23:11 - block 763191 is mined
>=C2=A0 - 23:17 - block 763192 is mined including 397dcbe4
>
> miningpool.observer reports both 397dcbe4 and ba967010 as missing in the
> first three blocks, and gives similar mempool ages for those txs to what
> my logs report:
>
>=C2=A0 =C2=A0https://miningpool.observer/template-= and-block/0000000000000000000436aba59d8430061e0e50592215f7f263bfb1073ccac7<= /a>
>=C2=A0 =C2=A0https://miningpool.observer/template-= and-block/00000000000000000005600404792bacfd8a164d2fe9843766afb2bfbd937309<= /a>
>=C2=A0 =C2=A0https://miningpool.observer/template-= and-block/00000000000000000004a3073f58c9eae40f251ea7aeaeac870daeac4b238fd1<= /a>
>
> That presumably means those pools (AntPool twice and "unknown") are
> running with large mempools that didn't kept the earlier 1.2sat/vb txs.

To be clear, you think that AntPool and that other exchange is running with a
larger than normal max mempool size limit? You mean those miners *did* keep the
earlier 1.2sat/vb tx?

> The txs were mined by Foundry:
>
>=C2=A0 =C2=A0https://miningpool.observer/template-= and-block/00000000000000000001382a226aedac822de80309cca2bf1253b35d4f8144f5<= /a>
>
> This seems to be pretty good evidence that we currently don't have any
> significant hashrate mining with fullrbf policies (<0.5% if there was a
> high fee replacement available prior to every block having been mined),
> despite the bounty having been collected.

Oh, we can put much lower bounds on that. I've been running OTS calendars with
full-rbf replacements for a few months without clear evidence of a full-rbf
replacement.=C2=A0 While there was good reason to think some mine= rs were mining
full-rbf before a few years back, they probably didn't bother to reapply their
patches each upgrade. `mempoolfullrbf=3D1` is much simpler to use.

--
https://petertodd.org 'peter'[:-1]@petertodd.org
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundatio= n.org/mailman/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--00000000000050c4cf05ef218374--