Skip to content

Conversation

bskrksyp9
Copy link
Contributor

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.

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.
Copy link

netlify bot commented Aug 5, 2025

Deploy Preview for ethereumorg ready!

Name Link
🔨 Latest commit b84c585
🔍 Latest deploy log https://app.netlify.com/projects/ethereumorg/deploys/68921de314dba10008dcfacd
😎 Deploy Preview https://deploy-preview-16024--ethereumorg.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
7 paths audited
Performance: 51 (no change from production)
Accessibility: 94 (no change from production)
Best Practices: 92 (no change from production)
SEO: 99 (no change from production)
PWA: 59 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions bot added the content 🖋️ This involves copy additions or edits label Aug 5, 2025
Copy link
Contributor

github-actions bot commented Sep 5, 2025

This issue is stale because it has been open 30 days with no activity.

@github-actions github-actions bot added the Status: Stale This issue is stale because it has been open 30 days with no activity. label Sep 5, 2025
Copy link
Member

@wackerow wackerow left a 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

@bskrksyp9
Copy link
Contributor Author

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.

@github-actions github-actions bot removed the Status: Stale This issue is stale because it has been open 30 days with no activity. label Sep 11, 2025
@wackerow
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content 🖋️ This involves copy additions or edits
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants