public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Upal Chakraborty <bitcoin@upalc.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] SegWit activation proposal with 2MB Hard Fork by next Block Halving on 2020
Date: Tue, 6 Jun 2017 02:00:23 +0530	[thread overview]
Message-ID: <CAED3CWg-Ss_4q6WzRh3ue+NP69Z8-xTztQw-=gO9Pc_j+pGiVg@mail.gmail.com> (raw)

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

*Proposal*: Verify whether 50% Tx mined from SegWit activation block to
block 630000 are SegWit Tx. If yes, increase legacy max block size to 2MB
and SegWit max block size to 8MB.

*Implementation*: This proposal either needs to be implemented in next
release of Bitcoin Core or require SegWit activation period restart while
it is implemented & released.

*Rationale*: This proposal minimizes the chance of a chain split, while
sticking to the original bitcoin scaling roadmap, i.e.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html


Thanks & Regards,
Upal Chakraborty

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

                 reply	other threads:[~2017-06-05 20:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAED3CWg-Ss_4q6WzRh3ue+NP69Z8-xTztQw-=gO9Pc_j+pGiVg@mail.gmail.com' \
    --to=bitcoin@upalc.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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