From: Natanael <natanael.l@gmail.com>
To: "Jorge Timón" <jtimon@jtimon.cc>,
"Bitcoin Dev" <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segwit2Mb - combined soft/hard fork - Request For Comments
Date: Sat, 1 Apr 2017 15:15:15 +0200 [thread overview]
Message-ID: <CAAt2M19PvHLY0PA6iy+wiPg10vqONDApTLDuxzEcte=KUZLoaQ@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDrAHo2P7t6SjituURqMUqs_=Lbp7X=g_j8nGoNKMKCRKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Den 1 apr. 2017 14:33 skrev "Jorge Timón via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org>:
Segwit replaces the 1 mb size limit with a weight limit of 4 mb.
That would make it a hardfork, not a softfork, if done exactly as you say.
Segwit only separates out signature data. The 1 MB limit remains, but would
now only cover the contents of the transaction scripts. With segwit that
means we have two (2) size limits, not one. This is important to remember.
Even with segwit + MAST for large complex scripts, there's still going to
be a very low limit to the total number of possible transactions per block.
And not all transactions will get the same space savings.
[-- Attachment #2: Type: text/html, Size: 1128 bytes --]
next prev parent reply other threads:[~2017-04-01 13:15 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 [this message]
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
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='CAAt2M19PvHLY0PA6iy+wiPg10vqONDApTLDuxzEcte=KUZLoaQ@mail.gmail.com' \
--to=natanael.l@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jtimon@jtimon.cc \
/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