public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] The increase of max block size should be determined by block height instead of block time
@ 2015-12-18 19:17 Chun Wang
  2015-12-18 19:52 ` Jorge Timón
  2015-12-19 18:20 ` Peter Todd
  0 siblings, 2 replies; 10+ messages in thread
From: Chun Wang @ 2015-12-18 19:17 UTC (permalink / raw)
  To: bitcoin-dev

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.


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2015-12-19 18:20 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-18 19:17 [bitcoin-dev] The increase of max block size should be determined by block height instead of block time 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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox