public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Billy Tetrud <billy.tetrud@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>,
	"Bitcoin Protocol Discussion"
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin covenants are inevitable
Date: Wed, 8 Jun 2022 23:30:45 -0500	[thread overview]
Message-ID: <CAGpPWDY_FivTFSQnUM5P5oCT9WX3+NSm61UHOSa2bERVMPH6ow@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDr6QyVUPFODRBBvWY-sukX+k9-kLKpjPnwwaQqejQL88w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 8364 bytes --]

@jorge

> Who do you mean by "the non technical folks"?

I mean people that don't have software engineering skills. This is the
twittersphere, reddit, most podcasters, etc etc. This is the vast majority
of the bitcoin community, and the vast majority of.. everyone.

> You don't include alicexbt or yourself as a "technical folk", do you?

I have no idea what alicexbt's skillset is. I do include myself. I have a
degree in software engineering. I work as a programmer in the bitcoin
space. I have written papers on technical aspects of bitcoin. Why would you
assume that I'm not technical as someone who participates in the bitcoin
developers mailing list? Perhaps its projection?

On Wed, Jun 8, 2022 at 3:31 PM Jorge Timón via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Who do you mean by "the non technical folks"?
> You don't include alicexbt or yourself as a "technical folk", do you?
>
>
> On Wed, Jun 8, 2022 at 8:38 AM Billy Tetrud via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> Wholeheartedly agree with you alicexbt. There are no technical issues
>> that have been shown that I'm aware of. Once the non-technical folks have
>> time to discuss it and realize that, I'm hopeful things will move forward.
>> Perhaps we can learn from this and figure out how to better catch the
>> attention of the larger bitcoin community  for important changes without
>> alarming them.
>>
>> On Sun, Jun 5, 2022 at 2:48 AM alicexbt via bitcoin-dev <
>> bitcoin-dev@lists•linuxfoundation.org> wrote:
>>
>>> Hi Jorge,
>>>
>>>
>>> Misinformation is false or inaccurate information, especially that which
>>> is deliberately intended to deceive. A combination of 'misleading' and
>>> 'information'. Here are a few examples and I am sure I missed a lot of
>>> others but its difficult for me to keep a track of everything:
>>>
>>>
>>> 1) Sapio is open source and everything mentioned in tweet is false:
>>> https://web.archive.org/web/20220503050140/https://twitter.com/coinableS/status/1521354192434073602
>>>
>>> 2) Personal attacks on author of BIP 119 with false information:
>>> https://nitter.net/s3cp256k1/status/1521238634111770624
>>>
>>> 3) Andreas Antonopoulos shared false things about CTV and explained by
>>> Ryan in this email:
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020414.html
>>>
>>> 4) Misleading things shared in these emails by Michael Folkson:
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019728.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020235.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020286.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020343.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020386.html
>>>
>>> 5) Peter Todd and Zac shared misleading things about BIP 119, bitcoin
>>> and L2. I replied in this email:
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020322.html
>>>
>>> 6) Social media influencers like Peter McCormack tweeted they don't
>>> understand BIP 119 but its an attack (this was even retweeted by developers
>>> like Peter Todd):
>>> https://nitter.net/PeterMcCormack/status/1521253840963653632
>>>
>>> 7) Some misconceptions about BIP 119 cleared by Bitcoin Magazine:
>>> https://bitcoinmagazine.com/technical/what-is-bip-119-bitcoin-controversy-explained
>>>
>>> 8) There were lies and misinformation about BIP 119 on social media
>>> according to this Bitcoin Magazine article:
>>> https://bitcoinmagazine.com/technical/analyzing-bip119-and-the-controversy-surrounding-it
>>>
>>> 9) John Carvalho tweeting false things:
>>>
>>>     https://nitter.net/BitcoinErrorLog/status/1468599535538745359
>>>
>>>     https://nitter.net/BitcoinErrorLog/status/1522652884218822658
>>>
>>>     https://nitter.net/BitcoinErrorLog/status/1442554615967354880
>>>
>>>     https://nitter.net/search?q=MIT%20(from%3ABitcoinErrorLog)
>>>
>>> 10) Greg Maxwell responding to misinformation related to BIP 119 but
>>> adding false things in the comments:
>>> https://www.reddit.com/r/Bitcoin/comments/uim560/bip_119/i7dhfpb/
>>>
>>>
>>> I am not surprised by your email but it would be better if the people
>>> who are interested in reviewing BIP 119 could raise the bar and not share
>>> misleading information.
>>>
>>>
>>> /dev/fd0
>>>
>>>
>>> Sent with Proton Mail secure email.
>>> ------- Original Message -------
>>> On Sunday, June 5th, 2022 at 12:12 AM, Jorge Timón <jtimon@jtimon•cc>
>>> wrote:
>>>
>>>
>>> > "Some people say CTV is contentious, but they're spreading
>>> misinformation"? Really? Seriously?Come on, guys, we can do better than
>>> nina jankovich and the "fact checkers".
>>> > Please, rise the bar.
>>> > On Fri, Jun 3, 2022, 19:44 alicexbt via bitcoin-dev <
>>> bitcoin-dev@lists•linuxfoundation.org> wrote:
>>> >
>>> > > Note: This email is an opinion and not an attack on bitcoin
>>> > >
>>> > > Covenants on bitcoin will eventually be implemented with a soft
>>> fork. CTV is the easiest and best possible way OP_TX looks good as well.
>>> Apart from the technical merits, covenants will improve a few other things:
>>> > >
>>> > > - Developers can build interesting projects with real demand in
>>> market.
>>> > > - Students learn Sapio and not just solidity.
>>> > > - Better tooling could be available for application developers.
>>> > > - Maybe we see bitcoin developer hackathons in different countries.
>>> > > - Demand for block space might increase, it wont be just exchanges
>>> and coinjoin.
>>> > > - Funding of bitcoin developers and projects might improve. Wont
>>> need to convince a few people for grants.
>>> > >
>>> > > **Why covenants are not contentious?**
>>> > >
>>> > > Some people may write paragraphs about CTV being contentious, spread
>>> misinformation and do all types of drama, politics etc. on social media but
>>> there are zero technical NACKs for CTV. We have discussed other covenant
>>> proposals in detail on mailing list and IRC meetings with an open minded
>>> approach.
>>> > >
>>> > > All the developers that participated in the discussion are either
>>> okay with CTV or OP_TX or covenants in general.
>>> > >
>>> > > **How and when should covenants be implemented in Bitcoin?**
>>> > >
>>> > > I don't think we should wait for years anticipating a proposal that
>>> everyone will agree on or argue for years to pretend changes are hard in
>>> Bitcoin. We should improve the review process for soft fork BIPs and share
>>> honest opinions with agreement, disagreement on technical merits.
>>> > >
>>> > > I prefer BIP 8 or improved BIP 8 for soft fork but I won't mind
>>> anything else being used if that improves Bitcoin. Covenants implemented in
>>> Bitcoin before the next cycle would provide opportunity for developers to
>>> build interesting things during the bear market. Ossification supporters
>>> also believe there is some window that will close soon, maybe doing changes
>>> considering each case individually will be a better approach. CTV is not a
>>> rushed soft fork, less people followed the research and it was not
>>> mentioned on social media repeatedly by the respected developers like other
>>> soft forks.
>>> > >
>>> > > /dev/fd0
>>> > >
>>> > >
>>> > > Sent with Proton Mail secure email.
>>> > > _______________________________________________
>>> > > bitcoin-dev mailing list
>>> > > bitcoin-dev@lists•linuxfoundation.org
>>> > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists•linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 12481 bytes --]

  reply	other threads:[~2022-06-09  4:31 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 18:39 alicexbt
2022-06-04  0:29 ` micaroni
2022-06-04 18:43 ` Jorge Timón
2022-06-05  4:18   ` alicexbt
2022-06-08  3:51     ` Billy Tetrud
2022-06-08  9:22       ` Jorge Timón
2022-06-09  4:30         ` Billy Tetrud [this message]
2022-06-09  0:03     ` Ryan Grant
2022-07-19  4:44 ` Anthony Towns
2022-07-19 14:46   ` alicexbt
     [not found] <mailman.9.1654344003.14400.bitcoin-dev@lists.linuxfoundation.org>
2022-06-04 12:27 ` John Carvalho
2022-06-04 13:48   ` Keagan McClelland
2022-06-04 16:12   ` alicexbt
2022-06-06 13:02   ` Erik Aronesty
2022-06-12  3:36     ` Peter Todd
2022-06-12 13:02       ` Erik Aronesty
2022-06-12 16:35         ` Corey Haddad
2022-06-12 19:16       ` alicexbt
2022-06-19 10:31         ` Peter Todd
2022-06-19 15:54           ` Manuel Costa
2022-06-19 18:26             ` Kate Salazar
2022-06-19 22:35             ` Erik Aronesty
2022-06-21 19:00               ` Keagan McClelland
2022-06-21 20:10                 ` Eric Voskuil
2022-06-23 19:17                 ` Peter Todd
2022-06-28  3:55                   ` Billy Tetrud
2022-06-28 16:23                     ` Alex Lee
2022-06-28 23:22                       ` Peter Todd
2022-06-29  5:02                         ` Alex Lee
2022-06-28 23:20                     ` Peter Todd
2022-06-29 10:44                     ` Kate Salazar
2022-06-30 15:25                       ` Billy Tetrud
2022-07-03  9:43                       ` Peter Todd
2022-07-03 10:30                         ` Giuseppe B
2022-07-06  4:28                           ` Corey Haddad
2022-07-06 11:10                             ` vjudeu
2022-07-07  0:46                               ` Billy Tetrud
2022-07-07 12:15                                 ` vjudeu
2022-07-07 14:05                                 ` Erik Aronesty
2022-07-07 14:10                               ` Giuseppe B
2022-07-08  5:03                                 ` Billy Tetrud
2022-06-30 17:04                     ` Erik Aronesty
     [not found] <mailman.9.1657195203.20624.bitcoin-dev@lists.linuxfoundation.org>
2022-07-07 13:24 ` John Carvalho
2022-07-07 14:12   ` Peter Todd
2022-07-07 16:24     ` Eric Voskuil
2022-07-07 17:37       ` Erik Aronesty
2022-07-07 19:57         ` Eric Voskuil
2022-07-07 21:11           ` Erik Aronesty
2022-07-08  0:28             ` Eric Voskuil
2022-07-08  4:59               ` vjudeu
2022-07-08  7:26                 ` John Carvalho
2022-07-08 15:14               ` Erik Aronesty
2022-07-14  4:55                 ` Billy Tetrud
2022-07-07 22:06     ` Anthony Towns
2022-07-07 22:02   ` Corey Haddad

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=CAGpPWDY_FivTFSQnUM5P5oCT9WX3+NSm61UHOSa2bERVMPH6ow@mail.gmail.com \
    --to=billy.tetrud@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=jtimon@jtimon$(echo .)cc \
    /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