From: Matt Corallo <lf-lists@mattcorallo.com>
To: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Some real-world results about the current Segwit Discount
Date: Wed, 10 May 2017 16:39:00 +0000 [thread overview]
Message-ID: <B067643A-FBFD-4F59-B7AE-77769B9A9ACE@mattcorallo.com> (raw)
In-Reply-To: <CAKzdR-r=y=myz60v9FnYr3tJbW9LgNQkAoA9+F-+jaLScg2PJw@mail.gmail.com>
I highly disagree about the "not shit" part. You're advocating for throwing away one of the key features of Segwit, something that is very important for Bitcoin's long-term reliability! If you think doing so is going to somehow help get support in a divided community, I don't understand how - more likely you're only going to make things significantly worse.
On May 10, 2017 11:25:27 AM EDT, Sergio Demian Lerner <sergio.d.lerner@gmail.com> wrote:
>Jaja. But no shit. Not perfect maybe, but Bitcoin was never perfect. It
>has
>always been good enough. And at the beginning it was quite simple.
>Simple
>enough it allowed gradual improvements that anyone with some technical
>background could understand. Now we need a full website to explain an
>improvement.
>But this is becoming more and more out of topic.
>
>
>On Wed, May 10, 2017 at 11:05 AM, Matt Corallo
><lf-lists@mattcorallo.com>
>wrote:
>
>> I'm highly unconvinced of this point. Sure, you can change fewer
>lines
>> of code, but if the result is, lets be honest, shit, how do you
>believe
>> its going to have a higher chance of getting acceptance from the
>broader
>> community? I think you're over-optimizing in the wrong direction.
>>
>> Matt
>>
>> On 05/09/17 20:58, Sergio Demian Lerner wrote:
>> > I agree with you Matt.
>> > I'm artificially limiting myself to changing the parameters of
>Segwit as
>> > it is..
>> >
>> > This is motivated by the idea that a consensual HF in the current
>state
>> > would have greater chance of acceptance if it changes the minimum
>number
>> > of lines of code.
>> >
>> >
>> >
>> > On Tue, May 9, 2017 at 5:13 PM, Gregory Maxwell <greg@xiph.org
>> > <mailto:greg@xiph.org>> wrote:
>> >
>> > On Tue, May 9, 2017 at 7:42 PM, Matt Corallo
>> > <lf-lists@mattcorallo.com <mailto:lf-lists@mattcorallo.com>>
>wrote:
>> > > at beast.
>> >
>> > Rawr.
>> >
>> >
>>
next prev parent reply other threads:[~2017-05-10 16:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 22:42 [bitcoin-dev] Some real-world results about the current Segwit Discount Sergio Demian Lerner
2017-05-08 23:47 ` Alphonse Pace
2017-05-09 13:49 ` Sergio Demian Lerner
2017-05-09 14:33 ` James Hilliard
2017-05-09 15:45 ` Johnson Lau
2017-05-09 16:19 ` Sergio Demian Lerner
2017-05-09 16:27 ` Johnson Lau
2017-05-09 16:27 ` James Hilliard
2017-05-09 18:15 ` Matt Corallo
2017-05-09 18:58 ` Sergio Demian Lerner
2017-05-09 19:15 ` Sergio Demian Lerner
2017-05-09 19:30 ` Gregory Maxwell
2017-05-09 19:42 ` Matt Corallo
2017-05-09 20:13 ` Gregory Maxwell
2017-05-09 20:58 ` Sergio Demian Lerner
2017-05-10 5:37 ` Jorge Timón
2017-05-10 14:05 ` Matt Corallo
2017-05-10 15:25 ` Sergio Demian Lerner
2017-05-10 16:39 ` Matt Corallo [this message]
2017-05-10 19:40 ` Sergio Demian Lerner
2017-05-08 23:56 ` Gregory Maxwell
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=B067643A-FBFD-4F59-B7AE-77769B9A9ACE@mattcorallo.com \
--to=lf-lists@mattcorallo.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=sergio.d.lerner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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