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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
Return-Path: <rhavar@protonmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 041EF120B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 18 Feb 2018 19:05:10 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 133DDFE
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 18 Feb 2018 19:05:08 +0000 (UTC)
Date: Sun, 18 Feb 2018 14:04:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=default; t=1518980705;
bh=T3HKk7vJDddKRHqxGbZNEOtzU8Aoj6ltaRTvCRQmgSI=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:
Feedback-ID:From;
b=TF8MuYUaP2dgEhswXrFHvtVlgQCz9kXNP1yH38PJtPnr9FsjDinBr96Sjgu2w40m9
R30YCPXKete7wWjn+f6Y2aw4NyMU+VcUvZi8O/Wk9f1lVIKgpmYDzJmtcblG/CmEpE
ziL4SMqdLRE9lrH5pI2jSx1jKJ7+ChPKuzG4WjoA=
To: Eric Voskuil <eric@voskuil.org>
From: rhavar@protonmail.com
Reply-To: rhavar@protonmail.com
Message-ID: <Jy0MuLuWihgu3VcuWL_kxYtFK-JTx0u17G3MhQw1EIp4sXTNWBMfhoNruAfrPp3A17HRNXwpbTIAXiTBKHYOKgf3LFfUZEXoglp5VSiC3wc=@protonmail.com>
In-Reply-To: <5E8E7227-8F90-40A2-B3D6-CA9D03CD3FEC@voskuil.org>
References: <640e2daf-343d-62be-d6da-a2c1b4bc2bfd@cannon-ciota.info>
<9IZu22-jNUMzMcq7VK0qdzd2tj333lWOhOUe3A5V6OUaFlpQiS8lRFm-ZdGew4Im5KQ9qF4nF3WT3QugHMVrOi3Lr82FvyH9w-XG32NH7oQ=@protonmail.com>
<5E8E7227-8F90-40A2-B3D6-CA9D03CD3FEC@voskuil.org>
Feedback-ID: RdfuD--Ffc-FNb_4UIG1XA3s5stj1f6Yt84KENdha_3WoiW3STYpu7X5uGR72LvTfQZpxEhSRHGSlNfV5XM5RA==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sun, 18 Feb 2018 19:06:14 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Increased blockspace enabled by SegWit limited to
just witness data?
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: Sun, 18 Feb 2018 19:05:10 -0000
> No rule has been =E2=80=9Creplaced=E2=80=9D.
It really has been. The code is no longer checks the size of a block, but t=
he weight of it. For all intents and purposes the block size limits has bee=
n replaced in favor of a block weight limit. It's just been designed such t=
hat the new rule is more restrictive than the one it replaces.
Now, I'm not doubting you can argue the semantics on the difference between=
"replacing with a more restrictive rule" and "leaving the existing rules, =
but adding a new one" -- but it's uninteresting and only serves to confuse =
novice's like CANNON into thinking that there are two rules/spaces/limits f=
or transactions.
=E2=80=8B-Ryan
=E2=80=8B
-------- Original Message --------
On February 18, 2018 1:39 PM, Eric Voskuil <eric@voskuil.org> wrote:
>As a soft fork, all preceding rules remain in effect. No rule has been =
=E2=80=9Creplaced=E2=80=9D. Blocks must validate against pre-segwit rules o=
r are invalid. Additional rules are applied that further restrict validity,=
and consider additional (witness) data in the context of the block.
>
> e
>
>>On Feb 18, 2018, at 09:04, Ryan Havar via bitcoin-dev bitcoin-dev@lists.l=
inuxfoundation.org wrote:
>>No, you are misunderstanding. The block size limit (1MB) has been replace=
d in favor of a block weight limit (4M weight). Bytes which must be sent to=
old clients are weighted at 4 units each which is what allows it to be a s=
oft fork.
>>So as such, there's not two separate limits or anything.
>>P.S. what's up with your signature lol
>>=E2=80=8B-Ryan
>>=E2=80=8B
>>-------- Original Message --------
>>>On February 18, 2018 11:26 AM, CANNON via bitcoin-dev bitcoin-dev@lists.=
linuxfoundation.org wrote:
>>>-----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA512
>>>I have a question in reference to the increased blockspace enabled
>>> by the segregated witness upgrade. Is this extra blockspace beyond
>>> the legacy 1 MB limit limited to just witness data?
>>>Cannon
>>> PGP Fingerprint: 2BB5 15CD 66E7 4E28 45DC 6494 A5A2 2879 3F06 E832
>>> Email: cannon@cannon-ciota.info
>>>NOTICE: ALL EMAIL CORRESPONDENCE NOT SIGNED/ENCRYPTED WITH PGP SHOULD
>>> BE CONSIDERED POTENTIALLY FORGED, AND NOT PRIVATE.
>>> -----BEGIN PGP SIGNATURE-----
>>>iQIcBAEBCgAGBQJaiajLAAoJEAYDai9lH2mwDbMQAKgJseZG9oOoP9WJlESFdAzm
>>> jLM69KLF4RVWDQjMWCtyVayyolXMLavW6fL4GL7/ztLYSl9Pz+FDlH3Qgo1GLDx4
>>> fRUkmb0ApLBSAjmdqM+kWjgq3s6/oZaIkNxGeyK5SYY4QhF80Z42PWLBPKjAc7vn
>>> pe7Im13NwtyJiRuCmq4e1z6GmW86fFOKOsR4rlWcftHOFmH8Gz5d9KK9LbPqU6Ca
>>> +rde8yb+A9uXEv3O9MqeLId7FYSJixgzFGJosidVkAVQI7YZ0TAfG4HSwKjtqDz7
>>> SW2Bs3nDeiCr2QN7Su9TUaoSN/yKTBOw5jnql9cNOYuf4GAG0MXWinmYP8MWCiqh
>>> bIrzvOnlZGapX/36Fpab67VDcFnXJJc8ofqYmn+oUoW/q7geQpu/V1oz+AR9nD/d
>>> n8wFxvZdRlTbq2XDXySaontxNH0rd80fSG5SJtO5Js9hK/vNG+Xa7Zc+76gEtvlF
>>> 5G1F6MOcsoXUDCnMteuNxaZx6TPML6RuWVmbR1wXOaX4qZ01p7AsjQlTIcrlVDsB
>>> LVGW70wjfETBCffn1JQvFmIK7NzggIUuYfLF0IrfM4BrTa/01RnmfBOpWGiIvyIG
>>> qZqKLYDbW7BDkc/HMtAonR/0t6bTUv/388USSnbMakO9bvih0xxIw4NWTyoSoef/
>>> I+W6ny7qXt+pegLF4cYL
>>> =3DYqEM
>>> -----END PGP SIGNATURE-----
>>>bitcoin-dev mailing list
>>>bitcoin-dev@lists.linuxfoundation.org
>>>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>>bitcoin-dev mailing list
>>bitcoin-dev@lists.linuxfoundation.org
>>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
|
