From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A53B21055 for ; Sun, 18 Feb 2018 17:04:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9D211E6 for ; Sun, 18 Feb 2018 17:04:25 +0000 (UTC) Date: Sun, 18 Feb 2018 12:04:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1518973462; bh=HsLZ57uFlldDzIu3xIToWnmXqJUwN7XPM3s88So7S8g=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=T4B+wv33ZGpIH+8g11OrlL8NGgBW0V+qkYAalE4n2t/rrJOvRm2OnzhqjnYDyWqlC Rsnb9ZDQ6DkJP1KlmTceXVVTdoMujHUFiE6IwkWUZm4bGRz2PBuwteqB9AsIaasoPA iRMSQBGKiHNDvmeqb9QpSKXMPoAwjbv7jbR1/HZA= To: CANNON From: rhavar@protonmail.com Reply-To: rhavar@protonmail.com Message-ID: <9IZu22-jNUMzMcq7VK0qdzd2tj333lWOhOUe3A5V6OUaFlpQiS8lRFm-ZdGew4Im5KQ9qF4nF3WT3QugHMVrOi3Lr82FvyH9w-XG32NH7oQ=@protonmail.com> In-Reply-To: <640e2daf-343d-62be-d6da-a2c1b4bc2bfd@cannon-ciota.info> References: <640e2daf-343d-62be-d6da-a2c1b4bc2bfd@cannon-ciota.info> 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 18:27:42 +0000 Cc: Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 17:04:26 -0000 No, you are misunderstanding. The block size limit (1MB) has been replaced = in favor of a block weight limit (4M weight). Bytes which must be sent to o= ld clients are weighted at 4 units each which is what allows it to be a sof= t fork. So as such, there's not two separate limits or anything.=20 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 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 >