From: Sergio Demian Lerner <sergio.d.lerner@gmail•com>
To: Johnson Lau <jl2012@xbt•hk>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Some real-world results about the current Segwit Discount
Date: Tue, 9 May 2017 13:19:13 -0300 [thread overview]
Message-ID: <CAKzdR-rKQaiKF18j44HjxuHY5pcmPwsce5ab-+zGRDnxjhBQdw@mail.gmail.com> (raw)
In-Reply-To: <7B918396-5968-4908-83C8-0F77DA8DB037@xbt.hk>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
Thanks Johnson and Hampus for the clarifications.
However, I would rather do the opposite: soft-fork to 50% now, and
soft-fork again to 75% discount later if needed, because it doesn't affect
the max transactions/second.
Segwit as it is today should be activated. However if it is not before
November, then for the next Segwit attempt I would choose a more
conservative 50% discount.
On Tue, May 9, 2017 at 12:45 PM, Johnson Lau <jl2012@xbt•hk> wrote:
>
> > On 9 May 2017, at 21:49, Sergio Demian Lerner via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
> >
> >
> > So it seems the 75% discount has been chosen with the idea that in the
> future the current transaction pattern will shift towards multisigs. This
> is not a bad idea, as it's the only direction Bitcoin can scale without a
> HF.
> > But it's a bad idea if we end up doing, for example, a 2X blocksize
> increase HF in the future. In that case it's much better to use a 50%
> witness discount, and do not make scaling risky by making the worse case
> block size 8 Mbytes, when it could have been 2*2.7=5.4 Mbytes.
> >
>
> As we could change any parameter in a hardfork, I don’t think this has any
> relation with the current BIP141 proposal. We could just use 75% in a
> softfork, and change that to a different value (or completely redefine the
> definition of weight) with a hardfork later.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1903 bytes --]
next prev parent reply other threads:[~2017-05-09 16:19 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 [this message]
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
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-rKQaiKF18j44HjxuHY5pcmPwsce5ab-+zGRDnxjhBQdw@mail.gmail.com \
--to=sergio.d.lerner@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jl2012@xbt$(echo .)hk \
/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