Return-Path: <thomashartman1@gmail.com>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 7ECD4C0051
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  1 Sep 2020 20:07:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by fraxinus.osuosl.org (Postfix) with ESMTP id 7AF58866A9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  1 Sep 2020 20:07:26 +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 cbsrLSEDylpD
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  1 Sep 2020 20:07:25 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-vk1-f182.google.com (mail-vk1-f182.google.com
 [209.85.221.182])
 by fraxinus.osuosl.org (Postfix) with ESMTPS id BE29386670
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  1 Sep 2020 20:07:25 +0000 (UTC)
Received: by mail-vk1-f182.google.com with SMTP id h23so663508vkn.4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 01 Sep 2020 13:07:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=from:message-id:mime-version:subject:date:in-reply-to:cc:to
 :references; bh=7dhu53RiPa7zdBTk9hZwHe9Dzn4mOsL/HzNeRJMcM78=;
 b=UjYYK2afo7B0rqXibSo0ZnXNXYEZ7lZCWlmDBpW4NSH4coocCxDaAyyJTSD0ddOx4D
 l4s8B2JdQBYGOwSbQ4x4i8R4u9z57MsQ1dnpagBy01z9uyurUHl0tKSXNKYX+iffpUsx
 fWCg3ySGz3pni3DmekvV6lA6R8op1JoHHzu7brNQWzdTGf3C/TrkCm+QVv9FlxqDD8u3
 e0ayhmA5UnLF04zjXIEqw88KeU++lDtBv9HGtImuuxQQa29JB7f9q35Eq+CRljEYiBBn
 rQUOiZs3Ck+GwXB01xkdRzJGaxn5KWYXZNyDsGSQQa/odvcuxF+3caUc+XPebHD8qJLZ
 GiMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:message-id:mime-version:subject:date
 :in-reply-to:cc:to:references;
 bh=7dhu53RiPa7zdBTk9hZwHe9Dzn4mOsL/HzNeRJMcM78=;
 b=CAv0P2j8iE/wL80gUqfDgN8soheqSfthPvNZomyVtiLFQU6RJvjDI3q7l9Tlf2Dd8+
 20vfGI69AyykRRNooPBKDebYgiM2sJtDOAvpnkhljhr9M1wwF3dIstDe9QBWvigkwLSB
 zRC3kE7mkDNwZII68ybUz99r1Oaizd56K5BguMKienC9adNT5dL8CcjzuNqOhb/bUEzv
 myDCzFLPlmwLECbkCNhmmXIuU5Ya9MFDTkv1aBnCDYs4ZjYif8zSFA0fOgyDTspJZT4v
 Y1yuECX79z1h0h2i/evLGE0OStxKeTfnnhXY/Q7qqk04+U2eOViACOjgv6qDj6uwUl0a
 Mtcg==
X-Gm-Message-State: AOAM53046VKTFw5taDrEgBbNReZsW4QaShk2AL1X4TyGYP128pQ7pxq1
 NGh7moval9MAUfdALViYopaqDgyL1ngQZA==
X-Google-Smtp-Source: ABdhPJy7S6VEm3M0wqZ0yjiQvFtoRG+q9XSa+25E6JHdwDO1Y3Y7Lz09jPZqFSHqMXtZRw8atFZ9Lw==
X-Received: by 2002:a1f:a8d4:: with SMTP id r203mr3265692vke.49.1598990844242; 
 Tue, 01 Sep 2020 13:07:24 -0700 (PDT)
Received: from [192.168.0.2] ([70.45.100.193])
 by smtp.gmail.com with ESMTPSA id q2sm337733vsd.6.2020.09.01.13.07.22
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 01 Sep 2020 13:07:23 -0700 (PDT)
From: Thomas Hartman <thomashartman1@gmail.com>
Message-Id: <966B6C4B-3EA0-4E5A-BDE9-C7EB3E8C1EF0@gmail.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_6685B6C6-0F2F-4B2D-BBBC-6B3AD50B4FDE"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 1 Sep 2020 16:07:21 -0400
In-Reply-To: <bc0SG26C9FUzZO4l9cGDtbBGb0lrhsxrcvDoJXpJGUbyKEUq3eE3vLwTu_WufWOsN6DK3lPcKttNdEa9h7_tqixk12sBVErMi0YYF_HNBGo=@protonmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <CAHAXnDXhAFQHiBCJ=H=1ZGHdHWhgLh1rG3pCPR5o48ziZzV+zQ@mail.gmail.com>
 <CAE-z3OVCcAL2x39TswA8zrZ+yjSqdx4hccTWn9Ug8MQ5=k-Pgg@mail.gmail.com>
 <Y9rFseQ13QJ0TspORM_a542mUib8lJV2IiDe8GXS5SrxkvXbVI13MfbgGqVoSVftumcYNBBKut6Fz840ehS5VfvF2AsO_qNTyzvs6tTCpBk=@protonmail.com>
 <C7C0864D-5635-43B8-88B6-E53A14C3066C@gmail.com>
 <bc0SG26C9FUzZO4l9cGDtbBGb0lrhsxrcvDoJXpJGUbyKEUq3eE3vLwTu_WufWOsN6DK3lPcKttNdEa9h7_tqixk12sBVErMi0YYF_HNBGo=@protonmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Mailman-Approved-At: Tue, 01 Sep 2020 20:59:18 +0000
