How to Contribute to Ethereum Translation Now: Verify ETHGlossary
Full-page Crowdin translation is paused, so the current contribution path is reviewing Ethereum terms on ETHGlossary. Here is how to check that setup before you spend time.
The useful answer first: full-page translation through Crowdin is paused, and new translation submissions there are not being accepted. According to the ethereum.org Translation Program page, the current way to help is reviewing terms on ETHGlossary, a shared, community-reviewed glossary of Ethereum terms. Before you invest time, verify that this is the right channel for your language and that your review will actually feed back into published translations.
What changed and what is still live
The source states that the best way to help right now is ETHGlossary, described as a shared, community-reviewed glossary of Ethereum terms in 24 languages. It also states that full-page translation through Crowdin is paused and that new translation submissions are not being accepted there.
That does not erase past work. The page says ethereum.org was translated by thousands of community members and that their work remains live on the site. Recognition on the acknowledgements and contributors pages stays in place. So the change is about the contribution channel, not about removing existing translations.
One wording point matters for verification. The page describes the Translation Program in the past tense in places, saying it aimed to make Ethereum accessible by translating ethereum.org and other Ethereum content into as many languages as possible. Treat the paused Crowdin intake as the confirmed current operational fact, and treat the broader program status as something the page does not fully spell out.
Why the glossary is the live channel
The page explains the reasoning: the terms you approve are the terms ethereum.org uses in your language. Reviewed terms guide ethereum.org's translations and are published through the ETHGlossary API. Wallets, apps and documentation teams can use them too, through that open API.
That last point is the part worth checking for your own use. If you hold crypto assets and read wallet or app documentation in a non-English language, the glossary is upstream of the wording you see in those products. A term review is therefore not just a translation chore; it is a decision about how a safety-relevant word is rendered.
The page frames this in terms of inclusion, noting that much Ethereum content caters to English speakers and that providing non-English speakers with content in their native languages is seen as essential.
Verification checklist before you review
This is a multi-step task, so a checklist is appropriate. Each step maps to something the source states or leaves open.
- Confirm your language is supported. The page lists 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. If your language is not on that list, the source does not offer a path for you.
- Expect a draft for every term. The page states that every language has the same set of Ethereum terms, each with a draft translation. You are not starting from a blank page.
- Choose your action. You can approve a draft, propose a better alternative, or add context on how the term is used in your community.
- Budget the time honestly. The page says reviewing a single term takes a couple of minutes. That is the only timing figure given; any total for a full language pass would be a calculation, not a published number.
- Know where errors go. If you spot an error in an existing translation, the page asks you to open an issue on GitHub rather than route it through the glossary.
- Know where questions go. The page points to the ethereum.org Discord for questions or feedback.
A worked example of the decision
Suppose you read wallet documentation in Turkish and a term for a recovery-related concept feels ambiguous. Hypothetical: if the glossary has 40 terms for Turkish and each takes a couple of minutes to review, a full pass is roughly 80 minutes of review time. Calculation: 40 terms multiplied by 2 minutes equals 80 minutes. That is a planning estimate built on the page's stated per-term time, not a published total.
The better first move in that example is narrower. Find the specific term, check whether the draft matches how your community actually uses the word, and either approve it or propose an alternative with context. The page explicitly invites that context, which is the part a machine translation cannot supply.
What the source does not say
Several things a careful reader would want to know are not established by this page.
- It does not give a date for when Crowdin translation was paused or when ETHGlossary review became the recommended path.
- It does not state whether full-page translation will resume, or on what timeline.
- It does not explain how quickly an approved term reaches the live ethereum.org pages, only that reviewed terms guide translations.
- It does not describe account requirements, moderation rules, or how disputes between reviewers are resolved.
- It does not quantify how many terms exist per language, so any total review time is an estimate.
- It does not say whether the API has usage limits or access conditions.
How to read the status labels
Keep three labels separate. Confirmed current state: Crowdin full-page translation is paused and new submissions are not accepted. Confirmed available alternative: ETHGlossary review, with approve, propose, and add-context actions. Unclear: the long-term future of the program and the speed of downstream publication.
For a reader who cares about access continuity, the practical takeaway is modest and concrete. The translation channel you may remember is closed to new submissions, the glossary is the stated alternative, and the output feeds both site translations and third-party documentation through an open API. Verify your language, pick the terms that affect how you read recovery and wallet instructions, and use the GitHub issue path for errors in existing pages.
Sources
Informational only. Not financial, legal or investment advice. Check the primary sources listed above before you act on anything here.