Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
From: Eric Voskuil <eric@voskuil.org>
In-Reply-To: <Jy0MuLuWihgu3VcuWL_kxYtFK-JTx0u17G3MhQw1EIp4sXTNWBMfhoNruAfrPp3A17HRNXwpbTIAXiTBKHYOKgf3LFfUZEXoglp5VSiC3wc=@protonmail.com>
Date: Sun, 18 Feb 2018 11:14:22 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <54BE283E-5DD2-4BD4-9218-DD9E9AFC8A99@voskuil.org>
References: <640e2daf-343d-62be-d6da-a2c1b4bc2bfd@cannon-ciota.info>
	<9IZu22-jNUMzMcq7VK0qdzd2tj333lWOhOUe3A5V6OUaFlpQiS8lRFm-ZdGew4Im5KQ9qF4nF3WT3QugHMVrOi3Lr82FvyH9w-XG32NH7oQ=@protonmail.com>
	<5E8E7227-8F90-40A2-B3D6-CA9D03CD3FEC@voskuil.org>
	<Jy0MuLuWihgu3VcuWL_kxYtFK-JTx0u17G3MhQw1EIp4sXTNWBMfhoNruAfrPp3A17HRNXwpbTIAXiTBKHYOKgf3LFfUZEXoglp5VSiC3wc=@protonmail.com>
To: rhavar@protonmail.com
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Increased blockspace enabled by SegWit limited to
	just witness data?
Precedence: list

If the new rule is more restrictive the original limit remains.

e

On Feb 18, 2018, at 11:04, rhavar@protonmail.com wrote:

>> No rule has been =E2=80=9Creplaced=E2=80=9D.
>=20
> 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 been=
 replaced in favor of a block weight limit. It's just been designed such tha=
t the new rule is more restrictive than the one it replaces.
>=20
> Now, I'm not doubting you can argue the semantics on the difference betwee=
n "replacing with a more restrictive rule" and "leaving the existing rules, b=
ut adding a new one" -- but it's uninteresting and only serves to confuse no=
vice's like CANNON into thinking that there are two rules/spaces/limits for t=
ransactions.
>=20
>=20
>=20
> =E2=80=8B-Ryan
>=20
> =E2=80=8B
>=20
> -------- Original Message --------
>> On February 18, 2018 1:39 PM, Eric Voskuil <eric@voskuil.org> wrote:
>>=20
>> 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 or ar=
e invalid. Additional rules are applied that further restrict validity, and c=
onsider additional (witness) data in the context of the block.
>>=20
>> e
>>=20
>>> On Feb 18, 2018, at 09:04, Ryan Havar via bitcoin-dev bitcoin-dev@lists.=
linuxfoundation.org wrote:
>>> No, you are misunderstanding. The block size limit (1MB) has been replac=
ed 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 so=
ft 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
>>>>=20
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>=20
>>=20
>=20