You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Ask for derivation path -> find deposit key and withdrawal key
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.
Ask for the new ETH1 address to be added to the credentials
Form message and request signature
NOTE: We could also add another screen to the Lattice for updating credentials, just like for generating deposit data
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: