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 894A4EB2 for ; Fri, 4 Sep 2015 15:37:40 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 17570223 for ; Fri, 4 Sep 2015 15:37:40 +0000 (UTC) Received: by pacfv12 with SMTP id fv12so28062973pac.2 for ; Fri, 04 Sep 2015 08:37:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=e4ghbmq6S64WP6GwZ7S71r00waAbGnxenKZI8r8DxLU=; b=T3+lrSIC+R2sje/iNsC/2DZLgJ3IGnERQK3XA7mfEoWEcb9o5ZlUYv1rt//GxAx8oC 6K7vIieKj/dBFccOj257A8PR9rxifMhORKQV8Rp2T1rj9/BZlw5FjtYefIK1A85NxXg0 zS9aecI2wdjNjnMQn5h2FFqDP4iNKFdxeZI1A7zC+rZJ7LtPBzBnIzUCNnCfpcZ0C+8y GA8wl3j9eMLXaalJqZkNTWp3+yQT0zzuePcGqo9s8edkZmFBT/rl1ojtr5SmkYJN0TJx fNenL2EBgX75lceWyVq1EctGCDBe52bKsYY3k8Z5CQaM8a4LCt7A6lMsihGHmB9DWPqJ jtPg== X-Gm-Message-State: ALoCoQl1lORexwRm8VX0U0ngEKgvWbs+wQ64ToJscBBgFJM6+IPI/2c60UoWZv5jHVWh72HZeBUU X-Received: by 10.66.159.162 with SMTP id xd2mr9388779pab.91.1441381059678; Fri, 04 Sep 2015 08:37:39 -0700 (PDT) Received: from [192.168.2.13] (c-24-5-43-190.hsd1.ca.comcast.net. [24.5.43.190]) by smtp.googlemail.com with ESMTPSA id jv5sm2918826pbc.47.2015.09.04.08.37.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Sep 2015 08:37:33 -0700 (PDT) Message-ID: <55E9BABD.7080505@bitcartel.com> Date: Fri, 04 Sep 2015 08:37:33 -0700 From: Simon Liu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Andy Chase , Tier Nolan , jgarzik@gmail.com, bitcoin-dev@lists.linuxfoundation.org References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 Subject: Re: [bitcoin-dev] BIP 100 specification X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2015 15:37:40 -0000 Maybe grab some code from BIP101 ? It permits block messages > 2MB, while retaining the current limit of 2 MB imposed on other network messages. The 32 MB limit was patched a few months ago. Links to code: https://www.reddit.com/r/bitcoinxt/comments/3in5mm/psa_correction_to_btcchina_letter_which_states/ On 09/04/2015 12:53 AM, Andy Chase via bitcoin-dev wrote: > The 32Mb limit is > here: https://github.com/bitcoin/bitcoin/blob/master/src/serialize.h#L25 > > It's to keep the message size small enough that messages can be > serialized in memory. > > Jeff if you decide to lift the 32MB limit (you really should, unless > your plan is to potentially hard force another Blocksize discussion > again which might be okay). I suggest having the 32MB ceiling auto-raise > according to a exponential factor (1.5?) starting 1 year from now. > > Basically hard limit ceiling 2016-2017: 32 MB > Hard limit ceiling 2018+: 32*((currentYear-2018)*1.5) MB > > The factor could be 2 like BIP-101 but I imagine you will want to be > more conservative. The delay time could also be longer if you think it > will take longer to fix the message size issue across all implementations. >