eth-clients / eth2-networks Goto Github PK

For e.g: the single-client folders in the root of the repo is kinda un-necessary right now since we mostly do shared testnets. It would be useful in the future to separate them into phase0, altair and merge to make it easier to know what testnet to recreate/join.

Given how sepolia and görli already have their own repos in the same format as clients use for loading genesis etc, I'd suggest the following changes given that the rest of the information in this repo in particular is mostly obsolete:

• create a new mainnet project (https://github.com/eth-clients/mainnet probably)
• move the current state of shared/mainnet there
• mark this repository archived

if nobody disagrees, I would like to move the prater config to the stand-alone goerli repository:

• https://github.com/eth-clients/goerli (formerly https://github.com/goerli/testnet)

the rationale is that the merge is not only technical but also logical. also, long-standing testnets should have their dedicated home.

edit: here https://github.com/eth-clients/goerli/tree/main/prater

Now that the Altair fork is complete and stable on Pyrmont, we are inducing a number of behaviors on the soon-to-be-deprecated Pyrmont.

The following list are the low hanging fruit. Feel free to do additional tests.

• Operations (many of each)
  • Validator deposit
  • Validator exit
  • Proposer slashing [1000 completed]
  • Attester slashing (double)
  • Attester slashing (surround)
• Sync committees
  • Produce (valid) block with empty sync committee
• Sync (for each client)
  • Block sync from genesis [all clients completed]
  • Block sync from after Altair fork
  • Checkpoint sync from before Altair [clients with functionality completed]
  • Checkpoint sync from after Altair [clients with functionality completed]
• Stress
  • Turn off 50% of nodes, observe non-finality, turn them back on, observe finality [completed]
• Bad network data
  • Gossip invalid blocks
  • Gossip invalid attestations

Original doc

To avoid confusion about different technical notions on what Eth2 is, I suggest renaming eth2 to consensus or beacon-chain. Repository is full of references to Eth2, at least name of the repo and readme could reflect this.

Would it be possible and desirable to create a docker-compose file that launches all of the available eth2 clients so that people can easily participate in testing with a simple docker-compose up? I think many of the clients already have automated docker builds so it would mostly be a task of collecting all of the configuration options.

Would this be the right repo for such a script?

We have two repos keeping track of known eth2 networks - this one and https://github.com/eth2-clients/eth2-mainnet - life can be made easier by simply renaming this one to eth2-networks and deprecating eth2-mainnet - conveniently, the mainnet data is already in this repo and more recent than the eth2-mainnet data (eth-clients/eth2-mainnet#5)