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

Improve Charon compatibility matrix #3574

Open
5 tasks
KaloyanTanev opened this issue Mar 6, 2025 · 0 comments
Open
5 tasks

Improve Charon compatibility matrix #3574

KaloyanTanev opened this issue Mar 6, 2025 · 0 comments
Assignees
Labels
protocol Protocol Team tickets
Milestone

Comments

@KaloyanTanev
Copy link
Collaborator

KaloyanTanev commented Mar 6, 2025

🎯 Problem to be solved

Currently we are supporting 5x5 combinations of BN and VC - Lighthouse, Lodestar, Prysm, Teku, Nimbus. However, we do not have 100% passing duties in some of the combinations. It would be nice if we can guarantee 100% success in all 25 combos. The current failing ones are:

  • Prysm VC rarely fails penalisd duties (1-2% of the time) in combinations with Teku, Lodestar and Nimbus BNs.
  • Teku and Prysm VCs fail ~50% of the time aggregation duties with all BNs.
  • Lighthouse VC fails all aggregation duties with all BNs.

🛠️ Proposed solution

Prysm VC failing penalised duties
There is no current diagnose of the issue, however, a good guess is that this is caused by putting the BN under too much load and it's unable to process the requests on time. There seemed to be a pattern of it happening once per epoch, but not for specific duty per se. Sometimes attestation was failing, sometimes proposal, sometimes both. After we put some work on our traceability #3429 and reduce the requests we send to the BN, there is a slight chance this problem resolves by itself.

Teku and Prysm VCs fail ~50% of aggregations
There is no current diagnose of the issue and no guess can be made at this stage.

Lighthouse VC fails aggregations
Lighthouse is not supporting the logic of aggregations from a DV. It is an acknowledged issue by the sigma prime team and they are working on it, see sigp/lighthouse#6610.

🧪 Tests

  • Manually tested on core team/canary/test clusters
  • Manually tested on local Kurtosis simnet
@KaloyanTanev KaloyanTanev added this to the v1.4.0 milestone Mar 6, 2025
@github-actions github-actions bot added the protocol Protocol Team tickets label Mar 6, 2025
@KaloyanTanev KaloyanTanev self-assigned this Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol Protocol Team tickets
Projects
None yet
Development

No branches or pull requests

1 participant