Verifying the ethereum.org Translation Program: What Changed
Crowdin page translation is paused; ETHGlossary term review is the active way to contribute. Here is how to verify that shift and what remains unstated.
The verified change is this: full-page translation through Crowdin is paused, and new translation submissions are not being accepted there. Reviewing terms on ETHGlossary is the current route for contributing in the meantime. A reader who wants to check whether a translation program is still open should confirm both of those points against the source before acting.
The stated goal behind the program is broad accessibility. Ethereum, the source says, should read naturally in every language, and much of the community's content has catered to English speakers, leaving out the world's 6 billion non-English speakers. The program aimed to translate ethereum.org and other Ethereum content into as many languages as possible. Those are stated aims, not measured outcomes.
What the current contribution path is
The source names ETHGlossary as the best way to help right now: a shared, community-reviewed glossary of Ethereum terms in 24 languages. The workflow described is review rather than page translation. Each language has the same set of Ethereum terms, each with a draft translation. A reviewer can approve the draft, propose a better alternative, or add context on how the term is used in the community.
The stated consequence of that review matters for anyone checking quality. The terms you approve are the terms ethereum.org uses in your language, and reviewed terms guide ethereum.org's translations and are published through the ETHGlossary API. Wallets, apps and documentation teams can also use them through that open API. So a term decision is not confined to one page; it can travel.
- Step 1: Confirm the contribution channel. The source says Crowdin full-page translation is paused and new submissions are not accepted there.
- Step 2: Confirm the active channel. The source says reviewing terms on ETHGlossary is how to contribute in the meantime.
- Step 3: Check language coverage. The source lists 24 languages, including 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.
- Step 4: Check the review options. The source describes three: approve the draft, propose a better alternative, or add context on community usage.
- Step 5: Know where results go. Reviewed terms guide ethereum.org translations and are published through the ETHGlossary API, which other teams can use.
Effort and error routing
The source states that reviewing a single term takes a couple of minutes. That is a stated estimate, not a benchmark anyone here measured. For a reader deciding whether to start, it implies the unit of work is small and repeatable rather than a full-page commitment.
Two correction paths are given. If you spot an error in an existing translation, the source asks you to open an issue on GitHub. To ask questions or share feedback, it points to the ethereum.org Discord. Neither path is described in further detail, so the exact response time and triage process are not established by the source.
The source also credits past contributors. It says thousands of community members translated ethereum.org and are the key part of the program, that their work remains live on the site, and that recognition on the acknowledgements and contributors pages stays in place. This is a statement about attribution, not a statement that the old submission channel has reopened.
Why this matters for access continuity
For readers who hold crypto assets and depend on wallets and documentation in their own language, the practical link is terminology. The source says wallets, apps and documentation teams can use the glossary terms through the open API. Shared, reviewed terms reduce the chance that the same concept carries different labels across a wallet, an app, and a help page. The source does not claim that terminology alignment prevents loss or speeds recovery; it describes the glossary as a shared reference.
A cautious reader should treat glossary review as a contribution task, not as a security control. Nothing in the source says that reviewing or approving a term changes a wallet's behavior, recovery process, or backup requirements.
What the source does not say
- No date is given for when Crowdin page translation paused, when it might resume, or when ETHGlossary review began.
- No total number of terms, no per-language completion percentage, and no review queue size is stated.
- No criteria are given for who may approve a term, whether an account is required, or how disputes between reviewers are resolved.
- No API documentation, rate limits, or versioning details are described beyond the existence of an open API.
- No statement confirms that any specific reviewer's proposed term has been accepted, published, or adopted by a wallet or app team.
- The source does not say whether paused Crowdin work will be migrated to ETHGlossary or handled some other way.
- No measured impact is provided for the accessibility goal or the 6 billion non-English speakers figure.
- No verification of translation accuracy, testing of exported glossary data, or independent audit is described.
How to read the program status without overreaching
Separate the announcement from availability. The source announces a pause on Crowdin page translation and names ETHGlossary review as the interim way to contribute. It does not announce a new translation submission intake, an approval of any particular term set, or a completion date. Treat "paused" and "available" as different states, and check the named channel rather than assuming the older one still accepts work.
Separate the stated purpose from evidence of results. The source says Ethereum should read naturally in every language and that translating content is essential for a global portal. Those are stated beliefs and aims. The source provides no measurement showing that the program achieved natural reading in any language, and no data on how many terms have been finalized.
Finally, distinguish a term recommendation from adoption. The source says reviewed terms guide ethereum.org translations and are published through the API, and that wallets, apps and documentation teams can use them. "Can use" is permission and availability, not proof of use. A reader checking a glossary claim should look for the published term itself, not for an inference that every downstream team has adopted it.
Sources
Informational only. Not financial, legal or investment advice. Check the primary sources listed above before you act on anything here.