Skip to content

Ropsten beacon chain #525

@djrtwo

Description

@djrtwo

We need to launch a Ropsten beacon chain to handle the merge of that testnet.

In our last CL call, it was generally decided that Ropsten should be unpermissioned but for devs to have the majority of validators (similar to prater/goerli).

So this would entail

  • deciding on a genesis validator set size and genesis time
  • creating a genesis state with well-distributed validators across EL teams, CL teams, EF and launching the chain soon (before end of may)

I suggest we do 100k vals. This is reasonably resistant to disruptions due to external deposits in the near-term, and it seems likely Ropsten is deprecated not too far out after it's merge

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions