Module Mavryk_raw_protocol_001_PtAtLas.Amendment

Amendments and proposals.

Only delegates having the minimal required stake take part in the amendment procedure. It works as follows:

The current protocol parameters are documented in src/proto_alpha/lib_parameters/default_parameters.ml

In practice, the real constants used are defined in the migration code. In src/proto_alpha/lib_protocol/init_storage.ml, function prepare_first_block introduces new constants and redefines the existing ones.

If at the end of a voting period, moves to the next one following the state machine of the amendment procedure.

Return the registered testchain dictator, if any. This function will always return None on mainnet.

Check whether the given public key hash corresponds to the registered testchain dictator, if any. This function will always return false on mainnet.

Application of voting operations

There are two kinds of voting operations:

Update the context with the effects of a Proposals operation:

  • Its proposals are added to the source's recorded proposals.
  • The recorded proposal count of the source is increased by the number of proposals in the operation.

Note that a Proposals operation from a testnet dictator (which may be set up when a test chain is initialized) has completely different effects:

  • If the operation contains no proposal, then the current voting period is immediately and forcibly set to a Proposal period.
  • If the operation contains exactly one proposal, then the current voting period is immediately and forcibly set to an Adoption period for this proposal.

validate_proposals must have been called beforehand, and is responsible for ensuring that apply_proposals cannot fail.

Update the context with the effects of a Ballot operation:

The couple (source of the operation, submitted ballot) is recorded.

validate_ballot must have been called beforehand, and is responsible for ensuring that apply_ballot cannot fail.