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.

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

Using Goerli for Prysm testnet #38

Closed
prestonvanloon opened this issue Jan 19, 2019 · 3 comments
Closed

Using Goerli for Prysm testnet #38

prestonvanloon opened this issue Jan 19, 2019 · 3 comments

Comments

@prestonvanloon
Copy link
Member

Hi Goerli team,

We, at Prysmatic Labs, are planning to launch a publicly accessible test network for our Ethereum 2.0 client, Prysm, soon ™️. Part of this network relies on a validator deposit contract to exist in an Ethereum 1.0 blockchain, such as Goerli.

We would like to participate in the PoA clique to provide our team and interested testers to join this Ethereum 2.0 testnet by depositing Goerli ETH into some smart deposit contract.

Initially, we would set the deposit requirement parameters to some low value for easier iteration, but the eventual goal would be to simulate the full deployment with validators depositing with 32 ETH.
How can we join the Goerli network as a PoW participant or otherwise collect large amounts of ETH for testing the validator deposits for Ethereum 2.0?

@5chdn
Copy link
Contributor

5chdn commented Jan 19, 2019

How can we join the Goerli network as a PoW participant or otherwise collect large amounts of ETH for testing the validator deposits for Ethereum 2.0?

I would encourage you to run a validator node because this is what the network keeps alive, not only users but also people help to seal the blocks. However, block rewards are zero, so we could add an allocation to the genesis if that works for you.

How much do you need? What's your validator address?

@prestonvanloon
Copy link
Member Author

prestonvanloon commented Jan 20, 2019

We'd be happy to run a validator node for goerli in exchange for genesis allocation.
We can use 0xd9a5179f091d85051d3c982785efd1455cec8699 as our validator.

In terms of quantity of GöETH, we can take a look at some of the numbers for validators in Ethereum 2.0:

Parameter Amount
Minimum number of validators to start ETH2.0 2**14 (16384)
Validator deposit size 32 ETH

More on ETH2.0 deposit lockup amounts

During testing, we could set the deposit size to gwei instead of ETH which would give us more flexibility with the amount of GöETH have. However, when we want to test out a full system, it might be more meaningful to test with the "real" contract as these constants are hardcoded in the production version and we would want to simulate a test network as close to reality as possible.

With that said, I think we'd (eventually) want to be able to test with

  • The minimum amount of validators at 32 ETH (total of 525k GöETH)
  • A realistic amount of validators ~100k @ 32 ETH (total of 3.1MM GöETH)

If genesis allocations are little to no effort, can we grant each team with 10MM GöETH?

I think it is unrealistic for a single team to run 100k validators independently, but they should be able to run their own ETH 2.0 faucet-like validator setup to reduce the load on the Goerli core team from "can I have 32 GöETH?" requests from interested testers.

@5chdn
Copy link
Contributor

5chdn commented Jan 20, 2019

10 million for such a use-case is no problem at all. I created a tracker for the rollout. #39

Stay tuned for genesis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants