From: Sergio Demian Lerner <sergio.d.lerner@gmail•com>
To: Matt Corallo <lf-lists@mattcorallo•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 12:25:27 -0300 [thread overview]
Message-ID: <CAKzdR-r=y=myz60v9FnYr3tJbW9LgNQkAoA9+F-+jaLScg2PJw@mail.gmail.com> (raw)
In-Reply-To: <b24b84bf-315c-1463-acee-4b6edab41d52@mattcorallo.com>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
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.
> >
> >
>
[-- Attachment #2: Type: text/html, Size: 2229 bytes --]
next prev parent reply other threads:[~2017-05-10 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 22:42 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 [this message]
2017-05-10 16:39 ` Matt Corallo
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='CAKzdR-r=y=myz60v9FnYr3tJbW9LgNQkAoA9+F-+jaLScg2PJw@mail.gmail.com' \
--to=sergio.d.lerner@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(echo .)com \
/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