Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Update Withdrawal Credentials option #3

Closed
alex-miller-0 opened this issue Dec 10, 2022 · 0 comments · Fixed by #13
Closed

Add Update Withdrawal Credentials option #3

alex-miller-0 opened this issue Dec 10, 2022 · 0 comments · Fixed by #13

Comments

@alex-miller-0
Copy link
Contributor

It appears the ETH2 spec has moved on from BLS withdrawal keys and will force a transition from BLS -> ETH1 withdrawal credentials for 0x00 type credentials in order to do any withdrawals. I suppose this makes sense because you need to be able to withdraw to an execution-layer address.

In the upcoming Capella fork, there is a new method to allow updating of withdrawal credentials.

The method is called SignedBLSToExecutionChange.

The workflow should look like:

  1. Ask for derivation path -> find deposit key and withdrawal key
  2. Obtain validator index associated with deposit key. This can either be done by a lookup from the CLI using e.g. Beaconscan OR by asking the user to input the index. We could also attempt to lookup on Beaconscan and fall back to the validator index.
  3. Ask for the new ETH1 address to be added to the credentials
  4. Form message and request signature

NOTE: We could also add another screen to the Lattice for updating credentials, just like for generating deposit data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant