1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EDE3B7A8
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 1 Apr 2017 14:07:34 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f48.google.com (mail-vk0-f48.google.com
[209.85.213.48])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 81576E3
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 1 Apr 2017 14:07:34 +0000 (UTC)
Received: by mail-vk0-f48.google.com with SMTP id r69so109191081vke.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 01 Apr 2017 07:07:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-transfer-encoding;
bh=8F5jUTphNuBCNzwbonG496xTN+U7ucT/xM8DEYT4Ulc=;
b=bJo468ZxZQiJXGJXG+BPGa9QJLqSqX57jndj01o/Zy2+UddrkO+Cb8Wf9hNM1hkbca
vIXnv15zAZlEMFtHNHUX7XTQEk/sFOC7KL32bwQBud6hOIZFmG+/GGeV4qxp1y+krE+/
q1wII3np14j3oUobWUsGT6Y7NkBmXvBEUZ2KHrlpSQzI5Tpg8A+mP6nQBZfHDGy7v8MK
rUYPrvxxW0JmmOc/dmSnQaecbQjI6S+qXoG3vLRyS/acaOwifCh2GfyI0M0CT/8qOdlp
lQr9bwzjKgAwFequfoZpXCb9iYc73vigSLAh00vKdxrIGma7wSfjqGZk7/EZGCEkg3Km
8xig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-transfer-encoding;
bh=8F5jUTphNuBCNzwbonG496xTN+U7ucT/xM8DEYT4Ulc=;
b=L8moUlSW6CINynTQWto0AyQ9PfPJeX8Y0YezeaHixw8x6yedGwq63uWxVS5SRjO0VZ
5rbASpWwPnSMm40sN/U6oOyyKZQZhI+10DtqQa6p1mvYlZlrtgFcyjwZyAvk8P0/ob1g
kempVTJlaRWPmOFBxKl5smlCUDl3a+8Hagr1fUNhWGi7/W2gXJ1E3vF2JAq1+LCWRKS8
tnJ6qS/Q4KBpsn21zdfAojSHAaO+qg5Bdu0TYHd5T5RhhaRu6Z0KGxu9LQbWX27VmPnI
jNeDQvpyEWq7+jnoBDBCIaql4SAntVgh/1+ylFzKlWxBnzRp0N9GpPlxbP5EKnrHPqf7
Yecw==
X-Gm-Message-State: AFeK/H0h4LTu5uxAJtMsoN06zT22scBQYoiNlWHBxzpuzYAm4lm9H0O1ObQct1whDhZzPTNQ8fWbooZTxgL47Q==
X-Received: by 10.31.234.3 with SMTP id i3mr3928583vkh.36.1491055653480; Sat,
01 Apr 2017 07:07:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.151.136 with HTTP; Sat, 1 Apr 2017 07:07:32 -0700 (PDT)
In-Reply-To: <CAAt2M19PvHLY0PA6iy+wiPg10vqONDApTLDuxzEcte=KUZLoaQ@mail.gmail.com>
References: <CAKzdR-oN6tGvGSb04_awCf=Jsf3wgKJN5xUhCr8G2D2W9YgJww@mail.gmail.com>
<1CF1FD5D-8D29-4783-823F-B3F588D5C5CE@mattcorallo.com>
<CAD1TkXse5O6nEw9-EPsNp4c56YJ+OnM=F1uf8w+tyB=_+hFzFQ@mail.gmail.com>
<CAKzdR-rFJNOZ856rA_q8C=zEUj_X561OSOwW+KZr4nRJ51w3HA@mail.gmail.com>
<CABm2gDrAHo2P7t6SjituURqMUqs_=Lbp7X=g_j8nGoNKMKCRKQ@mail.gmail.com>
<CAAt2M19PvHLY0PA6iy+wiPg10vqONDApTLDuxzEcte=KUZLoaQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Sat, 1 Apr 2017 16:07:32 +0200
Message-ID: <CABm2gDqw2TayGvaH_nz3jrF8Cz2V=SbB4begD6+K=Ye=Msw4mg@mail.gmail.com>
To: Natanael <natanael.l@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segwit2Mb - combined soft/hard fork - Request For
Comments
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Apr 2017 14:07:35 -0000
On Sat, Apr 1, 2017 at 3:15 PM, Natanael <natanael.l@gmail.com> wrote:
>
>
> Den 1 apr. 2017 14:33 skrev "Jorge Tim=C3=B3n 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 wou=
ld
> 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. The weight is also the only notion of cost miners need
to consider when comparing txs by feerate (fee per cost, before segwit
tx_fee/tx_size, post-segwit tx_fee/tx_weight).
This is important to remember, because having 2 separated limits or
costs would make block creation and relay policies much harder to
implement.
Therefore a hardfork after segwit can just increase the weight limit
and completely forget about the pre-segwit 1 mb size limit.
|
