From: Oliver Petruzel <opetruzel@gmail.com>
To: Erik Aronesty <erik@q32.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segwit2Mb - combined soft/hard fork - Request For Comments
Date: Sat, 3 Jun 2017 17:05:23 -0400 [thread overview]
Message-ID: <CALhpmH1RHRWagteFTm+_HM4t2wBQEV60qO0AkL3_pPKPy2D+tw@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgLmhWG6YjobTDS-F+ER2sr1tW38tjQZy=5LHt-YikEj6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
>>2.1MB capacity in August via segwit, with 4MB weight, and 4.2MB capacity
in December with 8MB<<
I'm not sure how many people to not of the draft BIP I submitted to the
list in early April. It was essentially a combination of Gavin's BIP 109,
Adam's 2-4-8 idea, and something I added to SegWit that I call "Discount
Governing."
It basically takes the idea of gradual increases one step farther: a
gradual increase of both the Total weight and SegWit discount rate over a
period of X years (a schedule of Flag Day + X blocks increases).
Would this be something that some in the dev community might consider
if/when SegWit is combined with a block increase?
Original draft here:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/
2017-April/013984.html
Ollie
[-- Attachment #2: Type: text/html, Size: 1463 bytes --]
next prev parent reply other threads:[~2017-06-03 21:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 21:09 [bitcoin-dev] Segwit2Mb - combined soft/hard fork - Request For Comments Sergio Demian Lerner
2017-03-31 21:18 ` Matt Corallo
2017-03-31 21:22 ` praxeology_guy
2017-03-31 21:50 ` Sergio Demian Lerner
2017-03-31 21:22 ` Matt Corallo
2017-03-31 22:13 ` Sergio Demian Lerner
2017-04-01 3:03 ` Samson Mow
2017-04-01 3:35 ` Sergio Demian Lerner
2017-06-02 20:04 ` Erik Aronesty
2017-04-01 6:55 ` Jared Lee Richardson
2017-04-01 11:44 ` Sergio Demian Lerner
2017-04-01 12:33 ` Jorge Timón
2017-04-01 13:15 ` Natanael
2017-04-01 14:07 ` Jorge Timón
[not found] ` <CAAt2M1_gDzEuDLSvVsJARvdCAtUyM3Yuu7TT25sbm3L-Zi6+0Q@mail.gmail.com>
[not found] ` <CAAt2M18=Tjw+05QCv6G7Abv=idB6ONgU9xvtrR=fn731452_mg@mail.gmail.com>
2017-04-01 15:34 ` Natanael
2017-04-02 4:57 ` Jorge Timón
2017-04-02 10:03 ` Natanael
2017-04-02 11:43 ` Jorge Timón
2017-06-02 20:04 ` Erik Aronesty
2017-06-02 21:51 ` Sergio Demian Lerner
2017-06-03 0:53 ` Erik Aronesty
2017-06-03 2:03 ` Oliver Petruzel
2017-06-03 21:05 ` Oliver Petruzel [this message]
2017-04-03 14:40 ` Btc Drak
2017-04-06 2:27 ` Erik Aronesty
2017-04-06 20:58 ` Sergio Demian Lerner
2017-04-06 20:42 ` Sergio Demian Lerner
2017-04-06 21:03 ` Sergio Demian Lerner
2017-04-06 22:29 ` Aymeric Vitte
2017-06-02 12:29 ` R E Broadley
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=CALhpmH1RHRWagteFTm+_HM4t2wBQEV60qO0AkL3_pPKPy2D+tw@mail.gmail.com \
--to=opetruzel@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=erik@q32.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