From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 62E7D40D for ; Thu, 30 Jul 2015 04:52:02 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6BA78116 for ; Thu, 30 Jul 2015 04:52:00 +0000 (UTC) Received: by obdeg2 with SMTP id eg2so23025586obd.0 for ; Wed, 29 Jul 2015 21:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=FOo6p9PcgCMN9ZTQjUMxAmn5KnMGk4EKwAU/ronnm6M=; b=hnbDxsKMYwym9+sgKbKsaH3nksGbn8Yy1sZnT1nSMo7gyzmTWHzzDGjX3FFsAOdoC7 dKn97ncFj2vUs5IRX/A3KUpVVOuRtWJhqH/NM49alcuGzAWan8wRKVYryWR4eOkhDaaK 5XAxW3TKALJnv1VRA0lHsYRbeDzN/eeStz4zSL084jcphznKmFP3vv1tLvLBBLiUuWm5 c4xLi6suyZwRgzhjBYO1ucvDVDnhbTBVw8r3Eps4osmvTwHkdibafiGm9nI7knIJmaoD OWAa6H5HZFFrTxOqG2OHZmCMmRQI/PSYCanbjBfBuXcm3P4u9U/hAbw2Cw+G4Ksfcjbk mYZQ== X-Received: by 10.60.134.19 with SMTP id pg19mr45655115oeb.12.1438231919729; Wed, 29 Jul 2015 21:51:59 -0700 (PDT) MIME-Version: 1.0 References: <1B7F00D3-41AE-44BF-818D-EC4EF279DC11@gmail.com> <37D282C2-EF9C-4B8B-91E8-7D613B381824@phauna.org> <55B94FAD.7040205@mail.bihthai.net> In-Reply-To: From: Andrew LeCody Date: Thu, 30 Jul 2015 04:51:50 +0000 Message-ID: To: Adam Back , "Raystonn ." Content-Type: multipart/alternative; boundary=047d7b471dbeae37f9051c1076c4 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn'ttemporary X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2015 04:52:02 -0000 --047d7b471dbeae37f9051c1076c4 Content-Type: text/plain; charset=UTF-8 tl;dr $100 worth of hardware and $1/mo of expenses, should be able to run a full Bitcoin node until 2020 with BIP101-size blocks. ---- I got into Bitcoin in the summer of 2010. I'm not a cryptographer, up until recently my profession has been as a server administrator or systems engineer. I'd like to take a second to address the concern that larger blocks would make it harder to run a full node on limited hardware and would therefore hurt decentralization. I run two nodes today, one on server-grade hardware at a datacenter and another on a mini-ITX Atom (dual core) system at my home. I detailed the operational costs of my home node today on reddit: https://www.reddit.com/r/Bitcoin/comments/3f0h8e/mike_h_shuts_down_eric_ls_attempt_to_rewrite/ctkigpr If I was a new user, wanting to run a full node. The most cost effective way would likely be with a Raspberry Pi 2 and a 2TB external HDD. Total cost about $100, including charger, microSD card, etc. That is less than the cost of a TREZOR hardware wallet. As far as home projects go, not terribly expensive. Next, it will need power. According to the Wikipedia article, the rpi 2 model B uses 3.5 watts of power max. The 2TB external drive will draw about 5 watts at max. That's a total of 8.5 watts or 6.205 Kwh per month. In my area (North Texas) power is about $0.10/Kwh, which means my little node costs $0.62 per month in power. Last, lets look at bandwidth. It's difficult to quantify bandwidth cost in the same way because this is a home connection, mainly because I don't know how to price in the loss of enjoyment if the system impacts my Internet usage to a noticeable degree. Luckily, I have some real world data from my existing home node. Here is the last month: http://imgur.com/YmJwQpN This system averages 120 Kbps in and 544 Kbps out. Note, this data is somewhat skewed, because the system is also used for seeding torrents of various open source projects. The Bitcoin node itself is typically connected to about 20 peers at any given time (maxconnections=20). Subjectively, my wife and I have never noticed any degradation of performance due to my home server using too much bandwidth. I think it's safe to say that I can treat the bandwidth is uses as effectively free, since it's piggybacking on a connection I would be paying for even if I was not running a Bitcoin node. The bandwidth usage of this Bitcoin node could increase significantly, without any noticeable impact. If it did, I could always lower maxconnections back to 8. The only real constraint seems to be hard drive space, as the full blockchain and indexes take up about 50GB of space currently. If BIP101 is implemented, 2TB of storage should be enough for me to continue running my hypothetical $100 node until about 2020. It seems to me that at least for the next 5 years, the "small devices" of today can easily run Bitcoin nodes with BIP101-size blocks, with very little operational cost. If anyone would like more detailed data on my existing nodes, please let me know and I'll attempt to provide it (so long as it doesn't impact my privacy of course). On Wed, Jul 29, 2015 at 10:49 PM Adam Back via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > I dont think people consider other blockchains as a competitive > threat. A PoW-blockchain is a largely singleton data structure for > security reasons (single highest hashrate), it is hard for an > alternative chain to bootstrap or provide meaningful security. > Secondly the world largely lacks expertise to maintain a blockchain to > bitcoin's security level, perhaps you can see a hint of this in the > recently disclosed security vulnerability by Pieter Wuille and Gregory > Maxwell. Calls to this as an argument are not resonating and probably > not helping your argument. Bitcoin has security properties, and a > competing system cant achieve better properties by bypassing security, > any blockchain faces the same fundamental security / decentralisation > limitations. > > Secondly Bitcoin can obviously compete with itself with different > parameters and defacto *does* today. I think it is a safe estimate > that > 99% of Bitcoin transactions right now are happening in Bitcoin > related systems with various degrees of audit, reconciliation, > provable reserves etc. I think we can expect this to continue and > become more secure via more reconciliation, and longer term via > lightning or Bitcoin sidechains with different parameters. It is a > different story to have a single central system (Bitcoin with > parameters changed to the point of centralisation failure) vs having > multiple choices, because some transactions can more easily use > relatively centralised systems (eg micropayments), and more > interestingly the combination of a secure and decentralised layer 1 > plus choices of less decentralised layer 2 options, can be interesting > because the layer 2 is provided cover from attack. There is less to > be gained by attacking relatively centralised layer 2 because any > payments at risk of policy abuse (which is typically a small subset) > can easily switch to layer 1. That in itself makes layer 2 > transactions also less susceptible to policy abuse. Further lightning > it appears from work so far should add significant scale while > retaining trustlessness and a good degree of decentralisation. > > Finally you seem to be focusing on "artificial" limits where that is > not the issue under consideration. The limits are technical and > relating to decentralisation and security. I wont go over them again > as this topic has been covered many times in recent months. Any chain > that tried to go to extreme parameters (very low block intervals, or > very large blocksizes) would have the same decentralisation problems > as Bitcoin would if it did the same thing. There are a number of alt > coins that have failed as a result of poor parameter choices, there > are inherent security limits. > > Adam > > ps Etiquette note for yourself and others: please dont be repetitive > or attempt to be forceful. Many people have spent many years > understanding this very complex system, from my own experience it is > rare indeed to think of an entirely new concept or analysis, that > hasnt' been long considered and put to bed 3 or 4 years ago. > Thoughtful polite and constructive comments are welcome but I > recommend to not start from an assumption that you have a clear and > better insight than the entire technical community, because I have to > say from my own experience that is very rarely the case. It can be > useful to test theories on #bitcoin IRC channel to find out what has > been already concluded, find the references and avoid having to have > that hashed out on this list which is trying to be focussed on > technical solutions. > > > On 29 July 2015 at 16:10, Raystonn . via bitcoin-dev > wrote: > >> Cheapest way to send value? Is this what Bitcoin is trying to do? So > >> all of the smart contract, programmable money, consensus coding and > >> tremendous developer effort is bent to the consumer demand for cheaper > >> fees. Surely thou jests! > > > > > > These other features can be replicated into any alternative blockchain, > > including those with lower fees. In the open-source world of > > cryptocurrency, no feature will remain a value-add for very long after it > > has been identified to be such. Anything adding value will quickly be > > absorbed into competing alternative blockchains. That will leave > economic > > policy as the distinguishing factor. > > > >> ... it is not the case ... that reluctance to concede > >> blocksize is an attempt to constrain capacity. Greg Maxwell thoroughly > >> explained in this thread that the protocol's current state of > >> development relies on blocksize for security and, ultimately, as a > >> means of protecting its degree of decentralization. > > > > > > A slow or lack of increase to maximum transaction rate will cause > pressure > > on fees. Whether this is the desired goal is not relevant. Everyone has > > agreed this will be the outcome. As to a smaller block size being needed > > for additional decentralization, one must simply ask how much we are all > > willing to pay for that additional decentralization. It is likely that > the > > benefit thereto will have to be demonstrated by some power attacking and > > destroying a less decentralized currency before the benefit of this > feature > > is given monetary value by the market. Until then, value will bleed to > the > > network with the least friction, because it will have the greatest > ability > > to grow its network effect. That means the blockchain with adequate > > features and cheapest fees will eventually have the largest market share. > > > > > > -----Original Message----- From: Venzen Khaosan > > Sent: Wednesday, July 29, 2015 3:11 PM > > To: Raystonn . > > Cc: bitcoin-dev@lists.linuxfoundation.org > > Subject: Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure > > isn'ttemporary > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Raystonn, I'm aware that you're addressing your question to Greg > > Maxwell, however a point you keep stating as fact calls for reference: > > > > On 07/30/2015 04:28 AM, Raystonn . via bitcoin-dev wrote: > > [snip] > >> > >> How do you plan to address the bleeding of value from Bitcoin to > >> alternative lower-fee blockchains created by the artificially-high > >> bitcoin transaction fees when users begin looking for the cheapest > >> way to send value? > > > > Cheapest way to send value? Is this what Bitcoin is trying to do? So > > all of the smart contract, programmable money, consensus coding and > > tremendous developer effort is bent to the consumer demand for cheaper > > fees. Surely thou jests! > > > >> Modern economic study has shown that liquidity moves to the > >> location of least friction. > > > > Modern economic study? Can you please provide a link or reference to > > the study you are referring to. > > > > "liquidity moves to the location of least friction" > > > > This sounds like "econo-speak" and makes no sense. The definition of > > Liquidity is the degree to which an asset/security can be bought or > > sold in the market without affecting the price. > > > > That is why bitcoin is said to have low liquidity: buying or selling > > only 100 BTC visibly affects the exchange price. You probably mean > > "people like cheap fees", which is true, but as others have said, > > because of Bitcoin's powerful features, they are willing to pay higher > > fees and wait longer for transactions to execute. > > > > As for your public cross-examination of Greg Maxwell, your case seems > > to be made on the assumption that limiting the size of the blockchain > > is an attempt to artificially raise tx fees, but it is not the case > > (as you and others repeatedly argue) that reluctance to concede > > blocksize is an attempt to constrain capacity. Greg Maxwell thoroughly > > explained in this thread that the protocol's current state of > > development relies on blocksize for security and, ultimately, as a > > means of protecting its degree of decentralization. > > > > Surely, this is an obvious concern even for those who are campaigning > > for the hare-brained ideal of making Bitcoin a "faster, cheaper > > alternative" to visa or paypal? If we lose decentralization, we lose > > the whole thing, right? Incorrect or correct? > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1 > > > > iQEcBAEBAgAGBQJVuU+rAAoJEGwAhlQc8H1m9nkH/00xXJ53H4qvHjPrdNRniwvB > > RXi96QjbnVj/fxU2J2TBPYF1LxJ13avyL58bbaJF7GKqcpoYNZArCKLQyGaZGCTp > > h7Oe/0S+b1QCrvxcVK8Ikeb7a1h9wnhAPf1FvAWoJ1cFGx/qGHetKqx1dQTWkVWz > > Mp17vjaofmp2OhBzh0Smj+wV9hXn9w9giZKc6UGvC0Qc7Rf3GL/YVJzM2CZNvlLS > > YhQSqnnqduugYztqLV/NvNExF41zC2IMyNmA41q46v/nh8stNSIcJleD39csNMfx > > BXjrlnPfZ+JI4RhiH3I0qjOYWPtBH9od788DY509EOn3MT4vU+EVcQaxyuFqZyw= > > =lQvy > > -----END PGP SIGNATURE----- > > _______________________________________________ > > 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 > --047d7b471dbeae37f9051c1076c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
tl;dr
$100 worth of hardware and $1/mo= of expenses, should be able to run a full Bitcoin node until 2020 with BIP= 101-size blocks.

