path: root/56/417b208e2b42ca8c2f5c9e3050cf5a7cd643a5

Return-Path: <eric@voskuil.org>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 15D84C0177
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 22 Mar 2020 17:01:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by fraxinus.osuosl.org (Postfix) with ESMTP id 04DF8863E1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 22 Mar 2020 17:01:04 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
 by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id wWGnihepqqao
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 22 Mar 2020 17:01:02 +0000 (UTC)
X-Greylist: delayed 00:06:41 by SQLgrey-1.7.6
Received: from mail-pf1-f196.google.com (mail-pf1-f196.google.com
 [209.85.210.196])
 by fraxinus.osuosl.org (Postfix) with ESMTPS id C308A86329
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 22 Mar 2020 17:01:02 +0000 (UTC)
Received: by mail-pf1-f196.google.com with SMTP id d25so6227599pfn.6
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 22 Mar 2020 10:01:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=voskuil-org.20150623.gappssmtp.com; s=20150623;
 h=content-transfer-encoding:from:mime-version:subject:date:message-id
 :references:in-reply-to:to;
 bh=WFYCi8f6qrsEdMWTzp03VBbmTxHzHj9Q6wFxoBRTjiQ=;
 b=lx7dlz+onB4l0HLqGIPwqCjDf+io9uIuWhA0GV0gI1UOQrrXvUdF6KT9WxIkYzi0kR
 nJLGYPDzS2M8tfXYu9E6hctNBceDVlOQXeMXC5YLeKU1TdByZVCIyA8srqlYrADtPePN
 6mQIV2qzThLkSLXxCvWB4jpsH/mCA5GVWdNtAzR6m+7XwPSk/nDeGhIYu7xfHhkoKhPr
 hXklfJayXmMLUMrAIXB2fcwelKJcbF/sahbfcxhacN6g9MS44CaSYDxIVw4BlCRU44wp
 PA+Q13sQmDE7e8qOnZFem9MXjGXdcfRvcFhUnqzYgjqFKRUDBLul+JDnAQdn54I7RjDI
 rwmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:content-transfer-encoding:from:mime-version
 :subject:date:message-id:references:in-reply-to:to;
 bh=WFYCi8f6qrsEdMWTzp03VBbmTxHzHj9Q6wFxoBRTjiQ=;
 b=KE+gNKzNb+Z7Z315+cAkuM9wrlTx6auU4eelINbh1y5iHnZU09pYtKvWHf4pIXRsm1
 r4/4O067p3ldswa6OjerD2XaBKbvSTrkeExx4fPOEPM2KUcsdC+8F0J/KmXcrxN538Gu
 mzvURJyUuVuFZhpOPexlMdzxQXUIBOBgTB+f5u85LFkQk3ID0LlBiRECLu+48tt7MSyH
 fM9B6BAsHLxhJfJwCNp+bwCYECYmPdbhjQQcb9QKSB2WBnLVfB5L49RZwQEWuGUqsD+W
 iN3MZWdRsY4Ph+6C5uHqTKXPjGxEPSjO2GzixXBH7cTyJ5r6Vx3E4jt4Xvseyl87OFEm
 Zeag==
X-Gm-Message-State: ANhLgQ125H4PUg5qjf8QjwcmEehCcD9mE1HDYvv65BFPzQaUB8qcz0Ty
 xVy62nJfj3YgEZbQCekaXbNF8gh5/H+DMQ==
X-Google-Smtp-Source: ADFU+vsymnifb8c0/jztm4rovMH6lFqIm2iT2pxl4cfwXn1ntJL3g/QwlG1I5b9wBpMFK9mPq9k+tA==
X-Received: by 2002:a63:4cc:: with SMTP id 195mr18229229pge.93.1584896061367; 
 Sun, 22 Mar 2020 09:54:21 -0700 (PDT)
Received: from ?IPv6:2601:602:9a00:370e:1126:a0ba:3b7:657e?
 ([2601:602:9a00:370e:1126:a0ba:3b7:657e])
 by smtp.gmail.com with ESMTPSA id z30sm10882788pfq.84.2020.03.22.09.54.20
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Sun, 22 Mar 2020 09:54:20 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary=Apple-Mail-4A986AED-8909-46CD-9F1E-3C7F98FB00B2
Content-Transfer-Encoding: 7bit
From: Eric Voskuil <eric@voskuil.org>
Mime-Version: 1.0 (1.0)
Date: Sun, 22 Mar 2020 09:54:19 -0700
Message-Id: <F713CAAC-1997-4645-A166-57358E520594@voskuil.org>
References: <PS2P216MB0179EC99BDE0E3388F2627F89DF30@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
In-Reply-To: <PS2P216MB0179EC99BDE0E3388F2627F89DF30@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
To: LORD HIS EXCELLENCY JAMES HRMH <willtech@live.com.au>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (17D50)
X-Mailman-Approved-At: Sun, 22 Mar 2020 17:09:32 +0000
Subject: Re: [bitcoin-dev] Block solving slowdown question/poll
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2020 17:01:04 -0000


--Apple-Mail-4A986AED-8909-46CD-9F1E-3C7F98FB00B2
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Mining is a lottery.

e

