Aura - Authority Round - Wiki Parity Tech Documentation

Aura (Authority Round) is one of the Blockchain consensus algorithms available in Parity.

Parameters

Description

Time is divided into discrete steps of duration , determined by . At each step , a primary will be assigned. Only the primary at a step may issue a block. It is misbehavior to produce more than one block per step or to produce a block out of turn.

The primary for a step is the node with index: .

The protocol contains a chain scoring rule for a given chain .

On each step, each honest node will propagate the chain with the highest score it knows about to all other nodes. Honest primaries will only issue blocks on top of the best chain they are aware of during their turn.

Finality

Under the assumption of a synchronous network which propagates messages within the step duration , let be the set of signatures from all authors in the set of blocks :

If there is a valid chain ending with , where , then and all of its ancestors are finalized.

This definition of finality stems from a simple majority vote. In this setting, , so the faulty nodes cannot finalize a block all on their own.

Empty steps

In order to reach finality in a timely fashion it is necessary for the nodes to keep sealing blocks even when there are no transactions. To reduce blockchain bloat while still maintaining the same finality guarantees the nodes can sign and broadcast an EmptyStep(step, parent_hash) message instead of producing an empty block. All of the nodes accumulate the broadcasted empty step messages and they are included and rewarded in the next non-empty block.

The empty step messages included in blocks are also taken into account for finality.

To enable empty step messages set the emptyStepsTransition to enable it at the given block number. You can also specify a maximum number of empty steps with maximumEmptySteps in your chain spec.

Node Configuration

This consensus requires a ValidatorSet to be specified, which determines the list of blockchain addresses at each height which participate in the consensus.

A node can represent a validator when it is run with --engine-signer VALIDATOR-ADDRESS.

The consensus can be run with --force-sealing which ensures that blocks are produced even if there are no transactions. This is necessary for blocks to reach finality in a timely fashion.

Wishlist