----

I got into Bitcoin in the summer of 2010. I'= ;m not a cryptographer, up until recently my profession has been as a serve= r administrator or systems engineer.


I'd like to take a second to address the concern = that larger blocks would make it harder to run a full node on limited hardw= are and would therefore hurt decentralization. I run two nodes today, one o= n server-grade hardware at a datacenter and another on a mini-ITX Atom (dua= l core) system at my home.

I detailed the operational costs of= my home node today on reddit:

If I was a= new user, wanting to run a full node. The most cost effective way would li= kely be with a=C2=A0Raspberry Pi 2 and a 2TB external HDD. Total cost about= $100, including charger, microSD card, etc. That is less than the cost of = a TREZOR hardware wallet. As far as home projects go, not terribly expensiv= e.

Next, it will need power. According to the Wiki= pedia article, the rpi 2 model B uses 3.5 watts of power max. The 2TB exter= nal drive will draw about 5 watts at max. That's a total of 8.5 watts o= r 6.205 Kwh per month. In my area (North Texas) power is about $0.10/Kwh, w= hich means my little node costs $0.62 per month in power.

Last, lets look at bandwidth. It's difficult to quantify bandwi= dth cost in the same way because this is a home connection, mainly because = I don't know how to price in the loss of enjoyment if the system impact= s my Internet usage to a noticeable degree. Luckily, I have some real world= data from my existing home node. Here is the last month:
This system averages 120 Kbps in and 544 Kbps out. Note, this = data is somewhat skewed, because the system is also used for seeding torren= ts of various open source projects. The Bitcoin node itself is typically co= nnected to about 20 peers at any given time (maxconnections=3D20).

Subjectively, my wife and I have never noticed any degrada= tion of performance due to my home server using too much bandwidth. I think= it's safe to say that I can treat the bandwidth is uses as effectively= free, since it's piggybacking on a connection I would be paying for ev= en if I was not running a Bitcoin node. The bandwidth usage of this Bitcoin= node could increase significantly, without any noticeable impact. If it di= d, I could always lower maxconnections back to 8.

= The only real constraint seems to be hard drive space, as the full blockcha= in and indexes take up about 50GB of space currently. If BIP101 is implemen= ted, 2TB of storage should be enough for me to continue running my hypothet= ical $100 node until about 2020.

It seems to me th= at at least for the next 5 years, the "small devices" of today ca= n easily run Bitcoin nodes with BIP101-size blocks, with very little operat= ional cost.

If anyone would like more detailed dat= a on my existing nodes, please let me know and I'll attempt to provide = it (so long as it doesn't impact my privacy of course).

On Wed, Jul 29, 2015 at 10:49 PM Adam= Back via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wro= te:
I dont think people consider ot= her blockchains as a competitive
threat.=C2=A0 A PoW-blockchain is a largely singleton data structure for security reasons (single highest hashrate), it is hard for an
alternative chain to bootstrap or provide meaningful security.
Secondly the world largely lacks expertise to maintain a blockchain to
bitcoin's security level, perhaps you can see a hint of this in the
recently disclosed security vulnerability by Pieter Wuille and Gregory
Maxwell.=C2=A0 Calls to this as an argument are not resonating and probably=
not helping your argument.=C2=A0 Bitcoin has security properties, and a
competing system cant achieve better properties by bypassing security,
any blockchain faces the same fundamental security / decentralisation
limitations.

