From: jl2012@xbt•hk
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 102 - kick the can down the road to 2MB
Date: Wed, 22 Jul 2015 17:00:41 +0000 [thread overview]
Message-ID: <20150722170041.Horde.N2psXR0k1XYN4_s0phBwGg1@server47.web-hosting.com> (raw)
In-Reply-To: <20150721130412.GA4551@savin.petertodd.org>
Quoting Peter Todd via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>:
>
> Having said that, in general triggering events without verifying a
> supermajority of miner support can be very dangerous. Without miner
> support the chain is insecure, and can be attacked. For instance a
> blocksize limit increase that a majority of miners choose not to
> implement raises huge risks of reorg for any miners who attempt to
> create large blocks, and huge risks of payment reversal for any
> merchants accepting transactions in such blocks. Note how with BIP102,
> extending the original Bitcoin chain is inherently an attack on the
> Garzik chain.
>
> For that reason I think BIP102 is extremely poorly designed. I can only
> conclude that Jeff Garzik is either deliberately trolling us and/or
> manipulating discussion with a badly designed proposal that he doesn't
> actually expect to be adopted verbatim, or is incompetent.
>
> --
> 'peter'[:-1]@petertodd.org
> 0000000000000000031c12b6af038524fd5dd28115b7f5591e046423cebaf6d1
To avoid any risk of reorg, the hardfork may require that the first
block with GetMedianTimePast() after a pre-determined time (the "flag
block") MUST be version 0. The exception is applied ONLY to the flag
block.
Alternatively, the hardfork may require that the flag block MUST be
larger than 1MB. Comparing with exploiting the block version, this
does not require additional exceptions in consensus rules. However,
miner may need to artificially inflate the size of the flag block and
that could be trouble in coding. I don't have any preference.
Old nodes will not accept the new chain because it violates BIP66 /
block size limit. New nodes will not accept the old chain because its
flag block is not version 0 / not larger than 1MB.
This is actually checkpointing in a decentralized way. In that case,
we can say goodbye to the old chain forever, as long as all major
merchants and exchanges agree to upgrade. Miner support is less
relevant. It is a no-brainer for miners to support the new chain,
unless they don't want to sell or spend their bitcoin, or just give up
mining after heavily investing in ASIC.
jl2012
next prev parent reply other threads:[~2015-07-22 17:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 15:55 Jeff Garzik
2015-07-17 16:11 ` Andrew
2015-07-17 16:12 ` Tier Nolan
2015-07-17 16:14 ` Tier Nolan
2015-07-17 17:57 ` Ross Nicoll
2015-07-17 19:06 ` Chris Wardell
2015-07-17 19:13 ` Ross Nicoll
2015-07-19 22:51 ` Ross Nicoll
2015-07-21 9:26 ` Jorge Timón
2015-07-21 13:04 ` Peter Todd
2015-07-21 13:58 ` Peter Todd
2015-07-22 15:51 ` Tom Harding
2015-07-22 17:02 ` Sriram Karra
2015-07-22 17:40 ` Sriram Karra
2015-07-22 17:43 ` Jeff Garzik
2015-07-22 22:30 ` Peter Todd
2015-07-23 5:39 ` jl2012
2015-07-22 17:00 ` jl2012 [this message]
2015-07-21 22:05 ` Ross Nicoll
2015-07-23 11:24 ` Jorge Timón
2015-07-17 20:29 ` Luke Dashjr
2015-07-17 21:13 ` Angel Leon
2015-07-17 22:25 ` Tier Nolan
2015-07-18 9:22 ` Jorge Timón
2015-07-18 9:24 ` Jorge Timón
2015-07-24 8:52 ` Thomas Zander
2015-07-24 9:43 ` Slurms MacKenzie
2015-07-18 4:32 ` Venzen Khaosan
2015-07-17 22:40 Raystonn
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=20150722170041.Horde.N2psXR0k1XYN4_s0phBwGg1@server47.web-hosting.com \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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