-
Notifications
You must be signed in to change notification settings - Fork 356
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
Ropsten beacon chain #525
Comments
Another thing to note is that we should have good documentation (and ideally faucets) for stakers who want to launch validators before The Merge on Ropsten to make sure their setup works as expected. |
As discussed on ACD, Ropsten will have a validator set of ~100k. I'd say 10000 validator keys per entity taking part (Assuming that every client team wants to take part) => Validator set of 110012 (9 client teams + EF + Attestant/Vouch + 12 for EF security). If there are entities outside of client teams that would like to take part, please comment below. I propose genesis for the ropsten beaconchain on 30th of May (~2.5 weeks from now). That should give us enough time for clients to have releases, blogposts to come out, explorers to be setup. At the same time, it would be an overlap of ~1 week before the proposed merge with Ropsten PoW chain. If we have altair + bellatrix happening in quick succession, the beaconchain would be ready well in advance. |
do i count as an entity |
@0xWildhare If you have a reason for wanting to be a validator on ropsten (something to test, represent a significant part of mainnet, significant experience running validators) and so on, then you would count as an entity :) |
Is there documentation on how to run Ropsten beacon chain? Just test, personal. |
@vieyang we'll have a post at blog.ethereum.org by the end of the week :-) |
@timbeiko ok, thank you. I have 32 rETH ready. |
any tips on how to get 32 rETH? wen faucet? |
@0xWildhare if I don't have a validator setup before the merge, I can endow you with 32 rETH |
@parithosh We (https://www.kiln.fi/) would like to take part. Besides running multiple validators on the mainnet, we run some validators on the Kiln testnet and would really like to have validators running during Ropsten merge. |
Thank you pour your answer, we will try not to be late for Sepolia! @parithosh, we are currently struggling to find enough rETH (Ropsten ETH) to launch 100 validators (our target). Thanks a lot! |
@nalepae sure, comment your address here :) |
@parithosh, here is my address:
==> Ideally we would like to launch 100 validators, so we would need 3200 rETH, if it is possible for you (we already have enough rETH for gas). Thanks a lot! |
Done. 🚀 |
Closing this as the beacon chain is alive and well! |
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
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
The text was updated successfully, but these errors were encountered: