From: Natanael <natanael.l@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
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 17:34:24 +0200 [thread overview]
Message-ID: <CAAt2M1835S3YYJ_p0_zvDR9U6EfYAt7SWTAEPNHnNfgstKpgMg@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M18=Tjw+05QCv6G7Abv=idB6ONgU9xvtrR=fn731452_mg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
Den 1 apr. 2017 16:07 skrev "Jorge Timón" <jtimon@jtimon•cc>:
On Sat, Apr 1, 2017 at 3:15 PM, Natanael <natanael.l@gmail•com> wrote:
>
>
> 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.
No, because of the way the weight is calculated, it is impossible to
create a block that old nodes would perceive as bigger than 1 mb
without also violating the weight limit.
After segwit activation, nodes supporting segwit don't need to
validate the 1 mb size limit anymore as long as they validate the
weight limit.
https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#Block_size
Huh, that's odd. It really does still count raw blockchain data blocksize.
It just uses a ratio between how many units each byte is worth for block
data vs signature data, plus a cap to define the maximum. So the current
max is 4 MB, with 1 MB of non-witness blockchain data being weighted to 4x
= 4 MB. That just means you replaced the two limits with one limit and a
ratio.
A hardfork increasing the size would likely have the ratio modified too.
With exactly the same effect as if it was two limits...
Either way, there's still going to be non-segwit nodes for ages.
[-- Attachment #2: Type: text/html, Size: 2976 bytes --]
next prev parent reply other threads:[~2017-04-01 15:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 21:09 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 [this message]
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=CAAt2M1835S3YYJ_p0_zvDR9U6EfYAt7SWTAEPNHnNfgstKpgMg@mail.gmail.com \
--to=natanael.l@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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