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

You cannot do a consolidation request from a 0x01 source validator to a different 0x01 #229

Open
remyroy opened this issue Jan 31, 2025 · 1 comment · May be fixed by #238
Open

You cannot do a consolidation request from a 0x01 source validator to a different 0x01 #229

remyroy opened this issue Jan 31, 2025 · 1 comment · May be fixed by #238

Comments

@remyroy
Copy link

remyroy commented Jan 31, 2025

From what I understand, you cannot do a consolidation request from a 0x01 source validator to a different 0x01 target validator. The source and the target validator must be the same for an in-place upgrade from 0x01 to a 0x02 validator or the target validator must be a 0x02 one. This is currently possible through the dora UI and it will show in the consolidation requests tab on a validator's page.

See https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md#new-process_consolidation_request

    # Verify that target has compounding withdrawal credentials
    if not has_compounding_withdrawal_credential(target_validator):
        return
@remyroy
Copy link
Author

remyroy commented Jan 31, 2025

In short, when you select your target validator in dora UI for the consolidation request, it should either be the same as the source validator or one that is of 0x02 type.

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