Verifying ETHGlossary Term Reviews: What the Page Establishes
Ethereum.org's full-page Crowdin translation work is paused; term review on ETHGlossary is the current path. Here is what the page does and does not establish.
The useful answer: on ethereum.org's Translation Program page, the current contribution route is reviewing terms on ETHGlossary, not submitting full-page translations. The page states that full-page translation through Crowdin is paused and that new translation submissions there are not being accepted (c10). Reviewing terms on ETHGlossary is described as how to contribute in the meantime (c11).
That matters for anyone who wants to check whether a translation effort is active, welcome, or finished. The page distinguishes status clearly: full-page work is paused (c10), while glossary review is presented as the open option (c02, c11). Existing community translations remain live on the site, and recognition on the acknowledgements and contributors pages stays in place (c12).
What the schedule change actually means
The announcement is not that translation stopped. It is that one intake channel — full-page translation through Crowdin — is paused and not accepting new submissions (c10). The page points contributors to term review on ETHGlossary during that period (c11) and says this is the best way to help right now (c02).
Contributors who previously submitted pages through Crowdin should read the page as a redirection, not a shutdown of translated content. The page says the thousands of community translators' work remains live and their recognition stays in place (c12). That is a statement about the past work, not a promise about any individual submission in the paused queue.
How the glossary review loop is described
ETHGlossary is described as a shared, community-reviewed glossary of Ethereum terms in 24 languages (c02). Every language has the same set of Ethereum terms, each with a draft translation (c05). A reviewer can approve a draft, propose a better alternative, or add context on how the term is used in the community (c06). The page says reviewing a single term takes a couple of minutes (c08).
The consequence chain is stated plainly: terms you approve are the terms ethereum.org uses in your language (c03); reviewed terms guide ethereum.org's translations and are published through the ETHGlossary API (c07); and wallets, apps and documentation teams can use them too, through the glossary's open API (c04). This is the page's own description of how review feeds downstream use. It is an explanation of intent and mechanism, not evidence that any specific term has already propagated to any specific wallet or app.
A verification walk-through for a term
The page supplies enough structure to check one term at a time. For a reader deciding whether to take part, the steps the source supports are:
- Confirm the language is among the 24 listed: Arabic, Bengali, Chinese (Simplified and Traditional), Czech, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Marathi, Polish, Portuguese (Brazil), Russian, Spanish, Swahili, Tamil, Telugu, Turkish, Ukrainian, Urdu and Vietnamese (c09).
- Expect a draft translation already present for each term in that language (c05).
- Choose one action per term: approve, propose an alternative, or add community context (c06).
- Treat the stated time cost as roughly a couple of minutes per term (c08).
- If the problem is an error in an existing page translation rather than a glossary term, the page directs readers to open an issue on GitHub (c13).
The checklist above is a reading of what the page describes, not a test of the interface. The page does not describe what a reviewer sees on screen, how disagreements between reviewers are resolved, or how quickly a reviewed term goes live.
Why ethereum.org frames this as essential
The page argues that Ethereum should read naturally in every language (c01). It says the community aims to be global and inclusive, yet much content only caters to English speakers, leaving out the world's 6 billion non-English speakers (c15). For ethereum.org to act as a portal into Ethereum for the worldwide community, the page says providing non-English speakers with content in their native languages is essential (c16).
The glossary is presented as a way to align terminology before or alongside page-level work. Because reviewed terms are published through the ETHGlossary API (c07) and can be used by wallets, apps and documentation teams (c04), the page positions term review as infrastructure rather than a one-off copy edit.
What the source does not say
- No publication date is stated for the page, so the direction described here cannot be dated from the source.
- No date is given for when Crowdin submissions will reopen, or whether a backlog will be reviewed.
- No review SLA, reviewer count, per-term acceptance threshold or dispute process is described.
- No commitment is made that a specific approved term will appear in a specific wallet, app or documentation set.
- The page does not state how API consumers license or version glossary terms.
- The page does not confirm that every language currently has active reviewers.
Which channel to use, by problem type
| Problem | Channel the page names |
|---|---|
| A term should be approved, replaced or annotated | ETHGlossary term review (c02, c06) |
| An existing page translation contains an error | Open an issue on GitHub (c13) |
| Questions or feedback about the program | ethereum.org Discord (c14) |
| Submitting a new full-page translation | Paused via Crowdin; not accepted (c10) |
The split matters because the page sends term problems and page-translation errors to different destinations. A reader who opens a GitHub issue for a glossary term, or tries Crowdin to fix a page translation, is using a channel the page does not assign to that task.
For this site's readers, the practical takeaway is narrower than a call to action. The page establishes that term review is the supported contribution path while full-page intake is paused, names the languages in scope, and explains where reviewed terms are intended to go. It does not establish timeline, throughput or downstream adoption for any individual term. Treat any claim beyond that as unconfirmed by this source.
Sources
Informational only. Not financial, legal or investment advice. Check the primary sources listed above before you act on anything here.