Secondly Bitcoin can obviously compete with itself with different
parameters and defacto *does* today.=C2=A0 I think it is a safe estimate that > 99% of Bitcoin transactions right now are happening in Bitcoin related systems with various degrees of audit, reconciliation,
provable reserves etc.=C2=A0 I think we can expect this to continue and
become more secure via more reconciliation, and longer term via
lightning or Bitcoin sidechains with different parameters.=C2=A0 It is a different story to have a single central system (Bitcoin with
parameters changed to the point of centralisation failure) vs having
multiple choices, because some transactions can more easily use
relatively centralised systems (eg micropayments), and more
interestingly the combination of a secure and decentralised layer 1
plus choices of less decentralised layer 2 options, can be interesting
because the layer 2 is provided cover from attack.=C2=A0 There is less to be gained by attacking relatively centralised layer 2 because any
payments at risk of policy abuse (which is typically a small subset)
can easily switch to layer 1.=C2=A0 That in itself makes layer 2
transactions also less susceptible to policy abuse.=C2=A0 Further lightning=
it appears from work so far should add significant scale while
retaining trustlessness and a good degree of decentralisation.

Finally you seem to be focusing on "artificial" limits where that= is
not the issue under consideration.=C2=A0 The limits are technical and
relating to decentralisation and security.=C2=A0 I wont go over them again<= br> as this topic has been covered many times in recent months.=C2=A0 Any chain=
that tried to go to extreme parameters (very low block intervals, or
very large blocksizes) would have the same decentralisation problems
as Bitcoin would if it did the same thing.=C2=A0 There are a number of alt<= br> coins that have failed as a result of poor parameter choices, there
are inherent security limits.

