From: Btc Drak <btcdrak@gmail•com>
To: Simon Liu <simon@bitcartel•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 100 specification
Date: Fri, 4 Sep 2015 16:40:26 +0100 [thread overview]
Message-ID: <CADJgMzvM4ZfjktS9KwbtJ52x5Ea75OXy9c_ngTCXyAw7uDyB1g@mail.gmail.com> (raw)
In-Reply-To: <55E9BABD.7080505@bitcartel.com>
If you read between the lines of what was recently changed and why
(reducing to 2MB), it seems reasonable to assume BIP101's allowance
opens up some of the attack vector again.
On Fri, Sep 4, 2015 at 4:37 PM, Simon Liu via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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.
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-09-04 15:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 3:33 Jeff Garzik
2015-09-03 4:45 ` Dave Scotese
2015-09-03 7:57 ` jl2012
2015-09-03 11:20 ` Btc Drak
2015-09-03 14:34 ` Jeff Garzik
2015-09-03 15:58 ` Btc Drak
2015-09-03 16:13 ` Jorge Timón
2015-09-03 11:59 ` Tier Nolan
2015-09-03 16:32 ` jl2012
2015-09-03 16:35 ` Jeff Garzik
2015-09-03 17:32 ` Btc Drak
2015-09-03 17:52 ` Peter Todd
2015-09-04 7:53 ` Andy Chase
2015-09-04 15:37 ` Simon Liu
2015-09-04 15:40 ` Btc Drak [this message]
2015-09-03 14:35 ` Jeff Garzik
2015-09-03 19:40 ` Simon Liu
2015-09-03 20:15 ` Oliver Petruzel
2015-09-03 20:34 ` Dave Scotese
2015-09-04 3:50 ` Peter Todd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADJgMzvM4ZfjktS9KwbtJ52x5Ea75OXy9c_ngTCXyAw7uDyB1g@mail.gmail.com \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=simon@bitcartel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox