-
Notifications
You must be signed in to change notification settings - Fork 303
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
voluntary exits 'no peers on channel' #8158
Comments
I haven't got confirmation from the other client teams if we should fix the fork digest, but I checked a Lighthouse node in Sepolia and all topics are using an updated fork digest after Deneb, and all topics match the topics that our Teku nodes in Sepolia are subscribed to. So either we do not need to fix the fork digest for the |
Spec:The voluntary_exit topic is implicitly modified due to the lock-in use of CAPELLA_FORK_VERSION for this message signature validation for EIP-7044. spec
EIP-7044, which is the part of Deneb
Our code:Create Voluntary Exits (subcommand) - no lock-in: [1], [2] Gossip subscriptions - no lock-in |
Issue opened for topic clarification ethereum/consensus-specs#3638 as we are not sure on this |
|
The advantage of this is that the message can avoid epoch validation, and also it can separate the submission of the exit from creation, so if something fails, it can have further investigation. The format saved to json will allow it to be posted directly to the voluntary exits beacon-api POST endpoint. Assists with Consensys#8158 but only as a potential workaround, allowing us to avoid setting up the keymanager-api to generate an exit. Signed-off-by: Paul Harris <[email protected]>
) * Allow voluntary exit command to write to file rather than publish The advantage of this is that the message can avoid epoch validation, and also it can separate the submission of the exit from creation, so if something fails, it can have further investigation. The format saved to json will allow it to be posted directly to the voluntary exits beacon-api POST endpoint. Assists with #8158 but only as a potential workaround, allowing us to avoid setting up the keymanager-api to generate an exit. Signed-off-by: Paul Harris <[email protected]>
|
Fixed with #8205 |
When submitting a voluntary exit in deneb, 'no peers on topic' has been reported.
We need to investigate this, the Deneb spec says
The voluntary_exit topic is implicitly modified due to the lock-in use of CAPELLA_FORK_VERSION for this message signature validation for EIP-7044.
This possibly means that the voluntary exit digest should be locked at the capella digest, so we're essentially on the wrong gossip topic to find peers for exits.
The text was updated successfully, but these errors were encountered: