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

voluntary exits 'no peers on channel' #8158

Closed
rolfyone opened this issue Mar 28, 2024 · 6 comments
Closed

voluntary exits 'no peers on channel' #8158

rolfyone opened this issue Mar 28, 2024 · 6 comments
Assignees
Labels
bug 🐞 Something isn't working

Comments

@rolfyone
Copy link
Contributor

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.

@rolfyone rolfyone added the bug 🐞 Something isn't working label Mar 28, 2024
@lucassaldanha
Copy link
Member

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 voluntary_exit topic, or both Teku and LH are doing something wrong :)

@zilm13
Copy link
Contributor

zilm13 commented Mar 30, 2024

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

I read it that topic is Capella fixed.

The specific makes one change to the state transition function:

    Modify `process_voluntary_exit` to compute the signing domain and root fixed on `CAPELLA_FORK_VERSION`.

Additionally, the `voluntary_exit` gossip conditions are implicitly modified to support this change.

EIP-7044, which is the part of Deneb

This could be read in two ways: either topic is Capella-fixed or topic is changed according to the fork, but validation should not reject Capella-signed voluntary exits.

Our code:

Validation lock-in to Capella

Create Voluntary Exits (subcommand) - no lock-in: [1], [2]

Gossip subscriptions - no lock-in

@zilm13 zilm13 self-assigned this Mar 30, 2024
@zilm13
Copy link
Contributor

zilm13 commented Mar 30, 2024

Issue opened for topic clarification ethereum/consensus-specs#3638 as we are not sure on this

@zilm13
Copy link
Contributor

zilm13 commented Mar 31, 2024

Create Voluntary Exits (subcommand) - no lock-in: - not true
Actually we do this deep in spec beacon state accessors. Just added more tests to avoid confusion on this side.

rolfyone added a commit to rolfyone/teku that referenced this issue Apr 4, 2024
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 <paul.harris@consensys.net>
rolfyone added a commit that referenced this issue Apr 5, 2024
)

* 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 <paul.harris@consensys.net>
@rolfyone
Copy link
Contributor Author

Not publishing voluntary exit because no gossip subscriptions are active for slot xxxx

@zilm13
Copy link
Contributor

zilm13 commented May 21, 2024

Fixed with #8205

@zilm13 zilm13 closed this as completed May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants