path: root/77/62162e6bf87c1b7b6e2283c375613b1dc42650

Delivery-date: Thu, 19 Dec 2024 11:48:17 -0800
Received: from mail-qk1-f192.google.com ([209.85.222.192])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBDAKTXPD5QCRB6HQSG5QMGQEGFR4EQQ@googlegroups.com>)
	id 1tOMVM-0005EC-UD
	for bitcoindev@gnusha.org; Thu, 19 Dec 2024 11:48:17 -0800
Received: by mail-qk1-f192.google.com with SMTP id af79cd13be357-7b7477f005esf203900585a.0
        for <bitcoindev@gnusha.org>; Thu, 19 Dec 2024 11:48:16 -0800 (PST)
ARC-Seal: i=2; a=rsa-sha256; t=1734637690; cv=pass;
        d=google.com; s=arc-20240605;
        b=hmNH2LLiUj0DLCsLuxtOBYNwm0rLnT2YpQZ0iMbwhbWyaRNWYOeqI+CX5S21aTlLXj
         J2q3nMSCbajagyOaWg6bR3ROuIqusQTMudRAoI3ThGu4EKr06swlNSqCJ8UldE37+bUH
         G6kFmBMjBAzyTQkWo41+H0157mSG90Zs85Kjh+9kZKvz1MbXReZ/WIv8mkybCNQ8GwjT
         1JgTWyzSBA0hOQ4M2gxMflG2FSBqZs5tXbj7H8OJz8SG2mH+nBX2wQ+p2ayIoJdkkQrw
         bFesw1ooFk68YbPUp2pp3NHudjULsOo1j1d2p7IFBCSqEoQ1kWrUByzIkusFDv0jIFM/
         moOg==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from
         :in-reply-to:references:mime-version:sender:dkim-signature
         :dkim-signature;
        bh=DvXFTC1VUURiUjZrJHmKO5gfxNWWzqrfnoJNe5z/MHs=;
        fh=hr08B3SuB+tA0H7T1Qcz+yOqAjmQ0aHC8VUFmlaf7GE=;
        b=IYANLwGzlLar4wbDXN7rx0hhNBmQITQBGFrSVqSAmXS8VMbbIJbgvU0tq/PDKyipMx
         aqvhBjQIlfB85xY7ee5stVzPwGS7F88PAjBdvXWWE9FXjzNzXPv858zBkPET5r4sWboi
         6lkHocI1kQfrHVjd9Obi0cOtc4XagGL0EnDnd95o5ty4hhLwAYNM0JM+TxdytFyXo8CY
         NwOxf4d+MqS8VUBvut/4U1VAoQJmXRlKmfewpHl9nNPDZS0wzhNWGgmuKXmm2f0Yt1JA
         RYWB3tqTOBSsLgtWUJDghPnIO4ikfQOcWqKl0tu0615zZYuV4aovoVzZLCvAP8xlyDuT
         DzjQ==;
        darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20230601 header.b="HSt1Jz/v";
       spf=pass (google.com: domain of mcassano@gmail.com designates 2a00:1450:4864:20::331 as permitted sender) smtp.mailfrom=mcassano@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
       dara=pass header.i=@googlegroups.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1734637690; x=1735242490; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:sender:from:to:cc:subject:date:message-id
         :reply-to;
        bh=DvXFTC1VUURiUjZrJHmKO5gfxNWWzqrfnoJNe5z/MHs=;
        b=LxjwUjYsnXCejS3Z/TPNW9kEhUtHxW9KTupreZq7Oaby/KHXi6thTbbakRc3BIm9Mr
         3O/n/YNhZz5H7XQEX95lXGlk5CbyJ0pCKkiXSUeLIFIH8TPRjnDgPHACnfhXcyN2ASFQ
         6w3i5sER+t0h5wFJRzTRR1IcXLUy78SDZrcK8zyTzDTBRNnfP3OhhBSeXTUdrjIpsD3r
         w6rUg6a8gKpVtIZw79/7PPBAttKFNMRqBKMuURHYUoPGrf3DAF9tG/JoMHNCafBDjgvJ
         TWF+/j3Rv1owVPPEv1QNxmfGcFYbSnq6CuqykzhZLgOkQWaGHuP0uYmAvgEVz/mb649G
         t6HQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1734637690; x=1735242490; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:from:to:cc:subject:date:message-id:reply-to;
        bh=DvXFTC1VUURiUjZrJHmKO5gfxNWWzqrfnoJNe5z/MHs=;
        b=Bg5xQbZxMFyTMhUC8GWFKKfXg5inIPVazmx1YNUPNTRadY3SROV5gswus0pjEiEx6p
         d9swLCaNNVy6kCIdWryvL2gxz2NBwZpSSokPlo4deNy5obGhjQWZ251sjOVUJmSieVgc
         QHXTFUux6o2hZC/1FLf7zk9QlUUiFdxRJDRR7Ad8l4/xqBCgGY8yeL5u5aym2cyrZycp
         ztNvQkD+spubeulCq6cH1BZ6YTBB7XyAe91/AxXGjNNUCjfsFf1/9P4GzezpCtibCtWx
         k1q6OvwXjnuhQ5ceWDleGudZCouqjZLmlcD6QUnOmhcOPCoGTbLb87GJO7od3N6yCUG1
         WIlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1734637690; x=1735242490;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:x-beenthere:x-gm-message-state:sender:from
         :to:cc:subject:date:message-id:reply-to;
        bh=DvXFTC1VUURiUjZrJHmKO5gfxNWWzqrfnoJNe5z/MHs=;
        b=uybjslu7ZcwRuaqLrjvFTdRbFY7ISu88S2XH6zsy8Z60gXIayyMndXyBi6e8p2QfnD
         VuW2mWR0y1GqkX2762rMD7llq/tEgaOsMq+fBXMGQecvFXM/1w0C7RKgjezhcBO+EJV7
         fHVKuhvqw2UEthoRT3Zb7SZ8J66hQ7DVJ8+StH0SRx++O4rJRRHYrFauPZubCtiV/dj0
         fNtCUYpiGitNpbJhdHUi20xDfAS1ATWf85XDP4iUt6yLZN0ueXaTTt+Xy+3G40nUlB91
         dM4UxKhaj+5o8SrbcKEp2+7YhaDuYMmd5R+CcCDBeA+PVIaVm6xeHCKIa9WiQRT8ELw0
         xGkA==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCWkfVI48sTWgBLeGvKY0fa7h0cESTTvcvxXmVxJQkbZds/1gFcFKVLhUZAroJOgYcn8nQDPEZwF3K/i@gnusha.org
