BLS to Execution Change

[pablomendezroyo]

In order to withdraw your validator, Ethereum needs to associate an Ethereum execution address with your validator’s keys. Underneath the hood, submitting a bls-to-execution-change (withdrawal) request updates the withdrawal credentials.

To sign and submit the bls-to-execution to a beacon node there are several toolings:

• Ethdo: https://github.com/wealdtech/ethdo/blob/master/docs/changingwithdrawalcredentials.md
• Deposit-cli (work in progress): Add generate_bls_to_execution_change ethereum/staking-deposit-cli#313
• Consensus teams CLI`s

The ethdo tool allows non-interactive usage and it has already implemented this feature.

To execute bls-to-execution-change:

ethdo validator credentials set --mnemonic="abandon abandon abandon … art" --withdrawal-address=0x0123…cdef

The inputs required are:

• mnemonic
• withdrawal-address

The above command will

1. obtain information from your consensus node about all currently-running validators and various additional information required to generate the operations
2. scan your mnemonic to find any validators that were generated by it, and create the operations to change their credentials
3. broadcast the credentials change operations to the Ethereum network

Approach

Use ethdo tool as a binary to be executed by the backend brain tool. Consider adding a post-check to ensure the withdrawal address was set correctly

Requirements:

• Connectivity to a beacon node
• Inputs: nmnemonic and withdrawal-address

Caveats

• Ideally, the process of introducing the mnemonic should be performed offline
• The withdrawal address should be asked up to 3 times in the frontend. It cannot be changed once set