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.

Sign up for GitHub

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

Jump to bottom

Implement Beacon Node Tests #2998

Closed
5 tasks done
boulder225 opened this issue Mar 27, 2024 · 0 comments
Closed
5 tasks done

Implement Beacon Node Tests #2998

boulder225 opened this issue Mar 27, 2024 · 0 comments
Assignees
@KaloyanTanev
Labels
alpha network test protocol Protocol Team tickets

Comments

@boulder225
Copy link
Collaborator

boulder225 commented Mar 27, 2024 •
edited by KaloyanTanev
Loading

🎯 Problem to be solved

Assess the functionality and performance of the beacon node within the Charon cluster.

🛠️ Proposed solution

  • Implement a test to verify beacon node can be pinged
  • Implement a test to measure the round-trip time (RTT) to the beacon node
  • Implement a test to check if the beacon node is synced with the network
  • Accumulate and evaluate the beacon node connection test results
  • Include the beacon node connection test results in the report
@boulder225 boulder225 added alpha network test protocol Protocol Team tickets labels Mar 27, 2024
@boulder225 boulder225 changed the title Copy of Implement Peer-to-Peer Connection Tests Implement Beacon Node Tests Mar 27, 2024
@KaloyanTanev KaloyanTanev mentioned this issue Apr 29, 2024
Merged
obol-bulldozer bot pushed a commit that referenced this issue May 8, 2024
@KaloyanTanev
cmd: alpha test beacon (#3059)
32d2655 
Charon alpha beacon node testing. Structure is identical to what we have in peers tests, with the exception that here we do not have separation between self and external (peers). The 4 test cases can be fired against multiple beacon nodes.

To test on your own machine:
```
make charon && ./charon alpha test beacon --endpoints="https://ethereum-holesky-beacon-api.publicnode.com,https://ethereum-sepolia-beacon-api.publicnode.com"
```

Similarly to peers tests, const values used to determine whether a measured test result is average or bad are nothing more than estimates for now on my side. I am open to suggestions on that front.

category: feature
ticket: #2998
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KaloyanTanev KaloyanTanev

Labels
alpha network test protocol Protocol Team tickets
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KaloyanTanev @boulder225