X-Gm-Message-State: AOJu0YxbGBsSm3qr1lkVgX4PEC4lWHZmElZd1SoaVRvczjgfYp71aGTI
	KX4ikxX4WsQ5iUlgKDr42VezljDzlFgYMNZhmPTRDTgxwh9SdHTx
X-Google-Smtp-Source: AGHT+IGp3dqO7hF4al9iaplwQpyXsdvSZaYepPQdrucYFlFZXwQ+rOxkz644NdMVNEzJ+27JwROcRw==
X-Received: by 2002:a05:620a:600e:b0:7b6:6756:eefc with SMTP id af79cd13be357-7b9ba7a4a5amr20853185a.27.1734637690378;
        Thu, 19 Dec 2024 11:48:10 -0800 (PST)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:ac8:4f4b:0:b0:467:6771:ac55 with SMTP id d75a77b69052e-46a3b17a2a6ls19212411cf.1.-pod-prod-06-us;
 Thu, 19 Dec 2024 11:48:07 -0800 (PST)
X-Received: by 2002:a05:620a:4692:b0:7b1:1cb8:1a56 with SMTP id af79cd13be357-7b9ba735fd3mr24112985a.14.1734637687718;
        Thu, 19 Dec 2024 11:48:07 -0800 (PST)
Received: by 2002:a05:620a:470b:b0:7b6:dcc4:6708 with SMTP id af79cd13be357-7b9ab1e40f7ms85a;
        Thu, 19 Dec 2024 09:25:48 -0800 (PST)
X-Received: by 2002:a05:6000:1ac6:b0:385:effc:a279 with SMTP id ffacd0b85a97d-388e4da6fabmr5813575f8f.58.1734629146542;
        Thu, 19 Dec 2024 09:25:46 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1734629146; cv=none;
        d=google.com; s=arc-20240605;
        b=T+XWT7dxXBjKraIDA9K9W89ECDsmSyPsc4rpnUadM3QE+okzaz5upU7GtMUavzols3
         cazKN1gGyi6mhvnmK+59FNw5P4TwKRyIJzGW6y8tt3rmfT8H4RL91rwb/38rIjGLow72
         nOQBRq8sVLkF3puBbeG//RWe3kKbBxhuV5w9vYMUZY+n9bhXrIrajygpaKffQ9Q2NGGL
         Y+LUTkkv8Ju9PUN16GH7Z/OtOuRejwiQ0fDCV0HULQKu3oNA3XFX3iN+bIfIzCHjIWXN
         /4g+58zNgtCu+fr5pH6/fryaFXWZKW/0sT6Wp/MxrauDHfuZVSDL0DtAeU6zaRHo6t92
         v0Lw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:dkim-signature;
        bh=oIqu4yRRx3O15fmgiyIShASuY4DhA4gqV+pkLFnA5I4=;
        fh=Tmyfg32jD7VgMpSBD0ClGwkfxFimM6L5RkiIl0E1f2Y=;
        b=EEF6il1jRRULOMjYRfGZ7CEIdLOqi9T1eaMrgCIAk1+ogfNL1krwCDLr/7RmI+6vNb
         wVWudJMLC4H05tGly1yJsQyq1PznNszw9UkO9wTI36IA3UUV8cgbVNbK0PRnL9T7pYmy
         IK2TcAeTmAwblNPJvQqkxdKmvuTw6E33KHd+DQRQVsrx5toZo1UHs3tYXojUtzYQ/Jc8
         jUyMNTYMeyiNLO/aG1bHJ9JfQ6Ix5dj4qJ3dXOG5r/GKbdJYmQl1nzufVal3A3T1hlV3
         PxGyUkgJXreVbAef+m2qXIJ4gWWDLZ6CRh7AkPWu9anLOrfzoh5I426yAJEYYTlVl3i8
         M0/A==;
        dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20230601 header.b="HSt1Jz/v";
       spf=pass (google.com: domain of mcassano@gmail.com designates 2a00:1450:4864:20::331 as permitted sender) smtp.mailfrom=mcassano@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
       dara=pass header.i=@googlegroups.com
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com. [2a00:1450:4864:20::331])
        by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-4364a376b54si4956585e9.0.2024.12.19.09.25.46
        for <bitcoindev@googlegroups.com>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Thu, 19 Dec 2024 09:25:46 -0800 (PST)
Received-SPF: pass (google.com: domain of mcassano@gmail.com designates 2a00:1450:4864:20::331 as permitted sender) client-ip=2a00:1450:4864:20::331;
Received: by mail-wm1-x331.google.com with SMTP id 5b1f17b1804b1-4364a37a1d7so10829125e9.3
        for <bitcoindev@googlegroups.com>; Thu, 19 Dec 2024 09:25:46 -0800 (PST)
X-Gm-Gg: ASbGncu5ysASgK0ufGBJ06jQZS8V/+0+wp89emol18knQwGwnhK9sP5FIFR2IvmD2T8
	tRgp8NrDiSOURCkeM0PlXTsQBUlyD0lfwNcv3
X-Received: by 2002:a05:600c:4f44:b0:435:9ed3:5698 with SMTP id
 5b1f17b1804b1-43655400035mr71264575e9.24.1734629145655; Thu, 19 Dec 2024
 09:25:45 -0800 (PST)