Adam

ps Etiquette note for yourself and others: please dont be repetitive
or attempt to be forceful.=C2=A0 Many people have spent many years
understanding this very complex system, from my own experience it is
rare indeed to think of an entirely new concept or analysis, that
hasnt' been long considered and put to bed 3 or 4 years ago.
Thoughtful polite and constructive comments are welcome but I
recommend to not start from an assumption that you have a clear and
better insight than the entire technical community, because I have to
say from my own experience that is very rarely the case.=C2=A0 It can be useful to test theories on #bitcoin IRC channel to find out what has
been already concluded, find the references and avoid having to have
that hashed out on this list which is trying to be focussed on
technical solutions.


On 29 July 2015 at 16:10, Raystonn . via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>> Cheapest way to send value? Is this what Bitcoin is trying to do? = So
>> all of the smart contract, programmable money, consensus coding an= d
>> tremendous developer effort is bent to the consumer demand for che= aper
>> fees. Surely thou jests!
>
>
> These other features can be replicated into any alternative blockchain= ,
> including those with lower fees.=C2=A0 In the open-source world of
> cryptocurrency, no feature will remain a value-add for very long after= it
> has been identified to be such.=C2=A0 Anything adding value will quick= ly be
> absorbed into competing alternative blockchains.=C2=A0 That will leave= economic
> policy as the distinguishing factor.
>
>> ... it is not the case ... that reluctance to concede
>> blocksize is an attempt to constrain capacity. Greg Maxwell thorou= ghly
>> explained in this thread that the protocol's current state of<= br> >> development relies on=C2=A0 blocksize for security and, ultimately= , as a
>> means of protecting its degree of decentralization.
>
>
> A slow or lack of increase to maximum transaction rate will cause pres= sure
> on fees.=C2=A0 Whether this is the desired goal is not relevant.=C2=A0= Everyone has
> agreed this will be the outcome.=C2=A0 As to a smaller block size bein= g needed
> for additional decentralization, one must simply ask how much we are a= ll
> willing to pay for that additional decentralization.=C2=A0 It is likel= y that the
> benefit thereto will have to be demonstrated by some power attacking a= nd
> destroying a less decentralized currency before the benefit of this fe= ature
> is given monetary value by the market.=C2=A0 Until then, value will bl= eed to the
> network with the least friction, because it will have the greatest abi= lity
> to grow its network effect.=C2=A0 That means the blockchain with adequ= ate
> features and cheapest fees will eventually have the largest market sha= re.
>
>
> -----Original Message----- From: Venzen Khaosan
> Sent: Wednesday, July 29, 2015 3:11 PM
> To: Raystonn .
> Cc: bitcoin-dev@lists.linuxfoundation.org
> Subject: Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measu= re
> isn'ttemporary
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Raystonn, I'm aware that you're addressing your question to Gr= eg
> Maxwell, however a point you keep stating as fact calls for reference:=
>
> On 07/30/2015 04:28 AM, Raystonn . via bitcoin-dev wrote:
> [snip]
>>
>> How do you plan to address the bleeding of value from Bitcoin to >> alternative lower-fee blockchains created by the artificially-high=
>> bitcoin transaction fees when users begin looking for the cheapest=
>> way to send value?
>
> Cheapest way to send value? Is this what Bitcoin is trying to do? So > all of the smart contract, programmable money, consensus coding and > tremendous developer effort is bent to the consumer demand for cheaper=
> fees. Surely thou jests!
>
>> Modern economic study has shown that liquidity moves to the
>> location of least friction.
>
> Modern economic study? Can you please provide a link or reference to > the study you are referring to.
>
> "liquidity moves to the location of least friction"
>
> This sounds like "econo-speak" and makes no sense. The defin= ition of
> Liquidity is the degree to which an asset/security can be bought or > sold in the market without affecting the price.
>
> That is why bitcoin is said to have low liquidity: buying or selling > only 100 BTC visibly affects the exchange price. You probably mean
> "people like cheap fees", which is true, but as others have = said,
> because of Bitcoin's powerful features, they are willing to pay hi= gher
> fees and wait longer for transactions to execute.
>
> As for your public cross-examination of Greg Maxwell, your case seems<= br> > to=C2=A0 be made on the assumption that limiting the size of the block= chain
> is an attempt to artificially raise tx fees, but it is not the case > (as you and others repeatedly argue) that reluctance to concede
> blocksize is an attempt to constrain capacity. Greg Maxwell thoroughly=
> explained in this thread that the protocol's current state of
> development relies on=C2=A0 blocksize for security and, ultimately, as= a
> means of protecting its degree of decentralization.
>
> Surely, this is an obvious concern even for those who are campaigning<= br> > for the hare-brained ideal of making Bitcoin a "faster, cheaper > alternative" to visa or paypal? If we lose decentralization, we l= ose
> the whole thing, right? Incorrect or correct?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJVuU+rAAoJEGwAhlQc8H1m9nkH/00xXJ53H4qvHjPrdNRniwvB
> RXi96QjbnVj/fxU2J2TBPYF1LxJ13avyL58bbaJF7GKqcpoYNZArCKLQyGaZGCTp
> h7Oe/0S+b1QCrvxcVK8Ikeb7a1h9wnhAPf1FvAWoJ1cFGx/qGHetKqx1dQTWkVWz
> Mp17vjaofmp2OhBzh0Smj+wV9hXn9w9giZKc6UGvC0Qc7Rf3GL/YVJzM2CZNvlLS
> YhQSqnnqduugYztqLV/NvNExF41zC2IMyNmA41q46v/nh8stNSIcJleD39csNMfx
> BXjrlnPfZ+JI4RhiH3I0qjOYWPtBH9od788DY509EOn3MT4vU+EVcQaxyuFqZyw=3D
> =3DlQvy
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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/mail= man/listinfo/bitcoin-dev
--047d7b471dbeae37f9051c1076c4--