Date: Tue, 18 Jan 2022 02:57:30 +0100 (CET)
From: Prayank <prayank@tutanota.de>
To: pete@petertodd.org
Message-ID: <MtetoOZ--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_331500_1870845089.1642471050921"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Stumbling into a contentious soft fork activation
 attempt
Precedence: list

------=_Part_331500_1870845089.1642471050921
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Peter,

> that current lacks compelling use-cases clearly beneficial to all users

All the use cases shared in below links look compelling enough to me and we can do anything that a programmer could think of using such restrictions:

 https://utxos.org/uses/

https://rubin.io/archive/

> I don't think CTV in its current form makes that case sufficiently, and the technical details are lacking.
CTV cannot be compared to segwit or taproot. We are expecting different things in that case. CTV is trying to do add basic covenants in Bitcoin that would help all Bitcoin users. Most important thing missing in lot of conversations is the low demand for block space which affects everyone who understands importance of fees in long term. Right now fee rates only spike during peak bull markets which indicate the only use case is speculation and this can be improved if developers could do better things with Bitcoin smart contracts.

This would also ensure that we don't end up with something really contentious in future that changes supply.

> DoS Attacks

I think this was already answered by Jeremy and pull request to add related information is also merged:

https://github.com/bitcoin/bips/pull/1272


-- 
Prayank

A3B1 E430 2298 178F

------=_Part_331500_1870845089.1642471050921
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=3DUTF-8=
">
  </head>
  <body>
<div>Hi Peter,<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">&gt; =
that current lacks compelling use-cases clearly beneficial to all users<br>=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">All the use cases share=
d in below links look compelling enough to me and we can do anything that a=
 programmer could think of using such restrictions:<br></div><div dir=3D"au=
to"><br></div><div dir=3D"auto"> https://utxos.org/uses/<br></div><div dir=
=3D"auto"><br></div><div dir=3D"auto">https://rubin.io/archive/<br></div><d=
iv dir=3D"auto"><br>&gt; I don't think CTV in its current form makes that c=
ase sufficiently, and the technical details are lacking.</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">CTV cannot be compared to segwit or taproo=
t. We are expecting different things in that case. CTV is trying to do add =
basic covenants in Bitcoin that would help all Bitcoin users. Most importan=
t thing missing in lot of conversations is the low demand for block space w=
hich affects everyone who understands importance of fees in long term. Righ=
t now fee rates only spike during peak bull markets which indicate the only=
 use case is speculation and this can be improved if developers could do be=
tter things with Bitcoin smart contracts.<br></div><div dir=3D"auto"><br></=
div><div dir=3D"auto">This would also ensure that we don't end up with some=
thing really contentious in future that changes supply.<br></div><div dir=
=3D"auto"><br></div><div dir=3D"auto">&gt; DoS Attacks<br></div><div dir=3D=
"auto"><br></div><div dir=3D"auto">I think this was already answered by Jer=
emy and pull request to add related information is also merged:<br></div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">https://github.com/bitcoin/bips=
/pull/1272<br></div><div><br></div><div dir=3D"auto"><br></div><div dir=3D"=
auto">-- <br></div><div>Prayank<br></div><div><br></div><div dir=3D"auto">A=
3B1 E430 2298 178F<br></div>  </body>
</html>

------=_Part_331500_1870845089.1642471050921--