MIME-Version: 1.0
References: <e86753f2-1c79-484d-8f61-47a5dd148b45n@googlegroups.com>
In-Reply-To: <e86753f2-1c79-484d-8f61-47a5dd148b45n@googlegroups.com>
From: Michael Cassano <mcassano@gmail.com>
Date: Thu, 19 Dec 2024 10:25:34 -0700
Message-ID: <CAAg3Je1hVqcR_DGZEXhaeO7CEU1k-SLx_1QX=XmnS2Bn11joXw@mail.gmail.com>
Subject: Re: [bitcoindev] Double Exponential Hash Rate Growth and Difficulty Adjustment
To: Anders <blabline@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="0000000000000b41e90629a2d261"
X-Original-Sender: mcassano@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com;       dkim=pass
 header.i=@gmail.com header.s=20230601 header.b="HSt1Jz/v";       spf=pass
 (google.com: domain of mcassano@gmail.com designates 2a00:1450:4864:20::331
 as permitted sender) smtp.mailfrom=mcassano@gmail.com;       dmarc=pass
 (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;       dara=pass header.i=@googlegroups.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.5 (/)

--0000000000000b41e90629a2d261
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Anders,

Thank you for the question.

A solution is to keep miners on SHA256 (instead of switching to a hash that
allows for a larger range of difficulty targets) but to require them to
hash again to achieve a secondary difficulty target.

At max target difficulty miners would publish blocks when SHA256(header) =
=3D=3D
1 and when SHA256(SHA256(header)) <=3D secondary_target where
secondary_target adjusts up and down if primary_target is 1 (where
primary_target represents today's target difficulty).

Nodes then verify blocks by checking that SHA256(header) is =3D=3D 1 and th=
at
SHA256(SHA256(header) is less than secondary_target.

Best regards,
Mike

On Wed, Dec 18, 2024 at 6:21=E2=80=AFPM Anders <blabline@gmail.com> wrote:

> Hi,
>
> I've been looking into the long-term implications of the Bitcoin hash rat=
e
> growth for the difficulty adjustment mechanism, and I'd like to discuss a
> potential concern related to double exponential growth.
>
> As we know, the difficulty adjustment mechanism aims to maintain an
> average block time of approximately 10 minutes by adjusting the target
> value every 2016 blocks. This target value, when represented in
> hexadecimal, effectively determines the number of leading zeros required
> for a valid block hash.
>
> The Bitcoin hash rate has historically shown a strong exponential growth
> trend, driven by advancements in ASIC technology. However, some
> observations suggest that this growth might be accelerating, potentially
> exhibiting double exponential growth (meaning the rate of exponential
> growth is itself increasing exponentially).
>
> If the hash rate were to continue to grow at a double exponential rate,
> the difficulty would need to increase at an accelerating pace to maintain
> the 10-minute block time. This would mean the number of leading zeros in
> the target value would also need to increase at an accelerating rate.
>
> Since the target value is a 256-bit number (64 hexadecimal digits),
> there's a finite limit to the number of leading zeros it can have. With
> approximately 19-20 leading zeros currently observed, there are only abou=
t
> 44-45 zeros "left" before reaching this limit.
>
> My concern is that with double exponential hash rate growth, we could
> reach this limit much faster than a simple linear projection would sugges=
t,
> potentially within a decade. Once this limit is reached, the current
> difficulty adjustment mechanism would become ineffective, potentially
> leading to unstable block times and network instability.
>
> My questions for the list are:
>
> 1. Has there been more formal analysis of the Bitcoin hash rate trend to
> assess the likelihood of double exponential growth? Are there any existin=
g
> studies or analyses I should be aware of?
>
> 2. If double exponential growth continues, what are the most promising
> approaches to address this potential issue in the long term?
>
> 3. What are the trade-offs associated with different solutions, such as
> more frequent difficulty adjustments, changing the difficulty adjustment
> algorithm, or changing the proof-of-work algorithm entirely?
>
> Thanks,
>
> Anders
>
> --
> You received this message because you are subscribed to the Google Groups
> "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/e86753f2-1c79-484d-8f61-47a5=
dd148b45n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/e86753f2-1c79-484d-8f61-47a=
5dd148b45n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>
> .
>

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
CAAg3Je1hVqcR_DGZEXhaeO7CEU1k-SLx_1QX%3DXmnS2Bn11joXw%40mail.gmail.com.

--0000000000000b41e90629a2d261
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Anders,<div><br></div><div>Thank you for the question.<=
/div><div><br></div><div>A solution is to keep miners on SHA256 (instead of=
 switching to a hash that allows for a larger range of difficulty targets) =
but to require them to hash again to achieve a secondary difficulty target.=
</div><div><br></div><div>At max target difficulty miners would publish blo=
cks when SHA256(header) =3D=3D 1 and when SHA256(SHA256(header)) &lt;=3D se=
condary_target where secondary_target adjusts up and down if primary_target=
 is 1 (where primary_target represents today&#39;s target difficulty).</div=
><div><br></div><div>Nodes then verify blocks by checking that SHA256(heade=
r) is =3D=3D 1 and that SHA256(SHA256(header) is less than secondary_target=
.</div><div><br></div><div>Best regards,</div><div>Mike</div></div><br><div=
 class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Wed, Dec 18, 2024 at 6:21=E2=80=AFPM Anders &lt;<a href=3D"mailt=
o:blabline@gmail.com">blabline@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width=
:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-lef=
t:1ex">Hi,<br><br>I&#39;ve been looking into the long-term implications of =
the Bitcoin hash rate growth for the difficulty adjustment mechanism, and I=
&#39;d like to discuss a potential concern related to double exponential gr=
owth.<br><br>As we know, the difficulty adjustment mechanism aims to mainta=
in an average block time of approximately 10 minutes by adjusting the targe=
t value every 2016 blocks. This target value, when represented in hexadecim=
al, effectively determines the number of leading zeros required for a valid=
 block hash.<br><br>The Bitcoin hash rate has historically shown a strong e=
xponential growth trend, driven by advancements in ASIC technology. However=
, some observations suggest that this growth might be accelerating, potenti=
ally exhibiting double exponential growth (meaning the rate of exponential =
growth is itself increasing exponentially).<br><br>If the hash rate were to=
 continue to grow at a double exponential rate, the difficulty would need t=
o increase at an accelerating pace to maintain the 10-minute block time. Th=
is would mean the number of leading zeros in the target value would also ne=
ed to increase at an accelerating rate.<br><br>Since the target value is a =
256-bit number (64 hexadecimal digits), there&#39;s a finite limit to the n=
umber of leading zeros it can have. With approximately 19-20 leading zeros =
currently observed, there are only about 44-45 zeros &quot;left&quot; befor=
e reaching this limit.<br><br>My concern is that with double exponential ha=
sh rate growth, we could reach this limit much faster than a simple linear =
projection would suggest, potentially within a decade. Once this limit is r=
eached, the current difficulty adjustment mechanism would become ineffectiv=
e, potentially leading to unstable block times and network instability.<br>=
<br>My questions for the list are:<br><br>1. Has there been more formal ana=
lysis of the Bitcoin hash rate trend to assess the likelihood of double exp=
onential growth? Are there any existing studies or analyses I should be awa=
re of?<div><br>2. If double exponential growth continues, what are the most=
 promising approaches to address this potential issue in the long term?</di=
v><div><br>3. What are the trade-offs associated with different solutions, =
such as more frequent difficulty adjustments, changing the difficulty adjus=
tment algorithm, or changing the proof-of-work algorithm entirely?</div><di=
v><br>Thanks,<br><div><br></div><div>Anders</div></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/e86753f2-1c79-484d-8f61-47a5dd148b45n%40googlegroups.com?utm_med=
ium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">https://groups.googl=
e.com/d/msgid/bitcoindev/e86753f2-1c79-484d-8f61-47a5dd148b45n%40googlegrou=
ps.com</a>.<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/CAAg3Je1hVqcR_DGZEXhaeO7CEU1k-SLx_1QX%3DXmnS2Bn11joXw%40mail.gma=
il.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/=
msgid/bitcoindev/CAAg3Je1hVqcR_DGZEXhaeO7CEU1k-SLx_1QX%3DXmnS2Bn11joXw%40ma=
il.gmail.com</a>.<br />

--0000000000000b41e90629a2d261--