Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of
	national.shitposting.agency designates 75.102.27.230 as
	permitted sender) client-ip=75.102.27.230;
	envelope-from=insecurity@national.shitposting.agency;
	helo=mail.cock.li; 
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 11 May 2015 08:50:20 +0000
From: insecurity@national.shitposting.agency
To: sergiolerner@certimix.com
Message-ID: <0cda31e339cfa74351ff7264ac07b406@national.shitposting.agency>
User-Agent: Roundcube Webmail/0.9.5
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development]
 =?utf-8?q?Reducing_the_block_rate_instead_o?=
 =?utf-8?q?f_increasing=09the_maximum_block_size?=
Precedence: list

> So if the server pushes new block
> header candidates to clients, then the problem boils down to increasing
> bandwidth of the servers to achieve a tenfold increase in work
> distribution.

Most Stratum pools already do multiple updates of the header every block 
period,
bandwidth is really inconsequential, it's the latency that kills. At the 
present
time you are looking up to 15 seconds between the first and last pools 
to push
headers to their clients for the latest block. It's sort of 
inconsequential with
a 10 minute block time, but it cuts into a 1 minute one very heavily.

Some pools already don't do their own validation of blocks, but simply 
mirror
other pools, pushing them to be even more latency focused will just make 
this an
epidemic of invalidity rather than a solution.


> There are several proof-of-work cryptocurrencies in existence
> that have lower than 1 minute block intervals and they work just fine.
> First there was Bitcoin with a 10 minute interval, then was LiteCoin
> using a 2.5 interval, then was DogeCoin with 1 minute, and then
> QuarkCoin with just 30 seconds.

You can't really use these as examples of things going just fine. None 
of these
networks see anything approaching the Bitcoin transaction volume and 
none have
even remotely the same network size. Some Bitcoin forks use floats in 
consensus
critical code and work "just fine", for the moment. We can't justify 
poor
decisions with "but the altcoins are doing it".

Is there even a single study of the stale rates within these networks?