MIME-Version: 1.0
References: <CAH5Bsr2vxL3FWXnJTszMQj83jTVdRvvuVpimEfY7JpFCyP1AZA@mail.gmail.com>
 <CAD5xwhiJiopwH87Bn+yq_0-XXSJYOtNzUg4JCaYwuj=oo9CacA@mail.gmail.com>
 <CAH5Bsr1d0_xaVW59i+pzKtU2yb1FFMG7CJZgTueJwEO7XmkdYw@mail.gmail.com>
In-Reply-To: <CAH5Bsr1d0_xaVW59i+pzKtU2yb1FFMG7CJZgTueJwEO7XmkdYw@mail.gmail.com>
From: Jeremy Rubin <jeremy.l.rubin@gmail.com>
Date: Sun, 6 Feb 2022 09:56:12 -0800
Message-ID: <CAD5xwhhL_+wdUboJZ6i-WvJou7LQHq043ELr1ogOq5OH12iuNQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b4f78d05d75d3321"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 dlc-dev@mailmanlists.org
Subject: Re: [bitcoin-dev] CTV dramatically improves DLCs
Precedence: list

--000000000000b4f78d05d75d3321
Content-Type: text/plain; charset="UTF-8"

I'm not sure what is meant concretely by (5) but I think overall
performance is ok here. You will always have 10mins or so to confirm the
DLC so you can't be too fussy about performance!


I mean that if you think of the CIT points as being the X axis (or
independent axes if multivariate) of a contract, the Y axis is the
dependent variable represented by the CTV hashes.


For a DLC living inside a lightning channel, which might be updated between
parties e.g. every second, this means you only have to recompute the
cheaper part of the DLC only if you update the payoff curves (y axis) only,
and you only have to update the points whose y value changes.

For on chain DLCs this point is less relevant since the latency of block
space is larger.

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

<div dir=3D"auto"><div style=3D"color:rgb(80,0,80);font-size:12.8px" dir=3D=
"auto"><div dir=3D"auto" class=3D"elided-text"><blockquote style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div class=3D"elided-text"><div>I&#39;m not sure what is m=
eant concretely by (5) but I think overall performance is ok here. You will=
 always have 10mins or so to confirm the DLC so you can&#39;t be too fussy =
about performance!<br></div></div></div></blockquote></div><div dir=3D"auto=
"><br></div></div><div dir=3D"auto" style=3D"font-size:12.8px">I mean that =
if you think of the CIT points as being the X axis (or independent axes if =
multivariate) of a contract, the Y axis is the dependent variable represent=
ed by the CTV hashes.=C2=A0</div><div dir=3D"auto" style=3D"font-size:12.8p=
x"><br></div><div dir=3D"auto" style=3D"font-size:12.8px"><br></div><div di=
r=3D"auto" style=3D"font-size:12.8px">For a DLC living inside a lightning c=
hannel, which might be updated between parties e.g. every second, this mean=
s you only have to recompute the cheaper part of the DLC only if you update=
 the payoff curves (y axis) only, and you only have to update the points wh=
ose y value changes.</div><div dir=3D"auto" style=3D"font-size:12.8px"><br>=
</div><div dir=3D"auto" style=3D"font-size:12.8px">For on chain DLCs this p=
oint is less relevant since the latency of block space is larger.=C2=A0</di=
v></div>

--000000000000b4f78d05d75d3321--