Verifying the Translation Program: What Contributors Should Know
Full-page translation on Crowdin is paused; ETHGlossary term review is the current contribution path. Here is what to verify before you start.
The useful answer first: as of the source page, full-page translation through Crowdin is paused and no new translation submissions are accepted there. Reviewing terms on ETHGlossary is the described way to contribute in the meantime. If you are checking whether the program still matches what you remember, that pause is the change to verify, and the active task is term review rather than page translation.
This guide lays out what the page states, what it does not state, and how to confirm each point against the page itself. It does not describe anyone testing the workflow, and nothing here was independently verified.
What the program is for
The source frames the goal plainly: Ethereum should read naturally in every language (c01). The stated motivation is reach. The Ethereum community aims to be global and inclusive, yet much of its content only caters to English speakers, leaving out the world's 6 billion non-English speakers (c15). Providing non-English speakers with Ethereum content in their native languages is described as essential for the site to act as a portal for the worldwide community (c16).
The historical program aimed to make Ethereum accessible to everyone by translating ethereum.org and other Ethereum content into as many languages as possible (c17). Ethereum.org has been translated by thousands of community members, who are described as the key part of the program (c18).
What changed, and what is still live
Two statements matter for anyone deciding where to spend time. First, full-page translation through Crowdin is paused, and new translation submissions there are not being accepted (c10). Second, reviewing terms on ETHGlossary is how to contribute in the meantime (c11). Those two claims together define the current state: one channel is closed to new work, the other is the named alternative.
The page also states that existing translations remain live on the site, and that recognition on the acknowledgements and contributors pages stays in place for the thousands of community translators who worked over the years (c12). That matters if you are checking whether past contributions were withdrawn. The page says they were not.
How the glossary review loop works
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). For each term, you can approve it, propose a better alternative, or add context on how it is used in your community (c06).
The claimed consequence is direct: the 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). Wallets, apps and documentation teams can use them too, through that open API (c04). Reviewing a single term is estimated to take a couple of minutes (c08).
The language list is explicit: 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). That enumeration is worth checking against your own language before you invest time, because a language absent from it is a mismatch between your intent and the listed scope.
A checklist for confirming the state before you contribute
- Confirm the pause. Check that the page still says full-page translation through Crowdin is paused with no new submissions accepted (c10). If that sentence is gone or revised, the state has changed and the rest of this guide may not apply.
- Confirm the named alternative. Check that term review on ETHGlossary is still presented as the interim contribution path (c11).
- Confirm your language is listed. Compare your language against the enumerated set (c09).
- Confirm the action set. Verify that approve, propose an alternative, and add community context are the described options (c06).
- Note the downstream effect. Understand that approved terms are stated to drive the site's translations in your language and to be published through the API (c03, c07).
- Check where errors go. The page directs you to open an issue on GitHub if you spot an error in an existing translation (c13), and to the ethereum.org Discord for questions or feedback (c14).
Where an access-continuity reader should slow down
If your interest is documentation you rely on during recovery, the glossary is the layer that shapes wording, not the layer that stores keys. Nothing in the source describes wallet recovery procedures, seed phrases, or backup verification. The only product linkage stated is that wallets, apps and documentation teams can consume glossary terms through the open API (c04). That is a statement of availability, not evidence that any specific wallet uses it.
Two status words deserve care. 'Paused' is not 'shut down,' and the page gives no restart date. 'Approved' is a review state, not a guarantee of accuracy in every context. The page also notes reviewing a single term takes a couple of minutes (c08), which is an estimate, not a measured average.
What the source does not say
- No date is given for when full-page translation was paused, or whether it will resume.
- No volume figures are given for how many terms exist per language or how many have been reviewed.
- No named individuals, teams, or reviewers are identified.
- No process is described for approving a term that another contributor disputes.
- No statement is made about whether any specific wallet or app currently consumes the API (c04 only says teams can).
- No claim is made that glossary terms are error-free, or that reviewing a term is audited.
- No token, market, or pricing information appears anywhere in the source.
The honest position is therefore narrow. The page tells you what to do now, in what languages, with what effect, and where to report errors. It does not tell you when the other channel reopens or how quality is enforced. Treat the checklist above as a way to confirm the current wording on the page before acting, not as proof that any specific workflow will behave as described.
Sources
Informational only. Not financial, legal or investment advice. Check the primary sources listed above before you act on anything here.