Keys in proof-of-stake Ethereum

Ethereum secures user assets using public-private key cryptography. The public key is used as the basis for an Ethereum address—that is, it is visible to the general public and used as a unique identifier. The private (or 'secret') key should only ever be accessible to an account owner. The private key is used to 'sign' transactions and data so that cryptography can prove that the holder approves some action of a specific private key.

Ethereum's keys are generated using elliptic-curve cryptography(opens in a new tab).

However, when Ethereum switched from proof-of-work to proof-of-stake a new type of key was added to Ethereum. The original keys still work exactly the same as before—there were no changes to the elliptic-curve-based keys securing accounts. However, users needed a new type of key for participating in proof-of-stake by staking ETH and running validators. This need arose from scalability challenges associated with many messages passing between large numbers of validators that required a cryptographic method that could easily be aggregated to reduce the amount of communication required for the network to come to consensus.

This new type of key uses the Boneh-Lynn-Shacham (BLS) signature scheme(opens in a new tab). BLS enables a very efficient aggregation of signatures but also allows reverse engineering of aggregated individual validator keys and is ideal for managing actions between validators.

The two types of validator keys

Before the switch to proof-of-stake, Ethereum users only had a single elliptic-curve-based private key to access their funds. With the introduction of proof-of-stake, users that wished to be solo stakers also required a validator key and a withdrawal key.

The validator key

The validator signing key consists of two elements:

• Validator private key
• Validator public key

The purpose of the validator private key is to sign on-chain operations such as block proposals and attestations. Because of this, these keys must be held in a hot wallet.

This flexibility has the advantage of moving validator signing keys very quickly from one device to another, however, if they have gotten lost or stolen, a thief may be able to act maliciously in a few ways:

• Get the validator slashed by:
  • Being a proposer and signing two different beacon blocks for the same slot
  • Being an attester and signing an attestation that "surrounds" another one
  • Being an attester and signing two different attestations having the same target
• Force a voluntary exit, which stops the validator from staking, and grants access to its ETH balance to the withdrawal key owner

The validator public key is included in the transaction data when a user deposits ETH to the staking deposit contract. This is known as the deposit data and it allows Ethereum to identify the validator.

Withdrawal credentials

Every validator has a property known as withdrawal credentials. This 32-byte field begins with either a 0x00, representing BLS withdrawal credentials, or a 0x01, representing credentials that point to an execution address.

Validators with 0x00 BLS keys must update these credentials to point to an execution address in order to activate excess balance payments or full withdrawal from staking. This can be done by providing an execution address in the deposit data during initial key generation, OR by using the withdrawal key at a later time to sign and broadcast a BLSToExecutionChange message.

The withdrawal key

The withdrawal key will be required to update withdrawal credentials to point to an execution address, if not set during initial deposit. This will enable excess balance payments to begin being processed, and will also allow users to fully withdraw their staked ETH.

Just like the validator keys, the withdrawal keys also consist of two components:

• Withdrawal private key
• Withdrawal public key

Losing this key before updating withdrawal credentials to 0x01 type means losing access to the validator balance. The validator can still sign attestations and blocks since these actions require the validator's private key, however there is little to no incentive if the withdrawal keys are lost.

Separating the validator keys from the Ethereum account keys enables multiple validators to be run by a single user.

Deriving keys from a seed phrase

If every 32 ETH staked required a new set of 2 completely independent keys, key management would quickly become unwieldy, especially for users running multiple validators. Instead, multiple validator keys can be derived from a single common secret and storing that single secret allows access to multiple validator keys.

Mnemonics(opens in a new tab) and paths are prominent features that users often encounter when they access(opens in a new tab) their wallets. The mnemonic is a sequence of words that act as an initial seed for a private key. When combined with additional data, the mnemonic generates a hash known as the 'master key'. This can be thought of as the root of a tree. Branches from this root can then be derived using a hierarchical path so that child nodes can exist as combinations of their parent node's hash and their index in the tree. Read about BIP-32(opens in a new tab) and BIP-19(opens in a new tab) standards for mnemonic-based key generation.

These paths have the following structure, which will be familiar to users who have interacted with hardware wallets:

1m/44'/60'/0'/0`

The slashes in this path separate components of the private key as follows:

1master_key / purpose / coin_type / account / change / address_index

This logic enables users to attach as many validators as possible to a single mnemonic phrase because the tree root can be common, and differentiation can happen at the branches. The user can derive any number of keys from the mnemonic phrase.

1      [m / 0]
2     /
3    /
4[m] - [m / 1]
5    \
6     \
7      [m / 2]

Each branch is separated by a / so m/2 means start with the master key and follow branch 2. In the schematic below a single mnemonic phrase is used to store three withdrawal keys, each with two associated validators.

Further reading

• Ethereum Foundation blog post by Carl Beekhuizen(opens in a new tab)
• EIP-2333 BLS12-381 key generation(opens in a new tab)