Cc: jr@mit.edu
Subject: Re: [bitcoin-dev] reviving op_difficulty
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: Tue, 01 Sep 2020 20:07:26 -0000


--Apple-Mail=_6685B6C6-0F2F-4B2D-BBBC-6B3AD50B4FDE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This is in reply to David harding=E2=80=99s message at=20

=
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-August/018129=
.html =
<https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-August/01812=
9.html>

(For some reason didn=E2=80=99t arrive in my inbox, so I was late =
noticing it, and I am replying in this way. Sorry if it screws up =
threading.)

Powswap sounds great! And it doesn=E2=80=99t require any protocol =
changes! Very cool.

One potential problem I see with powswap is iiuc you need something like =
watchtowers, or the loser of the bet can sweep the funds if the winner =
is napping. Related, I=E2=80=99d also like to have trades happening in =
lightning channels, and I=E2=80=99m not sure how this race affects the =
security assumptions there.=20

Further question about powswap.=20

It=E2=80=99s currently block 64632 with retarget in 808 blocks. I=E2=80=99=
d like to bet that=20

* the first 6 blocks after the retarget are found in under an hour
* AND the new difficulty exceeds some threshold. Is such a bet currently =
possible with powswap?

I see how pow swap lets you bet on hashrate (ie block times) from =
current time till some future time. But I would like to also bet on =
hashrate of slices of time in the future. Possible?=20



--Apple-Mail=_6685B6C6-0F2F-4B2D-BBBC-6B3AD50B4FDE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">This =
is in reply to David harding=E2=80=99s message at&nbsp;<div class=3D""><br=
 class=3D""></div><div class=3D""><a =
href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-Augus=
t/018129.html" =
class=3D"">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-Au=
gust/018129.html</a></div><div class=3D""><br class=3D""></div><div =
class=3D"">(For some reason didn=E2=80=99t arrive in my inbox, so I was =
late noticing it, and I am replying in this way. Sorry if it screws up =
threading.)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Powswap sounds great! And it doesn=E2=80=99t require any =
protocol changes! Very cool.</div><div class=3D""><br =
class=3D""></div><div class=3D"">One potential problem I see with =
powswap is iiuc you need something like watchtowers, or the loser of the =
bet can sweep the funds if the winner is napping. Related, I=E2=80=99d =
also like to have trades happening in lightning channels, and I=E2=80=99m =
not sure how this race affects the security assumptions =
there.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Further question about powswap.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">It=E2=80=99s currently block&nbsp;<span =
style=3D"background-color: rgb(255, 255, 255);" class=3D""><font =
face=3D"Menlo" class=3D""><span style=3D"font-size: 11px;" =
class=3D"">64632 with retarget in 808 blocks. I=E2=80=99d like to bet =
that&nbsp;</span></font></span></div><div class=3D""><span =
style=3D"background-color: rgb(255, 255, 255);" class=3D""><font =
face=3D"Menlo" class=3D""><span style=3D"font-size: 11px;" class=3D""><br =
class=3D""></span></font></span></div><div class=3D""><span =
style=3D"background-color: rgb(255, 255, 255);" class=3D""><font =
face=3D"Menlo" class=3D""><span style=3D"font-size: 11px;" class=3D"">* =
the first 6 blocks after the retarget are found in under an =
hour</span></font></span></div><div class=3D""><span =
style=3D"background-color: rgb(255, 255, 255);" class=3D""><font =
face=3D"Menlo" class=3D""><span style=3D"font-size: 11px;" class=3D"">* =
AND the new difficulty exceeds some&nbsp;threshold. Is such a bet =
currently possible with&nbsp;powswap?</span></font></span></div><div =
class=3D""><span style=3D"background-color: rgb(255, 255, 255);" =
class=3D""><font face=3D"Menlo" class=3D""><span style=3D"font-size: =
11px;" class=3D""><br class=3D""></span></font></span></div><div =
class=3D""><span style=3D"background-color: rgb(255, 255, 255);" =
class=3D""><font face=3D"Menlo" class=3D""><span style=3D"font-size: =
11px;" class=3D"">I see how&nbsp;pow swap lets you bet on hashrate (ie =
block times) from current time till some future time. But I would like =
to also bet on hashrate of slices of time in the future. =
Possible?&nbsp;</span></font></span></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_6685B6C6-0F2F-4B2D-BBBC-6B3AD50B4FDE--