-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Updated info on testnet naming convention #16024
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
base: dev
Are you sure you want to change the base?
Conversation
Ethereum testnets often follow a tradition of being named after metro stations or easily recognizable places. The goal is to make them memorable and distinguishable from mainnet. This naming pattern reflects community culture and developer convenience. These insights are drawn from Ethereum Cat Herders (ECH) developer calls and other public sources.
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This issue is stale because it has been open 30 days with no activity. |
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.
Hey @bskrksyp9, thanks for this! Learned a few things here =)
Couple things... For this page specifically I wonder if it's worth including testnets that are no longer active, which would be all of them aside from Sepolia, Hoodi and Ephemery.
This feels kind of like a historical fun-fact, akin to where we explain the naming behind upgrades, on our history page ("Why do some upgrades have multiple names?").
Curious opinions here, but not necessarily against adding to where you placed it, though at the least I would move this outside (above) the "Further reading" section which follows a pattern on all pages with just links.
If we keep this here, would decrement the heading levels and switch the headers to use "Sentence casing" instead of "Title Casing", amd add custom header IDs... ie:
### 🚉 Why Are Ethereum Testnets Named After Metro Stations?
Should be
## 🚉 Why are Ethereum testnets named after metro stations? {#why-naming}
with similar pattern to the others.
Let me know your thoughts... cc: @konopkja also curious your take on this
Appreciate for your thoughtful feedback I see your point about inactive testnets fitting more as historical context, and the notes on placement and heading style make sense. I’d just love if we can keep this story somewhere on the site, even if not right here, since it adds background and character worth preserving. |
@bskrksyp9 Yeah sounds good... as next steps let's go ahead with keeping it on this page, with the adjustments requested above. I believe there is some discussion around expanding the "history" part of the site between a "timeline" like we have now at /history and a "story" approach that is less bulleted. This could potentially be modified then when those changes are being planned/implemented. |
Description
Ethereum testnets often follow a tradition of being named after metro stations or easily recognizable places. The goal is to make them memorable and distinguishable from mainnet. This naming pattern reflects community culture and developer convenience. These insights are drawn from Ethereum Cat Herders (ECH) developer calls and other public sources.