> On Mar 22, 2020, at 07:10, LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev <=
bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> =EF=BB=BF
> There seems to be the real possibility that miners are simply trying to op=
timise mining profit by limiting the average hash rate during the retargetin=
g, saving some electricity but poorly considering the overall situation wher=
e they give opportunity to other miners probably raising the hashrate for th=
e next period. It is far more profitable for the ecosystem considering the w=
hole to hold a lottery for minig as has been discussed elsewhere some time a=
go.
>=20
> Regards,
> LORD HIS EXCELLENCY JAMES HRMH
>=20
>=20
> From: bitcoin-dev <bitcoin-dev-bounces@lists.linuxfoundation.org> on behal=
f of David A. Harding via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org=
>
> Sent: Sunday, 22 March 2020 6:54 PM
> To: Dave Scotese <dscotese@litmocracy.com>; Bitcoin Protocol Discussion <b=
itcoin-dev@lists.linuxfoundation.org>
> Subject: Re: [bitcoin-dev] Block solving slowdown question/poll
> =20
> On Sat, Mar 21, 2020 at 11:40:24AM -0700, Dave Scotese via bitcoin-dev wro=
te:
> > [Imagine] we also see mining power dropping off at a rate that
> > suggests the few days [until retarget] might become a few weeks, and
> > then, possibly, a few months or even the unthinkable, a few eons.  I'm
> > curious to know if anyone has ideas on how this might be handled
>=20
> There are only two practical solutions I'm aware of:
>=20
> 1. Do nothing
> 2. Hard fork a difficulty reduction
>=20
> If bitcoins retain even a small fraction of their value compared to the
> previous retarget period and if most mining equipment is still available
> for operation, then doing nothing is probably the best choice---as block
> space becomes scarcer, transaction feerates will increase and miners
> will be incentivized to increase their block production rate.
>=20
> If the bitcoin price has plummeted more than, say, 99% in two weeks
> with no hope of short-term recovery or if a large fraction of mining
> equipment has become unusable (again, say, 99% in two weeks with no
> hope of short-term recovery), then it's probably worth Bitcoin users
> discussing a hard fork to reduce difficulty to a currently sustainable
> level.
>=20
> -Dave
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--Apple-Mail-4A986AED-8909-46CD-9F1E-3C7F98FB00B2
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr">Mining is a lottery.</div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr">e</div><div dir=3D"ltr"><br><blo=
ckquote type=3D"cite">On Mar 22, 2020, at 07:10, LORD HIS EXCELLENCY JAMES H=
RMH via bitcoin-dev &lt;bitcoin-dev@lists.linuxfoundation.org&gt; wrote:<br>=
<br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-1=
">



<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; colo=
r:rgb(0,0,0)">
There seems to be the real possibility that miners are simply trying to opti=
mise mining profit by limiting the average hash rate during the retargeting,=
 saving some electricity but poorly considering the overall situation where t=
hey give opportunity to other
 miners probably raising the hashrate for the next period. It is far more pr=
ofitable for the ecosystem considering the whole to hold a lottery for minig=
 as has been discussed elsewhere some time ago.<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; colo=
r:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; colo=
r:rgb(0,0,0)">
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; colo=
r:rgb(0,0,0)">
Regards,</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; colo=
r:rgb(0,0,0)">
LORD HIS EXCELLENCY JAMES HRMH </div>
</div>
<div><br>
</div>
<div>
<div id=3D"Signature">
<div>
<div id=3D"appendonsend"></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; colo=
r:rgb(0,0,0)">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=3D=
"Calibri, sans-serif" color=3D"#000000"><b>From:</b> bitcoin-dev &lt;bitcoin=
-dev-bounces@lists.linuxfoundation.org&gt; on behalf of David A. Harding via=
 bitcoin-dev &lt;bitcoin-dev@lists.linuxfoundation.org&gt;<br>
<b>Sent:</b> Sunday, 22 March 2020 6:54 PM<br>
<b>To:</b> Dave Scotese &lt;dscotese@litmocracy.com&gt;; Bitcoin Protocol Di=
scussion &lt;bitcoin-dev@lists.linuxfoundation.org&gt;<br>
<b>Subject:</b> Re: [bitcoin-dev] Block solving slowdown question/poll</font=
>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt">=

<div class=3D"PlainText">On Sat, Mar 21, 2020 at 11:40:24AM -0700, Dave Scot=
ese via bitcoin-dev wrote:<br>
&gt; [Imagine] we also see mining power dropping off at a rate that<br>
&gt; suggests the few days [until retarget] might become a few weeks, and<br=
>
&gt; then, possibly, a few months or even the unthinkable, a few eons.&nbsp;=
 I'm<br>
&gt; curious to know if anyone has ideas on how this might be handled<br>
<br>
There are only two practical solutions I'm aware of:<br>
<br>
1. Do nothing<br>
2. Hard fork a difficulty reduction<br>
<br>
If bitcoins retain even a small fraction of their value compared to the<br>
previous retarget period and if most mining equipment is still available<br>=

for operation, then doing nothing is probably the best choice---as block<br>=

space becomes scarcer, transaction feerates will increase and miners<br>
will be incentivized to increase their block production rate.<br>
<br>
If the bitcoin price has plummeted more than, say, 99% in two weeks<br>
with no hope of short-term recovery or if a large fraction of mining<br>
equipment has become unusable (again, say, 99% in two weeks with no<br>
hope of short-term recovery), then it's probably worth Bitcoin users<br>
discussing a hard fork to reduce difficulty to a currently sustainable<br>
level.<br>
<br>
-Dave<br>
</div>
</span></font></div>
</div>
</div>
</div>


<span>_______________________________________________</span><br><span>bitcoi=
n-dev mailing list</span><br><span>bitcoin-dev@lists.linuxfoundation.org</sp=
an><br><span>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<=
/span><br></div></blockquote></body></html>=

--Apple-Mail-4A986AED-8909-46CD-9F1E-3C7F98FB00B2--