Skip to main content
Version: 15.0.0

Consensus Keys

The "consensus key" feature allows bakers to use a different key, called the consensus key. It will allow for baking and signing consensus operations (i.e. pre-endorsements and endorsements). For more detailed information on consensus keys, refer to this documentation

Starting from Lima protocol, these 2 new operations will be available:

Update Consensus Key

This is a manager operation that must be signed by the manager key of the baker. This operation updates the consensus key of the baker to PUBLIC_KEY starting from the current cycle plus PRESERVED_CYCLES + 1. A consensus key can only be used by a single baker, the operation will fail otherwise.

Examples

const op = await Tezos.contract.updateConsensusKey({
pk: 'PUBLIC_KEY'
});
await op.confirmation();
  • pk is the public key you want the consensus key to point to

Provide detailed feedback