-
Notifications
You must be signed in to change notification settings - Fork 305
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
Remove Kiln and Ropsten as supported networks #7343
Conversation
Might be worth adding a changelog entry? Not sure if you considered the fact that ppl using these configs (if any) won't be able to upgrade their nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing my approval for further discussion.
What's the logic behind removing ropsten? ropsten.beaconcha.in shows blocks being produced.. |
Ropsten has been shut down since December last year though. ropsten.beaconcha.in points to mainnet for some reason and when you try connecting to it, there are no peers, etc. |
Prysm also removed option few releases back: prysmaticlabs/prysm#12058 |
I got confused by ropsten.beaconcha.in |
ok all good, just no context as to why we were removing support for a network still progressing, but happy now. |
Yeah same. I will bring it up in their discord. |
PR Description
Kiln and Ropsten have been shut down for a long time, so there is no point in supporting them as a
--network
option.Fixed Issue(s)
N/A
Documentation
doc-change-required
label to this PR if updates are required.Changelog