From: Robin Linus <robinlinus@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] 7 Theses on a next step for BIP-119
Date: Wed, 20 Apr 2022 19:46:52 +0000 [thread overview]
Message-ID: <bIa-5T8hTN8nfjxj-jW7AN26E1LvwcD18D_Asem3dcjp3XFdFwv1HlbkxMJH25eujXf-tEzc0ppk0leC-mKdM10AqYu7QwQwfqZwe5qn5-0=@protonmail.com> (raw)
In-Reply-To: <eLc8PiheOGDBz7gS5qCMEK9D2UUdPhBbHXg3KnRhA8SPxzmc2rX72QNAhayCa83hTbvtKc20SQL9t0Ufh-D60xyRtYuH1un4HWcvnfZnZds=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]
Hi Michael,
Thank you for your reply. You wrote:
> I have a better (and safer) way forward which is to continue to build out use cases of CTV, convince the community it is the best tool for the job (whatever use case(s) that is), compare it to other existing covenant enabling proposals on those use cases and then get to a point where the community is confident that it is activating a proposal(s) that will stand the test of time.
Where can I see the use cases you have built out in recent years? Do you have a writeup in which you compare CTV to existing covenant enabling proposals? Do you have a strong reason to favour a different proposal? Have you written any code?
I've seen pages of text of you complaining about details of CTV activation but nothing tangible that would prove that you are actually interested in real progress on covenants.
In contrast, Jeremy has been doing exactly what you are proposing. He wrote the BIP, implemented it, explained use cases in detail, spoke at conferences, organised workshops, and built the Sapio framework for the community to experiment with covenants. He even puts his money where his mouth is and offers a bug bounty for any security flaw in the code.
> You may not like that way forward because it requires a lot of work, a lot of time and a lot of patience.
A lot of work, a lot of time and a lot of patience is exactly what Jeremy has been investing for years. I think by framing his contributions as "immature" you are disrespecting all the work he put into BIP-119. If you could point me to essays of you thoughtfully comparing various covenant proposals then I could see your point, but you're only ranting on other people's work which requires no real effort and it doesn't contribute much. If you are not willing to do what you are suggesting for years why should anybody else do it? Should the entire community stall progress on covenants until somebody else works on what you think is ideal?
Bike shedding is just as big of an issue as "contentious soft forks". Pointless activation drama is a huge issue of bitcoin protocol development because it is so draining. Some of the most respected devs do not participate in activation politics anymore because it harms their health. That's nuts. If you really want to be of service to the Bitcoin community you should work on what you think is the right path forward and not just criticise Jeremy for progressing with his excellent work.
Looking forward to check out your contributions!
Regards,
Robin
[-- Attachment #2: Type: text/html, Size: 3948 bytes --]
next prev parent reply other threads:[~2022-04-20 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:31 Jeremy Rubin
2022-04-20 13:24 ` Michael Folkson
2022-04-20 17:13 ` Robin Linus
2022-04-20 18:19 ` Michael Folkson
2022-04-20 19:46 ` Robin Linus [this message]
2022-04-20 22:04 ` Michael Folkson
2022-04-21 9:05 ` Robin Linus
2022-04-21 4:03 ` Billy Tetrud
2022-04-21 12:49 ` Zac Greenwood
2022-04-21 13:40 ` alicexbt
2022-04-21 14:16 ` Greg Sanders
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='bIa-5T8hTN8nfjxj-jW7AN26E1LvwcD18D_Asem3dcjp3XFdFwv1HlbkxMJH25eujXf-tEzc0ppk0leC-mKdM10AqYu7QwQwfqZwe5qn5-0=@protonmail.com' \
--to=robinlinus@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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