From: Peter Todd <pete@petertodd•org>
To: Chun Wang <1240902@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] The increase of max block size should be determined by block height instead of block time
Date: Sat, 19 Dec 2015 10:20:38 -0800 [thread overview]
Message-ID: <20151219182038.GA12893@muck> (raw)
In-Reply-To: <CAFzgq-xNZmWrdwCDv3twdsqSWk-FyMuLYJjZ_bA42_5Po0mgEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Sat, Dec 19, 2015 at 03:17:03AM +0800, Chun Wang via bitcoin-dev wrote:
> In many BIPs we have seen, include the latest BIP202, it is the block
> time that determine the max block size. From from pool's point of
> view, it cannot issue a job with a fixed ntime due to the existence of
> ntime roll. It is hard to issue a job with the max block size unknown.
> For developers, it is also easier to implement if max block size is a
> function of block height instead of time. Block height is also much
> more simple and elegant than time.
If size is calculated from the median time past, which is fixed for a
given block and has no dependency on the block header's nTime field,
does that solve your problem?
By "median time past" I mean the median time for the previous block.
--
'peter'[:-1]@petertodd.org
00000000000000000188b6321da7feae60d74c7b0becbdab3b1a0bd57f10947d
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
prev parent reply other threads:[~2015-12-19 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 19:17 Chun Wang
2015-12-18 19:52 ` Jorge Timón
2015-12-18 20:02 ` Jeff Garzik
2015-12-18 20:10 ` Jorge Timón
2015-12-18 20:15 ` Jeff Garzik
2015-12-18 20:20 ` Jorge Timón
2015-12-18 20:58 ` gb
2015-12-18 20:43 ` Peter Todd
2015-12-18 22:58 ` Jorge Timón
2015-12-19 18:20 ` Peter Todd [this message]
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=20151219182038.GA12893@muck \
--to=pete@petertodd$(echo .)org \
--cc=1240902@gmail$(echo .)com \
--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