lighthouse
lighthouse copied to clipboard
Add Peering Simulator
Issue Addressed
#6109
Proposed Changes
Adds a new simulator to CI which launches with 2 beacon nodes and every 2 epochs adds a new BN to the network. After 16 epochs it checks to see if all new BNs are synced to the head.
Additional Info
This might be overkill in the long term, but hopefully will be useful for DAS testing and CI.
From my initial local testing, if I disable the eip7594_fork_epoch, the nodes all sync fine and the simulation exits successfully. However if I leave in the eip7594_fork_epoch, the nodes consistently get stuck despite seemingly having peers.
However if I leave in the eip7594_fork_epoch, the nodes consistently get stuck despite seemingly having peers.
Nice! that useful finding - will look into this tomorrow.
Hi @macladson
I haven't been able to get to this, do you have some capacity to look into the issues? It would be useful to complete this change, as we're now picking up on PeerDAS development speed again.
The test will need a bit of update now we've switched to activating PeerDAS at the Fulu hard fork. Let me know if you're busy with something else and I can look into this.
I'll take a look into this as well!
I created https://github.com/macladson/lighthouse/pull/7. peering-sim has run successfully in my local tests, though NoPeersSubscribedToTopic still appears.
https://github.com/sigp/lighthouse/actions/runs/14413837149/job/40430090447?pr=6395
Created https://github.com/macladson/lighthouse/pull/8 to fix the CI failure. 🙏
This pull request has merge conflicts. Could you please resolve them @macladson? 🙏
Some required checks have failed. Could you please take a look @macladson? 🙏
Hi @macladson, this pull request has been closed automatically due to 30 days of inactivity. If you’d like to continue working on it, feel free to reopen at any time.