Batching of transactions

[mikera]

It has been noted in cloud tests that Peers are often creating blocks with small number of transactions, which is likely to be suboptimal for throughput and consensus efficiency (we want many transactions per block)

Most promising design solution is likely to be to have a Peer avoid publishing blocks when an existing block from that Peer is already in flight (either until final confirmation, or to some advanced consensus stage.