charon
charon copied to clipboard
ObolNetwork
Test Obol commands on Gnosis clusters
🎯 Problem to be solved
Testing Obol commands on Gnosis chain testnet clusters
🛠️ Proposed solution
- [ ] Reach out to potential Gnosis chain node operators with cluster config form https://docs.google.com/forms/d/e/1FAIpQLSewiiUOGGXrNpSosW2MPWziMYKV0yfIQRneGLFuSzi0o2Ahtg/viewform
- [ ] Ask them for their current node setup details (locations, specs, number of keys)
- [ ] Schedule a time for all operators to run the test ping commands simultaneously
- [ ] Evaluate feedback and pivot cluster setup if needed, based on latencies observed
- [ ] After ping commands, proceed with testing beacon node commands if successful
- [ ] Determine criteria for assessing "good enough" performance on Gnosis, since Obol monitoring may not cover Gnosis-specific metrics currently
Included Test Commands in the current rc1
- test peers -- Ping -- PingMeasure -- PingLoad -- IsLibp2pPortOpen
- test beacon -- Ping -- PingMeasure -- IsSynced -- PeerCount
- no testnet, straight to gnosis mainnet
- form is posted in #biz-partnerships slack. gets tentative node locations + buy in.
- once agreed, we will get them to create ENRs and report them to us, ideally with more firm node details for our CRM. We'll decide the two clusters.
- we send the two clusters separate cal invites and in the description we say "run this command at this time if you can't attend" . We attend the call and watch/learn/debug.
- If all goes to plan we send them the invites? Maybe there and then? and get them through DKG?
