From: Prayank <prayank@tutanota•de>
To: pete@petertodd•org
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Stumbling into a contentious soft fork activation attempt
Date: Tue, 18 Jan 2022 02:57:30 +0100 (CET) [thread overview]
Message-ID: <MtetoOZ--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1988 bytes --]
next reply other threads:[~2022-01-18 1:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 1:57 Prayank [this message]
2022-02-18 23:41 ` Peter Todd
2022-02-20 18:35 ` Erik Aronesty
2022-02-21 3:03 ` Prayank
2022-02-21 9:02 ` ZmnSCPxj
2022-02-21 9:11 ` ZmnSCPxj
2022-02-21 9:48 ` Prayank
2022-02-22 12:57 ` Billy Tetrud
2022-02-21 9:09 ` ZmnSCPxj
-- strict thread matches above, loose matches on Subject: below --
2022-01-04 11:53 Prayank
2022-01-04 14:15 ` Michael Folkson
2022-01-04 15:06 ` Prayank
2022-01-04 16:48 ` Michael Folkson
2022-01-04 17:07 ` Prayank
2022-01-04 14:42 ` Christian Decker
2022-01-04 15:45 ` Prayank
2022-01-03 2:05 Michael Folkson
2022-01-09 11:38 ` Peter Todd
2022-01-11 3:42 ` Jeremy
2022-01-11 4:38 ` Jeremy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MtetoOZ--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox