Round time and block size

Consensus
#1

In each round, a validator takes the role of leader and proposes a block of transactions to
extend a certified sequence of blocks (see quorum certificates below) that contain the full previous
transaction history.

Does anyone know what is the average time value of each round?
And similarly, what is the default expiring time of a round a leader node has to follow?

And from what I understood, in the Libra Blockchain:

There is no concept of a block of transactions in the ledger history.

But do we have an estimation of the average size of blocks generated by the network?

1 Like
#2

Thanks for your questions. Answers below:

Does anyone know what is the average time value of each round?
And similarly, what is the default expiring time of a round a leader node has to follow?

A round that is successful (i.e. gathers a QC) depends on the network speeds to send a proposal and gather votes. The timeouts of a round are configurable and grow according to a formula according to the number of rounds since commit. You can see ExponentialTimeInterval for details (https://github.com/libra/libra/blob/master/consensus/src/chained_bft/liveness/local_pacemaker.rs#L84)

But do we have an estimation of the average size of blocks generated by the network?

Providing a concrete number is difficult as the block size depends on workload and the speed to gather a QC.

4 Likes