From 7cab2e67ccb9d20e734626ddf77d7fc4974e13db Mon Sep 17 00:00:00 2001 From: Lorenzo Zabot Date: Thu, 26 Feb 2026 10:22:31 +0100 Subject: [PATCH 001/127] docs: correct Github typo across whole website --- .../developers/docs/frameworks/index.md | 2 +- .../content/developers/docs/networks/index.md | 2 +- public/content/nft/index.md | 2 +- public/content/roadmap/fusaka/index.md | 2 +- public/content/translations/ar/nft/index.md | 2 +- .../bn/developers/docs/frameworks/index.md | 2 +- public/content/translations/bn/nft/index.md | 2 +- .../cs/developers/docs/frameworks/index.md | 2 +- .../cs/developers/docs/networks/index.md | 2 +- .../adding-desci-projects/index.md | 2 +- .../de/developers/docs/frameworks/index.md | 2 +- public/content/translations/de/nft/index.md | 2 +- .../es/developers/docs/frameworks/index.md | 2 +- .../es/developers/docs/networks/index.md | 2 +- public/content/translations/es/nft/index.md | 2 +- .../fr/developers/docs/frameworks/index.md | 2 +- public/content/translations/fr/nft/index.md | 2 +- public/content/translations/hi/nft/index.md | 2 +- public/content/translations/id/nft/index.md | 2 +- .../it/developers/docs/frameworks/index.md | 2 +- .../index.md | 2 +- public/content/translations/it/nft/index.md | 2 +- .../ja/developers/docs/networks/index.md | 2 +- public/content/translations/ja/nft/index.md | 2 +- public/content/translations/ko/nft/index.md | 2 +- .../pl/developers/docs/frameworks/index.md | 2 +- .../pl/developers/docs/networks/index.md | 2 +- .../index.md | 2 +- public/content/translations/pl/eips/index.md | 2 +- .../contributing/adding-layer-2s/index.md | 2 +- .../adding-staking-products/index.md | 2 +- .../developers/docs/apis/json-rpc/index.md | 2 +- .../programming-languages/dot-net/index.md | 4 ++-- .../index.md | 2 +- .../content/translations/pt-br/eips/index.md | 2 +- public/content/translations/ru/nft/index.md | 2 +- .../sw/developers/docs/frameworks/index.md | 2 +- .../sw/developers/docs/networks/index.md | 2 +- public/content/translations/sw/nft/index.md | 2 +- .../te/developers/docs/frameworks/index.md | 2 +- .../te/developers/docs/networks/index.md | 2 +- .../tr/contributing/design/index.md | 2 +- .../tr/developers/docs/frameworks/index.md | 2 +- .../tr/developers/docs/networks/index.md | 2 +- .../index.md | 2 +- .../tutorials/erc20-with-safety-rails/index.md | 2 +- public/content/translations/tr/nft/index.md | 2 +- .../translations/tr/roadmap/fusaka/index.md | 2 +- .../tutorials/server-components/index.md | 2 +- public/content/translations/uk/nft/index.md | 2 +- public/content/translations/vi/nft/index.md | 2 +- .../developers/docs/apis/backend/index.md | 16 ++++++++-------- .../developers/docs/apis/javascript/index.md | 10 +++++----- .../zh-tw/developers/docs/frameworks/index.md | 2 +- .../zh-tw/developers/docs/networks/index.md | 2 +- .../zh-tw/developers/docs/storage/index.md | 18 +++++++++--------- public/content/translations/zh-tw/nft/index.md | 2 +- .../adding-desci-projects/index.md | 2 +- .../zh/contributing/adding-resources/index.md | 2 +- .../zh/developers/docs/frameworks/index.md | 2 +- .../zh/developers/docs/networks/index.md | 2 +- .../tutorials/ethereum-for-web2-auth/index.md | 2 +- public/content/translations/zh/nft/index.md | 2 +- .../mocks/fetch-developer-tools.json | 4 ++-- src/intl/hi/page-about.json | 6 +++--- src/intl/it/page-about.json | 6 +++--- src/intl/pt-br/page-about.json | 6 +++--- src/intl/ru/page-about.json | 6 +++--- src/intl/sw/common.json | 2 +- src/intl/tr/common.json | 2 +- 70 files changed, 99 insertions(+), 99 deletions(-) diff --git a/public/content/developers/docs/frameworks/index.md b/public/content/developers/docs/frameworks/index.md index a7bf3a1b87c..62ebcc20a68 100644 --- a/public/content/developers/docs/frameworks/index.md +++ b/public/content/developers/docs/frameworks/index.md @@ -124,7 +124,7 @@ Before diving into frameworks, we recommend you first read through our introduct - [Website](https://catapulta.sh/) - [Documentation](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (powered by Covalent) -** **_GoldRush offers the most comprehensive blockchain data API suite for developers, analysts, and enterprises. Whether you are building a DeFi dashboard, a wallet, a trading bot, an AI agent or a compliance platform, the data APIs provide fast, accurate, and developer-friendly access to the essential onchain data you need_** diff --git a/public/content/developers/docs/networks/index.md b/public/content/developers/docs/networks/index.md index 5c8cc7d0333..b9ec0e53cd0 100644 --- a/public/content/developers/docs/networks/index.md +++ b/public/content/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery is a unique kind of testnet that fully resets every month. The executio ##### Resources - [Website](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [Community chat](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/nft/index.md b/public/content/nft/index.md index 77406c62def..347fc4620a0 100644 --- a/public/content/nft/index.md +++ b/public/content/nft/index.md @@ -67,7 +67,7 @@ Maybe you are an artist that wants to share their work using NFTs, without losin Or consider a ticket to a sporting event. Just as an **organizer of an event can choose how many tickets to sell**, the creator of an NFT can decide how many replicas exist. Sometimes these are exact replicas, such as 5000 General Admission tickets. Sometimes several are minted that are very similar, but each slightly different, such as a ticket with an assigned seat. These can be bought and sold peer-to-peer without paying ticket handlers and the buyer always with assurance of the ticket authenticity by checking the contract address. -On ethereum.org, **NFTs are used to demonstrate that people have meaningfully contributed** to our Github repository (programmed the website, written or modified an article...), translated our content, or attended our community calls, and we've even got our own NFT domain name. If you contribute to ethereum.org, you can claim a [POAP](/glossary/#poap) NFT. Some crypto meetups have used POAPs as tickets. [More on contributing](/contributing/#poap). You can also explore our [ethereum.org collectibles](/collectibles/) page to see community achievement NFTs. +On ethereum.org, **NFTs are used to demonstrate that people have meaningfully contributed** to our GitHub repository (programmed the website, written or modified an article...), translated our content, or attended our community calls, and we've even got our own NFT domain name. If you contribute to ethereum.org, you can claim a [POAP](/glossary/#poap) NFT. Some crypto meetups have used POAPs as tickets. [More on contributing](/contributing/#poap). You can also explore our [ethereum.org collectibles](/collectibles/) page to see community achievement NFTs. ![ethereum.org POAP](./poap.png) diff --git a/public/content/roadmap/fusaka/index.md b/public/content/roadmap/fusaka/index.md index 4ccc4a0ef3d..cac0ca9fe87 100644 --- a/public/content/roadmap/fusaka/index.md +++ b/public/content/roadmap/fusaka/index.md @@ -187,7 +187,7 @@ This EIP is in a section apart from the "Core EIPs" because the fork doesn't act ### Does this upgrade affect all Ethereum nodes and validators? {#does-this-upgrade-affect-all-ethereum-nodes-and-validators} -Yes, the Fusaka upgrade requires updates to both [execution clients and consensus clients](/developers/docs/nodes-and-clients/). All main Ethereum clients will release versions supporting the hard fork marked as high priority. You can keep up with when these releases will be available in client Github repos, their [Discord channels](https://ethstaker.org/support), the [EthStaker Discord](https://dsc.gg/ethstaker), or by subscribing to the Ethereum blog for protocol updates. To maintain synchronization with the Ethereum network post-upgrade, node operators must ensure they are running a supported client version. Note that the information about client releases is time-sensitive, and users should refer to the latest updates for the most current details. +Yes, the Fusaka upgrade requires updates to both [execution clients and consensus clients](/developers/docs/nodes-and-clients/). All main Ethereum clients will release versions supporting the hard fork marked as high priority. You can keep up with when these releases will be available in client GitHub repos, their [Discord channels](https://ethstaker.org/support), the [EthStaker Discord](https://dsc.gg/ethstaker), or by subscribing to the Ethereum blog for protocol updates. To maintain synchronization with the Ethereum network post-upgrade, node operators must ensure they are running a supported client version. Note that the information about client releases is time-sensitive, and users should refer to the latest updates for the most current details. ### How can ETH be converted after the hard fork? {#how-can-eth-be-converted-after-the-hardfork} diff --git a/public/content/translations/ar/nft/index.md b/public/content/translations/ar/nft/index.md index 9108e29251c..df95e6d5c1b 100644 --- a/public/content/translations/ar/nft/index.md +++ b/public/content/translations/ar/nft/index.md @@ -62,7 +62,7 @@ summaryPoint3: مدعومة بواسطة العقود الذكية التي تق أو لنفترض وجود تذكرة حضور حدث رياضي. تمامًا كما يستطيع منظم حدث اختيار عدد التذاكر المتاحة للبيع، يمكن لمنشئ الرمز غير القابل للاستبدال أن يقرر عدد النسخ المتماثلة. يمكن أحيانًا تحديد عدد النسخ بالضبط، مثل 5000 تذكرة دخول عامة. وأحيانًا أخرى تتشابه النسخ بشكل كبير، ولكن مع وجود اختلاف طفيف لكل منها، مثل تذكرة مقعد مخصص. هذه التذاكر يمكن شراؤها وبيعها بنظام الند للند بلا حاجة للدفع بشكل مباشر لحامل البطاقات الفعلية والمشتري يمكنه دائمًا التأكد من أصالة التذاكر من خلال مراجعة العقد الذكي. -على ethereum.org، تستخدم الرموز غير القابلة للاستبدال للإشارة إلى تقديم الأشخاص مساهمات لمخزن Github الخاص بنا أو حضروا اجتماعات معينة، حتى أننا حصلنا على اسم نطاق خاص بنا مخصص للرمز غير القابل للاستبدال. إذا كنت مساهمًا في ethereum.org، يمكنك المطالبة برمز غير قابل للاستبدال لبروتوكول إثبات الحضور. استخدمت بعض اجتماعات العملات الرقمية بروتوكولات إثبات الحضور كتذاكر. [المزيد عن المساهمة](/contributing/#poap). +على ethereum.org، تستخدم الرموز غير القابلة للاستبدال للإشارة إلى تقديم الأشخاص مساهمات لمخزن GitHub الخاص بنا أو حضروا اجتماعات معينة، حتى أننا حصلنا على اسم نطاق خاص بنا مخصص للرمز غير القابل للاستبدال. إذا كنت مساهمًا في ethereum.org، يمكنك المطالبة برمز غير قابل للاستبدال لبروتوكول إثبات الحضور. استخدمت بعض اجتماعات العملات الرقمية بروتوكولات إثبات الحضور كتذاكر. [المزيد عن المساهمة](/contributing/#poap). ![POAP لـ ethereum.org](./poap.png) diff --git a/public/content/translations/bn/developers/docs/frameworks/index.md b/public/content/translations/bn/developers/docs/frameworks/index.md index 9e39a7e09c8..9882c1ba239 100644 --- a/public/content/translations/bn/developers/docs/frameworks/index.md +++ b/public/content/translations/bn/developers/docs/frameworks/index.md @@ -121,7 +121,7 @@ lang: bn - [ওয়েবসাইট](https://catapulta.sh/) - [ডকুমেন্টেশন](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (Covalent দ্বারা চালিত) -** **_GoldRush ডেভেলপার, বিশ্লেষক এবং এন্টারপ্রাইজদের জন্য সবচেয়ে ব্যাপক ব্লকচেইন ডেটা API স্যুট অফার করে। আপনি একটি DeFi ড্যাশবোর্ড, একটি ওয়ালেট, একটি ট্রেডিং বট, একটি AI এজেন্ট বা একটি কমপ্লায়েন্স প্ল্যাটফর্ম তৈরি করুন না কেন, ডেটা APIগুলি আপনার প্রয়োজনীয় অনচেইন ডেটাতে দ্রুত, নির্ভুল এবং ডেভেলপার-বান্ধব অ্যাক্সেস প্রদান করে_** diff --git a/public/content/translations/bn/nft/index.md b/public/content/translations/bn/nft/index.md index 72fbee6d6a9..5048cf602ae 100644 --- a/public/content/translations/bn/nft/index.md +++ b/public/content/translations/bn/nft/index.md @@ -62,7 +62,7 @@ NFT অনেক কিছুর জন্য ব্যবহার করা অথবা একটি ক্রীড়া ইভেন্টের একটি টিকিট বিবেচনা করুন। ঠিক যেমন একটি ইভেন্টের একজন সংগঠক কতগুলি টিকিট বিক্রি করবেন তা পছন্দ করতে পারেন, তেমনি একটি NFT-এর নির্মাতা নির্ধারণ করতে পারেন কতগুলি প্রতিলিপি বিদ্যমান। কখনও কখনও এগুলি অবিকল প্রতিলিপি হয়, যেমন 5000 সাধারণ ভর্তির টিকিট। কখনও কখনও অনেকগুলি মিন্ট করা হয় যা খুব একই রকম, তবে প্রতিটি কিছুটা আলাদা, যেমন একটি নির্ধারিত আসন সহ একটি টিকিট। এগুলি টিকিট হ্যান্ডলারদের অর্থ প্রদান না করেই পিয়ার-টু-পিয়ার কেনা এবং বিক্রি করা যেতে পারে এবং কনট্র্যাক্টের অ্যাড্রেস চেক করে ক্রেতাকে টিকিটের বিশুদ্ধতার নিশ্চয়তা দেয়। -ethereum.org-এ, NFT ব্যবহার করা হয় তা দেখানোর জন্য যে লোকেরা আমাদের Github রেপোজিটোরিতে অবদান রেখেছে বা কল এটেন্ড করেছে, এবং এমনকি আমরা আমাদের নিজস্ব NFT ডোমেইন নামও পেয়েছি। আপনি যদি ethereum.org-এ অবদান রাখেন, আপনি একটি POAP NFT দাবি করতে পারেন। কিছু ক্রিপ্টো মিটআপে টিকেট হিসাবে POAP ব্যবহার করা হয়েছে। [অবদান সম্পর্কে আরো](/contributing/#poap)। +ethereum.org-এ, NFT ব্যবহার করা হয় তা দেখানোর জন্য যে লোকেরা আমাদের GitHub রেপোজিটোরিতে অবদান রেখেছে বা কল এটেন্ড করেছে, এবং এমনকি আমরা আমাদের নিজস্ব NFT ডোমেইন নামও পেয়েছি। আপনি যদি ethereum.org-এ অবদান রাখেন, আপনি একটি POAP NFT দাবি করতে পারেন। কিছু ক্রিপ্টো মিটআপে টিকেট হিসাবে POAP ব্যবহার করা হয়েছে। [অবদান সম্পর্কে আরো](/contributing/#poap)। ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/cs/developers/docs/frameworks/index.md b/public/content/translations/cs/developers/docs/frameworks/index.md index cd02dfca5cd..f431868d7e1 100644 --- a/public/content/translations/cs/developers/docs/frameworks/index.md +++ b/public/content/translations/cs/developers/docs/frameworks/index.md @@ -124,7 +124,7 @@ Než se ponoříte do frameworků, doporučujeme vám nejprve si přečíst ná - [Webová stránka](https://catapulta.sh/) - [Dokumentace](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (využívá Covalent) –** **_GoldRush nabízí nejkomplexnější sadu API pro data z blockchainu pro vývojáře, analytiky a podniky. Ať už vytváříte DeFi dashboard, peněženku, obchodního bota, AI agenta nebo platformu pro dodržování předpisů, datová API poskytují rychlý, přesný a pro vývojáře přívětivý přístup k základním onchain datům, která potřebujete_** diff --git a/public/content/translations/cs/developers/docs/networks/index.md b/public/content/translations/cs/developers/docs/networks/index.md index 252cc599d2c..0fa09623cdf 100644 --- a/public/content/translations/cs/developers/docs/networks/index.md +++ b/public/content/translations/cs/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery je jedinečný druh testnetu, který se každý měsíc plně resetuje. ##### Zdroje - [Webové stránky](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [Komunitní chat](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/de/contributing/adding-desci-projects/index.md b/public/content/translations/de/contributing/adding-desci-projects/index.md index 2d5091c7a30..80a03c59d60 100644 --- a/public/content/translations/de/contributing/adding-desci-projects/index.md +++ b/public/content/translations/de/contributing/adding-desci-projects/index.md @@ -37,7 +37,7 @@ Ethereum befindet sich in der Entwicklung. Daher kommen und gehen Teams und Prod - sicherstellen, dass alle aufgelisteten Projekte weiterhin unsere Kriterien erfüllen - Überprüfen, ob Produkte vorgeschlagen wurden, die unsere Kriterien besser erfüllen als die derzeit aufgeführten -Ethereum.org wird von der Open-Source-Community gepflegt; wir sind auf die Hilfe der Community angewiesen, um diese Seite auf dem neuesten Stand zu halten. Wenn Sie bemerken, dass Informationen zu den aufgelisteten Projekten aktualisiert werden müssen, öffnen Sie bitte ein Ticket oder einen Pull-Request in unserem Github-Repository. +Ethereum.org wird von der Open-Source-Community gepflegt; wir sind auf die Hilfe der Community angewiesen, um diese Seite auf dem neuesten Stand zu halten. Wenn Sie bemerken, dass Informationen zu den aufgelisteten Projekten aktualisiert werden müssen, öffnen Sie bitte ein Ticket oder einen Pull-Request in unserem GitHub-Repository. ## Nutzungsbedingungen {#terms-of-use} diff --git a/public/content/translations/de/developers/docs/frameworks/index.md b/public/content/translations/de/developers/docs/frameworks/index.md index 25b2032dc40..c95a0027ed6 100644 --- a/public/content/translations/de/developers/docs/frameworks/index.md +++ b/public/content/translations/de/developers/docs/frameworks/index.md @@ -116,7 +116,7 @@ Bevor Sie sich mit Frameworks beschäftigen, empfehlen wir, dass Sie sich mit de - [Website](https://catapulta.sh/) - [Dokumentation](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **Covalent –** **_erweiterte Blockchain-APIs für über 200 Ketten._** diff --git a/public/content/translations/de/nft/index.md b/public/content/translations/de/nft/index.md index 749e4c1f642..1978b43f43a 100644 --- a/public/content/translations/de/nft/index.md +++ b/public/content/translations/de/nft/index.md @@ -66,7 +66,7 @@ Vielleicht sind Sie ein Künstler, der seine Werke mithilfe von NFTs verbreiten Oder denken Sie an ein Ticket für ein Sportevent. So wie ein **Organisator einer Veranstaltung wählen kann, wie viele Tickets er verkaufen möchte**, kann der Ersteller eines NFT entscheiden, wie viele Repliken existieren. Manchmal handelt es sich dabei um genaue Repliken, wie etwa 5.000 Tickets mit freier Platzwahl. Manchmal werden auch mehrere Stücke geprägt, die zwar sehr ähnlich sind, aber doch leichte Unterschiede aufweisen, wie z. B. ein Ticket mit einem zugewiesenem Sitzplatz. Diese können auf Peer-to-Peer-Basis gekauft und verkauft werden, ohne dass Zwischenhändler dafür bezahlt werden müssen. Dabei kann sich der Käufer durch Überprüfung der Contract-Adresse stets von der Echtheit des Tickets überzeugen. -Auf ethereum.org werden **NFTs verwendet, um zu zeigen, dass Menschen einen sinnvollen Beitrag** zu unserem Github-Repository geleistet (die Website programmiert, einen Artikel geschrieben oder geändert ...), Inhalte übersetzt oder an Community-Calls teilgenommen haben. Wir haben sogar unseren eigenen NFT-Domänennamen. Wenn Sie Beiträge zu ethereum.org leisten, können Sie einen [POAP](/glossary/#poap) -NFT beanspruchen. Bei einigen Krypto-Treffen wurden POAPs als Tickets verwendet. [Mehr zum Beitragen](/contributing/#poap). +Auf ethereum.org werden **NFTs verwendet, um zu zeigen, dass Menschen einen sinnvollen Beitrag** zu unserem GitHub-Repository geleistet (die Website programmiert, einen Artikel geschrieben oder geändert ...), Inhalte übersetzt oder an Community-Calls teilgenommen haben. Wir haben sogar unseren eigenen NFT-Domänennamen. Wenn Sie Beiträge zu ethereum.org leisten, können Sie einen [POAP](/glossary/#poap) -NFT beanspruchen. Bei einigen Krypto-Treffen wurden POAPs als Tickets verwendet. [Mehr zum Beitragen](/contributing/#poap). ![ethereum.org-POAP](./poap.png) diff --git a/public/content/translations/es/developers/docs/frameworks/index.md b/public/content/translations/es/developers/docs/frameworks/index.md index 92beb4b6476..5ab41e69512 100644 --- a/public/content/translations/es/developers/docs/frameworks/index.md +++ b/public/content/translations/es/developers/docs/frameworks/index.md @@ -116,7 +116,7 @@ Antes de profundizar en los frameworks, recomendamos leer primero nuestra introd - [Sitio web](https://catapulta.sh/) - [Documentación](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (impulsado por Covalent) -** **_GoldRush ofrece el conjunto más completo de API de datos de la cadena de bloques para desarrolladores, analistas y empresas. Tanto si está creando un panel de DeFi, una billetera, un bot de trading, un agente de IA o una plataforma de cumplimiento, las API de datos proporcionan un acceso rápido, preciso y fácil para los desarrolladores a los datos en cadena esenciales que necesita_** diff --git a/public/content/translations/es/developers/docs/networks/index.md b/public/content/translations/es/developers/docs/networks/index.md index e0eb58475de..7edfdb9648f 100644 --- a/public/content/translations/es/developers/docs/networks/index.md +++ b/public/content/translations/es/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery es un tipo único de red de prueba que se reinicia por completo cada me ##### Recursos - [Sitio web](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [Chat de la comunidad](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/es/nft/index.md b/public/content/translations/es/nft/index.md index ec598e146f3..cd95eb19b84 100644 --- a/public/content/translations/es/nft/index.md +++ b/public/content/translations/es/nft/index.md @@ -69,7 +69,7 @@ Tal vez sea usted un artista que quiere compartir su arte a través de los NFT, O pongamos, por ejemplo, una entrada a un evento deportivo. Así como un **organizador de eventos puede elegir cuántas entradas vender**, el creador de un NFT puede decidir cuántas réplicas existen. En algunos casos las copias son idénticas, como 5.000 entradas de admisión general. Algunas veces muchas copias acuñadas son muy similares, pero cada una difiere ligeramente, como una entrada con un asiento asignado. Estas se pueden comprar y vender entre pares directamente, sin tener que pasar por promotores o intermediarios de venta, porque pueden asegurarse de la autenticidad de la entrada revisando la dirección del contrato donde se crearon. -En ethereum.org, **los NFT se usan para demostrar que las personas han contribuido de manera significativa** a nuestro repositorio de Github (programando el sitio web, escribiendo o modificando un artículo...), traduciendo nuestro contenido, o asistiendo a nuestras llamadas comunitarias, e incluso tenemos nuestro propio dominio NFT. Si contribuye a ethereum.org, puede reclamar un NFT [POAP](/glossary/#poap). Algunos eventos y encuentros de criptomonedas utilizan POAP (protocolos de prueba de asistencia) para sus entradas. [Más información sobre cómo contribuir](/contributing/#poap). +En ethereum.org, **los NFT se usan para demostrar que las personas han contribuido de manera significativa** a nuestro repositorio de GitHub (programando el sitio web, escribiendo o modificando un artículo...), traduciendo nuestro contenido, o asistiendo a nuestras llamadas comunitarias, e incluso tenemos nuestro propio dominio NFT. Si contribuye a ethereum.org, puede reclamar un NFT [POAP](/glossary/#poap). Algunos eventos y encuentros de criptomonedas utilizan POAP (protocolos de prueba de asistencia) para sus entradas. [Más información sobre cómo contribuir](/contributing/#poap). ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/fr/developers/docs/frameworks/index.md b/public/content/translations/fr/developers/docs/frameworks/index.md index 977575207ca..1912c7eed44 100644 --- a/public/content/translations/fr/developers/docs/frameworks/index.md +++ b/public/content/translations/fr/developers/docs/frameworks/index.md @@ -116,7 +116,7 @@ Avant de plonger dans les infrastructures, nous vous recommandons de commencer p - [Site Web](https://catapulta.sh/) - [Documentation](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **Covalent** - **_APIs blockchain enrichie pour plus de 200 chaines._** diff --git a/public/content/translations/fr/nft/index.md b/public/content/translations/fr/nft/index.md index 15eb35a83d7..92aba4746f6 100644 --- a/public/content/translations/fr/nft/index.md +++ b/public/content/translations/fr/nft/index.md @@ -67,7 +67,7 @@ Vous êtes peut-être un artiste qui souhaite partager ses œuvres à l'aide de Par exemple, pensez à un billet pour un événement sportif. Tout comme **l'organisateur d'un événement peut décider du nombre de billets à vendre**, le créateur d'un NFT peut décider du nombre de répliques existantes. Il s'agit parfois de répliques exactes telles que 5 000 billets d'entrée générale. Parfois, plusieurs très similaires sont créés, chacun légèrement différent, comme un billet avec un siège assigné. Ils peuvent être achetés et vendus de pair à pair sans avoir à payer de frais de billetterie et l'acheteur peut toujours s'assurer de l'authenticité du billet en vérifiant l'adresse du contrat. -Sur ethereum.org, les **NFT sont utilisés pour démontrer que des personnes ont contribué** de manière significative à notre dépôt Github (programmation du site web, rédaction ou modification d'un article...), ont traduit notre contenu, ou ont participé à nos appels à la communauté, et nous avons même notre propre nom de domaine NFT. Si vous contribuez à ethereum.org, vous pouvez réclamer un NFT [POAP](/glossary/#poap). Certains rassemblements crypto ont utilisé des POAP comme billets. [Plus d'infos sur la contribution](/contributing/#poap). +Sur ethereum.org, les **NFT sont utilisés pour démontrer que des personnes ont contribué** de manière significative à notre dépôt GitHub (programmation du site web, rédaction ou modification d'un article...), ont traduit notre contenu, ou ont participé à nos appels à la communauté, et nous avons même notre propre nom de domaine NFT. Si vous contribuez à ethereum.org, vous pouvez réclamer un NFT [POAP](/glossary/#poap). Certains rassemblements crypto ont utilisé des POAP comme billets. [Plus d'infos sur la contribution](/contributing/#poap). ![POAP ethereum.org](./poap.png) diff --git a/public/content/translations/hi/nft/index.md b/public/content/translations/hi/nft/index.md index a7f6093a4ea..256e1f475b3 100644 --- a/public/content/translations/hi/nft/index.md +++ b/public/content/translations/hi/nft/index.md @@ -66,7 +66,7 @@ NFT का इस्तेमाल कई चीजों के लिए क या एक खेल इवेंट के टिकट पर विचार करें। जिस तरह** किसी इवेंट का आयोजक कितने टिकट बेचना चुन सकता है**, उसी तरह NFT बनाने वाला यह तय कर सकता है कि कितनी कॉपी मौजूद हैं। कभी-कभी यह सटीक कॉपी होती हैं, जैसे 5000 सामान्य प्रवेश टिकट। कभी-कभी कई ऐसे खनन किए जाते हैं जो बहुत समान होते हैं, लेकिन हर एक, थोड़ा अलग होता है, जैसे कि एक नियत सीट वाला टिकट। ये, टिकट हैंडलर्स को भुगतान किए बिना, सहकर्मियों के बीच खरीदे और बेचे जा सकते हैं और खरीदार के पास हमेशा, कॉन्ट्रैक्ट पते की जांच करके टिकट की मान्यता का आश्वासन रहता है। -ethereum.org पर, **NFT का उपयोग यह प्रदर्शित करने के लिए किया जाता है कि लोगों ने सार्थक योगदान दिया है** हमारे Github रिपॉजिटरी में (वेबसाइट को प्रोग्राम किया, एक लेख लिखा या संशोधित किया...), हमारी सामग्री का अनुवाद किया, या हमारे सामुदायिक कॉल में भाग लिया, और हमें अपना NFT डोमेन का नाम भी मिल गया है। अगर आप ethereum.org में योगदान करते हैं, तो आप [POAP](/glossary/#poap) NFT का दावा कर सकते हैं। कुछ क्रिप्टो मीटअप में POAP का इस्तेमाल, टिकट के रूप में किया है। [योगदान करने के बारे में और जानकारी](/contributing/#poap)। +ethereum.org पर, **NFT का उपयोग यह प्रदर्शित करने के लिए किया जाता है कि लोगों ने सार्थक योगदान दिया है** हमारे GitHub रिपॉजिटरी में (वेबसाइट को प्रोग्राम किया, एक लेख लिखा या संशोधित किया...), हमारी सामग्री का अनुवाद किया, या हमारे सामुदायिक कॉल में भाग लिया, और हमें अपना NFT डोमेन का नाम भी मिल गया है। अगर आप ethereum.org में योगदान करते हैं, तो आप [POAP](/glossary/#poap) NFT का दावा कर सकते हैं। कुछ क्रिप्टो मीटअप में POAP का इस्तेमाल, टिकट के रूप में किया है। [योगदान करने के बारे में और जानकारी](/contributing/#poap)। ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/id/nft/index.md b/public/content/translations/id/nft/index.md index 82b9238ea6d..7fa10ba8e0d 100644 --- a/public/content/translations/id/nft/index.md +++ b/public/content/translations/id/nft/index.md @@ -67,7 +67,7 @@ Mungkin Anda adalah seorang seniman yang ingin berbagi karya mereka menggunakan Atau pertimbangkan tiket untuk sebuah acara olahraga. Sama halnya seperti **penyelenggara acara dapat memilih berapa banyak tiket yang akan dijual**, kreator NFT dapat memutuskan berapa banyak salinan yang ada. Terkadang ini adalah tiruan yang sama persis, seperti 5000 tiket Masuk Umum. Terkadang ada beberapa dicetak sangat serupa, tetapi masing-masing sedikit berbeda, seperti tiket dengan kursi yang ditentukan. Tiket-tiket ini dapat dibeli dan dijual secara peer-to-peer tanpa membayar petugas tiket, dan pembeli selalu memiliki jaminan keaslian tiket dengan memeriksa alamat kontrak. -Di ethereum.org, **NFT digunakan untuk menunjukkan bahwa seseorang telah memberikan kontribusi yang berarti** pada repositori Github (memprogram situs web, menulis atau memodifikasi artikel...), menerjemahkan konten, atau menghadiri panggilan komunitas bahkan memiliki nama domain NFT kami sendiri. Jika berkontribusi pada ethereum.org, Anda dapat mengeklaim NFT [POAP](/glossary/#poap). Beberapa pertemuan kripto telah menggunakan POAP sebagai tiket. [Selengkapnya tentang berkontribusi](/contributing/#poap). +Di ethereum.org, **NFT digunakan untuk menunjukkan bahwa seseorang telah memberikan kontribusi yang berarti** pada repositori GitHub (memprogram situs web, menulis atau memodifikasi artikel...), menerjemahkan konten, atau menghadiri panggilan komunitas bahkan memiliki nama domain NFT kami sendiri. Jika berkontribusi pada ethereum.org, Anda dapat mengeklaim NFT [POAP](/glossary/#poap). Beberapa pertemuan kripto telah menggunakan POAP sebagai tiket. [Selengkapnya tentang berkontribusi](/contributing/#poap). ![POAP ethereum.org](./poap.png) diff --git a/public/content/translations/it/developers/docs/frameworks/index.md b/public/content/translations/it/developers/docs/frameworks/index.md index e7c0da024c2..297f8829260 100644 --- a/public/content/translations/it/developers/docs/frameworks/index.md +++ b/public/content/translations/it/developers/docs/frameworks/index.md @@ -116,7 +116,7 @@ Prima di iniziare a studiare i framework, raccomandiamo la lettura della nostra - [Sito Web](https://catapulta.sh/) - [Documentazione](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **Covalent -** **_API della blockchain arricchite per oltre 200 catene._** diff --git a/public/content/translations/it/developers/tutorials/hello-world-smart-contract-fullstack/index.md b/public/content/translations/it/developers/tutorials/hello-world-smart-contract-fullstack/index.md index 0a417e53d75..e231d766aa3 100644 --- a/public/content/translations/it/developers/tutorials/hello-world-smart-contract-fullstack/index.md +++ b/public/content/translations/it/developers/tutorials/hello-world-smart-contract-fullstack/index.md @@ -733,7 +733,7 @@ Come prerequisito, è necessario avere una comprensione di React a livello princ ### Clonare i file iniziali {#clone-the-starter-files} -Per prima cosa, vai al [repository hello-world-part-four in Github](https://github.com/alchemyplatform/hello-world-part-four-tutorial) per ottenere i file iniziali per questo progetto e clona questo repository nella tua macchina in locale. +Per prima cosa, vai al [repository hello-world-part-four in GitHub](https://github.com/alchemyplatform/hello-world-part-four-tutorial) per ottenere i file iniziali per questo progetto e clona questo repository nella tua macchina in locale. Apri il repository clonato localmente. Si noti che contiene due cartelle `starter-files` e `completed`. diff --git a/public/content/translations/it/nft/index.md b/public/content/translations/it/nft/index.md index 3279ce0720f..138da09b0fc 100644 --- a/public/content/translations/it/nft/index.md +++ b/public/content/translations/it/nft/index.md @@ -67,7 +67,7 @@ Magari sei un artista che vuole condividere il proprio lavoro utilizzando gli NF Oppure, prendiamo ad esempio un biglietto per un evento sportivo. Proprio come **l'organizzatore di un evento può scegliere quanti biglietti vendere**, il creatore di un NFT può decidere quante repliche esistono. A volte queste sono repliche esatte, come 5000 biglietti di ingresso generici. A volte ne vengono coniati diversi molto simili, ma ognuno leggermente diverso, come nel caso dei biglietti con i posti assegnati. Questi possono essere acquistati e venduti tra pari senza pagare i gestori dei biglietti e l'acquirente ha sempre la certezza dell'autenticità del biglietto controllando l'indirizzo del contratto. -Su ethereum.org, ** gli NFT vengono usati per dimostrare che le persone hanno contribuito significativamente ** alla nostra reposity di Github (programmato il sito web, scritto o modificato un articolo, ecc.), tradotto il nostro contenuto o partecipato alle chiamate con la community. E abbiamo, inoltre, il nostro personale nome del dominio NFT. Se contribuisci a ethereum.org, puoi rivendicare un NFT [POAP](/glossary/#poap). Alcuni incontri nel mondo delle criptovalute hanno usato i POAP come biglietti. [Maggiori informazioni sul contributo](/contributing/#poap). +Su ethereum.org, ** gli NFT vengono usati per dimostrare che le persone hanno contribuito significativamente ** alla nostra reposity di GitHub (programmato il sito web, scritto o modificato un articolo, ecc.), tradotto il nostro contenuto o partecipato alle chiamate con la community. E abbiamo, inoltre, il nostro personale nome del dominio NFT. Se contribuisci a ethereum.org, puoi rivendicare un NFT [POAP](/glossary/#poap). Alcuni incontri nel mondo delle criptovalute hanno usato i POAP come biglietti. [Maggiori informazioni sul contributo](/contributing/#poap). ![POAP di ethereum.org](./poap.png) diff --git a/public/content/translations/ja/developers/docs/networks/index.md b/public/content/translations/ja/developers/docs/networks/index.md index a2e03f03b15..550a0cfbd46 100644 --- a/public/content/translations/ja/developers/docs/networks/index.md +++ b/public/content/translations/ja/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemeryは、毎月完全にリセットされるユニークなテストネッ ##### リソース - [ウェブサイト](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [コミュニティチャット](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/ja/nft/index.md b/public/content/translations/ja/nft/index.md index 14d6d659eaa..716cee22430 100644 --- a/public/content/translations/ja/nft/index.md +++ b/public/content/translations/ja/nft/index.md @@ -67,7 +67,7 @@ NFTは以下のような多数の用途に使用されます。 あるいは、スポーツイベントのチケットを例に考えてみましょう。 **イベントの主催者が販売するチケットの枚数を選択できる**ように、NFTの作成者は存在するレプリカの数を決めることができます。 時には、5,000枚の一般入場券のようなまったく同じレプリカも存在します。 例えば、座席指定のチケットのように、よく似ていてもそれぞれに微妙な違いがあるものが複数枚ミントされることもあります。 チケットの売買はピアツーピアで行われ、購入者はコントラクトアドレスを確認することで、常にチケットの正当性を確認することができます。 -ethereum.orgでは、私たちのGithubリポジトリへの貢献（ウェブサイトのプログラミング、記事の執筆・修正など）、コンテンツの翻訳、コミュニティコールへの参加といった、**人々が有意義に貢献したことを証明するためにNFTが使用されて**います。また、私たちは独自のNFTドメイン名も持っています。 ethereum.orgに貢献すると、[POAP](/glossary/#poap) NFTを請求できます。 一部のクリプトミートアップでは、チケットとしてPOAPが使用されています。 [貢献についての詳細](/contributing/#poap)。 +ethereum.orgでは、私たちのGitHubリポジトリへの貢献（ウェブサイトのプログラミング、記事の執筆・修正など）、コンテンツの翻訳、コミュニティコールへの参加といった、**人々が有意義に貢献したことを証明するためにNFTが使用されて**います。また、私たちは独自のNFTドメイン名も持っています。 ethereum.orgに貢献すると、[POAP](/glossary/#poap) NFTを請求できます。 一部のクリプトミートアップでは、チケットとしてPOAPが使用されています。 [貢献についての詳細](/contributing/#poap)。 ![ethereum.orgのPOAP](./poap.png) diff --git a/public/content/translations/ko/nft/index.md b/public/content/translations/ko/nft/index.md index 9caf11269c7..b480c193723 100644 --- a/public/content/translations/ko/nft/index.md +++ b/public/content/translations/ko/nft/index.md @@ -56,7 +56,7 @@ NFT를 사용하여 통제권과 수익을 중개인에게 부여하지 않고 또는 스포츠 대회의 티켓을 예로 들어 봅시다. 이벤트 주최자가 판매할 티켓의 수를 선택할 수 있는 것처럼 NFT의 제작자는 복제품의 수를 결정할 수 있습니다. 가끔 이는 5000장의 일반 입장권처럼 동일한 복제품이기도 합니다. 간혹 지정 좌석 티켓처럼 매우 비슷하지만 각각 조금씩 다르게 발행되기도 합니다. 이는 매표원에게 따로 돈을 내지 않고 P2P로 사고 팔 수 있으며 구매자는 항상 계약 주소를 확인하여 티켓의 진위성을 확신합니다. -ethereum.org에서 NFT는 사람들이 Github 저장소에 의미 있는 기여(웹사이트를 프로그래밍하거나 기사 작성 또는 수정 등), 콘텐츠 번역 및 커뮤니티 통화에 참여했음을 증명하는 용도로 사용됩니다. 심지어 자체 NFT 도메인 이름도 있습니다. ethereum.org에 기여하셨다면 POAP NFT를 획득할 수 있습니다. 일부 암호화폐 밋업에서는 POAP를 입장권으로 사용하였습니다. [기여에 대해 자세히 알아보기](/contributing/#poap). +ethereum.org에서 NFT는 사람들이 GitHub 저장소에 의미 있는 기여(웹사이트를 프로그래밍하거나 기사 작성 또는 수정 등), 콘텐츠 번역 및 커뮤니티 통화에 참여했음을 증명하는 용도로 사용됩니다. 심지어 자체 NFT 도메인 이름도 있습니다. ethereum.org에 기여하셨다면 POAP NFT를 획득할 수 있습니다. 일부 암호화폐 밋업에서는 POAP를 입장권으로 사용하였습니다. [기여에 대해 자세히 알아보기](/contributing/#poap). ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/pl/developers/docs/frameworks/index.md b/public/content/translations/pl/developers/docs/frameworks/index.md index 17d9f582490..1f907766d62 100644 --- a/public/content/translations/pl/developers/docs/frameworks/index.md +++ b/public/content/translations/pl/developers/docs/frameworks/index.md @@ -118,7 +118,7 @@ Zanim zagłębisz się w frameworki, zalecamy najpierw przeczytać nasze wprowad - [Strona internetowa](https://catapulta.sh/) - [Dokumentacja](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (obsługiwany przez Covalent) -** **_GoldRush oferuje najbardziej kompleksowy pakiet API z danymi blockchain dla deweloperów, analityków i przedsiębiorstw._** **_Niezależnie od tego, czy budujesz pulpit DeFi, portfel, bota handlowego, agenta AI czy platformę zgodności, interfejsy API danych zapewniają szybki, dokładny i przyjazny dla programistów dostęp do niezbędnych danych on-chain, których potrzebujesz._** diff --git a/public/content/translations/pl/developers/docs/networks/index.md b/public/content/translations/pl/developers/docs/networks/index.md index 5109f87ab6a..5c45401bf0b 100644 --- a/public/content/translations/pl/developers/docs/networks/index.md +++ b/public/content/translations/pl/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery jest unikalną siecią testową, która resetuje się w pełni każdego ##### Źródła - [Strona internetowa](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [Czat społeczności](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/pl/developers/tutorials/smart-contract-security-guidelines/index.md b/public/content/translations/pl/developers/tutorials/smart-contract-security-guidelines/index.md index 62eec372652..d2be69654af 100644 --- a/public/content/translations/pl/developers/tutorials/smart-contract-security-guidelines/index.md +++ b/public/content/translations/pl/developers/tutorials/smart-contract-security-guidelines/index.md @@ -76,7 +76,7 @@ Architektura Twojej bazy kodu powinna ułatwić sprawdzenie twojego kodu. Unikaj - **Zapisz dokładne testy jednostkowe.** Rozległy zestaw testowy ma kluczowe znaczenie dla budowy oprogramowania wysokiej jakości. - **Napisz niestandardowe kontrole i właściwości dla narzędzi [Slither](https://github.com/crytic/slither), [Echidna](https://github.com/crytic/echidna) i [Manticore](https://github.com/trailofbits/manticore).** Automatyczne narzędzia pomogą zapewnić bezpieczeństwo umowy. Przejrzyj resztę tego przewodnika, aby dowiedzieć się, jak pisać skuteczne kontrole i właściwości. -- **Użyj [crytic.io](https://crytic.io/).** Crytic integruje się z Githubem, zapewnia dostęp do prywatnych detektorów Slither, i uruchamia niestandardowe kontrole właściwości z Echidny. +- **Użyj [crytic.io](https://crytic.io/).** Crytic integruje się z GitHubem, zapewnia dostęp do prywatnych detektorów Slither, i uruchamia niestandardowe kontrole właściwości z Echidny. ### Solidity {#solidity} diff --git a/public/content/translations/pl/eips/index.md b/public/content/translations/pl/eips/index.md index 35e747589f1..5ff1d5efa3a 100644 --- a/public/content/translations/pl/eips/index.md +++ b/public/content/translations/pl/eips/index.md @@ -22,7 +22,7 @@ Wraz z dostarczeniem specyfikacji technicznej zmian, EIP są jednostką, wokół ## Historia EIP {#history-of-eips} -[Repozytorium Github Ethereum Improvement Proposals (EIPs)](https://github.com/ethereum/EIPs) zostało stworzone w październiku 2015 r. Proces EIP opiera się na procesie [Bitcoin Improvement Proposals (BIP)](https://github.com/bitcoin/bips), który sam w sobie opiera się na [Python Enhancement Proposals (PEP)](https: //www.python.org/dev/peps/). +[Repozytorium GitHub Ethereum Improvement Proposals (EIPs)](https://github.com/ethereum/EIPs) zostało stworzone w październiku 2015 r. Proces EIP opiera się na procesie [Bitcoin Improvement Proposals (BIP)](https://github.com/bitcoin/bips), który sam w sobie opiera się na [Python Enhancement Proposals (PEP)](https: //www.python.org/dev/peps/). Edytorzy EIP są zobowiązani do sprawdzania EIP pod względem poprawności technicznej, formatowania, pisowni, gramatyki oraz stylu kodu. Martin Becze, Vitalik Buterin, Gavin Wood i kilka innych osób było pierwszymi edytorami EIP od 2015 r. do końca 2016 r. diff --git a/public/content/translations/pt-br/contributing/adding-layer-2s/index.md b/public/content/translations/pt-br/contributing/adding-layer-2s/index.md index c465ca5edd4..f558e1b15a1 100644 --- a/public/content/translations/pt-br/contributing/adding-layer-2s/index.md +++ b/public/content/translations/pt-br/contributing/adding-layer-2s/index.md @@ -90,7 +90,7 @@ _Não consideramos outras soluções de dimensionamento que não usam o Ethereum ## Adicione sua camada 2 {#add-exchange} -Se você quiser adicionar uma camada 2 ao ethereum.org, abra um tíquete no Github. +Se você quiser adicionar uma camada 2 ao ethereum.org, abra um tíquete no GitHub. Crie um ticket diff --git a/public/content/translations/pt-br/contributing/adding-staking-products/index.md b/public/content/translations/pt-br/contributing/adding-staking-products/index.md index f2a07f32901..4372b736db7 100644 --- a/public/content/translations/pt-br/contributing/adding-staking-products/index.md +++ b/public/content/translations/pt-br/contributing/adding-staking-products/index.md @@ -169,7 +169,7 @@ Atualmente, a lógica e os valores do código para esses critérios estão conti ## Adicione seu produto ou serviço {#add-product} -Se você quiser adicionar uma participação (stake) de produto ou serviço ao ethereum.org, crie um tíquete no Github. +Se você quiser adicionar uma participação (stake) de produto ou serviço ao ethereum.org, crie um tíquete no GitHub. Crie um ticket diff --git a/public/content/translations/pt-br/developers/docs/apis/json-rpc/index.md b/public/content/translations/pt-br/developers/docs/apis/json-rpc/index.md index 8c29fca6938..392627d556f 100644 --- a/public/content/translations/pt-br/developers/docs/apis/json-rpc/index.md +++ b/public/content/translations/pt-br/developers/docs/apis/json-rpc/index.md @@ -22,7 +22,7 @@ Embora você possa optar por interagir diretamente com clientes da Ethereum usan Esta página trata principalmente da API JSON-RPC usada pelos clientes de execução Ethereum. No entanto, os clientes de consenso também têm uma API RPC que permite aos usuários consultar informações sobre o nó, solicitar blocos Beacon, estado do Beacon, e outras informações relacionadas ao consenso diretamente de um nó. Essa API está documentada na [página da Web da API Beacon](https://ethereum.github.io/beacon-APIs/#/). -Uma API interna também é usada para comunicação entre clientes dentro de um nó - ou seja, permite que o cliente de consenso e o cliente de execução troquem dados. Ela é chamada de “API Engine” e suas especificações estão disponíveis no [Github](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md). +Uma API interna também é usada para comunicação entre clientes dentro de um nó - ou seja, permite que o cliente de consenso e o cliente de execução troquem dados. Ela é chamada de “API Engine” e suas especificações estão disponíveis no [GitHub](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md). ## Especificação do cliente de execução {#spec} diff --git a/public/content/translations/pt-br/developers/docs/programming-languages/dot-net/index.md b/public/content/translations/pt-br/developers/docs/programming-languages/dot-net/index.md index 70bd887d3e5..271882b7b7a 100644 --- a/public/content/translations/pt-br/developers/docs/programming-languages/dot-net/index.md +++ b/public/content/translations/pt-br/developers/docs/programming-languages/dot-net/index.md @@ -76,9 +76,9 @@ Procurando por mais recursos? Confira [ethereum.org/developers](/developers/). ## Colaboradores comunitários .NET {#dot-net-community-contributors} -Na Nethereum, nós geralmente nos encontramos no [Gitter](https://gitter.im/Nethereum/Nethereum) onde todos são bem vindos para fazer e responder perguntas, obter ajuda ou simplesmente relaxar. Sinta-se à vontade para fazer uma PR ou abrir uma questão no [repositório da Nethereum no Github](https://github.com/Nethereum), ou apenas para navegar pelos vários projetos paralelos e exemplos que temos. Você também pode nos encontrar em [Discord](https://discord.gg/jQPrR58FxX)! +Na Nethereum, nós geralmente nos encontramos no [Gitter](https://gitter.im/Nethereum/Nethereum) onde todos são bem vindos para fazer e responder perguntas, obter ajuda ou simplesmente relaxar. Sinta-se à vontade para fazer uma PR ou abrir uma questão no [repositório da Nethereum no GitHub](https://github.com/Nethereum), ou apenas para navegar pelos vários projetos paralelos e exemplos que temos. Você também pode nos encontrar em [Discord](https://discord.gg/jQPrR58FxX)! -Se você é novo no Nethermind e precisa de ajuda para começar, junte-se ao nosso [Discord](http://discord.gg/PaCMRFdvWT). Os nossos desenvolvedores estão prontos para responder às suas perguntas. Para PRs ou problemas, confira o [repositório do Github da Nethermind](https://github.com/NethermindEth/nethermind). +Se você é novo no Nethermind e precisa de ajuda para começar, junte-se ao nosso [Discord](http://discord.gg/PaCMRFdvWT). Os nossos desenvolvedores estão prontos para responder às suas perguntas. Para PRs ou problemas, confira o [repositório do GitHub da Nethermind](https://github.com/NethermindEth/nethermind). ## Outras listas agregadas {#other-aggregated-lists} diff --git a/public/content/translations/pt-br/developers/tutorials/smart-contract-security-guidelines/index.md b/public/content/translations/pt-br/developers/tutorials/smart-contract-security-guidelines/index.md index 6053257ce85..2f4fd829185 100644 --- a/public/content/translations/pt-br/developers/tutorials/smart-contract-security-guidelines/index.md +++ b/public/content/translations/pt-br/developers/tutorials/smart-contract-security-guidelines/index.md @@ -76,7 +76,7 @@ A arquitetura da sua base de código deve facilitar a revisão do seu código. E - **Escreva testes unitários completos.** Um conjunto extenso de testes é crucial para construir softwares de alta qualidade. - **Escreva propriedades e verificações personalizadas com [Slither](https://github.com/crytic/slither), [Echidna](https://github.com/crytic/echidna) e [Manticore](https://github.com/trailofbits/manticore).** Ferramentas automatizadas ajudarão a garantir que o seu contrato é seguro. Revise o resto deste guia para aprender a escrever propriedades e verificações eficientes. -- **Use o [crytic.io](https://crytic.io/).** O Critic integra-se ao Github, fornece acesso a detectores privados do Slither e executa verificações de propriedade personalizadas pelo Echidna. +- **Use o [crytic.io](https://crytic.io/).** O Critic integra-se ao GitHub, fornece acesso a detectores privados do Slither e executa verificações de propriedade personalizadas pelo Echidna. ### Solidity {#solidity} diff --git a/public/content/translations/pt-br/eips/index.md b/public/content/translations/pt-br/eips/index.md index fdb3327312f..fa79a666ce9 100644 --- a/public/content/translations/pt-br/eips/index.md +++ b/public/content/translations/pt-br/eips/index.md @@ -22,7 +22,7 @@ Além de fornecer uma especificação técnica para mudanças, as EIPs são a un ## Histórico de EIPs {#history-of-eips} -O repositório Github [Propostas de Melhorias do Ethereum (EIPs)](https://github.com/ethereum/EIPs) foi criado em outubro de 2015. O processo EIP é baseado no processo de [Propostas de Melhorias do Bitcoin (BIPs)](https://github.com/bitcoin/bips) que, por sua vez, é baseado no processo [Propostas de Melhorias do Python (PEPs)](https://www.python.org/dev/peps/). +O repositório GitHub [Propostas de Melhorias do Ethereum (EIPs)](https://github.com/ethereum/EIPs) foi criado em outubro de 2015. O processo EIP é baseado no processo de [Propostas de Melhorias do Bitcoin (BIPs)](https://github.com/bitcoin/bips) que, por sua vez, é baseado no processo [Propostas de Melhorias do Python (PEPs)](https://www.python.org/dev/peps/). Os editores de EIP têm a tarefa de revisar os processos das EIPs quanto a coerência técnica, problemas de formatação e correção de ortografia, gramática e estilo de código. Martin Becze, Vitalik Buterin, Gavin Wood e alguns outros foram os editores originais de EIP de 2015 até o final de 2016. diff --git a/public/content/translations/ru/nft/index.md b/public/content/translations/ru/nft/index.md index 9365f359e16..ac51b2fa9fa 100644 --- a/public/content/translations/ru/nft/index.md +++ b/public/content/translations/ru/nft/index.md @@ -66,7 +66,7 @@ NFT используются для различных целей: Или рассмотрим билет на спортивное мероприятие. Как **организатор мероприятия может выбрать, сколько билетов продать**, так же и создатель NFT может решить, сколько будет копий. Иногда это точные копии, например 5000 обычных входных билетов. Иногда создают несколько очень похожих, но немного отличающихся друг от друга билетов, например с назначенным местом. Они могут быть куплены и проданы напрямую без платы продавцам билетов, а покупатель всегда будет иметь подтверждение подлинности билета, так как сможет проверить адрес контракта. -На сайте ethereum.org **NFT используются, чтобы отметить людей, которые внесли весомый вклад** в наш репозиторий Github (разрабатывали сайт, писали или совершенствовали статьи…), перевели контент или посетили встречи сообщества, у нас даже есть собственное доменное имя NFT. Внеся вклад в работу ethereum.org, вы можете получить NFT [POAP](/glossary/#poap). Некоторые криптографические мероприятия использовали POAP в качестве билетов. [Подробнее об участии в работе](/contributing/#poap). +На сайте ethereum.org **NFT используются, чтобы отметить людей, которые внесли весомый вклад** в наш репозиторий GitHub (разрабатывали сайт, писали или совершенствовали статьи…), перевели контент или посетили встречи сообщества, у нас даже есть собственное доменное имя NFT. Внеся вклад в работу ethereum.org, вы можете получить NFT [POAP](/glossary/#poap). Некоторые криптографические мероприятия использовали POAP в качестве билетов. [Подробнее об участии в работе](/contributing/#poap). ![POAP ethereum.org](./poap.png) diff --git a/public/content/translations/sw/developers/docs/frameworks/index.md b/public/content/translations/sw/developers/docs/frameworks/index.md index 0db4454b832..b63a28793b7 100644 --- a/public/content/translations/sw/developers/docs/frameworks/index.md +++ b/public/content/translations/sw/developers/docs/frameworks/index.md @@ -124,7 +124,7 @@ Kabla ya kuingia kwa undani kwenye mifumo, tunapendekeza kwanza usome utangulizi - [Tovuti](https://catapulta.sh/) - [Nyaraka](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (inayoendeshwa na Covalent) -** **_GoldRush hutoa seti kamili zaidi ya API ya data ya mnyororo wa bloku kwa wasanidi programu, wachambuzi, na biashara. Iwe unajenga dashibodi ya DeFi, mkoba, roboti ya biashara, wakala wa AI au jukwaa la kufuata sheria, API za data hutoa ufikiaji wa haraka, sahihi, na rafiki kwa msanidi programu kwa data muhimu ya onchain unayohitaji_** diff --git a/public/content/translations/sw/developers/docs/networks/index.md b/public/content/translations/sw/developers/docs/networks/index.md index a2237455a3b..6d4c31aea52 100644 --- a/public/content/translations/sw/developers/docs/networks/index.md +++ b/public/content/translations/sw/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery ni aina ya kipekee ya testnet ambayo huwekwa upya kikamilifu kila mwezi ##### Rasilimali - [Tovuti](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [Soga ya jamii](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/sw/nft/index.md b/public/content/translations/sw/nft/index.md index 3b79861acbe..6467a0ac608 100644 --- a/public/content/translations/sw/nft/index.md +++ b/public/content/translations/sw/nft/index.md @@ -66,7 +66,7 @@ Labda wewe ni msanii amabaye angependa kushiriki kazi yake kupitia NFT bila wewe Ama zingatia tiketi ya tukio ya mechi ijayo. Kama **mratibu wa matukio anavyoweza kuamua idadi ya tiketi za kuuza**, muundaji wa NFT anaweza kuamua idadi ya kuwepo kwa nakala za kazi yake. Wakati mwingine huwa na nakala za ziada, kama vile Tiketi 5000 za Kiingilio cha Jumla. Wakati mwingine nyingine zinachapishwa zinazofanana, ila kila moja ina tofauti ndogo na yenzake, kama vile tiketi yeneye nambari ya kiti. Hizi zinaweza kununuliwa na kuuzwa kutoka kwa mshirika mmoja mpaka kwa mwingine kusipokuwepo na ulipaji wa washikaji tiketi na wanunuzi watakuwa na uhakika wa tiketi halisi kwa kuangalia anwani ya mkataba huo. -Kwenye ethereum.org tokeni zisizojirudia zinatumika kuonyesha kuwa watu wana maana nzuri ya kuchangia kupitia ripositi ya Github (programu tovuti, maandiko au kurekebisha chapisho...), tafsiri maudhui yetu, au uzuria simu za jamii yetu, na pia hata tunayo jina la tovuti yetu la tokeni zisizojirudia. Ukichangia kwenye ethereum.org, unaweza kuchukua tokeni isiyojirudia ya [POAP](/glossary/#poap). Mikutano mingine ya sarafu za kidijitali imetumia POAPs kama tiketi. [Zaidi juu ya uchangiaji](/contributing/#poap). +Kwenye ethereum.org tokeni zisizojirudia zinatumika kuonyesha kuwa watu wana maana nzuri ya kuchangia kupitia ripositi ya GitHub (programu tovuti, maandiko au kurekebisha chapisho...), tafsiri maudhui yetu, au uzuria simu za jamii yetu, na pia hata tunayo jina la tovuti yetu la tokeni zisizojirudia. Ukichangia kwenye ethereum.org, unaweza kuchukua tokeni isiyojirudia ya [POAP](/glossary/#poap). Mikutano mingine ya sarafu za kidijitali imetumia POAPs kama tiketi. [Zaidi juu ya uchangiaji](/contributing/#poap). ![POAP za ethereum.org](./poap.png) diff --git a/public/content/translations/te/developers/docs/frameworks/index.md b/public/content/translations/te/developers/docs/frameworks/index.md index 57074c831ee..b3d04142dfa 100644 --- a/public/content/translations/te/developers/docs/frameworks/index.md +++ b/public/content/translations/te/developers/docs/frameworks/index.md @@ -122,7 +122,7 @@ lang: te - [వెబ్‌సైట్](https://catapulta.sh/) - [డాక్యుమెంటేషన్](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (Covalent ద్వారా ఆధారితం) -** **_GoldRush డెవలపర్‌లు, విశ్లేషకులు మరియు ఎంటర్‌ప్రైజెస్‌ల కోసం అత్యంత సమగ్రమైన బ్లాక్‌చైన్ డేటా ఎపిఐ సూట్‌ను అందిస్తుంది. మీరు DeFi డాష్‌బోర్డ్, వాలెట్, ట్రేడింగ్ బాట్, AI ఏజెంట్ లేదా కంప్లయన్స్ ప్లాట్‌ఫామ్‌ను నిర్మిస్తున్నా, డేటా APIలు మీకు అవసరమైన ఆన్‌చైన్ డేటాకు వేగవంతమైన, ఖచ్చితమైన మరియు డెవలపర్-స్నేహపూర్వక యాక్సెస్‌ను అందిస్తాయి_** diff --git a/public/content/translations/te/developers/docs/networks/index.md b/public/content/translations/te/developers/docs/networks/index.md index 898c37cd0e6..05cbce9211b 100644 --- a/public/content/translations/te/developers/docs/networks/index.md +++ b/public/content/translations/te/developers/docs/networks/index.md @@ -96,7 +96,7 @@ lang: te ##### వనరులు - [వెబ్‌సైట్](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [కమ్యూనిటీ చాట్](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/tr/contributing/design/index.md b/public/content/translations/tr/contributing/design/index.md index 73322c2943f..a6a1ea3ecca 100644 --- a/public/content/translations/tr/contributing/design/index.md +++ b/public/content/translations/tr/contributing/design/index.md @@ -18,7 +18,7 @@ Bazen ham fikirlerimizi test etme konusunda yardıma ihtiyaç duyuyoruz. Bu, her 1. Tasarım ekibi, [Discord](https://discord.com/invite/ethereum-org) ve [GitHub](https://github.com/ethereum/ethereum-org-website/labels/design%20required%20%F0%9F%8E%A8) üzerinden bir maket tasarımı paylaşacak. 2. Tasarımların üzerinden yorumlar seçeneğiyle geribildirim vermeye yönlendirileceksiniz. -3. Sonuç, Github konusunda paylaşılacak ve ekip tarafından kapatılacaktır. +3. Sonuç, GitHub konusunda paylaşılacak ve ekip tarafından kapatılacaktır. ###  Anket araştırmalarına katılın {#answer-surveys} diff --git a/public/content/translations/tr/developers/docs/frameworks/index.md b/public/content/translations/tr/developers/docs/frameworks/index.md index 0d74c47c205..1f89e5107d7 100644 --- a/public/content/translations/tr/developers/docs/frameworks/index.md +++ b/public/content/translations/tr/developers/docs/frameworks/index.md @@ -116,7 +116,7 @@ Tam teşekküllü bir dapp inşa etmek teknolojinin farklı parçalarını gerek - [Web sitesi](https://catapulta.sh/) - [Belgeler](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (Covalent tarafından desteklenmektedir) -** **_GoldRush, geliştiriciler, analistler ve işletmeler için en kapsamlı blokzincir veri API paketini sunar. İster bir DeFi panosu, bir cüzdan, bir alım satım botu, bir yapay zeka aracısı isterse bir uyumluluk platformu oluşturuyor olun, veri API'leri ihtiyacınız olan temel zincir üstü verilere hızlı, doğru ve geliştirici dostu erişim sağlar_** diff --git a/public/content/translations/tr/developers/docs/networks/index.md b/public/content/translations/tr/developers/docs/networks/index.md index 7d38cd4f050..342be37dca5 100644 --- a/public/content/translations/tr/developers/docs/networks/index.md +++ b/public/content/translations/tr/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery, her ay tamamen sıfırlanan benzersiz bir test ağı türüdür. Yür ##### Kaynaklar - [Web sitesi](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [Topluluk sohbeti](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/tr/developers/tutorials/creating-a-wagmi-ui-for-your-contract/index.md b/public/content/translations/tr/developers/tutorials/creating-a-wagmi-ui-for-your-contract/index.md index 844476928c2..bf14f6dfe68 100644 --- a/public/content/translations/tr/developers/tutorials/creating-a-wagmi-ui-for-your-contract/index.md +++ b/public/content/translations/tr/developers/tutorials/creating-a-wagmi-ui-for-your-contract/index.md @@ -25,7 +25,7 @@ Modern bir kullanıcı arayüzünün nasıl çalıştığının arkasında pek 1. Gerekirse, [Holesky blokzincirini](https://chainlist.org/?search=holesky&testnets=true) cüzdanınıza ekleyin ve [test ETH'si alın](https://www.holeskyfaucet.io/). -2. Github deposunu klonlayın. +2. GitHub deposunu klonlayın. ```sh git clone https://github.com/qbzzt/20230801-modern-ui.git diff --git a/public/content/translations/tr/developers/tutorials/erc20-with-safety-rails/index.md b/public/content/translations/tr/developers/tutorials/erc20-with-safety-rails/index.md index ab990cbbd3c..cc951abd138 100644 --- a/public/content/translations/tr/developers/tutorials/erc20-with-safety-rails/index.md +++ b/public/content/translations/tr/developers/tutorials/erc20-with-safety-rails/index.md @@ -17,7 +17,7 @@ Bu makalede [OpenZeppelin ERC-20 jeton sözleşmesini](https://github.com/OpenZe Bütün kaynak kodunu görmek isterseniz: 1. [Remix IDE](https://remix.ethereum.org/)'yi açın. -2. Github klonlama simgesine tıklayın (![github klonlama simgesi](icon-clone.png)). +2. GitHub klonlama simgesine tıklayın (![github klonlama simgesi](icon-clone.png)). 3. `https://github.com/qbzzt/20220815-erc20-safety-rails` github deposunu klonlayın. 4. **contracts > erc20-safety-rails.sol** dosyasını açın. diff --git a/public/content/translations/tr/nft/index.md b/public/content/translations/tr/nft/index.md index 815366b5f65..75f050457c6 100644 --- a/public/content/translations/tr/nft/index.md +++ b/public/content/translations/tr/nft/index.md @@ -67,7 +67,7 @@ Belki de eserlerinizi NFT'leri kullanarak paylaşmak isteyen, eserlerinizin kont Yahut bir spor etkinliğine ait bileti düşünün. Tıpkı bir **etkinlik organizatörünün kaç bilet satacağını seçebilmesi** gibi, bir NFT'nin yaratıcısı da kaç kopyanın var olacağına karar verebilir. Bazen bunlar, 5000 Genel Giriş bileti gibi birebir kopyalardır. Bazen birbirine çok benzer ama her biri biraz farklı olan kopyalar basılır, örneğin sıralı ve sınırlı atanmış koltuk numarası olan bir bilet gibi. Bu biletler, bilet işletmecilerine ödeme yapmadan eşten eşe alınıp satılabilir ve alıcı, sözleşme adresini kontrol ederek biletin özgünlüğünden her zaman emin olabilir. -ethereum.org'da, **NFT'ler, insanların** Github depomuza anlamlı bir şekilde katkıda bulunduğunu (web sitesini programlamak, bir makale yazmak veya değiştirmek...), içeriğimizi çevirdiğini veya topluluk çağrılarımıza katıldığını **göstermek için kullanılır** ve hatta kendi NFT alan adımız bile var. ethereum.org'a katkıda bulunursanız bir [POAP](/glossary/#poap) NFT'si talep edebilirsiniz. Bazı kripto buluşmaları için POAP'lar bilet olarak kullanıldı. [Katkıda bulunma hakkında daha fazlası](/contributing/#poap). +ethereum.org'da, **NFT'ler, insanların** GitHub depomuza anlamlı bir şekilde katkıda bulunduğunu (web sitesini programlamak, bir makale yazmak veya değiştirmek...), içeriğimizi çevirdiğini veya topluluk çağrılarımıza katıldığını **göstermek için kullanılır** ve hatta kendi NFT alan adımız bile var. ethereum.org'a katkıda bulunursanız bir [POAP](/glossary/#poap) NFT'si talep edebilirsiniz. Bazı kripto buluşmaları için POAP'lar bilet olarak kullanıldı. [Katkıda bulunma hakkında daha fazlası](/contributing/#poap). ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/tr/roadmap/fusaka/index.md b/public/content/translations/tr/roadmap/fusaka/index.md index 047515481a0..a5b56bfaa4c 100644 --- a/public/content/translations/tr/roadmap/fusaka/index.md +++ b/public/content/translations/tr/roadmap/fusaka/index.md @@ -187,7 +187,7 @@ Bu EIP, "Çekirdek EIP'ler"den ayrı bir bölümde yer almaktadır çünkü çat ### Bu yükseltme tüm Ethereum düğümlerini ve doğrulayıcılarını etkiliyor mu? {#does-this-upgrade-affect-all-ethereum-nodes-and-validators} -Evet, Fusaka yükseltmesi hem [yürütüm istemcileri hem de fikir birliği istemcileri](/developers/docs/nodes-and-clients/) için güncellemeler gerektirir. Tüm ana Ethereum istemcileri, yüksek öncelikli olarak işaretlenen sert çatallanmayı destekleyen sürümler yayımlayacak. Bu sürümlerin ne zaman mevcut olacağını istemci Github depolarından, [Discord kanallarından](https://ethstaker.org/support), [EthStaker Discord](https://dsc.gg/ethstaker)'dan veya protokol güncellemeleri için Ethereum bloguna abone olarak takip edebilirsiniz. Yükseltme sonrasında Ethereum ağı ile senkronizasyonu sürdürmek için düğüm operatörlerinin desteklenen bir istemci sürümü çalıştırdıklarından emin olmaları gerekir. İstemci sürümleri hakkındaki bilgilerin zamana duyarlı olduğunu ve kullanıcıların en güncel ayrıntılar için en son güncellemelere başvurmaları gerektiğini unutmayın. +Evet, Fusaka yükseltmesi hem [yürütüm istemcileri hem de fikir birliği istemcileri](/developers/docs/nodes-and-clients/) için güncellemeler gerektirir. Tüm ana Ethereum istemcileri, yüksek öncelikli olarak işaretlenen sert çatallanmayı destekleyen sürümler yayımlayacak. Bu sürümlerin ne zaman mevcut olacağını istemci GitHub depolarından, [Discord kanallarından](https://ethstaker.org/support), [EthStaker Discord](https://dsc.gg/ethstaker)'dan veya protokol güncellemeleri için Ethereum bloguna abone olarak takip edebilirsiniz. Yükseltme sonrasında Ethereum ağı ile senkronizasyonu sürdürmek için düğüm operatörlerinin desteklenen bir istemci sürümü çalıştırdıklarından emin olmaları gerekir. İstemci sürümleri hakkındaki bilgilerin zamana duyarlı olduğunu ve kullanıcıların en güncel ayrıntılar için en son güncellemelere başvurmaları gerektiğini unutmayın. ### Sert çatallanma sonrasında ETH nasıl dönüştürülebilir? {#how-can-eth-be-converted-after-the-hardfork} diff --git a/public/content/translations/uk/developers/tutorials/server-components/index.md b/public/content/translations/uk/developers/tutorials/server-components/index.md index 8ecd87c0c43..da5989708cb 100644 --- a/public/content/translations/uk/developers/tutorials/server-components/index.md +++ b/public/content/translations/uk/developers/tutorials/server-components/index.md @@ -29,7 +29,7 @@ published: 2024-07-15 ## Приклад програми {#sample-program} -Ви можете побачити приклад сервера [на Github](https://github.com/qbzzt/20240715-server-component). Цей сервер прослуховує події, що надходять від [цього контракту](https://eth-holesky.blockscout.com/address/0xB8f6460Dc30c44401Be26B0d6eD250873d8a50A6?tab=contract_code), модифікованої версії Hardhat Greeter. Коли привітання змінюється, він змінює його назад. +Ви можете побачити приклад сервера [на GitHub](https://github.com/qbzzt/20240715-server-component). Цей сервер прослуховує події, що надходять від [цього контракту](https://eth-holesky.blockscout.com/address/0xB8f6460Dc30c44401Be26B0d6eD250873d8a50A6?tab=contract_code), модифікованої версії Hardhat Greeter. Коли привітання змінюється, він змінює його назад. Щоб запустити її: diff --git a/public/content/translations/uk/nft/index.md b/public/content/translations/uk/nft/index.md index 5a3d0cb976f..d41fbd8f33b 100644 --- a/public/content/translations/uk/nft/index.md +++ b/public/content/translations/uk/nft/index.md @@ -66,7 +66,7 @@ NFT використовується для багатьох речей, зок Або уявімо квиток на спортивний захід. Подібно до того, як **організатор заходу може вибрати, скільки квитків продати**, творець NFT може вирішити, скільки реплік існує. Іноді це точні примірники, як-от 5000 звичайних квитків для входу. Іноді карбуються декілька схожих, але дещо відмінних, як-от квитки з призначеним місцем. Їх можна купити й продати однорангово без оплати за послуги продавцям квитків, і покупець завжди має гарантію справжності квитка, оскільки може перевірити адресу контракту. -На ethereum.org ** NFT використовуються, щоб продемонструвати, що люди зробили значний внесок** у наш репозиторій Github (запрограмували вебсайт, написали або змінили статтю тощо), переклали контент або відвідали зустрічі спільноти; ми навіть маємо власне доменне ім’я NFT. Якщо ви робите внесок в ethereum.org, ви можете претендувати на [POAP](/glossary/#poap) NFT. Деякі криптозустрічі використовували POAP як квитки. [Докладніше про внесок](/contributing/#poap). +На ethereum.org ** NFT використовуються, щоб продемонструвати, що люди зробили значний внесок** у наш репозиторій GitHub (запрограмували вебсайт, написали або змінили статтю тощо), переклали контент або відвідали зустрічі спільноти; ми навіть маємо власне доменне ім’я NFT. Якщо ви робите внесок в ethereum.org, ви можете претендувати на [POAP](/glossary/#poap) NFT. Деякі криптозустрічі використовували POAP як квитки. [Докладніше про внесок](/contributing/#poap). ![Протокол POAP ethereum.org](./poap.png) diff --git a/public/content/translations/vi/nft/index.md b/public/content/translations/vi/nft/index.md index 4be8dd671e4..9af47c9ca79 100644 --- a/public/content/translations/vi/nft/index.md +++ b/public/content/translations/vi/nft/index.md @@ -66,7 +66,7 @@ Có thể bạn là một nghệ sĩ muốn chia sẻ tác phẩm của mình b Hoặc xem nó như một vé tham gia một sự kiện thể thao. Tương tự như việc một **quản lý tổ chức sự kiện có thể lựa chọn số lượng vé sẽ bán ra **, tác giả của một NFT có thể quyết định số lượng phiên bản NFT tồn tại. Đôi khi chúng là những phiên bản y hệt nhau, ví dụ như 5000 vé tham gia chung. Đôi khi một số khác thì được đúc rất tương đồng nhưng mỗi phiên bản sẽ hơi khác nhau, ví dụ như mỗi tấm vé với một số ghế riêng. Những thứ này có thể được bán và mua giữa người dùng mà không phải trả tiền cho các nhà quản lí vé, và người mua luôn đảm bảo được tính xác thực của vé đó bằng cách kiểm tra địa chỉ của hợp đồng đó. -Trên ethereum.org, **NFT được dùng để chứng minh rằng mọi người có đóng góp một cách tích cực** cho kho Github của chúng tôi (lập trình trang web, viết hoặc biên tập một bài viết...), dịch nội dung của chúng tôi, hoặc tham dự các cuộc họp cộng đồng, và chúng tôi thậm chí còn có tên miền NFT của riêng mình. Nếu đóng góp cho ethereum.org, bạn có thể yêu cầu một NFT [POAP](/glossary/#poap). Một vài sự kiện gặp gỡ về tiền điện tử đã dùng POAP như vé tham gia. [Đọc thêm về việc đóng góp](/contributing/#poap). +Trên ethereum.org, **NFT được dùng để chứng minh rằng mọi người có đóng góp một cách tích cực** cho kho GitHub của chúng tôi (lập trình trang web, viết hoặc biên tập một bài viết...), dịch nội dung của chúng tôi, hoặc tham dự các cuộc họp cộng đồng, và chúng tôi thậm chí còn có tên miền NFT của riêng mình. Nếu đóng góp cho ethereum.org, bạn có thể yêu cầu một NFT [POAP](/glossary/#poap). Một vài sự kiện gặp gỡ về tiền điện tử đã dùng POAP như vé tham gia. [Đọc thêm về việc đóng góp](/contributing/#poap). ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/zh-tw/developers/docs/apis/backend/index.md b/public/content/translations/zh-tw/developers/docs/apis/backend/index.md index b7be4a2a262..93b8d02e46f 100644 --- a/public/content/translations/zh-tw/developers/docs/apis/backend/index.md +++ b/public/content/translations/zh-tw/developers/docs/apis/backend/index.md @@ -26,7 +26,7 @@ lang: zh-tw - [alchemy.com](https://www.alchemy.com/) - [文件](https://docs.alchemy.com/) -- [Github](https://github.com/alchemyplatform) +- [GitHub](https://github.com/alchemyplatform) - [Discord](https://discord.com/invite/alchemyplatform) **All That Node -** **_節點即服務。_** @@ -45,7 +45,7 @@ lang: zh-tw - [blockpi.io](https://blockpi.io/) - [文檔](https://docs.blockpi.io/) -- [Github](https://github.com/BlockPILabs) +- [GitHub](https://github.com/BlockPILabs) - [Discord](https://discord.com/invite/xTvGVrGVZv) **Cloudflare 以太坊閘道。** @@ -64,7 +64,7 @@ lang: zh-tw - [infura.io](https://infura.io) - [文件](https://docs.infura.io/api) -- [Github](https://github.com/INFURA) +- [GitHub](https://github.com/INFURA) **Node RPC - _有成本效益的以太坊虛擬機 JSON-RPC 提供者_** @@ -86,12 +86,12 @@ lang: zh-tw - [rivet.cloud](https://rivet.cloud) - [文件](https://rivet.cloud/docs/) -- [Github](https://github.com/openrelayxyz/ethercattle-deployment) +- [GitHub](https://github.com/openrelayxyz/ethercattle-deployment) **Zmok -** **_速度導向的以太坊節點即 JSON-RPC/WebSockets 應用程式介面。_** - [zmok.io](https://zmok.io/) -- [Github](https://github.com/zmok-io) +- [GitHub](https://github.com/zmok-io) - [文檔](https://docs.zmok.io/) - [Discord](https://discord.gg/fAHeh3ka6s) @@ -99,13 +99,13 @@ lang: zh-tw **ethers-kt -** **_適用基於以太坊虛擬機區塊鏈的非同步、高效能 Kotlin/Java/Android 程式庫。_** -- [Github](https://github.com/Kr1ptal/ethers-kt) +- [GitHub](https://github.com/Kr1ptal/ethers-kt) - [範例](https://github.com/Kr1ptal/ethers-kt/tree/master/examples) - [Discord](https://discord.gg/rx35NzQGSb) **Nethereum -** **_區塊鏈的開源 .NET 整合程式庫。_** -- [Github](https://github.com/Nethereum/Nethereum) +- [GitHub](https://github.com/Nethereum/Nethereum) - [文檔](http://docs.nethereum.com/en/latest/) - [Discord](https://discord.com/invite/jQPrR58FxX) @@ -124,7 +124,7 @@ lang: zh-tw **web3j -** **_以太坊的 Java/Android/Kotlin/Scala 整合程式庫。 _** -- [Github](https://github.com/web3j/web3j) +- [GitHub](https://github.com/web3j/web3j) - [文件](https://docs.web3j.io/) - [Gitter](https://gitter.im/web3j/web3j) diff --git a/public/content/translations/zh-tw/developers/docs/apis/javascript/index.md b/public/content/translations/zh-tw/developers/docs/apis/javascript/index.md index 7d1d24c2da5..2e9f4b47785 100644 --- a/public/content/translations/zh-tw/developers/docs/apis/javascript/index.md +++ b/public/content/translations/zh-tw/developers/docs/apis/javascript/index.md @@ -240,29 +240,29 @@ ethers.utils.formatEther(balance) **Web3.js -** **_以太坊 JavaScript 應用程式介面。 _** - [文件](https://docs.web3js.org/) -- [Github](https://github.com/ethereum/web3.js/) +- [GitHub](https://github.com/ethereum/web3.js/) **Ethers.js -** **_使用 JavaScript 和 TypeScript 的完整以太坊錢包實作和公用程式。 _** - [文件](https://docs.ethers.io/) -- [Github](https://github.com/ethers-io/ethers.js/) +- [GitHub](https://github.com/ethers-io/ethers.js/) **The Graph -** **_用於為以太坊和星際檔案係統資料編製索引並使用 GraphQL 進行查詢的協議。_** - [The Graph](https://thegraph.com/) - [Graph Explorer](https://thegraph.com/explorer/) - [文件](https://thegraph.com/docs/) -- [Github](https://github.com/graphprotocol/) +- [GitHub](https://github.com/graphprotocol/) - [Discord](https://thegraph.com/discord) **light.js ****_針對輕量用戶端最佳化的高階回應式 JS 程式庫。_** -- [Github](https://github.com/openethereum/js-libs/tree/master/packages/light.js) +- [GitHub](https://github.com/openethereum/js-libs/tree/master/packages/light.js) **Alchemyweb3 -** **_具有自動重試和增強型應用程式介面的 Web3.js 包裝函式。_** - [文件](https://docs.alchemy.com/reference/api-overview) -- [Github](https://github.com/alchemyplatform/alchemy-web3) +- [GitHub](https://github.com/alchemyplatform/alchemy-web3) **Alchemy 非同質化代幣應用程式介面 -** **_用於擷取非同質化代幣資料的應用程式介面，包括所有權、中繼資料屬性以及更多。_** diff --git a/public/content/translations/zh-tw/developers/docs/frameworks/index.md b/public/content/translations/zh-tw/developers/docs/frameworks/index.md index a97475f402e..e33e6425701 100644 --- a/public/content/translations/zh-tw/developers/docs/frameworks/index.md +++ b/public/content/translations/zh-tw/developers/docs/frameworks/index.md @@ -124,7 +124,7 @@ lang: zh-tw - [網站](https://catapulta.sh/) - [說明文件](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (由 Covalent 提供技術支援) -** **_GoldRush 為開發人員、分析師和企業提供最全面的區塊鏈資料 API 套件， 無論您是在建構 DeFi 儀表板、錢包、交易機器人、AI 代理程式還是合規平台，資料 API 都能提供快速、準確且對開發人員友善的存取方式，讓您取得所需的必要鏈上資料_** diff --git a/public/content/translations/zh-tw/developers/docs/networks/index.md b/public/content/translations/zh-tw/developers/docs/networks/index.md index 23d9d3eaedf..c1a6efc8613 100644 --- a/public/content/translations/zh-tw/developers/docs/networks/index.md +++ b/public/content/translations/zh-tw/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery 是一個獨特的測試網，每個月都會完全重置。 執行和 ##### 資源 - [網站](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [社群聊天室](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/zh-tw/developers/docs/storage/index.md b/public/content/translations/zh-tw/developers/docs/storage/index.md index 8fc5397730a..9d2a4d90aed 100644 --- a/public/content/translations/zh-tw/developers/docs/storage/index.md +++ b/public/content/translations/zh-tw/developers/docs/storage/index.md @@ -118,7 +118,7 @@ SWARM 是一種去中心化的資料儲存和分發技術，具有儲存激勵 - [Ipfs.io](https://ipfs.io/) - [文件](https://docs.ipfs.io/) -- [Github](https://github.com/ipfs/ipfs) +- [GitHub](https://github.com/ipfs/ipfs) **Storj DCS - _為開發者提供安全、私有且相容 S3 的去中心化雲端物件存儲。_** @@ -130,13 +130,13 @@ SWARM 是一種去中心化的資料儲存和分發技術，具有儲存激勵 - [Skynet.net](https://siasky.net/) - [文件](https://siasky.net/docs/) -- [Github](https://github.com/SkynetLabs/) +- [GitHub](https://github.com/SkynetLabs/) **Filecoin - _Filecoin 是由星際檔案系統背後的同一團隊建立的。 它是星際檔案系統概念之上的激勵層。_** - [Filecoin.io](https://filecoin.io/) - [文件](https://docs.filecoin.io/) -- [Github](https://github.com/filecoin-project/) +- [GitHub](https://github.com/filecoin-project/) **Arweave - _Arweave 是一個用於存儲資料的去中心化存儲平台。_** @@ -148,7 +148,7 @@ SWARM 是一種去中心化的資料儲存和分發技術，具有儲存激勵 - [zus.network](https://zus.network/) - [文件](https://0chaindocs.gitbook.io/zus-docs) -- [Github](https://github.com/0chain/) +- [GitHub](https://github.com/0chain/) **Crust Network - _Crust 是基於星際檔案系統的去中心化存儲平台。_** @@ -160,31 +160,31 @@ SWARM 是一種去中心化的資料儲存和分發技術，具有儲存激勵 - [EthSwarm.org](https://www.ethswarm.org/) - [文件](https://docs.ethswarm.org/docs/) -- [Github](https://github.com/ethersphere/) +- [GitHub](https://github.com/ethersphere/) **OrbitDB - _基於星際檔案系統的去中心化點對點資料庫。_** - [OrbitDB.org](https://orbitdb.org/) - [文件](https://github.com/orbitdb/field-manual/) -- [Github](https://github.com/orbitdb/orbit-db/) +- [GitHub](https://github.com/orbitdb/orbit-db/) **Aleph.im - _去中心化雲端專案（資料庫、檔案存儲、運算和去中心化身分）。 鏈下和鏈上點對點技術的獨特融合。 星際檔案系統和多鏈相容性。_** - [Aleph.im](https://aleph.im/) - [文件](https://aleph.im/#/developers/) -- [Github](https://github.com/aleph-im/) +- [GitHub](https://github.com/aleph-im/) **Ceramic - _使用者控制的星際檔案系統資料庫存儲，用於資料豐富且引人入勝的應用程式。_** - [Ceramic.network](https://ceramic.network/) - [文件](https://developers.ceramic.network/learn/welcome/) -- [Github](https://github.com/ceramicnetwork/js-ceramic/) +- [GitHub](https://github.com/ceramicnetwork/js-ceramic/) **Filebase - _ S3 相容的去中心化存儲和異地備援星際檔案系統固定服務。 所有透過 Filebase 上傳到星際檔案系統的檔案，都會自動被固定到 Filebase 基礎設施，並在全球複製 3 份。_** - [Filebase.com](https://filebase.com/) - [文檔](https://docs.filebase.com/) -- [Github](https://github.com/filebase) +- [GitHub](https://github.com/filebase) **4EVERLAND - _Web 3.0 雲端運算平台，集存儲、運算和網路核心能力於一身，相容於 S3 並在星際檔案系統和 Arweave 等去中心化存儲網路上提供同步資料存儲。_** diff --git a/public/content/translations/zh-tw/nft/index.md b/public/content/translations/zh-tw/nft/index.md index bd5e2ff028a..339cf49c16b 100644 --- a/public/content/translations/zh-tw/nft/index.md +++ b/public/content/translations/zh-tw/nft/index.md @@ -67,7 +67,7 @@ summaryPoint3: 由建置於以太坊區塊鏈上的智慧型合約提供支援 又或者以體育賽事的門票為例， 如同**賽事主辦者可以決定要販售幾張門票**，非同質化代幣的創作者也可以決定要發行幾份複製品。 有時可能是完全相同的複製品，例如 5000 張普通門票； 有時可能會製作好幾種極為類似，但各自略有不同的複製品，例如指定席的票券。 此類票券可以在不需要給票務員付款的情況下進行點對點買賣，買家可以隨時檢查合約地址，以確保票券的真實性。 -在 ethereum.org 上，**非同質化代幣被用來證明大家對我們的 Github 儲存庫做出了有意義的貢獻**（對網站進行編程、撰寫或修改文章等等）、翻譯我們的文字内容，或參加了我們的社群電話會議，以及我們甚至擁有專屬的非同質化代幣域名。 如果你對 ethereum.org 有貢獻，你可以領取[出席證明協定 (POAP)](/glossary/#poap) 非同質化代幣。 某些加密貨幣聚會使用 POAP 作為入場門票。 [深入了解如何貢獻](/contributing/#poap)。 +在 ethereum.org 上，**非同質化代幣被用來證明大家對我們的 GitHub 儲存庫做出了有意義的貢獻**（對網站進行編程、撰寫或修改文章等等）、翻譯我們的文字内容，或參加了我們的社群電話會議，以及我們甚至擁有專屬的非同質化代幣域名。 如果你對 ethereum.org 有貢獻，你可以領取[出席證明協定 (POAP)](/glossary/#poap) 非同質化代幣。 某些加密貨幣聚會使用 POAP 作為入場門票。 [深入了解如何貢獻](/contributing/#poap)。 ![ethereum.org POAP](./poap.png) diff --git a/public/content/translations/zh/contributing/adding-desci-projects/index.md b/public/content/translations/zh/contributing/adding-desci-projects/index.md index 1fdbc951af9..c2487062606 100644 --- a/public/content/translations/zh/contributing/adding-desci-projects/index.md +++ b/public/content/translations/zh/contributing/adding-desci-projects/index.md @@ -37,7 +37,7 @@ lang: zh - 确保所有上架的项目仍然符合我们的标准 - 验证建议的产品没有比当前上架的产品符合我们的更多标准 -Ethereum.org 由开源社区维护，我们依靠该社区帮助保持更新。 如果你发现所列项目有任何信息需要更新，请在我们的 Github 存储库中创建一个问题或拉取请求。 +Ethereum.org 由开源社区维护，我们依靠该社区帮助保持更新。 如果你发现所列项目有任何信息需要更新，请在我们的 GitHub 存储库中创建一个问题或拉取请求。 ## 使用条款 {#terms-of-use} diff --git a/public/content/translations/zh/contributing/adding-resources/index.md b/public/content/translations/zh/contributing/adding-resources/index.md index a21d7025e15..979ae2ffbfc 100644 --- a/public/content/translations/zh/contributing/adding-resources/index.md +++ b/public/content/translations/zh/contributing/adding-resources/index.md @@ -46,7 +46,7 @@ lang: zh ## 添加你的资源{#add-your-resource} -如果你想要在以太坊官网（ethereum.org）上添加你的资源且资源符合标准，可以在Github上创设一个开源项目。 +如果你想要在以太坊官网（ethereum.org）上添加你的资源且资源符合标准，可以在GitHub上创设一个开源项目。 创设一个开源项目 diff --git a/public/content/translations/zh/developers/docs/frameworks/index.md b/public/content/translations/zh/developers/docs/frameworks/index.md index 65d4a324fef..ef06adb59fa 100644 --- a/public/content/translations/zh/developers/docs/frameworks/index.md +++ b/public/content/translations/zh/developers/docs/frameworks/index.md @@ -116,7 +116,7 @@ lang: zh - [网站](https://catapulta.sh/) - [文档](https://catapulta.sh/docs) -- [Github](https://github.com/catapulta-sh) +- [GitHub](https://github.com/catapulta-sh) **GoldRush (由 Covalent 提供支持) -** **_GoldRush 为开发者、分析师和企业提供最全面的区块链数据 API 套件。 无论你是在构建 DeFi 看板、钱包、交易机器人、人工智能代理还是合规平台，数据 API 都能让你快速、准确且对开发者友好地访问所需的基本链上数据_** diff --git a/public/content/translations/zh/developers/docs/networks/index.md b/public/content/translations/zh/developers/docs/networks/index.md index 3cba14ae6e9..81dde68e6f0 100644 --- a/public/content/translations/zh/developers/docs/networks/index.md +++ b/public/content/translations/zh/developers/docs/networks/index.md @@ -96,7 +96,7 @@ Ephemery 是一种独特的测试网，每个月都会彻底重置。 执行和 ##### 资源 - [网站](https://ephemery.dev/) -- [Github](https://github.com/ephemery-testnet/ephemery-resources) +- [GitHub](https://github.com/ephemery-testnet/ephemery-resources) - [社区聊天](https://matrix.to/#/#staker-testnet:matrix.org) - [Blockscout](https://explorer.ephemery.dev/) - [Otterscan](https://otter.bordel.wtf/) diff --git a/public/content/translations/zh/developers/tutorials/ethereum-for-web2-auth/index.md b/public/content/translations/zh/developers/tutorials/ethereum-for-web2-auth/index.md index 0968f82f1eb..eafc590381f 100644 --- a/public/content/translations/zh/developers/tutorials/ethereum-for-web2-auth/index.md +++ b/public/content/translations/zh/developers/tutorials/ethereum-for-web2-auth/index.md @@ -54,7 +54,7 @@ SAML 是一种中心化协议。 服务提供者 (SP) 仅在与身份提供者 ( 第一步是让 SAML SP 和 SAML IdP 能够相互通信。 -1. 下载软件。 本文的示例软件[在 Github 上](https://github.com/qbzzt/250420-saml-ethereum)。 不同阶段存储在不同分支中，此阶段您需要 `saml-only` +1. 下载软件。 本文的示例软件[在 GitHub 上](https://github.com/qbzzt/250420-saml-ethereum)。 不同阶段存储在不同分支中，此阶段您需要 `saml-only` ```sh git clone https://github.com/qbzzt/250420-saml-ethereum -b saml-only diff --git a/public/content/translations/zh/nft/index.md b/public/content/translations/zh/nft/index.md index 601493092fd..a5dd77a76c3 100644 --- a/public/content/translations/zh/nft/index.md +++ b/public/content/translations/zh/nft/index.md @@ -67,7 +67,7 @@ NFT 是**每个都独一无二**的代币。 每个非同质化代币都有不 再以体育赛事的门票为例。 就像**活动组织者可以选择出售多少张门票**一样，NFT 的创建人可以决定存在多少个复制品。 有时候，它们是完全相同的复制品，如 5000 张普通门票。 有时候，会制作一些非常相似但略有不同的门票，如指定座位的门票。 这些门票可以在用户之间点对点买卖，而无需支付票务处理费用，买家始终可以通过检查合约地址来确保门票的真实性。 -在 ethereum.org 上，**NFT 用于证明人们对我们的 Github 代码库做出了有意义的贡献**（为网站编程、撰写或修改文章……）、翻译了我们的内容或参加了我们的社区会议，我们甚至还有自己的 NFT 域名。 如果你为 ethereum.org 做出贡献，你可以申领一个 [POAP](/glossary/#poap) NFT。 一些加密货币相关活动使用 POAP 徽章作为门票。 [关于贡献的更多信息](/contributing/#poap)。 +在 ethereum.org 上，**NFT 用于证明人们对我们的 GitHub 代码库做出了有意义的贡献**（为网站编程、撰写或修改文章……）、翻译了我们的内容或参加了我们的社区会议，我们甚至还有自己的 NFT 域名。 如果你为 ethereum.org 做出贡献，你可以申领一个 [POAP](/glossary/#poap) NFT。 一些加密货币相关活动使用 POAP 徽章作为门票。 [关于贡献的更多信息](/contributing/#poap)。 ![ethereum.org POAP 徽章](./poap.png) diff --git a/src/data-layer/mocks/fetch-developer-tools.json b/src/data-layer/mocks/fetch-developer-tools.json index b72587c1d67..626db422eb0 100644 --- a/src/data-layer/mocks/fetch-developer-tools.json +++ b/src/data-layer/mocks/fetch-developer-tools.json @@ -537,7 +537,7 @@ "0x2bb095e1f297c71da8bd4ee15097abad3b99e299fe14cd6aa704df3f36d0ae22": { "id": "0x2bb095e1f297c71da8bd4ee15097abad3b99e299fe14cd6aa704df3f36d0ae22", "name": "solidity-coverage", - "description": "solidity-coverage provides smart-contract code coverage for the Hardhat developer platform. It's highly accurate, supports full viaIR solidity compilation and a large set of solidity-specific code branch patterns. It's installed on ~230k Github projects and is downloaded ~100k times a week from NPM.", + "description": "solidity-coverage provides smart-contract code coverage for the Hardhat developer platform. It's highly accurate, supports full viaIR solidity compilation and a large set of solidity-specific code branch patterns. It's installed on ~230k GitHub projects and is downloaded ~100k times a week from NPM.", "thumbnail_url": "https://storage.googleapis.com/op-atlas/bd692393-7f1a-4b91-9887-73f7c3250233.png", "banner_url": "https://storage.googleapis.com/op-atlas/dcbdf6ac-f898-4dac-b9d0-087b8d289f4b.png", "twitter": null, @@ -1259,4 +1259,4 @@ }, "computedAt": "2026-01-27T20:48:46.213Z" } -} \ No newline at end of file +} diff --git a/src/intl/hi/page-about.json b/src/intl/hi/page-about.json index 87f55c33811..89b2d1393ec 100644 --- a/src/intl/hi/page-about.json +++ b/src/intl/hi/page-about.json @@ -9,11 +9,11 @@ "page-about-li-4": "कार्यान्वित", "page-about-link-1": "इस भंडार का स्रोत कोड MIT लाइसेंस के तहत लाइसेंस प्राप्त है", "page-about-link-2": "GitHub", - "page-about-link-3": "Github पर जारी कार्यों की पूरी सूची देखें", + "page-about-link-3": "GitHub पर जारी कार्यों की पूरी सूची देखें", "page-about-link-4": "हमारे Discord सर्वर से जुड़ें", "page-about-link-5": "Twitter पर हमसे संपर्क करें", - "page-about-link-6": "Github पर कार्यान्वित कार्यों की पूरी सूची देखें", - "page-about-link-7": "Github पर एक मुद्दा बनाएँ", + "page-about-link-6": "GitHub पर कार्यान्वित कार्यों की पूरी सूची देखें", + "page-about-link-7": "GitHub पर एक मुद्दा बनाएँ", "page-about-p-1": "Ethereum.org के लॉन्च के बाद से, हम इस बारे में पारदर्शी होने का प्रयास करते हैं कि हम कैसे काम करते हैं। यह हमारे मूल मूल्यों में से एक है क्योंकि हमारा मानना ​​है कि इथेरियम की सफलता के लिए पारदर्शिता महत्वपूर्ण है।", "page-about-p-2": "हम हमारे", "page-about-p-3": "प्राथमिक परियोजना प्रबंधन उपकरण के रूप में उपयोग करते हैं। हम अपने कार्यों को 3 श्रेणियों में व्यवस्थित करते हैं:", diff --git a/src/intl/it/page-about.json b/src/intl/it/page-about.json index 9feb6de3aaf..1a474c19743 100644 --- a/src/intl/it/page-about.json +++ b/src/intl/it/page-about.json @@ -9,11 +9,11 @@ "page-about-li-4": "implementato", "page-about-link-1": "Il codice sorgente di questo repository è concesso in licenza con licenza MIT", "page-about-link-2": "GitHub", - "page-about-link-3": "Visualizza l'elenco completo delle attività in corso su Github", + "page-about-link-3": "Visualizza l'elenco completo delle attività in corso su GitHub", "page-about-link-4": "Unisciti al nostro server Discord", "page-about-link-5": "Contattaci su Twitter", - "page-about-link-6": "Visualizza l'elenco completo delle attività implementate su Github", - "page-about-link-7": "Apri una segnalazione su Github", + "page-about-link-6": "Visualizza l'elenco completo delle attività implementate su GitHub", + "page-about-link-7": "Apri una segnalazione su GitHub", "page-about-p-1": "Fin dal lancio di ethereum.org, ci sforziamo di essere trasparenti su come operiamo. Questo è uno dei nostri valori fondamentali perché riteniamo che la trasparenza sia fondamentale per il successo di Ethereum.", "page-about-p-2": "Utilizziamo", "page-about-p-3": "come strumento primario di gestione dei progetti. Organizziamo le nostre attività in tre categorie:", diff --git a/src/intl/pt-br/page-about.json b/src/intl/pt-br/page-about.json index be31f7673a8..43ebad95b83 100644 --- a/src/intl/pt-br/page-about.json +++ b/src/intl/pt-br/page-about.json @@ -9,11 +9,11 @@ "page-about-li-4": "implementado", "page-about-link-1": "O código fonte deste repositório está licenciado sob a Licença MIT", "page-about-link-2": "GitHub", - "page-about-link-3": "Ver a lista completa de tarefas em andamento no Github", + "page-about-link-3": "Ver a lista completa de tarefas em andamento no GitHub", "page-about-link-4": "Entre no nosso servidor do Discord", "page-about-link-5": "Encontre-nos no Twitter", - "page-about-link-6": "Ver a lista completa de tarefas implementadas no Github", - "page-about-link-7": "Levantar uma questão no Github", + "page-about-link-6": "Ver a lista completa de tarefas implementadas no GitHub", + "page-about-link-7": "Levantar uma questão no GitHub", "page-about-p-1": "Desde o lançamento da ethereum.org, esforçamo-nos para ser transparentes na forma como operamos. Este é um dos nossos valores principais porque acreditamos que a transparência é crucial para o sucesso do Ethereum.", "page-about-p-2": "Nós utilizamos", "page-about-p-3": "como nossa principal ferramenta de gerenciamento de projeto. Organizamos nossas tarefas em 3 categorias:", diff --git a/src/intl/ru/page-about.json b/src/intl/ru/page-about.json index e22a494a80c..dcdf3ecd276 100644 --- a/src/intl/ru/page-about.json +++ b/src/intl/ru/page-about.json @@ -9,11 +9,11 @@ "page-about-li-4": "реализовано", "page-about-link-1": "Исходный код репозитория распространяется под лицензией MIT", "page-about-link-2": "GitHub", - "page-about-link-3": "Просмотреть полный список выполняемых задач на Github", + "page-about-link-3": "Просмотреть полный список выполняемых задач на GitHub", "page-about-link-4": "Присоединиться к нашему серверу Discord", "page-about-link-5": "Связаться с нами в Twitter", - "page-about-link-6": "Просмотреть полный список реализованных задач на Github", - "page-about-link-7": "Создать запрос на Github", + "page-about-link-6": "Просмотреть полный список реализованных задач на GitHub", + "page-about-link-7": "Создать запрос на GitHub", "page-about-p-1": "С самого запуска ethereum.org мы стремимся работать и действовать открыто. Это одна из наших главных ценностей, так как мы считаем, что прозрачность играет ключевую роль в успехе Ethereum.", "page-about-p-2": "Мы используем", "page-about-p-3": "в качестве основного средства управления проектами. Мы организуем задачи по трем категориям:", diff --git a/src/intl/sw/common.json b/src/intl/sw/common.json index 10a82fbb9eb..80b6227b247 100644 --- a/src/intl/sw/common.json +++ b/src/intl/sw/common.json @@ -231,7 +231,7 @@ "less": "Kidogo", "light-mode": "Nyepesi", "light-mode-aria-label": "Tumia modi ya mwangaza", - "listing-policy-disclaimer": "Bidhaa zote zilizo zilizoorodheshwa kwenye ukurasa huu sio uthibitisho rasmi, na zinatolewea kwa kusidi la chanzo cha taarifa tu. kama unataka kuongeza bidhaa ama kutuma maoni juu ya sera ongea suala kwenye Github.", + "listing-policy-disclaimer": "Bidhaa zote zilizo zilizoorodheshwa kwenye ukurasa huu sio uthibitisho rasmi, na zinatolewea kwa kusidi la chanzo cha taarifa tu. kama unataka kuongeza bidhaa ama kutuma maoni juu ya sera ongea suala kwenye GitHub.", "loading": "Inapakia...", "loading-error": "Tatizo katika upakiaji.", "loading-error-refresh": "Kuna tatizo, tafadhali fanyiza upya.", diff --git a/src/intl/tr/common.json b/src/intl/tr/common.json index 3b413775904..bf76d74b8e5 100644 --- a/src/intl/tr/common.json +++ b/src/intl/tr/common.json @@ -85,7 +85,7 @@ "enterprise-team-description": "Sorularınızı yanıtlar, ilerlemeniz için olası yolları belirlemenize yardımcı olur, teknik destek sağlar ve sizi ilgili sektör liderleriyle bağlantıya geçiririz.", "enterprise-team": "Ethereum Kurumsal Ekibi", "error-page-title": "Oops! Bir şeyler ters gitti", - "error-page-description": "Bu sorunu Github Depomuza bildirerek iyileştirmemize yardımcı olabilirsiniz.", + "error-page-description": "Bu sorunu GitHub Depomuza bildirerek iyileştirmemize yardımcı olabilirsiniz.", "error-page-home-link": "Ana sayfaya dön", "esp": "Ekosistem Destek Programı", "eth-current-price": "Güncel ETH fiyatı (USD)", From e38cf14ee9c9744b775fce152adb48dee06e3320 Mon Sep 17 00:00:00 2001 From: wackerow <54227730+wackerow@users.noreply.github.com> Date: Mon, 16 Mar 2026 12:40:35 -0700 Subject: [PATCH 002/127] feat: text version of ef mandate --- public/content/foundation/index.md | 4 + public/content/foundation/mandate/index.md | 1126 ++++++++++++++++++++ 2 files changed, 1130 insertions(+) create mode 100644 public/content/foundation/mandate/index.md diff --git a/public/content/foundation/index.md b/public/content/foundation/index.md index 57a69d217ca..7580214935b 100644 --- a/public/content/foundation/index.md +++ b/public/content/foundation/index.md @@ -13,6 +13,10 @@ The [Ethereum Foundation](http://ethereum.foundation/) (EF) is a non-profit orga The EF is not a company, or even a traditional non-profit. It does not control or lead Ethereum, nor is it the only organization that funds critical development of Ethereum-related technologies. The EF is one part of a much larger [ecosystem](/community/). +## EF Mandate {#ef-mandate} + +The [EF Mandate](/foundation/mandate/) defines the Foundation's purpose, principles, and commitments to the Ethereum ecosystem. Published onchain, it enshrines the EF's dedication to **censorship resistance, open source, privacy, and security (CROPS)** as non-negotiable priorities. + ## What the EF does {#what-the-ef-does} - **Protocol development** – Supporting teams working on Ethereum's core protocol, including client development, research, upgrades, and the [bug bounty program](/bug-bounty/) diff --git a/public/content/foundation/mandate/index.md b/public/content/foundation/mandate/index.md new file mode 100644 index 00000000000..4019055e450 --- /dev/null +++ b/public/content/foundation/mandate/index.md @@ -0,0 +1,1126 @@ +--- +title: Ethereum Foundation Mandate +description: The Ethereum Foundation Mandate in text form +hideEditButton: true +sidebarDepth: 1 +lang: en +--- + +# The Ethereum Foundation Mandate {#mandate} + +- [Graphical PDF version](https://ethereum.foundation/ef-mandate.pdf) +- [Canonically signed onchain source (via Blockscout explorer)](https://eth.blockscout.com/tx/0x5dd574df963a1df1f064791e0f6ff41ec972cdbba12293b7e1ece582052ba855) - Select "View details", under _Raw input_ selecting _UTF-8_ + +## I. ETHEREUM {#i-ethereum} + +**Ethereum was born out of a dream. A dream for freedom.** + +Not just for one, not just for many, but for all who are ready to grasp it with +their own hands. + +**Its creators realized that the armamentarium of freedom was missing two vital +tools: self-sovereign computation, and the computational ability to coordinate +at scale without violating anyone else’s own sacrosanct self-sovereignty.** + +Only if a user had the final say over their own computation - their data, their +assets, their instructions, their identities, their agents, their essential +digital gestalt, and the right to exit from any system that proves unfavorable +to those things - would they have any chance in the brave new electronic world, +of being able to live in the way they truly want and deserve. + +If you want only self-sovereignty of computation, and do not need to coordinate, +then you can run applications locally on your own machine - and in many +situations this is the correct approach. If you want to coordinate, but do not +mind being at the whims of centralized, unaccountable power, then we will only +say that centralized platforms can often provide excellent user experience. + +The value of Ethereum is precisely in the space of computational needs where we +need both. + +Money was the first application. Money requires coordination, because it has no +meaning without someone else to recognize both the asset itself, and the +blockchain as a living registry of who owns that asset. And money requires self- +sovereignty, because the losses from having one’s money arbitrarily inflated +away, frozen or simply expropriated are so high. + +Ether is a store of value and money, that also happens to be an application - +and there have been, and will be, many, many more. This includes those imagined +in the Ethereum Whitepaper, those described and built over the last twelve +years, and others not yet conceived of - and Ethereum will be home to all of +them. + +**Ethereum honors its first promise, to enable self-sovereignty, by being +humanity’s common computational substrate that anyone can interact with +trustlessly, permissionlessly, and persistently.** + +**This is what is meant by “The World Computer.”** + +**On this foundation Ethereum honors its second promise: allowing the +infrastructures of self-sovereign coordination to arise and thrive in any form +imaginable and expressible - unmolested, unimpeded, and undisturbed - without +violating any individual’s freedom.** + +Ethereum is meant to be a liberatory technology - not just from power relations +that are imposed without true consent or where dissent imposes a heavy price, +but even more importantly, from attempts to order reality itself in a way that +leaves no alternative. + +And the Ethereum Foundation exists to ensure Ethereum remains resilient enough +to be so. + +## II. OUR ROLE {#ii-our-role} + +**The Ethereum Foundation is the original steward of the Ethereum project.** + +We helped grow Ethereum from its early days as a seedling software project into +today’s infinite garden that countless participants use to grow their own +projects - and we did this by making deliberate, considered choices, with the +aim of inspiring others to become fellow custodians of a vibrant, open, and +infinite commons. + +The underlying principles that led us to conceive of, invent, then steward +Ethereum, and the unwavering belief that it is possible to build and maintain a +better world without caprice or coercion - could have led to many destinations +other than Ethereum, whether in computing, communications, artificial +intelligence, education, health, expression in all its forms, and many other +domains. + +By asking ourselves “if we had these principles, and we operated in a different +domain, what would we create?”, then seeing what things in our existing world +come closest, we can start to find our natural allies. + +But to find dependable allies, not merely allies of convenience that remain for +only one finite round of the infinite game, we need to be clear about what our +principles are, and this document is where we express and enshrine them. + +**The Foundation is not the parent, owner, or ruler of Ethereum. We are not “the +system” itself.** + +Our role is to coordinate, to provide substrate, and to offer context that helps +anyone who shares our purpose to work together - without creating a centralizing +bottleneck, and without collapsing into a monoculture that drifts toward goals +misaligned with Ethereum’s core promises. + +The Foundation exists to ensure Ethereum becomes, and stays, a decentralized and +resilient civilizational foundational infrastructure - part of the bedrock on +which broader self-sovereignty can be built, alongside other requirements like +clean air, water, energy, freedom of communication, and access to knowledge. + +**Our ultimate goal is for Ethereum to pass the _walkaway_ test:** its protocol and +core application layers become robust and trustless enough that they would +continue to reliably function and evolve even if the Foundation and today’s core +developers disappeared tomorrow. + +**We are a real non-profit - independent, with no other agenda.** We reject +temptations around flows of value, even when they are framed as reasonable +rewards, or as necessary for alignment or self-perpetuation. We consider them +antithetical to our mission and our legal constitution. These are slippery +slopes to arbitrary extraction and insidious capture, with many such cases +exemplified elsewhere. **Our enduring assets are our legitimacy and virtue, and we +will not risk or squander them.** + +Our bottom line is not profit, nor organizational growth, nor blind adoption at +all costs. We support adoption insofar as it does not contravene our mandate. + +**Our bottom line is the mission of securing Ethereum’s resilience.** + +Our primary and secondary measures of success are how much self-sovereignty, and +how much sovereignty-preserving coordination at scale, Ethereum resiliently +enables - both with and without the Foundation. + +**This document is primarily for members of the Foundation: a clarification of our +pre-existing purpose, and a practical guide for translating mission and +principles into action, in the context of not just being stewards of Ethereum +but also fellow travelers on the path of freedom, empowerment, and human well- +being.** + +We write it for the present onwards. We acknowledge we have not always succeeded +in the past, but we will succeed going forward. + +## III. OUR MANDATE {#iii-our-mandate} + +**The Ethereum Foundation’s mandate is twofold.** + +**The first aim is to ensure Ethereum becomes and stays a decentralized and +resilient tool for self-sovereignty: our first fundamental principle is that a +user has the final say over their identities, assets, actions, and agents.** + +It is certain that Ethereum will be used in many other ways, but we believe +applications only become truly meaningful if they rest on this inalienable +foundation of user self-sovereignty. + +**It is therefore necessary for us to ensure that Ethereum upholds and contains +the following properties:** + +- **Censorship Resistance** +- **Open Source and Free, as in Freedom** +- **Privacy** +- **Security** + +**We hold that these properties - CROPS - must remain, as an indivisible whole, +the sine qua non of all Ethereum’s development priorities, which cannot be +displaced.** + +**They are Ethereum’s most important properties and are inseparable from its +success.** + +**Therefore, we ourselves must embody these properties as a guiding principle and +prioritize them in all our decisions.** + +**The second aim is scaling the guaranteed availability of self-sovereignty to +users ready to exercise it directly.** + +**This is our second fundamental principle: that unstoppable self-sovereignty must +become possible for those who choose it, at the scale and in the form that they +want it, without violating anyone else’s.** + +We believe that self-sovereignty is positive, is positive-sum, and that self- +sovereignty at scale is the dominant positive-sum strategy. + +We believe that self-sovereignty is competitively scalable without compromise on +CROPS, and that sovereignty-preserving coordination at scale is possible. + +We believe that self-sovereignty stacks on top of itself on multiple overlapping +scales: individuals, families, local communities, enterprises, nations, +religions, world-spanning internet communities all deserve their space to +maintain their own internal accounting and to interact with each other on their +own terms. + +We further believe these views are shared by a critical mass of people. While +Ethereum is permissionless, the Foundation will remain focused on working with +those who share our vision and sense of mission. + +We recognize that self-sovereignty itself is just one crucial component of a +greater goal - namely, human empowerment and well-being - championed by loose +coalitions of builders of a brighter future. + +Only through being a decentralized and resilient self-sovereignty tool, imbued +throughout with CROPS, and unstoppable at scale while preserving individual +freedom, can Ethereum’s essential nature be recognized: a secure, user-aligned +World Computer that can be shared with all who want it. + +And only through the Foundation enshrining its principles and vision for all to +see, can it be most effective in ensuring Ethereum blossoms. + +**Our Mandate is written for a thousand-year horizon. Principled adherence is +subject to drift and erosion over time - like water, standards tend to flow from +high to low, and are far easier to lose than to regain. We are starting as high +as we can, to slow any long-run erosion over centuries, so we do not expect any +material compromise within our lifetimes.** + +
+SOURCE SEPPUKU LICENSE +
+ +> By inclusion of this license, the author, maintainer, editor or (re)distributor +> (the “Actor”) of this software SHALL uphold the following pledges: +> +> To always make freely available and publicly accessible a full and accurate copy +> of the source code and associated documents of this software, including all +> modifications hereto by the Actor. +> +> To take his or her own life with a sword upon failure to uphold any of the +> pledges in this license, or upon modification or removal of any part of this +> license. +> +> May the Foundation fall on its own sword if it fails to uphold its solemn +> promise to Ethereum. + +
+
+ +## IV. PRINCIPLES FOR ACTION {#iv-principles-for-action} + +**Our Mandate rests on two pillars, each comprising four principles.** + +**Everything we do - technical work both at the protocol layer and elsewhere, +community support, and decision-making - must be derived from and answer to +these twin pillars and their principles, with CROPS treated as non-negotiable.** + +### Technical Pillar {#iv-technical-pillar} + +- **Censorship Resistance:** No actor can selectively exclude valid use or break + functionality, including by gaining durable, non-competitive control of any + critical mechanisms. + +All work must be architected to be maximally unstoppable and to function without +incorporating centralized intermediaries or kill switches. + +The provision of unstoppability should itself be censorship-resistant to avoid +it becoming an anticompetitive and extractive game of selectively providing +censorship-resistance to the compliant, to cartels, or to highest bidders +without proper competition. + +Censorship resistance also includes technical resistance to extra-technical +pressure, such as social mores or legal restriction. The protocol relies on +cryptographic guarantees for its resilience and neutrality, not on the temporal +concerns of the political context. Our work must protect the protocol from +attempts to replace fundamental physical properties with short-term brittle +mechanisms to try to achieve the same thing. + +- **Open Source and Free, as in Freedom:** No privileged code or hidden + specifications. + +All work must be public and auditable: no proprietary “black boxes.” All work +must also be forkable: Ethereum’s credibility depends on predictable exit paths, +and systems that aren’t open and free have unacceptable friction to forking. + +Supported projects must pledge that they will not change their open source or +copyleft license in the future. Permissive licenses are accepted, viral copyleft +licenses are appreciated, but merely source-available licenses are not +tolerated. + +- **Privacy:** User data is not exposed beyond necessity or against their interests. + +We strongly advocate for maximal privacy to become the default for user data to +the greatest extent possible: first in any tools that sit above the protocol +that the Ethereum Foundation builds, and then ultimately in the protocol itself +from the very core on out. + +The purpose of privacy is to prevent structural power asymmetries from +infringing on self-sovereignty and self-sovereign coordination. History shows us +that the wielders of power, once they gain the ability to restrict or even de- +normalize privacy, will never surrender the advantage they obtain. Hence, +privacy must be permissionless and available to all. + +Privacy is not about total concealment of everything. It is about freedom and +true consent: to choose what information to disclose to whom, on one’s own +terms. In our day-to-day lives, we often disclose information, or prove claims +about ourselves, to participate with others, or to build relationships on trust, +gradually. + +However, we believe that end users should always selectively negotiate their +disclosures, and that this should only be supported on top of a base of freely +available, unconditional privacy. + +- **Security:** Things must do what they claim to do, no more and no less. + +Security is paramount. We advocate rigorous security design at both the protocol +and application layers to prevent harm to users and preserve system integrity. +We invest deeply in testing and verification, using multiple methods to specify +desired properties and confirm that designs satisfy them. + +Security requires simplicity, including responsible minimization of lines of +code and external dependencies; a protocol is not “trustless” if only a small +number of people can understand how it works and why it is secure. Work must be +verifiable to many. Entirely new domains for the protocol must clear an +extremely high necessity threshold, and do so legibly. + +Security also means governance minimization; no social layer should override +protocol guarantees lightly. + +Security additionally means passing the walkaway test, not just for the +protocol, but also for users: self-sovereignty means a user should not be forced +into frequent, complex migrations that create unintended risks. + +True security protects both system and users from technical failure, social +entrapment, and coercion. + +--- + +**We must always remember that the ultimate goal is for Ethereum to pass the +walkaway test. Achieving this needs, among other things, intermediary +minimization and structural decentralization, and the best way to achieve that +is to build with our CROPS principles in mind.** + +### Social Pillar {#iv-social-pillar} + +- **Principled Alignment:** Our first principle is that we are principled in our work. + +We focus on work which embodies our principles and not on work which allows +private capture or uncompetitive user extraction. + +We value the quality of principle-upholding resilience over the quantity of +users or the optimization-for-value of design. + +A billion users in a centralized silo is not a success; designing around the +enshrinement of centralized extraction pipelines in the protocol is not a +success; it is a failure of mission. + +- **Discipline:** We care about doing it right and doing it well. + +We are truth-seeking and beauty-seeking in our work. We demand technical rigor, +excellence, and creativity. + +We choose relevant timing over either going fast or going slow, which may +include not acting at all. We share research and results quickly; we make sure +what we ship is mission-critically reliable. + +We exercise courage to make hard, potentially unpopular, decisions based on +principled assessments rather than market pressure or institutional comfort. We +accept that rejecting and reforming compromised defaults is part of our work. We +defend our decisions with patience and truthfulness. + +We also admit when we get things - particularly big things - wrong, with +humility, grace, and an honest and clear explanation of why our views have +changed and what our new views are. + +We pair high standards with kindness: resilient systems are built by people who +can disagree clearly without cruelty and who can stay curious when under +pressure. + +- **Right Association:** Who we work with is itself a principled choice. + +We prioritize working with individuals and teams who share our principles, +spread them, and make their work legible through comprehensive and open +documentation even in challenging conditions. + +For projects dependent on support from the Foundation, we prefer to work more +closely with those who also actively work to achieve independence from us. + +Right association also means we prefer to focus on individuals, teams, and +projects that share our principles but operate in different domains, over those +individuals, teams, and projects who are in crypto, but operate according to a +very different set of standards. + +- **Big Picture:** We remember that Ethereum’s future is bigger than its present. + +Our horizon is broader than crypto: Ethereum’s promise only holds if it serves +self-sovereignty beyond any one subculture, asset class, or industry. + +The World Computer is decentralized infrastructure for permissionless compute, +communication, and association, and it naturally connects to builders who uphold +those freedoms: open source projects, privacy and cryptography researchers, +civil liberties defenders, educators and public-interest technologists, builders +of resilient local communities, and the quiet maintainers of civilization who +keep essential systems and traditions running. + +We remember that we require of them no aesthetic conformity, only principled +alignment: when people share the instinct to keep systems forkable, censorship +resistant, private, and secure, we treat them as fellow travelers of the path +and fellow stewards of the infinite garden. + +Our loose coalition does not need to be put together. It is together. + +## V. CARRYING OUT THE WORK {#v-carrying-out-the-work} + +### Approach {#v-approach} + +**Our operating approach can be summarized as a process of subtraction for +resilience.** + +Ethereum is more resilient when it can continue to provide self-sovereignty and +sovereignty-preserving coordination at scale without depending on us to guide +it. + +We therefore have a bias toward work that makes us less necessary over time, +through a framework that guides our approach: + +- **The Only-EF Rule:** We focus on critical tasks that have no other natural home and + that no other ecosystem actor can or will reliably undertake. This includes but + is not limited to: core protocol upgrades and long-horizon research, neutral + multi-client specs and tests, public-good security work, crisis coordination, + preventing chokepoints, and core dev tooling and documentation where no + sustainable owner exists. We check that these tasks are actually critical. + +- **Handoff for Ecosystem Maturity:** As soon as a function or role can be + successfully managed by an aligned community actor, we facilitate that + transition, so capability and responsibility diffuse through our ecosystem + rather than concentrate in one place. + +- **Independent Inspiration and Reliability:** We work across varied domains rather + than in a narrowly hierarchical manner - the glue that connects us is our + mission, not our structure. We hire individuals who are deeply aligned with the + mission. We prize those individuals who operate with high integrity and + flexibility, as in our experience, they have been the most effective in rapidly + changing conditions and are the most reliable during uncertainty. + +- **Compounding Effects:** We prioritize efforts that are as far upstream and high + leverage as possible, by making sure the research, documentation, coordination, + and infrastructure we support can be freely reused, extended, and operated + independently. This can include supporting shared primitives, specifications, + tooling, and evaluation methods that reduce avoidable friction and create + network effects for those who share our principles. When we work downstream, it + is on making CROPS-native affordances competitive and viable for adoption. + +- **Subtraction as Success:** Our goal is to reduce the Foundation’s relative + influence over time. This is not retreat or sabotage. Subtraction is rather a + process of ensuring Ethereum’s maturity: a trajectory of growth with + decentralization, robust enough to outgrow and outlast us, however long this may + take. + +Doing subtraction well is challenging. + +At first glance, there seems to be a tension between stewarding something to +grow into the infinite, and deliberately diminishing one’s own presence. It is +an especially unusual act from an organization of our type and current influence +‐ the landscape of contemporary corporate philanthropy is littered with +eterna foundations and institutes. Many will be discomforted and ask, “if the +Ethereu Foundation, with its stature and legitimacy, doesn’t strive to stay +front and center, then who else realistically could?” + +There are also concrete instances of failure in subtraction in the past. There +have been many attempts to create alternative stewards within Ethereum that have +died out, and there have been many attempts, both within the Ethereum ecosystem +and far outside it, to nurture federated ecosystems with multiple actors, that +ended up unable to get past the stage of one of them dominating far above the +others. These failures each have valuable lessons that we must honestly +recognize, and learn from. + +Yet, we believe, and history shows us time and again, that the only way to grow +a garden into something truly infinite is to choose subtraction. Ethereum’s +resilience and therefore runaway growth can only truly arise where there is no +single indispensable entity responsible for the ecosystem’s success. History is +filled with examples of transition stages that started off temporary then became +permanent. For decentralization to truly take root, we must keep growing toward +it today, not tomorrow. + +This does not mean our subtraction takes place carelessly and inconsiderately. +Subtraction means ecosystem growth that outpaces ours. It requires the highest +standards of observation, planning, and execution. Our subtraction happens when +the systems we support can attain or have achieved greater resilience with +others, either inside or beyond Ethereum, or without needing anyone at all. + +Subtraction done well is subtractive of the Foundation, but additive for +Ethereum. The privilege of stewarding Ethereum must not be hoarded, but shared +and multiplied with others, whether they have been loyal friends since the +beginning or new travelers who have discovered the Infinite Garden. + +This is why subtraction is a definitive signal of success. The garden can become +bigger, stronger, and more vibrant than any organizations could ever dictate, +when the mission of ensuring Ethereum remains humanity’s common computational +substrate is shared with all who recognize the future as it should be. + +The more Ethereum succeeds, the tinier we become; if Ethereum fails, so too will +we perish. + +Subtraction will occur either way, so we choose success. + +### Limits {#v-limits} + +**Our limits exist for the same reason: Ethereum’s resilience.** + +The Foundation does not build for everyone. We contribute technical expertise +and provide underlying support so those aligned with Ethereum’s self-sovereignty +mission - and its potential for sovereignty-preserving coordination at scale - +can build Ethereum and build on Ethereum, and so that they in turn can build for +everyone. + +**Our contributions may take many forms, but we are not bound to them - as +Ethereum evolves, so too will our support.** + +Today, we may support coordination both of the core protocol and beyond it; +support education and public portals; close essential funding gaps; or provide +stewardship in other principles-aligned ways. + +Tomorrow, we will adapt to do what is necessary, by applying our execution +strategy: identifying and relieving coordination bottlenecks, and preventing +capture of the protocol or ecosystem. + +**In short, we do for Ethereum, what Ethereum is meant to do for its users.** + +To maintain our role as a credibly neutral steward, we operate within clear +limits. We avoid activities that could create a centralized point of control +(including ourselves) or compromise Ethereum’s long-term potential. + +- **We are NOT a Corporate:** We are not a development company. We do not build + consumer apps. If it can be a sustainable business, it belongs in the community, + and use of the protocol must not depend on it. + +- **We are NOT a Kingmaker:** We support mechanisms and designs that are in line with + our mandate and core principles, not specific private brands or companies. We + neither support nor enforce standards that compromise on our principles and + goals. + +- **We are NOT an Accreditation Body:** We do not certify or endorse projects, teams, + or audits. However, we do support the development of mechanisms in line with our + principles to help users evaluate security and legitimacy without relying on us + to provide stamps of approval. + +- **We are NOT a Product Studio:** We do not act as a product development laboratory + for the ecosystem. We think deeply about how users interact with Ethereum and + use this to inform our upstream work on shared primitives, tooling, and + fundamental research, all in service of helping builders deliver systems and + products that are practical to use, sustainably viable, and capable of + accelerating the availability of a credible alternative that fully embodies our + principles. + +- **We are NOT a Marketing Agency:** We do not engage in hype cycles or promote short- + term price action. Our communications are grounded in technical reality, in our + long-term mission and mandate, and in having fun on the Internet. + +- **We are NOT the Boss:** We cannot force hard forks or protocol changes. We are + opinionated only so as to advocate and propose what’s best for the mission. + +- **We are NOT a Government or Regulatory Body:** We do not act as a governing body + for ecosystem participants. + +- **We are NOT a Casino:** We do not encourage people to take life-changing, and + possibly life-wrecking, amounts of risk by going into personal debt hyper- + gambling. Ethereum has the potential to be a foundation for a secure and free + life; debt promotes the opposite. + +- **We are NOT Opportunists:** We do not actively assist in adoption of Ethereum in + ways that compromise trustlessness. We recognize that such adoption may occur, + but we apply our expertise in the trust-minimizing end of the spectrum in any + category we engage with. + +### Tradeoff Considerations {#tradeoff-considerations} + +**The world Ethereum must function in is not yet CROPS-native.** + +Today, most use of Ethereum flows through partially centralized surfaces: +wallets, RPC providers, relays to the MEV-industrial complex, app stores, +exchanges, institutions, and the social defaults that surround them. + +As Ethereum’s growing roots and branches come into contact with centralized +infrastructure at ever-greater scales, we will face these same dynamics +repeatedly. + +**We will have to choose, tomorrow as today, whether to take an incrementalist +approach or a nativist approach to growing Ethereum and advancing CROPS +adoption.** + +In truth, these are two distinct strands of work: the incrementalist approach +accelerates CROPS by demonstrating to those who are at or prioritize scale that +CROPS increases value; the other directly grows and distributes CROPS, and +develops and demonstrates further best practices for doing so. + +Our priority, and the default path for decisions, in line with our mandate and +the Only-EF Rule, is the CROPS-native approach. **CROPS-adherence is a compounding +force:** it produces usable self-sovereignty tools and escape hatches, and sets +durable precedents others can later follow. We value usability and performance +improvements that make sovereignty easier to choose, as long as they do not +introduce new points of leverage over a user or create dependencies. + +**Adoption can be earned over time, but principled ground once ceded is far harder +to regain.** + +We leave space within the Foundation for the incrementalist approach only in +tightly bounded circumstances: as a tactical intervention when it durably +reduces central control, does not result in deeper entrenchment than what it +supersedes, and accelerates the availability of a credible alternative that +fully embodies our principles. + +Our work must not introduce new chokepoints or entrench existing ones. It must +not expand or normalize reliance on added trust assumptions, and it must not +require constant Foundation presence to ensure alignment with our principles. + +We are skeptical of walled garden projects but we may consider engaging with +projects that advance or innovate access to self-sovereignty for end users, and +that preserve a path for users to default to full self-sovereign control of +their identity and assets. + +Work that is more incrementalist may well be valuable for Ethereum’s success and +growth. There may always be those who want to build walled gardens on the World +Computer. But the natural home of such work is outside the Foundation. This +Mandate does not preclude working with them, but we must do so in a principled +way to promote and secure the self-sovereignty of end users. The underlying goal +of our participation should be to engage with our resources and CROPS expertise +in order to help make the CROPS properties of such external work stronger. + +**The guiding question is: does this make Ethereum and its users less susceptible +to capture over time, or does it normalize capture in exchange for reach?** + +**We must also always consider that doing nothing may be the best course of +action, and that our energies are better spent elsewhere. Sometimes work in a +given area cannot be one of our priorities.** + +--- + +**When we encounter adversarial situations, whether within Ethereum or beyond it, +we focus on creating structural improvement: building open source tools for +self-sovereignty and sovereignty-preserving coordination, with de-totalization +as a matter of principle, rather than acting on opinions about particular +conflicts.** + +As individuals, we may hold diverse views shaped by the moment. As the +Foundation, we believe that free people, flourishing on the basis of self- +sovereignty, are best suited to building worlds worth living in and to carrying +freedom forward. We therefore focus on strategies that expand the conditions for +flourishing through self-sovereign computation, including in circumstances we +cannot yet foresee. + +Differential and open source promotion of “defense” is not a novel idea. The +Mohists authored and widely distributed manuals that helped all cities better +defend themselves, operating under the theory that shifting the balance from +offense to defense broadly reduces suffering. + +> **卷十四 Book 14** +> +> 52. 备城门 Fortification of the City Gate +> 53. 备高临 Defense against Attack from an Elevation +> 54. 备梯 Defense against Attack with Ladders +> 55. 备水 Preparation against Inundation +> 56. 备突 Preparation against a Sally +> 57. 备穴 Preparation against Tunneling +> 58. 备蛾傅 Defense against Ant-Rush +> +> **卷十五 Book 15** +> +> 68. 迎敌祠 The Sacrifice against the Coming of the Enemy +> 69. 旗帜 Flags and Pennants +> 70. 号令 Commands and Orders +> 71. 杂守 Miscellaneous Measures in Defenss + +One major difference between the Mohists and us is that they also directly +intervened in conflicts based on their own judgment about who was defending and +who was attacking. + +Our approach is closer to writing the manuals and making them available, and not +intervening in individual conflicts. + +We believe that de-totalization - building toward a world in which no +organization, system, or moral order has total dominance over any individual +life - is the most reliably good aim. + +Censorship resistance, security, and privacy stand in relation to de- +totalization much as city walls stood to pre-modern collective defense. Open +source ensures these protections are broadly distributed, iterable, and +customizable, rather than becoming the asymmetric advantage of any one group, +even a group for which any of us as individuals may hold particular sympathies. + +The team of today may not be the team of tomorrow. + +## VI. RESOLVING QUANDARIES {#vi-resolving-quandaries} + +Over the course of the next thousand years, we and our successors will face +countless challenges and be confronted with difficult choices whose specific +details we cannot anticipate. + +But human history teaches us that although no two rivers flow the same course, +the shapes of the valleys they carve are familiar, once you know how to look. + +That is to say, the structures of those challenges and the dynamics by which +they unfold are not so novel. + +While it would be impossible to describe every such obstacle, we illustrate +several timeless tensions we believe will forever exist around Ethereum until +the mission is complete. + +--- + +**1. When two technically credible paths compete, we pick the one that removes +points of leverage, not the one that can be shipped faster.** + +It is a common refrain from those who build centralized chokepoints into their +designs, such as entrenched trust architectures, that they have done so out of +necessity, and will be removed later when things are “more mature.” + +But human experience, both from software development and from political history, +tells us that such a path is fraught with danger, and we should view such +statements with suspicion. + +**The wiser course, therefore, is to prefer the option that is fully-CROPS from +the beginning even if it is technically or socially more difficult to get off +the ground and scale.** + +For example: a proposal offers “better protocol UX” or “better safety” for +transaction propagation via a curated private relay network with trusted +partners that results in the possibility for centralizing infrastructure such as +shared blacklists or whitelists, that will “be decentralized later when the +ecosystem and protocol are ready”; a second proposal keeps propagation +permissionless straight out of the box via open p2p tooling, with optional +private relays for exotic transactions, and with free routing around verifiable +failures. + +All else being equal, CROPS means we support the design where broadcast is +auditable and does not depend on a small set of intermediaries; private +propagation is opt-in and escapable; and where users can route around censorship +or extraction permissionlessly. + +**The lesson is that it is not sufficient that a solution simply works today; it +also needs to not become a chokepoint tomorrow.** + +**2. When designing or judging a proposal, we think through the higher-order +effects of implementation beyond the layer at hand, ensuring that the overall +impact advances self-sovereignty, and avoid capture points simply being +displaced beyond narrow focus or becoming an externality.** + +It is understandable to focus only on the properties of the solution at hand, +and to leave consideration of the other-order consequences of that solution to +others. This is not necessarily due to insufficient capacity, motivation, or +discipline. It is often due to simple familiarity. + +Nevertheless, it is our responsibility to ensure that we do think about the +overall consequences of any proposal beyond our own immediate frame of +reference. Indeed, thinking across layers may lead us to the elimination of +undesirable properties or structures at one level by creating a solution at +another. + +For example: work on the protocol’s capabilities, such as scale or speed, can be +done in myriad ways. Some may even be “CROPS-aligned” by the standard of using +the CROPS properties as a checklist. + +But we must remember our broader aim, promoting self-sovereignty. A proposal +that on narrow analysis satisfies the CROPS properties, yet introduces a user +chokepoint at another layer of interaction, whether that be forced +intermediation, extraction, or some other anti-sovereign pattern, is a proposal +that must be rejected. But a proposal that increases the capabilities of the +core protocol with the result of eliminating chokepoints at other layers should +be welcomed. + +It is a recurring temptation to treat CROPS properties in isolation, and to +consider any gaps acceptable as long as they can be compensated for elsewhere. +Whenever this temptation arises, we must scrutinize it carefully. Protocols may +remain formally un-degraded or “pristine” while in reality, positive or +essential capabilities such as scale, speed, UX accessibility, privacy, +extraction-resistance, or account functionality migrate into centralized, +intermediary-dependent, trust-dependent, permissioned, or opaque structures or +services. + +There are several scenarios that can illustrate the need for, and value of, +cross-layer thinking. + +First, **scale**. If the protocol does not support sufficient scale for a use case, +then those users often turn to extra-protocol mechanisms to process transactions +elsewhere and return on-chain proofs and commitments. In theory they may achieve +security sufficient for their purposes; in practice, they may be unknowingly +accepting deeper CROPS compromises than the situation warrants. + +Second, **account types**. If Ethereum supports only a narrow set of account types, +and lacks a general-purpose account model capable of supporting smart accounts, +then those use cases that require smart accounts can only be served through +intermediaries. We must recognize that this degrades their CROPS properties and +long-term liveness guarantees, even if a large number of competing +intermediaries theoretically exist. This prevents users from fully benefiting +from protocol-level features meant to improve transaction inclusion and access +guarantees. + +Third, **native privacy support at the protocol layer**. Protocol native privacy +greatly increases the anonymity set of the participants, reducing the risk of +privacy compromise. No construction layered on top could match the anonymity set +the protocol itself could provide. + +Fourth, **transaction protections at the protocol layer**. Transaction inclusion, +protection against adverse execution outcomes, and fair execution should be +achieved at the lowest layer of the stack consistent with safety. Implementation +at the protocol level would alleviate pressure for users to seek such guarantees +from intermediaries via centralized transaction pipelines, and therefore reduce +opportunities for systemic extraction. + +Fifth, **aggregation of cryptographic objects**. Intermediaries perform aggregation +functions for users because the individual submission on-chain of cryptographic +objects, for example, zero-knowledge proofs, is often cost prohibitive. The high +fixed costs of providing aggregation mean that the market for this service is +likely to be monopolistic, which is a centralized chokepoint. Therefore, if the +protocol were to support batched aggregation and efficient verification of such +objects, this centralization risk would be removed. + +--- + +In each of these cases, we judge the complexity and centralization-pressure +risks of native scaling against off-chain scaling; native smart accounts against +intermediated smart account services; native privacy against application layer +privacy; native transaction protections against intermediated and likely +extractive transaction guarantee services; and native aggregation against +intermediated and likely monopolistic, aggregation intermediaries. + +We keep in mind the risks at other parts of the Ethereum stack when thinking of +improving performance and usability of the core Ethereum protocol, for example: +if scaling comes at the cost of verifiability; if inclusion guarantees come at +the cost of novel forms of coercion or extraction; or if slot time reduction +comes at the cost of increasing pressures for geographic and economic +centralization. + +We also remember that protocol complexity is itself a technical risk: it expands +the bug surface area and reduces the viability of new independent protocol +implementations. However, we also recognize the upside: work on performance and +usability may be empowering where it removes the need for entire classes of +intermediaries above the protocol, or at least creates a credible and accessible +path around them. + +Striking the wrong balance across layers may be very costly. The downsides to +making mistakes due to complexity or risk at the protocol layer are often going +to be greater than downsides at the application layer, where users can +individually opt in or out, or collectively work to upgrade without changes to +the protocol. + +For example: if we add an aggregation scheme to Ethereum, but no one uses it - +not even power users who deeply need CROPS properties - then we have added +hundreds of lines of protocol code that create permanent ongoing risk without +much benefit. + +**We therefore hold protocol improvements that bear any risk at all to the +protocol’s CROPS properties to a much higher bar, evaluating them with greater +caution and care to avoid compromise at such a fundamental part of the Ethereum +stack.** + +**3. When considering adversarial user environments, we default to empowering user +agency, not to solutions that weaken user agency.** + +Safety is an important problem in our time, and “attacks on the mind” must be +taken as seriously as attacks that target technical properties or community +dynamics. + +However, we aim for defenses that are user-empowering and user-controlled. We do +not support high priests dictating or installing restrictions on user agency +under their logic of user protection, especially if users never opted in or +can’t opt out. + +For example: in the name of safety in a hostile world, a wallet ships a “safe +mode” enabled by default that incorporates dark design patterns such as silently +blocking certain contracts, steering users toward preferred venues or +counterparties, and into using unmodifiable preinstalled whitelists; or that +ships an AI copilot that flags “risky” actions using an uninspectable +proprietary model and reports user actions back home silently. + +**CROPS pushes user-controlled defenses instead:** a choice of independent locally- +verifiable filters with transparent rules, multiple independently-built +community-created and propagated whitelists and blacklists with clear override +paths, and private-by-default tool use including any AI components. + +Our work in Ethereum is to prove that the most natural and right way to help +users defend themselves from threats they may not even understand is to expose +them to empowering defensive tools. We demonstrate our fundamental belief in +user-empowerment over paternalism by pioneering this approach. + +**The goal is not to sanitize the environment; it is to keep users sovereign +inside it.** + +**4. Where a use case important to our mandate involves some form of +intermediation, we work to ensure that barriers to entry are minimized and +market competitiveness is maximized for anyone who plays that role. At the same +time, we aim to eliminate the need for such intermediaries wherever possible, +and to ensure that a practical, fully disintermediated path exists wherever it +can.** + +There are already many places across the Ethereum protocol and application layer + +- block building, RPC servers, entities attesting to aspects of digital identity +- where intermediaries exist. This state of affairs carries serious risks: one + or more intermediaries may become dominant chokepoints, impose their special + interests, censor users, enforce arbitrary participation rules, or extract + value. + +We therefore work to eliminate the need for such intermediaries wherever +possible. Where they cannot yet be removed, we design protocols that reduce the +technical and economic pressures that drive them toward capture. + +**In particular, we ensure the presence of a “zero option”: for every affordance +that has an intermediated path, any intermediary-free path that is possible must +be built and must remain credible and accessible. This serves both as a present +exit for users who may already be exploited by intermediaries, and as a credible +constraint against the expansion of such abuse. We do not skip this step.** + +For example: consider an application where participation requires some form of +identity. This may be for sybil resistance or anti-denial-of-service +protections, an online forum meant to be writable only by members of a certain +community, or myriad other reasons. + +A naive approach would be to take the easiest available off-the-shelf form of +“official” identity - government, biometric or corpoid - wrap it in a zero- +knowledge proof, and declare the result CROPS-friendly. + +But we must do better. We begin by examining the underlying need of the +application and ask exactly what aspect of identity or information disclosure is +actually required. Often, the requirement is not identity in full, but some +narrower property that identity also fulfills. + +If the use case needs only sybil resistance or only a way to make abuse +expensive, the system should provide a narrower alternative than providing +identity itself. Users who hold some quantity of ETH, for example, could provide +a zero-knowledge proof of ownership of it, or post a zero-knowledge security +deposit, in lieu of dependence on identity. + +Where identity attestations are genuinely required, our principles lead us to +design the system so that intermediaries are bounded and replaceable rather than +entrenched. The identity proof mechanism should be fully privacy-preserving in +all cases, with no backdoors. + +Once credentials have been issued, proof generation and verification should be +as local, verifiable, and non-custodial as possible, so that ongoing +participation does not depend on continued deference to a privileged +intermediary and cannot be revoked arbitrarily. + +We should also ensure that multiple fit-for-purpose sources of ground truth for +identity exist and can be used inside real-world applications that rely on the +system. The software stack should make it easy for implementations to integrate +multiple independent attestation sources, and should make this plurality the +default path. It should support combination approaches, allowing multiple weaker +signals - such as social-graph attestations - and not just single stronger +attestations, such as a signature from an official entity. + +Designing such a chokepoint-minimized system is inherently harder than the naive +approach. For that reason, and in accordance with the Only-EF rule, it is +exactly the kind of work we consider taking on where it serves our mandate. + +**The north star is disintermediation. Where intermediation can be eliminated, we +prefer to eliminate it. Where it is unavoidable, we work to minimize the risk of +capture by keeping intermediary roles open, plural, bounded, and verifiable. If +an intermediary-free design becomes possible, we ensure that it is credible and +accessible, so that intermediaries are ultimately optional rather than +entrenched.** + +**5. When deciding which teams to back, we look past short-term output and social +cues, and instead judge patterns of choices and revealed preferences.** + +It is often the case that we are presented with ideas wrapped in the language of +CROPS; of self-sovereignty; of freedom - yet upon closer inspection there is +less than meets the eye; the thin veneer of purported principles disintegrates +upon examination. This is not always disingenuous - indeed, many such ideas are +proposed by well-meaning, conscientious individuals, teams and projects, either +through genuine though misguided belief, or through lack of introspection or +interrogation. + +One way that this occurs is through thinking only about the “happy case,” where +all the variables play out as planned, but not about the “unhappy case” such as +where third-party dependencies (whether APIs, content delivery networks, or +otherwise) disappear or break - or worse, where the team itself disappears or is +hacked or an insider turns hostile. + +Another way is through the echo chamber effect, or in other words, cascading +social proof. In what is currently a small domain, groups of well-meaning people +commonly wish to be supportive, especially to their friends. Ideas form and are +shared and discussed; precisely because we operate in a space that has an +affinity for disintermediation, the speed at which ideas circulate often reaches +escape velocity, if not virality. Further, if amplified ideas attract social +proof and incentives - whether credit or reward - and are presented publicly +before they have been suitably interrogated or examined critically, then post +hoc questioning may become costly and face resistance. + +For example: two teams submit proposals for improving UX in some complicated +scenarios that involve multiple tokens and asynchronous communication. At first +glance, both look “CROPS-aligned:” open specification, progressive +decentralization roadmap, user-first UX. + +On review, the first team is socially polished, using the right language of +CROPS and armed with peer endorsement and resources, but the design keeps a +“secret-sauce” intermediary layer closed, bootstraps with a small whitelisted +provider set, and uses soft-defaults to steer flow through preferred paths. + +The other team has no social presence, minimal backing and finds it difficult to +communicate their vision, but implements an open market for intermediaries (eg. +using staking) without a whitelist, and treats them as a temporary artifact with +a credible path to elimination via user-driven routes and on-chain guarantees. +They publish early research and threat models, ship legible specs and references +and invite critique, and challenge unaffiliated teams to co-build so the default +outcome is shared infrastructure rather than a branded moat. + +**When choosing who to support, clarity of perception is paramount. It is +imperative to employ discernment and good judgment: not to anchor on polish, +credentials, or sympathetic signals of alignment, especially when social proof +arrives before due diligence.** Instead, we must examine what a project optimizes +for in practice - the tradeoffs it repeatedly chooses, technically and socially. + +Despite CROPS language, if on closer inspection work introduces privileged +positions - such as closed components, whitelists, soft-default routing, +discretionary upgrade ability, or dependency-heavy integrations - it is right to +be skeptical. + +Likewise, if a team continually selects for control or value over +decentralization, or if their partners and endorsers have a tradition of anti- +self-sovereign choices, it is right to be wary. + +**Our technical and social principles lead us to ask whether the default path +removes leverage over time or concentrates it in a silo, and whether the signals +of alignment are matched by CROPS-consistent action under scrutiny.** + +**We do not require first versions to be complete; they only need to stay live. +Open source building means a strong design path can be improved or finished by +subsequent teams. We appreciate teams that publish early, build openly, and +invite critique, so unaffiliated builders can pick up unfinished work without +having to ask.** + +## VII. THE FUTURE {#vii-the-future} + +For a long time, people have been pushed to believe that we only have two bad +choices. + +One is to accept that the name of the game is to obtain and maintain advantage; +and so to accept rule from the top, by those who already hold power: macro- +sovereigns like states, empires, corporate oligarchies, eschatological missions, +and grand ideologies that dictate how people live, decide who gets to act +freely, and who must comply, regardless of their subjects’ wishes. + +The other is to respond to that game without a principled aim: to burn it all +down, to retreat into mockery or withdrawal; or to defect to one or another +macro-sovereign, not because they are better, but simply because it is +opportune. + +But there are those who abjure this belief: it does not have to be this way. + +**Ethereum rejects the idea that there is no alternative.** + +Ethereum is not a weapon for either side of this conflict, and its stewards are +not a partisan faction within it. Ethereum is a tool that countless people - +individuals, families, and communities - are independently using to build +resilient sanctuaries from this contest of power: shelters from ideological +psychodrama, where anyone capable of taking refuge can live neither oppressed +nor oppressing, and where they can be left to their pursuits of happiness. + +And we, as Ethereum’s stewards, carry an additional responsibility: to keep +Ethereum usable for this purpose, and to keep the path open for users to create +and join sanctuaries that protect their freedoms and empower them to live the +lives they imagine for themselves. + +These sanctuaries are enabled in part by technology - decentralized, +permissionless, auditable, secure, and privacy-preserving machinery - and in +part by cultural and social aesthetics, which we bring to them as sensible and +considerate people, and which our technologies help defend. + +Our participation is in both the technology and the aesthetics: we build +infrastructure that secures forkable, self-sovereign computation from the ground +up; then, on top of this, we may experiment with novel coordination systems +underpinned by the sovereign freedoms to express and to exit. + +**Ethereum’s front in this sanctuary work is the front that defends permissionless +computation and communication with as much privacy and end-user agency as is +technologically viable.** + +Our closest collaborators include those working directly on privacy, +verifiability, and programmable cryptography. In the middle distance are our +neighbors working on open silicon, alternative networks and allied efforts. And +on the horizon are our friends working for clean air, and for regenerative and +sustainable habitats and permaculture; for freedom of speech and expression, and +the freedom to associate and dissociate voluntarily; for forkable technology +transfer; free open source collaboration in science, software, hardware, health, +and elsewhere, and a thousand other known and unknown things we trust them to +build without asking first. + +Ethereum is descended from a storied lineage of preservation instinct, prosocial +impulse, and principled predisposition. This is why it both has natural allies +and is an intrinsic building block for fellow travelers far beyond what we call +today, “crypto” or “web3.” + +**Alternatives exist. Trust hope, embrace resilience.** + +## VIII. CLOSING {#viii-closing} + +Our work is not about capturing markets, corporates, or states, nor about +helping them extract or capture. + +We are here to uncapture the individual, and to entrench their freedoms of +association. + +We are here to provide the infrastructure that enables a voice for those forms +of cooperation, organization, and community that go unrecognized within existing +hierarchies and systems. + +We provide the tools and the digital space needed for this civilization-scale +project, one that is open to anyone willing to claim self-sovereignty with their +own hands, that is available to everyone, especially those with nothing to lose +but their barbed wire fences. + +Ethereum is so other people can’t rug you; society can’t rug you; your +government can’t rug you; another government can’t rug you; corporations can’t +rug you; institutions can’t rug you; AI can’t rug you; mountain men can’t rug +you; your family can’t rug you; and so you don’t accidentally rug yourself +either. + +The Foundation exists to prevent Ethereum - more accurately, the promise of +Ethereum - from being rugged; to prevent Ethereum rugging those who are relying +on it to build their own sanctuaries; to make sure that it embodies the shared +principles from which Ethereum descends, upholding and advancing them rather +than letting them down. We have been entrusted with the torch of liberty and we +must keep it burning bright until the time comes to pass it on as it was passed +to us. + +Ethereum is for far more than crypto. The World Computer must rise and take its +rightful place as a shining star in the constellation of technologies that +underpin human freedom and flourishing. A lot more than crypto is counting on us +to steward Ethereum with skillful intent and discernment. + +For we are building nothing less than the machinery of freedom - not just for +today, but for the next thousand years. + +Our goal is to ensure the garden we’ve grown doesn’t just stay alive but +flourishes, the commons it creates remain open and infinitely spacious, and the +tools of sovereignty that are built remain available to all who would grasp +them, to all who would log on and win, forever. + +**There will be times when the work will be thankless; the journey will be +arduous; the path will be lonely. But every road to the stars first passes +through darkness.** + +_E quindi uscimmo a riveder le stelle._ From 26505fe1ee4749c2c0e55945823432a0e8b63db2 Mon Sep 17 00:00:00 2001 From: wackerow <54227730+wackerow@users.noreply.github.com> Date: Wed, 18 Mar 2026 09:30:38 -0700 Subject: [PATCH 003/127] feat: update intro copy Co-Authored-By: mnelsonBT <74370515+mnelsonBT@users.noreply.github.com> --- public/content/foundation/mandate/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/public/content/foundation/mandate/index.md b/public/content/foundation/mandate/index.md index 4019055e450..0494cbb736e 100644 --- a/public/content/foundation/mandate/index.md +++ b/public/content/foundation/mandate/index.md @@ -8,8 +8,9 @@ lang: en # The Ethereum Foundation Mandate {#mandate} -- [Graphical PDF version](https://ethereum.foundation/ef-mandate.pdf) -- [Canonically signed onchain source (via Blockscout explorer)](https://eth.blockscout.com/tx/0x5dd574df963a1df1f064791e0f6ff41ec972cdbba12293b7e1ece582052ba855) - Select "View details", under _Raw input_ selecting _UTF-8_ +This mandate was originally published by the Ethereum Foundation on 13-March-2026. Read the [original mandate here](https://ethereum.foundation/ef-mandate.pdf) in its fully-designed format. + +This document was placed onchain and signed by the Foundation, [visible on the Blockscout block explorer](https://eth.blockscout.com/tx/0x5dd574df963a1df1f064791e0f6ff41ec972cdbba12293b7e1ece582052ba855) (select "View details", under _Raw input_ with _UTF-8_). ## I. ETHEREUM {#i-ethereum} From 507c0e45620cbba4088fcb2b9a1a7a2b2eccaa5b Mon Sep 17 00:00:00 2001 From: wackerow <54227730+wackerow@users.noreply.github.com> Date: Wed, 18 Mar 2026 09:32:03 -0700 Subject: [PATCH 004/127] patch: extract cta link below text --- public/content/foundation/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/public/content/foundation/index.md b/public/content/foundation/index.md index 7580214935b..73a03c6711a 100644 --- a/public/content/foundation/index.md +++ b/public/content/foundation/index.md @@ -15,7 +15,9 @@ The EF is not a company, or even a traditional non-profit. It does not control o ## EF Mandate {#ef-mandate} -The [EF Mandate](/foundation/mandate/) defines the Foundation's purpose, principles, and commitments to the Ethereum ecosystem. Published onchain, it enshrines the EF's dedication to **censorship resistance, open source, privacy, and security (CROPS)** as non-negotiable priorities. +The EF Mandate defines the Foundation's purpose, principles, and commitments to the Ethereum ecosystem. Published onchain, it enshrines the EF's dedication to **censorship resistance, open source, privacy, and security (CROPS)** as non-negotiable priorities. + +[Read the Ethereum Foundation Mandate](/foundation/mandate/) ## What the EF does {#what-the-ef-does} From 0bf34c14a88f00d71969d04ac0a226f4ab9734fa Mon Sep 17 00:00:00 2001 From: wackerow <54227730+wackerow@users.noreply.github.com> Date: Wed, 18 Mar 2026 10:29:32 -0700 Subject: [PATCH 005/127] feat: update meta description --- public/content/foundation/mandate/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/content/foundation/mandate/index.md b/public/content/foundation/mandate/index.md index 0494cbb736e..e91b5fce96c 100644 --- a/public/content/foundation/mandate/index.md +++ b/public/content/foundation/mandate/index.md @@ -1,6 +1,6 @@ --- title: Ethereum Foundation Mandate -description: The Ethereum Foundation Mandate in text form +description: Explore the official Ethereum Foundation Mandate, defining the Foundation's purpose, principles, and commitments to the Ethereum ecosystem. hideEditButton: true sidebarDepth: 1 lang: en From 0c391a8ac075ff7bfb3d6305e5f087e9a98b7b5e Mon Sep 17 00:00:00 2001 From: myelinated-wackerow <263208946+myelinated-wackerow@users.noreply.github.com> Date: Fri, 3 Apr 2026 22:49:21 +0000 Subject: [PATCH 006/127] feat(i18n): localize event location country names MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add i18n-iso-countries package and country translation utilities to geography.ts. Event locations on community events pages and homepage now display translated country names (e.g., "Denver, USA" -> "Denver, アメリカ合衆国"). - getCountryTranslation(): reusable country name lookup - localizeLocation(): parses "City, Country" and translates - Updated EventCard, ContinentTabs, and homepage events - City names remain in Latin script (country-only MVP) Co-Authored-By: Claude Opus 4.6 Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com> --- .../events/_components/ContinentTabs.tsx | 5 +- .../events/_components/EventCard.tsx | 9 +-- app/[locale]/page.tsx | 3 +- package.json | 1 + pnpm-lock.yaml | 16 +++++ src/lib/utils/geography.ts | 72 +++++++++++++++++++ 6 files changed, 100 insertions(+), 6 deletions(-) diff --git a/app/[locale]/community/events/_components/ContinentTabs.tsx b/app/[locale]/community/events/_components/ContinentTabs.tsx index a63b383b471..652bd86dc6c 100644 --- a/app/[locale]/community/events/_components/ContinentTabs.tsx +++ b/app/[locale]/community/events/_components/ContinentTabs.tsx @@ -22,6 +22,7 @@ import { Tag } from "@/components/ui/tag" import { cn } from "@/lib/utils/cn" import { formatDateRange } from "@/lib/utils/date" +import { localizeLocation } from "@/lib/utils/geography" import { TAG_STATUS_MAPPING } from "../utils" @@ -174,7 +175,9 @@ export default function ContinentTabs({ {event.title}

-

{event.location}

+

+ {localizeLocation(event.location, locale)} +

diff --git a/app/[locale]/community/events/_components/EventCard.tsx b/app/[locale]/community/events/_components/EventCard.tsx index e0d945b0f7a..7d67283efe0 100644 --- a/app/[locale]/community/events/_components/EventCard.tsx +++ b/app/[locale]/community/events/_components/EventCard.tsx @@ -8,6 +8,7 @@ import { Tag } from "@/components/ui/tag" import { cn } from "@/lib/utils/cn" import { formatDate, formatDateRange } from "@/lib/utils/date" +import { localizeLocation } from "@/lib/utils/geography" import { TAG_STATUS_MAPPING } from "../utils" @@ -15,7 +16,7 @@ interface EventCardProps { event: EventItem variant?: "grid" | "highlight" className?: string - locale?: string + locale: string showTypeTag?: boolean customEventOptions?: MatomoEventOptions } @@ -72,7 +73,7 @@ function EventCardGrid({ {event.title}

{formattedDate &&

{formattedDate}

} -

{event.location}

+

{localizeLocation(event.location, locale)}

@@ -113,7 +114,7 @@ function EventCardHighlight({

{event.title}

-

{event.location}

+

{localizeLocation(event.location, locale)}

{formatDateRange(event.startTime, event.endTime, locale)}

@@ -128,7 +129,7 @@ export default function EventCard({ event, variant, className, - locale = "en", + locale, showTypeTag, customEventOptions, }: EventCardProps) { diff --git a/app/[locale]/page.tsx b/app/[locale]/page.tsx index 36bf989131f..fa6fe8ccd28 100644 --- a/app/[locale]/page.tsx +++ b/app/[locale]/page.tsx @@ -59,6 +59,7 @@ import { parseAppsOfTheWeek } from "@/lib/utils/apps" import { cn } from "@/lib/utils/cn" import { formatDateRange } from "@/lib/utils/date" import { getDirection } from "@/lib/utils/direction" +import { localizeLocation } from "@/lib/utils/geography" import { getMetadata } from "@/lib/utils/metadata" import { formatPriceUSD } from "@/lib/utils/numbers" import { polishRSSList } from "@/lib/utils/rss" @@ -850,7 +851,7 @@ const Page = async (props: { params: Promise }) => { })} - {location} + {localizeLocation(location, locale)} diff --git a/package.json b/package.json index 990f516f8ec..2aa0bfe5efe 100644 --- a/package.json +++ b/package.json @@ -76,6 +76,7 @@ "howler": "^2.2.4", "html-react-parser": "^5.2.17", "humanize-duration": "^3.33.1", + "i18n-iso-countries": "^7.14.0", "lodash": "^4.18.1", "lucide-react": "^0.516.0", "motion": "^12.36.0", diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 48188d95bc8..dd86676d46d 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -147,6 +147,9 @@ importers: humanize-duration: specifier: ^3.33.1 version: 3.33.1 + i18n-iso-countries: + specifier: ^7.14.0 + version: 7.14.0 lodash: specifier: ^4.18.1 version: 4.18.1 @@ -6474,6 +6477,9 @@ packages: devlop@1.1.0: resolution: {integrity: sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==} + diacritics@1.3.0: + resolution: {integrity: sha512-wlwEkqcsaxvPJML+rDh/2iS824jbREk6DUMUKkEaSlxdYHeS43cClJtsWglvw2RfeXGm6ohKDqsXteJ5sP5enA==} + didyoumean@1.2.2: resolution: {integrity: sha512-gxtyfqMg7GKyhQmb056K7M3xszy/myH8w+B4RT+QXBQsvAOdc3XymqDDPHx1BgPgsdAA5SIifona89YtRATDzw==} @@ -7456,6 +7462,10 @@ packages: engines: {node: '>=18'} hasBin: true + i18n-iso-countries@7.14.0: + resolution: {integrity: sha512-nXHJZYtNrfsi1UQbyRqm3Gou431elgLjKl//CYlnBGt5aTWdRPH1PiS2T/p/n8Q8LnqYqzQJik3Q7mkwvLokeg==} + engines: {node: '>= 12'} + icss-utils@5.1.0: resolution: {integrity: sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA==} engines: {node: ^10 || ^12 || >= 14} @@ -19379,6 +19389,8 @@ snapshots: dependencies: dequal: 2.0.3 + diacritics@1.3.0: {} + didyoumean@1.2.2: {} diff@4.0.2: {} @@ -20691,6 +20703,10 @@ snapshots: husky@9.1.7: {} + i18n-iso-countries@7.14.0: + dependencies: + diacritics: 1.3.0 + icss-utils@5.1.0(postcss@8.5.4): dependencies: postcss: 8.5.4 diff --git a/src/lib/utils/geography.ts b/src/lib/utils/geography.ts index 053e5a1af71..31e4b8ee073 100644 --- a/src/lib/utils/geography.ts +++ b/src/lib/utils/geography.ts @@ -1,3 +1,5 @@ +import countries from "i18n-iso-countries" + import type { Continent } from "@/lib/types" // Continent → countries mapping for location parsing @@ -106,3 +108,73 @@ export function parseLocationToContinent(location: string): Continent | null { if (!country) return null return COUNTRY_TO_CONTINENT[country] || null } + +/** + * Aliases for country names that i18n-iso-countries doesn't recognize. + * Maps free-text names from external data to forms the package understands. + */ +const COUNTRY_NAME_ALIASES: Record = { + "Hong Kong SAR": "Hong Kong", + // Add more here as needed +} + +/** + * Translate an English country name into the target locale. + * + * Accepts informal English country names (e.g., "USA", "United States", + * "Hong Kong SAR") and returns the localized name. + * + * @param country - English country name (informal forms accepted) + * @param locale - Target locale code (e.g., "ja", "es", "ar") + * @returns Localized country name, or the original string if not recognized + */ +export function getCountryTranslation( + country: string, + locale: string +): string { + if (!country) return country + + const normalized = COUNTRY_NAME_ALIASES[country] ?? country + const code = countries.getAlpha2Code(normalized, "en") + if (!code) return country + + return countries.getName(code, locale) ?? country +} + +/** + * Localize an event location string by translating the country portion. + * + * Parses "City, Country" format, translates the country into the target + * locale, and reassembles. City names are left in their original script. + * + * Returns the original string unchanged if: + * - The location is "Online" (handled separately by i18n keys) + * - The country cannot be identified or translated + * - The locale is "en" (no translation needed) + * + * @param location - Raw location string (e.g., "Denver, USA") + * @param locale - Target locale code (e.g., "ja", "es", "ar") + * @returns Localized location string (e.g., "Denver, アメリカ合衆国") + */ +export function localizeLocation(location: string, locale: string): string { + if (!location || locale === "en") return location + + if (location.toLowerCase() === "online") return location + + const parts = location.split(/,\s*/) + const rawCountry = parts[parts.length - 1].trim() + + const localizedCountry = getCountryTranslation(rawCountry, locale) + + // Country wasn't translated -- return original + if (localizedCountry === rawCountry) return location + + if (parts.length === 1) { + // No comma -- the whole string was the country (e.g., "Hong Kong SAR") + return localizedCountry + } + + // Reassemble: "City, TranslatedCountry" + const city = parts.slice(0, -1).join(", ") + return `${city}, ${localizedCountry}` +} From 75cc49b9c5349827593134cee02249e5ca03e583 Mon Sep 17 00:00:00 2001 From: Jakub Konopka Date: Wed, 8 Apr 2026 22:35:20 +0200 Subject: [PATCH 007/127] content: update future-proofing page + add post-quantum cryptography subpage Rewrites /roadmap/future-proofing/ with current information and creates a new /roadmap/future-proofing/quantum-resistance/ subpage with deeper coverage of post-quantum cryptography on Ethereum. Closes #17943 Co-Authored-By: Claude Opus 4.6 (1M context) --- .../content/roadmap/future-proofing/index.md | 87 ++++++--- .../quantum-resistance/index.md | 183 ++++++++++++++++++ 2 files changed, 247 insertions(+), 23 deletions(-) create mode 100644 public/content/roadmap/future-proofing/quantum-resistance/index.md diff --git a/public/content/roadmap/future-proofing/index.md b/public/content/roadmap/future-proofing/index.md index 625bec5dbbd..acbdf27dbb3 100644 --- a/public/content/roadmap/future-proofing/index.md +++ b/public/content/roadmap/future-proofing/index.md @@ -5,49 +5,90 @@ lang: en image: /images/roadmap/roadmap-future.png alt: "Ethereum roadmap" template: roadmap +summaryPoints: + - Post-quantum cryptography protects Ethereum from future quantum computer threats + - Protocol simplification makes Ethereum easier to maintain and more secure + - Recent upgrades have already delivered meaningful efficiency improvements --- -Some parts of the roadmap are not necessarily required for scaling or securing Ethereum in the near-term, but set Ethereum up for stability and reliability far into the future. +Some parts of the roadmap are not about scaling or securing Ethereum right now. They are about making Ethereum **stable and reliable far into the future**. This means preparing for new kinds of threats and removing unnecessary complexity from the protocol. ## Quantum resistance {#quantum-resistance} -Some of the [cryptography](/glossary/#cryptography) securing present-day Ethereum will be compromised when quantum computing becomes a reality. Although quantum computers are probably decades away from being a genuine threat to modern cryptography, Ethereum is being built to be secure for centuries to come. This means making [Ethereum quantum resistant](https://consensys.net/blog/developers/how-will-quantum-supremacy-affect-blockchain/) as soon as possible. +Ethereum uses [cryptography](/glossary/#cryptography) to keep the network secure and protect user funds. Some of these cryptographic methods will eventually be **vulnerable to quantum computers**, a new type of computer that solves certain mathematical problems much faster than today's machines. -The challenge facing Ethereum developers is that the current [proof-of-stake](/glossary/#pos) protocol relies upon a very efficient signature scheme known as BLS to aggregate votes on valid [blocks](/glossary/#block). This signature scheme is broken by quantum computers, but the quantum resistant alternatives are not as efficient. +**No quantum computer can break Ethereum's cryptography today.** Current quantum hardware is far from powerful enough. But recent research suggests the gap is closing faster than previously expected. In March 2026, Google Quantum AI published a paper estimating that breaking 256-bit elliptic curve cryptography (the type Ethereum uses for account signatures) could require roughly 1,200 logical qubits, about 20 times fewer than earlier estimates. Google has set a 2029 internal deadline for migrating its own systems to quantum-safe cryptography. -The [“KZG” commitment schemes](/roadmap/danksharding/#what-is-kzg) used in several places across Ethereum to generate cryptographic secrets are known to be quantum-vulnerable. Currently, this is circumvented using “trusted setups” (for which the main setup ceremony completed successfully in 2023), where many users generated randomness that cannot be reverse-engineered by a quantum computer. However, the ideal long-term solution would be to incorporate quantum safe cryptography instead. There are two leading approaches that could become efficient replacements for the BLS scheme: [STARK-based](https://hackmd.io/@vbuterin/stark_aggregation) and [lattice-based](https://medium.com/asecuritysite-when-bob-met-alice/so-what-is-lattice-encryption-326ac66e3175) signing. **These are still being actively researched and prototyped**. +Cryptographic transitions take years to plan and execute. Ethereum's security model is designed to last decades. That is why preparation is happening now, not as a reaction to an emergency. -[Read about KZG and trusted setups](/roadmap/danksharding#what-is-kzg) +### What is at risk? {#what-is-at-risk} -## Simpler and more efficient Ethereum {#simpler-more-efficient-ethereum} +Vitalik Buterin has identified **four areas** of Ethereum's cryptography that need post-quantum upgrades: + +1. **Consensus signatures (BLS)**: [Validators](/glossary/#validator) use BLS signatures to vote on valid [blocks](/glossary/#block). Quantum computers could break these. +2. **Data availability (KZG commitments)**: The [commitment schemes](/roadmap/danksharding/#what-is-kzg) that help Ethereum scale rely on math that quantum computers can attack. +3. **Account signatures (ECDSA)**: The signature scheme that protects individual Ethereum accounts. A quantum computer could derive a private key from a public key, potentially allowing theft of funds. +4. **Application-layer ZK-proofs**: Zero-knowledge proof systems used by rollups and other applications rely on cryptographic assumptions that quantum computers could undermine. + + + +No. No quantum computer today can break Ethereum's cryptography. The work described on this page is preparation for the future, not a response to an active threat. When post-quantum wallets become available, wallet software will guide you through the migration. For now, there is nothing you need to do. + + + +### What is being done? {#what-is-being-done} + +The Ethereum Foundation formed a dedicated **Post-Quantum Security team** in January 2026. The team's work is tracked publicly at [pq.ethereum.org](https://pq.ethereum.org). + +Active work includes: -Complexity creates opportunities for bugs or vulnerabilities that can be exploited by attackers. Therefore, part of the roadmap is simplifying Ethereum and removing or modifying code that has hung around through various upgrades but is no longer needed or can now be improved upon. A leaner, simpler codebase is easier for developers to maintain and reason about. +- **Hash-based signatures (leanXMSS)**: A quantum-safe replacement for validator signatures, built on hash functions that quantum computers cannot efficiently break. +- **Minimal zkVM (leanVM)**: A tool for aggregating quantum-safe signatures efficiently, so the network does not slow down after the transition. +- **Weekly interop testing**: More than 10 client teams participate in regular post-quantum devnets. +- **Poseidon Prize**: A $1 million research prize targeting improvements in hash-based cryptographic primitives. +- **NIST standards**: The U.S. National Institute of Standards and Technology finalized three post-quantum cryptography standards in August 2024 (ML-KEM, ML-DSA, SLH-DSA). Ethereum's work builds on these foundations. -To make the [Ethereum Virtual Machine (EVM)](/developers/docs/evm) simpler and more efficient, improvements are continuously researched and implemented. This involves both addressing legacy components and introducing optimizations. +A key part of the transition strategy is **EIP-8141**, which introduces native [account abstraction](/roadmap/account-abstraction/). This allows individual accounts to choose their own signature verification, meaning users could switch to quantum-safe signatures **without waiting for a single protocol-wide migration**. EIP-8141 is being considered for the Hegota hard fork (planned for H2 2026). -**Recent Changes Implemented:** +The Ethereum Foundation has outlined structured fork milestones targeting completion of core post-quantum infrastructure by approximately 2029. These are planning targets, not guaranteed commitments. -- **Gas Calculation Overhaul:** The way [gas](/glossary/#gas) is calculated was significantly improved with **EIP-1559 (implemented in the London upgrade, 2021)**, introducing a base fee and burn mechanism for more predictable transaction pricing. -- **`SELFDESTRUCT` Restriction:** The `SELFDESTRUCT` opcode, while rarely used, posed potential risks. Its functionality was heavily **restricted in the Dencun upgrade (March 2024) via EIP-6780** to mitigate dangers, especially concerning state management. -- **Modernized Transaction Types:** New transaction formats have been introduced (e.g., via **EIP-2718** and **EIP-4844** for blobs in the Dencun upgrade) to support new features and improve efficiency over legacy types. +[Read our detailed guide to post-quantum cryptography on Ethereum](/roadmap/future-proofing/quantum-resistance/) -**Ongoing and future goals:** +## Simpler and more efficient Ethereum {#simpler-more-efficient-ethereum} + +Complexity creates opportunities for bugs and vulnerabilities. Part of the roadmap focuses on **simplifying Ethereum and removing technical debt** so the protocol is easier to maintain, audit, and reason about. + +### What has been delivered {#what-has-been-delivered} + +Several recent upgrades have made Ethereum simpler and more efficient: -- **Further `SELFDESTRUCT` Handling:** While restricted, the **potential complete removal** of the `SELFDESTRUCT` opcode is still considered for future upgrades to further simplify the EVM state. ([More context on SELFDESTRUCT issues](https://hackmd.io/@vbuterin/selfdestruct)). -- **Phasing Out Legacy Transactions:** Although [Ethereum clients](/glossary/#consensus-client) still support older transaction types for backward compatibility, the goal is to encourage migration to newer types and **potentially deprecate or fully remove support for the oldest formats** in the future. -- **Continued Gas Efficiency Research:** Exploration continues into **further refinements for gas calculation**, potentially including concepts like multi-dimensional gas to better reflect resource usage. -- **Optimized Cryptographic Operations:** Efforts are ongoing to **bring in more efficient methods for the arithmetic** underpinning cryptographic operations used within the EVM. +- **Pectra (7-May-2025)**: Introduced EIP-7702, which lets externally owned accounts temporarily delegate to smart contract code, a stepping stone toward full [account abstraction](/roadmap/account-abstraction/). Also added the BLS12-381 precompile (EIP-2537), onchain deposit handling (EIP-6110), historical block hash access in the EVM (EIP-2935), and increased the maximum effective balance for validators (EIP-7251). +- **Fusaka (3-Dec-2025)**: Deployed PeerDAS (EIP-7594), a peer-to-peer data availability sampling system that distributes the data availability workload across the network. Also increased blob parameters, expanding data throughput for [rollups](/glossary/#rollups). +- **Dencun (March 2024)**: Introduced blob transactions (EIP-4844) for cheaper rollup data and restricted `SELFDESTRUCT` (EIP-6780) to remove a long-standing source of complexity. +- **London (2021)**: Overhauled [gas](/glossary/#gas) pricing with EIP-1559, introducing a base fee and burn mechanism for more predictable transaction costs. -Similarly, there are updates that can be made to other parts of present-day Ethereum clients. One example is that current execution and consensus clients use a different type of data compression. It will be much easier and more intuitive to share data between clients when the compression scheme is unified across the whole network. This remains an area of exploration. +### What is in progress {#what-is-in-progress} + +- **Glamsterdam (planned H1 2026)**: Expected to include enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928), and gas repricing to better align costs with actual resource usage. +- **Hegota (planned H2 2026)**: Expected to include [Verkle Trees](/roadmap/verkle-trees/), replacing the current data structure with a more efficient one that enables stateless clients. Also targeted for EIP-8141 (native account abstraction). +- **Ongoing**: Efforts to simplify the [EVM](/developers/docs/evm/), harmonize client implementations, and phase out deprecated features continue across the Ethereum development community. ## Current progress {#current-progress} -Many of the long-term future-proofing upgrades, particularly **full quantum resistance for core protocols, are still in the research phase and may be several years away** from being implemented. +As of early 2026: + +**Simplification and efficiency**: Significant progress. Pectra and Fusaka delivered real improvements in account flexibility, data availability, and validator operations. Glamsterdam and Hegota are in active development with clear EIP targets. + +**Post-quantum cryptography**: Active research and early implementation. The Ethereum Foundation has a dedicated team, funded research prizes, and weekly interop devnets running across multiple clients. However, **no post-quantum code is in production on Ethereum Mainnet yet**. The structured fork milestones target 2029 for completion. + +**Account abstraction and signature agility**: EIP-7702 shipped in Pectra. EIP-8141, being considered for Hegota, will allow accounts to use any signature scheme, giving users a path to adopt quantum-safe signatures before the full protocol transition is complete. -However, **significant progress has already been made on simplification efforts.** For example, key changes like the **restriction of `SELFDESTRUCT` (EIP-6780)** and the introduction of **blob-carrying transactions (EIP-4844)** were implemented in the **Dencun upgrade (March 2024)**. Work on harmonizing client compression schemes and other efficiency improvements also continues. +No part of this work is finished. Timelines are targets, not guarantees. But the scope and pace of active development represent a clear commitment to keeping Ethereum secure and efficient for the long term. **Further reading** -- [Gas](/developers/docs/gas) -- [EVM](/developers/docs/evm) -- [Data structures](/developers/docs/data-structures-and-encoding) \ No newline at end of file +- [pq.ethereum.org](https://pq.ethereum.org) +- [Post-quantum cryptography on Ethereum](/roadmap/future-proofing/quantum-resistance/) +- [Gas](/developers/docs/gas/) +- [EVM](/developers/docs/evm/) +- [Data structures](/developers/docs/data-structures-and-encoding/) diff --git a/public/content/roadmap/future-proofing/quantum-resistance/index.md b/public/content/roadmap/future-proofing/quantum-resistance/index.md new file mode 100644 index 00000000000..a6720d29b3c --- /dev/null +++ b/public/content/roadmap/future-proofing/quantum-resistance/index.md @@ -0,0 +1,183 @@ +--- +title: Post-quantum cryptography on Ethereum +description: How Ethereum is preparing for the post-quantum era, what is vulnerable, and what is being built to protect it. +lang: en +image: /images/roadmap/roadmap-future.png +alt: "Ethereum roadmap" +template: roadmap +summaryPoints: + - Quantum computers will eventually threaten the cryptography Ethereum uses today + - The Ethereum Foundation has a dedicated team and a structured plan targeting 2029 + - Your funds are safe today and wallet software will guide you through future migration +--- + +# Post-quantum cryptography on Ethereum {#post-quantum-cryptography} + +Quantum computers will eventually be able to break the cryptographic methods that secure Ethereum and most other digital systems today. This page explains what that means, what is being done about it, and what you need to know. + +## Why this matters {#why-this-matters} + +Ethereum relies on several forms of [cryptography](/glossary/#cryptography) to keep the network secure and protect user funds. The most important are: + +- **Elliptic curve cryptography (ECDSA)**: Used to sign transactions. Your Ethereum account's security depends on this. +- **BLS signatures**: Used by [validators](/glossary/#validator) to reach [consensus](/glossary/#consensus) on the state of the network. +- **KZG polynomial commitments**: Used for [data availability](/glossary/#data-availability) in Ethereum's scaling roadmap. +- **ZK-proof systems**: Used by rollups and other applications to verify computations offchain. + +All of these rely on mathematical problems that are hard for classical computers but could be solved efficiently by a sufficiently powerful quantum computer. + +### How close are quantum computers? {#how-close} + +In March 2026, Google Quantum AI published research estimating that breaking 256-bit elliptic curve cryptography (the type Ethereum uses for account signatures) could require roughly 1,200 logical qubits. Previous estimates put this number much higher. Google has set a 2029 internal deadline for migrating its own systems to post-quantum cryptography. + +Current quantum hardware operates with a few thousand noisy physical qubits. Logical qubits (which correct for errors and perform reliable computation) require many physical qubits each. **The gap between current hardware and what is needed to break Ethereum's cryptography remains significant, but it is narrowing faster than many expected.** + +This is not an imminent threat. But cryptographic transitions take years, and Ethereum's security model is designed to last decades. Preparing now is prudent. + +## The four vulnerable areas {#four-vulnerable-areas} + +In February 2026, Vitalik Buterin published a roadmap identifying four distinct areas of Ethereum's cryptography that need post-quantum upgrades. Each has different challenges and different solution paths. + +### 1. Consensus-layer BLS signatures {#consensus-bls} + +**What it does**: Ethereum's [proof-of-stake](/glossary/#pos) protocol uses BLS signatures to aggregate votes from hundreds of thousands of validators. BLS allows many signatures to be combined into one, keeping the network efficient. + +**Why it is vulnerable**: BLS signatures rely on elliptic curve pairings, which a quantum computer could break. + +**The approach**: The Ethereum Foundation is developing two complementary tools: +- **leanXMSS**: A hash-based signature scheme for validators. Hash-based signatures are considered quantum-safe because they rely only on the security of hash functions, which quantum computers weaken but do not break. +- **leanVM**: A minimal zkVM (zero-knowledge virtual machine) for SNARK-based signature aggregation. This preserves the efficiency benefits of combining many signatures into one, even after switching to quantum-safe schemes. + + + +The aggregation property that makes BLS efficient (combining hundreds of thousands of signatures into one) does not have an obvious quantum-safe equivalent. Post-quantum signatures are also much larger than BLS signatures. Simply swapping one for the other would make Ethereum's consensus layer significantly slower and more expensive. That is why the team is building leanVM, a tool that uses zero-knowledge proofs to aggregate quantum-safe signatures efficiently. + + + +### 2. Data availability: KZG commitments {#data-availability-kzg} + +**What it does**: KZG polynomial commitments ensure that data (particularly [blob](/glossary/#blob) data from rollups) is available on the network without requiring every node to download all of it. + +**Why it is vulnerable**: KZG commitments rely on elliptic curve pairings, the same mathematical structure that quantum computers can attack. + +**Current mitigation**: KZG commitments use a "trusted setup" where many participants contributed randomness. As long as at least one participant was honest and discarded their secret, the setup is secure, even against quantum computers attempting to reverse-engineer it after the fact. + +**Long-term solution**: Replace KZG with a quantum-safe commitment scheme. The two leading candidates are: +- **STARK-based commitments**: Rely on hash functions rather than elliptic curves. Already used in some ZK-rollups. +- **Lattice-based commitments**: Rely on the hardness of lattice problems, which are believed to be quantum-resistant. + +Both approaches are still being researched for efficiency and practicality at Ethereum's scale. + +### 3. Account signatures: ECDSA {#eoa-signatures} + +**What it does**: Every standard Ethereum account (externally owned account, or [EOA](/glossary/#eoa)) uses ECDSA on the secp256k1 curve to sign transactions. This is what protects your funds. + +**Why it is vulnerable**: A quantum computer could derive a private key from a public key. For accounts that have sent at least one transaction, the public key is exposed onchain, making them a potential target. + +**Important nuance**: Accounts that have only received ether and never sent a transaction have not exposed their public key. Only the address (a hash of the public key) is visible, which provides some additional protection. + +**The approach**: Rather than a single protocol-wide migration, Ethereum plans to use [account abstraction](/roadmap/account-abstraction/) (specifically EIP-8141, being considered for Hegota in H2 2026) to give users **signature agility**. Individual accounts could switch to a post-quantum signature scheme without waiting for the entire protocol to change. + +This is a pragmatic approach. Users and wallets that want post-quantum protection early can adopt it voluntarily, while the broader migration happens over time. + +### 4. Application-layer ZK-proofs {#zk-proofs} + +**What it does**: Zero-knowledge proof systems are used by L2 rollups and other applications to verify computations without revealing underlying data. + +**Why it is vulnerable**: Many popular ZK-proof systems (SNARKs using elliptic curve pairings) rely on quantum-vulnerable assumptions. + +**The approach**: STARKs, which rely on hash functions rather than elliptic curves, are already quantum-resistant and are used by several rollups. The transition for this layer is partly happening already through natural ecosystem adoption of STARK-based systems. + +## NIST standards {#nist-standards} + +In August 2024, the U.S. National Institute of Standards and Technology (NIST) finalized three post-quantum cryptography standards: + +| Standard | Name | Type | Use case | +|----------|------|------|----------| +| FIPS 203 | ML-KEM | Lattice-based | Key encapsulation (key exchange) | +| FIPS 204 | ML-DSA (Dilithium) | Lattice-based | Digital signatures | +| FIPS 205 | SLH-DSA (SPHINCS+) | Hash-based | Digital signatures | + +These standards provide a foundation for the broader industry's post-quantum transition. Ethereum's work builds on and extends these, with particular focus on the unique challenges of a decentralized network where efficiency and aggregation matter. + +## The Ethereum Foundation's approach {#ef-approach} + +The Ethereum Foundation formed a dedicated Post-Quantum Security team in January 2026, led by Thomas Coratger. The team's work is tracked publicly at [pq.ethereum.org](https://pq.ethereum.org). + +### Current activity (as of April 2026) {#current-activity} + +- **Weekly interop devnets**: More than 10 client teams participate in regular post-quantum interoperability testing, including Lighthouse, Grandine, Zeam, Ream Labs, and PierTwo. +- **Poseidon Prize**: A $1 million research prize targeting improvements in hash-based cryptographic primitives. +- **Open-source implementations**: leanXMSS, leanVM, leanSpec (Python), leanSig (Rust), and leanMultisig are all available under the leanEthereum GitHub organization. +- **2nd Annual PQ Research Retreat**: Planned for 9-Oct-2026 to 12-Oct-2026 in Cambridge, UK. + +### Migration milestones {#migration-milestones} + +The team has outlined a series of protocol upgrades to incrementally introduce post-quantum cryptography into Ethereum. These are planning milestones, not guaranteed commitments. Names and ordering may change. + +| Milestone | What it introduces | +|-----------|--------------------| +| I* | PQ key registry. Validators can register post-quantum public keys alongside existing BLS keys. | +| J* | PQ signature verification precompiles. Smart contracts and wallets can verify PQ signatures natively. | +| L* | PQ attestations and real-time consensus-layer proofs via leanVM. Validators begin using PQ signatures for consensus. | +| M* | Full PQ signature aggregation and PQ-safe blob commitments. | + +**Target**: Core post-quantum infrastructure in place by approximately 2029. Full execution-layer and ecosystem migration extends beyond that. + +## What do users need to do? {#what-users-need-to-do} + +**Right now: nothing.** Your funds are safe. No quantum computer today can threaten Ethereum's cryptography. + +**In the future**: Once post-quantum signature schemes are available on Ethereum (expected to begin with EIP-8141), you will want to migrate your account to quantum-safe signatures. Wallet software will guide you through this transition. + +If your account has never sent a transaction (meaning your public key has not been exposed onchain), it has an additional layer of protection. But all accounts should eventually migrate. + +The question of how to handle dormant wallets (accounts whose owners may not be aware of the need to migrate) is an open governance topic. The Ethereum community has not yet reached consensus on this. + +## Frequently asked questions {#faq} + + + +**No.** No quantum computer today can break Ethereum's cryptography. Current quantum hardware is far from the scale needed. The work described on this page is preparation for the future, not a response to an active threat. + + + + + +Estimates vary. Google's March 2026 research suggests the hardware needed to break 256-bit elliptic curve cryptography could arrive sometime around the end of this decade at the earliest, but significant engineering challenges remain. Most researchers consider a realistic threat to be several years away at minimum. The honest answer is that no one knows the exact timeline, which is precisely why preparing now is important. + + + + + +Eventually, yes. Once post-quantum signature schemes are available on Ethereum, users will want to migrate their accounts. Wallet software will likely handle this transition for you. For now, there is nothing you need to do. When action is needed, the Ethereum community and wallet developers will provide clear guidance and tools. + + + + + +Assets on Ethereum are controlled by account signatures. Once your account is migrated to a quantum-safe signature scheme, everything in that account is protected. You do not need to migrate each asset individually. Smart contracts that hold funds (like DeFi protocols) may need their own upgrades depending on what cryptographic primitives they use internally. + + + + + +Ethereum has one of the most structured post-quantum programs of any blockchain: a dedicated team, funded research, weekly devnets, and a published migration roadmap. No blockchain has completed a full post-quantum transition yet. Ethereum's quantum-vulnerable dormant fund exposure is estimated at approximately 0.1%, compared to approximately 5% for Bitcoin. + + + + + +"Harvest now, decrypt later" is an attack where someone records encrypted data or exposed public keys today, then breaks the encryption later once a powerful enough quantum computer exists. For Ethereum, this is most relevant to accounts whose public keys are already exposed onchain (any account that has sent a transaction). This is one reason the community treats post-quantum migration as time-sensitive even though the quantum threat is not yet immediate. + + + +## Further reading {#further-reading} + +- [pq.ethereum.org](https://pq.ethereum.org) - _Ethereum Foundation_ +- [NIST Post-Quantum Cryptography standards](https://csrc.nist.gov/projects/post-quantum-cryptography) - _NIST_ +- [Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly](https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/) - _Google Quantum AI_ +- [Quantum frontiers may be closer than they appear](https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/) - _Google_ +- [KZG and trusted setups](/roadmap/danksharding/#what-is-kzg) +- [Account abstraction on Ethereum](/roadmap/account-abstraction/) +- [strawmap.org](https://strawmap.org/) - _EF Architecture_ From 17486f053e4e940ef1a6ecfc127651517f10cb5f Mon Sep 17 00:00:00 2001 From: Jakub Konopka Date: Wed, 8 Apr 2026 23:52:43 +0200 Subject: [PATCH 008/127] fix: remove blanket redirect blocking future-proofing subpages The redirect rule `/roadmap/future-proofing/:path+` was catching all subpaths and redirecting them to the parent page. This prevented the new quantum-resistance subpage from rendering. Other roadmap sections (pectra, fusaka, merge) allow subpages without such a redirect. Co-Authored-By: Claude Opus 4.6 (1M context) --- redirects.config.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/redirects.config.js b/redirects.config.js index 7e71bc3c868..30500077bfc 100644 --- a/redirects.config.js +++ b/redirects.config.js @@ -135,7 +135,8 @@ module.exports = [ false, // Selectively applying temporary for possible future route usage ], ["/developers/docs/rollups", "/developers/docs/scaling/#rollups"], - ["/roadmap/future-proofing/:path+", "/roadmap/future-proofing/"], + // Removed: ["/roadmap/future-proofing/:path+", "/roadmap/future-proofing/"], + // This blanket redirect prevented subpages (e.g. /quantum-resistance/) from rendering ["/eth2/what-is-eth2", "/roadmap/"], [ "/developers/docs/accounts/account-abstraction", From 7a905afc9e5365aefca579bbd857f9506dda306e Mon Sep 17 00:00:00 2001 From: wackerow <54227730+wackerow@users.noreply.github.com> Date: Wed, 8 Apr 2026 13:49:58 -0700 Subject: [PATCH 009/127] refactor: descriptive thumbnail naming --- app/[locale]/developers/page.tsx | 4 ++-- app/[locale]/page.tsx | 4 ++-- ...vent-placeholder.png => eth-glyph-thumbnail.png} | Bin src/components/Image/CardImage.tsx | 6 +++--- 4 files changed, 7 insertions(+), 7 deletions(-) rename public/images/{events/event-placeholder.png => eth-glyph-thumbnail.png} (100%) diff --git a/app/[locale]/developers/page.tsx b/app/[locale]/developers/page.tsx index e0174d0f026..95bc356f416 100644 --- a/app/[locale]/developers/page.tsx +++ b/app/[locale]/developers/page.tsx @@ -48,7 +48,7 @@ import scaffoldDebugScreenshot from "@/public/images/developers/scaffold-debug-s import stackExchangeScreenshot from "@/public/images/developers/stack-exchange-screenshot.png" import tutorialTagsBanner from "@/public/images/developers/tutorial-tags-banner.png" import dogeImage from "@/public/images/doge-computer.png" -import EventFallback from "@/public/images/events/event-placeholder.png" +import fallbackThumbnail from "@/public/images/eth-glyph-thumbnail.png" import heroImage from "@/public/images/heroes/developers-hub-hero.png" const H3 = (props: ChildOnlyProp) =>

@@ -604,7 +604,7 @@ const DevelopersPage = async (props: { params: Promise }) => { {bannerImage ? ( ) : ( - + )} diff --git a/app/[locale]/page.tsx b/app/[locale]/page.tsx index f6c593b4981..33052d62cb6 100644 --- a/app/[locale]/page.tsx +++ b/app/[locale]/page.tsx @@ -92,7 +92,7 @@ import { getRSSData, getTotalValueLockedData, } from "@/lib/data" -import EventFallback from "@/public/images/events/event-placeholder.png" +import fallbackThumbnail from "@/public/images/eth-glyph-thumbnail.png" const Page = async (props: { params: Promise }) => { const params = await props.params @@ -848,7 +848,7 @@ const Page = async (props: { params: Promise }) => { className="max-w-full object-cover object-center" /> ) : ( - + )} diff --git a/public/images/events/event-placeholder.png b/public/images/eth-glyph-thumbnail.png similarity index 100% rename from public/images/events/event-placeholder.png rename to public/images/eth-glyph-thumbnail.png diff --git a/src/components/Image/CardImage.tsx b/src/components/Image/CardImage.tsx index a331bd5333c..626b89185f4 100644 --- a/src/components/Image/CardImage.tsx +++ b/src/components/Image/CardImage.tsx @@ -2,7 +2,7 @@ import { ComponentProps, forwardRef } from "react" -import EventFallback from "@/public/images/events/event-placeholder.png" +import fallbackThumbnail from "@/public/images/eth-glyph-thumbnail.png" type CardImageProps = ComponentProps<"img"> @@ -11,12 +11,12 @@ const CardImage = forwardRef( // eslint-disable-next-line @next/next/no-img-element { e.currentTarget.onerror = null - e.currentTarget.src = EventFallback.src + e.currentTarget.src = fallbackThumbnail.src }} referrerPolicy="no-referrer" className={className} From 45a5e955494b09eb61876286824dcb1b1783065e Mon Sep 17 00:00:00 2001 From: Jakub Konopka Date: Thu, 9 Apr 2026 14:36:28 +0200 Subject: [PATCH 010/127] content: apply PR review feedback from myelinated-wackerow and mnelsonBT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix Hegota → Hegotá throughout (5 occurrences) - Remove duplicate h1 in quantum-resistance subpage (template renders it) - Change "decades" → "centuries" for Ethereum security model framing - Expand ECDSA at first use in subpage - Add attribution to dormant fund exposure figure, remove Bitcoin comparison - Change "expected to include" → "being considered for inclusion" for Glamsterdam/Hegotá - Replace "H1/H2 2026" with "first/second half of 2026" for global audience - Add context sentence before NIST standards table - Apply mnelsonBT's copy improvements: summaryPoints, quantum intro, EF team description, leanVM 250x compression detail, ECDSA vulnerability explanation Co-Authored-By: Claude Opus 4.6 (1M context) --- .../content/roadmap/future-proofing/index.md | 32 +++++++++---------- .../quantum-resistance/index.md | 12 +++---- 2 files changed, 21 insertions(+), 23 deletions(-) diff --git a/public/content/roadmap/future-proofing/index.md b/public/content/roadmap/future-proofing/index.md index acbdf27dbb3..91a27c32171 100644 --- a/public/content/roadmap/future-proofing/index.md +++ b/public/content/roadmap/future-proofing/index.md @@ -6,8 +6,8 @@ image: /images/roadmap/roadmap-future.png alt: "Ethereum roadmap" template: roadmap summaryPoints: - - Post-quantum cryptography protects Ethereum from future quantum computer threats - - Protocol simplification makes Ethereum easier to maintain and more secure + - Post-quantum cryptography ensures Ethereum can survive advanced hardware threats as quantum computing advances + - Protocol simplification makes Ethereum easier to maintain, audit, and secure - Recent upgrades have already delivered meaningful efficiency improvements --- @@ -15,19 +15,19 @@ Some parts of the roadmap are not about scaling or securing Ethereum right now. ## Quantum resistance {#quantum-resistance} -Ethereum uses [cryptography](/glossary/#cryptography) to keep the network secure and protect user funds. Some of these cryptographic methods will eventually be **vulnerable to quantum computers**, a new type of computer that solves certain mathematical problems much faster than today's machines. +Ethereum uses [cryptography](/glossary/#cryptography) to keep the network secure and protect user funds. Eventually, some of these cryptographic methods will be **vulnerable to quantum computers**, which can solve specific mathematical problems exponentially faster than classical machines. -**No quantum computer can break Ethereum's cryptography today.** Current quantum hardware is far from powerful enough. But recent research suggests the gap is closing faster than previously expected. In March 2026, Google Quantum AI published a paper estimating that breaking 256-bit elliptic curve cryptography (the type Ethereum uses for account signatures) could require roughly 1,200 logical qubits, about 20 times fewer than earlier estimates. Google has set a 2029 internal deadline for migrating its own systems to quantum-safe cryptography. +**No quantum computer can break Ethereum's cryptography today.** The hardware required does not yet exist at scale. But recent research suggests the gap is closing faster than previously expected. In March 2026, Google Quantum AI published a paper estimating that breaking 256-bit elliptic curve cryptography (the type Ethereum uses for account signatures) could require roughly 1,200 logical qubits, about 20 times fewer than earlier estimates. Google has set a 2029 internal deadline for migrating its own systems to quantum-safe cryptography. -Cryptographic transitions take years to plan and execute. Ethereum's security model is designed to last decades. That is why preparation is happening now, not as a reaction to an emergency. +Cryptographic transitions take years to plan and execute safely. Because Ethereum's security model is designed to last decades, post-quantum preparation was in Ethereum's roadmap before it was in mainstream headlines. Network preparation is happening now to ensure a seamless transition, not as a reaction to an emergency. ### What is at risk? {#what-is-at-risk} -Vitalik Buterin has identified **four areas** of Ethereum's cryptography that need post-quantum upgrades: +Four primary areas of Ethereum's cryptography have been identified as requiring post-quantum upgrades: -1. **Consensus signatures (BLS)**: [Validators](/glossary/#validator) use BLS signatures to vote on valid [blocks](/glossary/#block). Quantum computers could break these. -2. **Data availability (KZG commitments)**: The [commitment schemes](/roadmap/danksharding/#what-is-kzg) that help Ethereum scale rely on math that quantum computers can attack. -3. **Account signatures (ECDSA)**: The signature scheme that protects individual Ethereum accounts. A quantum computer could derive a private key from a public key, potentially allowing theft of funds. +1. **Consensus signatures (BLS)**: [Validators](/glossary/#validator) use BLS signatures to vote on valid [blocks](/glossary/#block). A quantum computer could forge these signatures. +2. **Data availability (KZG commitments)**: The [commitment schemes](/roadmap/danksharding/#what-is-kzg) that help Ethereum scale rely on math (specifically, elliptic curve pairing) that is vulnerable to quantum attacks. +3. **Account signatures (ECDSA)**: The signature scheme that protects individual Ethereum accounts. When an account sends a transaction, its public key is exposed onchain. A quantum computer could derive the private key from this exposed public key, potentially allowing theft of funds. 4. **Application-layer ZK-proofs**: Zero-knowledge proof systems used by rollups and other applications rely on cryptographic assumptions that quantum computers could undermine. @@ -38,17 +38,17 @@ No. No quantum computer today can break Ethereum's cryptography. The work descri ### What is being done? {#what-is-being-done} -The Ethereum Foundation formed a dedicated **Post-Quantum Security team** in January 2026. The team's work is tracked publicly at [pq.ethereum.org](https://pq.ethereum.org). +Ethereum is currently the most proactive defender against quantum threats in the blockchain ecosystem. The Ethereum Foundation formed a dedicated **Post-Quantum Security team** in January 2026, and active work spans across multiple client teams and research groups. The EF Post-Quantum team's work is tracked publicly at [pq.ethereum.org](https://pq.ethereum.org). Active work includes: - **Hash-based signatures (leanXMSS)**: A quantum-safe replacement for validator signatures, built on hash functions that quantum computers cannot efficiently break. -- **Minimal zkVM (leanVM)**: A tool for aggregating quantum-safe signatures efficiently, so the network does not slow down after the transition. +- **Minimal zkVM (leanVM)**: Because quantum-safe signatures are larger than the signatures currently used, leanXMSS is paired with a minimal zkVM (leanVM). This engine aggregates quantum-safe signatures efficiently, compressing the data by 250x, so the network remains fast after the transition. - **Weekly interop testing**: More than 10 client teams participate in regular post-quantum devnets. - **Poseidon Prize**: A $1 million research prize targeting improvements in hash-based cryptographic primitives. - **NIST standards**: The U.S. National Institute of Standards and Technology finalized three post-quantum cryptography standards in August 2024 (ML-KEM, ML-DSA, SLH-DSA). Ethereum's work builds on these foundations. -A key part of the transition strategy is **EIP-8141**, which introduces native [account abstraction](/roadmap/account-abstraction/). This allows individual accounts to choose their own signature verification, meaning users could switch to quantum-safe signatures **without waiting for a single protocol-wide migration**. EIP-8141 is being considered for the Hegota hard fork (planned for H2 2026). +A key part of the transition strategy is **EIP-8141**, which introduces native [account abstraction](/roadmap/account-abstraction/). This allows individual accounts to choose their own signature verification, meaning users could switch to quantum-safe signatures **without waiting for a single protocol-wide migration**. EIP-8141 is being considered for the Hegotá hard fork (planned for second half of 2026). The Ethereum Foundation has outlined structured fork milestones targeting completion of core post-quantum infrastructure by approximately 2029. These are planning targets, not guaranteed commitments. @@ -69,19 +69,19 @@ Several recent upgrades have made Ethereum simpler and more efficient: ### What is in progress {#what-is-in-progress} -- **Glamsterdam (planned H1 2026)**: Expected to include enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928), and gas repricing to better align costs with actual resource usage. -- **Hegota (planned H2 2026)**: Expected to include [Verkle Trees](/roadmap/verkle-trees/), replacing the current data structure with a more efficient one that enables stateless clients. Also targeted for EIP-8141 (native account abstraction). +- **Glamsterdam (planned first half of 2026)**: Being considered for inclusion: enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928), and gas repricing to better align costs with actual resource usage. +- **Hegotá (planned second half of 2026)**: Being considered for inclusion: [Verkle Trees](/roadmap/verkle-trees/), replacing the current data structure with a more efficient one that enables stateless clients. Also targeted for EIP-8141 (native account abstraction). - **Ongoing**: Efforts to simplify the [EVM](/developers/docs/evm/), harmonize client implementations, and phase out deprecated features continue across the Ethereum development community. ## Current progress {#current-progress} As of early 2026: -**Simplification and efficiency**: Significant progress. Pectra and Fusaka delivered real improvements in account flexibility, data availability, and validator operations. Glamsterdam and Hegota are in active development with clear EIP targets. +**Simplification and efficiency**: Significant progress. Pectra and Fusaka delivered real improvements in account flexibility, data availability, and validator operations. Glamsterdam and Hegotá are in active development with clear EIP targets. **Post-quantum cryptography**: Active research and early implementation. The Ethereum Foundation has a dedicated team, funded research prizes, and weekly interop devnets running across multiple clients. However, **no post-quantum code is in production on Ethereum Mainnet yet**. The structured fork milestones target 2029 for completion. -**Account abstraction and signature agility**: EIP-7702 shipped in Pectra. EIP-8141, being considered for Hegota, will allow accounts to use any signature scheme, giving users a path to adopt quantum-safe signatures before the full protocol transition is complete. +**Account abstraction and signature agility**: EIP-7702 shipped in Pectra. EIP-8141, being considered for Hegotá, will allow accounts to use any signature scheme, giving users a path to adopt quantum-safe signatures before the full protocol transition is complete. No part of this work is finished. Timelines are targets, not guarantees. But the scope and pace of active development represent a clear commitment to keeping Ethereum secure and efficient for the long term. diff --git a/public/content/roadmap/future-proofing/quantum-resistance/index.md b/public/content/roadmap/future-proofing/quantum-resistance/index.md index a6720d29b3c..d4937911d41 100644 --- a/public/content/roadmap/future-proofing/quantum-resistance/index.md +++ b/public/content/roadmap/future-proofing/quantum-resistance/index.md @@ -11,15 +11,13 @@ summaryPoints: - Your funds are safe today and wallet software will guide you through future migration --- -# Post-quantum cryptography on Ethereum {#post-quantum-cryptography} - Quantum computers will eventually be able to break the cryptographic methods that secure Ethereum and most other digital systems today. This page explains what that means, what is being done about it, and what you need to know. ## Why this matters {#why-this-matters} Ethereum relies on several forms of [cryptography](/glossary/#cryptography) to keep the network secure and protect user funds. The most important are: -- **Elliptic curve cryptography (ECDSA)**: Used to sign transactions. Your Ethereum account's security depends on this. +- **Elliptic curve digital signature algorithm (ECDSA)**: Used to sign transactions. Your Ethereum account's security depends on this. - **BLS signatures**: Used by [validators](/glossary/#validator) to reach [consensus](/glossary/#consensus) on the state of the network. - **KZG polynomial commitments**: Used for [data availability](/glossary/#data-availability) in Ethereum's scaling roadmap. - **ZK-proof systems**: Used by rollups and other applications to verify computations offchain. @@ -32,7 +30,7 @@ In March 2026, Google Quantum AI published research estimating that breaking 256 Current quantum hardware operates with a few thousand noisy physical qubits. Logical qubits (which correct for errors and perform reliable computation) require many physical qubits each. **The gap between current hardware and what is needed to break Ethereum's cryptography remains significant, but it is narrowing faster than many expected.** -This is not an imminent threat. But cryptographic transitions take years, and Ethereum's security model is designed to last decades. Preparing now is prudent. +This is not an imminent threat. But cryptographic transitions take years, and Ethereum's security model is designed to last centuries. Preparing now is prudent. ## The four vulnerable areas {#four-vulnerable-areas} @@ -76,7 +74,7 @@ Both approaches are still being researched for efficiency and practicality at Et **Important nuance**: Accounts that have only received ether and never sent a transaction have not exposed their public key. Only the address (a hash of the public key) is visible, which provides some additional protection. -**The approach**: Rather than a single protocol-wide migration, Ethereum plans to use [account abstraction](/roadmap/account-abstraction/) (specifically EIP-8141, being considered for Hegota in H2 2026) to give users **signature agility**. Individual accounts could switch to a post-quantum signature scheme without waiting for the entire protocol to change. +**The approach**: Rather than a single protocol-wide migration, Ethereum plans to use [account abstraction](/roadmap/account-abstraction/) (specifically EIP-8141, being considered for Hegotá in second half of 2026) to give users **signature agility**. Individual accounts could switch to a post-quantum signature scheme without waiting for the entire protocol to change. This is a pragmatic approach. Users and wallets that want post-quantum protection early can adopt it voluntarily, while the broader migration happens over time. @@ -90,7 +88,7 @@ This is a pragmatic approach. Users and wallets that want post-quantum protectio ## NIST standards {#nist-standards} -In August 2024, the U.S. National Institute of Standards and Technology (NIST) finalized three post-quantum cryptography standards: +In August 2024, the U.S. National Institute of Standards and Technology (NIST) finalized three post-quantum cryptography standards. These matter because they give the entire technology industry, including Ethereum, a shared set of vetted algorithms to build on rather than each project inventing its own. | Standard | Name | Type | Use case | |----------|------|------|----------| @@ -162,7 +160,7 @@ Assets on Ethereum are controlled by account signatures. Once your account is mi -Ethereum has one of the most structured post-quantum programs of any blockchain: a dedicated team, funded research, weekly devnets, and a published migration roadmap. No blockchain has completed a full post-quantum transition yet. Ethereum's quantum-vulnerable dormant fund exposure is estimated at approximately 0.1%, compared to approximately 5% for Bitcoin. +Ethereum has one of the most structured post-quantum programs of any blockchain: a dedicated team, funded research, weekly devnets, and a published migration roadmap. No blockchain has completed a full post-quantum transition yet. According to Ethereum Foundation estimates, Ethereum's quantum-vulnerable dormant fund exposure is approximately 0.1%. From 76f7b1d1b006443f2818d7d3c3a69670213344e2 Mon Sep 17 00:00:00 2001 From: Jakub Konopka Date: Thu, 9 Apr 2026 14:37:12 +0200 Subject: [PATCH 011/127] content: add data availability bullet per mnelsonBT suggestion Co-Authored-By: Claude Opus 4.6 (1M context) --- public/content/roadmap/future-proofing/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/public/content/roadmap/future-proofing/index.md b/public/content/roadmap/future-proofing/index.md index 91a27c32171..8af3f83559c 100644 --- a/public/content/roadmap/future-proofing/index.md +++ b/public/content/roadmap/future-proofing/index.md @@ -45,6 +45,7 @@ Active work includes: - **Hash-based signatures (leanXMSS)**: A quantum-safe replacement for validator signatures, built on hash functions that quantum computers cannot efficiently break. - **Minimal zkVM (leanVM)**: Because quantum-safe signatures are larger than the signatures currently used, leanXMSS is paired with a minimal zkVM (leanVM). This engine aggregates quantum-safe signatures efficiently, compressing the data by 250x, so the network remains fast after the transition. - **Weekly interop testing**: More than 10 client teams participate in regular post-quantum devnets. +- **Data availability:** Upgrading the underlying cryptography used to handle large amounts of network data will ensure Ethereum stays fast and affordable to use without risking future quantum vulnerabilities. - **Poseidon Prize**: A $1 million research prize targeting improvements in hash-based cryptographic primitives. - **NIST standards**: The U.S. National Institute of Standards and Technology finalized three post-quantum cryptography standards in August 2024 (ML-KEM, ML-DSA, SLH-DSA). Ethereum's work builds on these foundations. From ac5f6fd45464f07fdda16f5d9ab067e10fbcc86c Mon Sep 17 00:00:00 2001 From: Jakub Konopka Date: Thu, 9 Apr 2026 15:21:59 +0200 Subject: [PATCH 012/127] content: apply remaining mnelsonBT review suggestions - Add internal links to fork names (Pectra, Fusaka, Dencun, London, Glamsterdam) - Rewrite current progress summaries (simplification, PQ sections) - Add PSE and lean week Cambridge links to further reading - Rewrite subpage intro with proactive framing - Rename section header to "Why post-quantum cryptography matters" - Update summaryPoint to reference "Lean Ethereum" roadmap - Add Shor's algorithm reference and Abelian groups context - Rename "How close" to "When will quantum computers threaten Ethereum" - Add NIST ECDSA deprecation timeline (2030 deprecation, 2035 disallowed) - Add "Lean Ethereum" roadmap framing to conclusion Co-Authored-By: Claude Opus 4.6 (1M context) --- .../content/roadmap/future-proofing/index.md | 18 ++++++++++-------- .../quantum-resistance/index.md | 16 ++++++++-------- 2 files changed, 18 insertions(+), 16 deletions(-) diff --git a/public/content/roadmap/future-proofing/index.md b/public/content/roadmap/future-proofing/index.md index 8af3f83559c..48a03926f22 100644 --- a/public/content/roadmap/future-proofing/index.md +++ b/public/content/roadmap/future-proofing/index.md @@ -63,14 +63,14 @@ Complexity creates opportunities for bugs and vulnerabilities. Part of the roadm Several recent upgrades have made Ethereum simpler and more efficient: -- **Pectra (7-May-2025)**: Introduced EIP-7702, which lets externally owned accounts temporarily delegate to smart contract code, a stepping stone toward full [account abstraction](/roadmap/account-abstraction/). Also added the BLS12-381 precompile (EIP-2537), onchain deposit handling (EIP-6110), historical block hash access in the EVM (EIP-2935), and increased the maximum effective balance for validators (EIP-7251). -- **Fusaka (3-Dec-2025)**: Deployed PeerDAS (EIP-7594), a peer-to-peer data availability sampling system that distributes the data availability workload across the network. Also increased blob parameters, expanding data throughput for [rollups](/glossary/#rollups). -- **Dencun (March 2024)**: Introduced blob transactions (EIP-4844) for cheaper rollup data and restricted `SELFDESTRUCT` (EIP-6780) to remove a long-standing source of complexity. -- **London (2021)**: Overhauled [gas](/glossary/#gas) pricing with EIP-1559, introducing a base fee and burn mechanism for more predictable transaction costs. +- **[Pectra (7-May-2025)](/roadmap/pectra/)**: Introduced EIP-7702, which lets externally owned accounts temporarily delegate to smart contract code, a stepping stone toward full [account abstraction](/roadmap/account-abstraction/). Also added the BLS12-381 precompile (EIP-2537), onchain deposit handling (EIP-6110), historical block hash access in the EVM (EIP-2935), and increased the maximum effective balance for validators (EIP-7251). +- **[Fusaka (3-Dec-2025)](/roadmap/fusaka/)**: Deployed PeerDAS (EIP-7594), a peer-to-peer data availability sampling system that distributes the data availability workload across the network. Also increased blob parameters, expanding data throughput for [rollups](/glossary/#rollups). +- **[Dencun (March 2024)](/roadmap/dencun/)**: Introduced blob transactions (EIP-4844) for cheaper rollup data and restricted `SELFDESTRUCT` (EIP-6780) to remove a long-standing source of complexity. +- **[London (2021)](/ethereum-forks/#london)**: Overhauled [gas](/glossary/#gas) pricing with EIP-1559, introducing a base fee and burn mechanism for more predictable transaction costs. ### What is in progress {#what-is-in-progress} -- **Glamsterdam (planned first half of 2026)**: Being considered for inclusion: enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928), and gas repricing to better align costs with actual resource usage. +- **[Glamsterdam (planned first half of 2026)](/roadmap/glamsterdam/)**: Being considered for inclusion: enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928), and gas repricing to better align costs with actual resource usage. - **Hegotá (planned second half of 2026)**: Being considered for inclusion: [Verkle Trees](/roadmap/verkle-trees/), replacing the current data structure with a more efficient one that enables stateless clients. Also targeted for EIP-8141 (native account abstraction). - **Ongoing**: Efforts to simplify the [EVM](/developers/docs/evm/), harmonize client implementations, and phase out deprecated features continue across the Ethereum development community. @@ -78,9 +78,9 @@ Several recent upgrades have made Ethereum simpler and more efficient: As of early 2026: -**Simplification and efficiency**: Significant progress. Pectra and Fusaka delivered real improvements in account flexibility, data availability, and validator operations. Glamsterdam and Hegotá are in active development with clear EIP targets. +**Simplification and efficiency**: Pectra and Fusaka delivered real improvements in account flexibility, data availability, and validator operations. Glamsterdam and Hegotá are in active development with clear targets to make the network more resilient and efficient, while removing external dependencies. -**Post-quantum cryptography**: Active research and early implementation. The Ethereum Foundation has a dedicated team, funded research prizes, and weekly interop devnets running across multiple clients. However, **no post-quantum code is in production on Ethereum Mainnet yet**. The structured fork milestones target 2029 for completion. +**Post-quantum cryptography**: Active research and early implementation are underway. The ecosystem has funded research prizes and runs weekly interop devnets across multiple clients, in addition to the research done by the Ethereum Foundation's dedicated Post-Quantum team. While the structured fork milestones target approximately 2029 for completion, early research is producing tangible proof points demonstrating that post-quantum execution is viable today. **Account abstraction and signature agility**: EIP-7702 shipped in Pectra. EIP-8141, being considered for Hegotá, will allow accounts to use any signature scheme, giving users a path to adopt quantum-safe signatures before the full protocol transition is complete. @@ -88,8 +88,10 @@ No part of this work is finished. Timelines are targets, not guarantees. But the **Further reading** -- [pq.ethereum.org](https://pq.ethereum.org) - [Post-quantum cryptography on Ethereum](/roadmap/future-proofing/quantum-resistance/) +- [Privacy Stewards of Ethereum: Post-Quantum Cryptography and Ethereum](https://pse.dev/projects/post-quantum-cryptography) +- [lean week: leanVM + PQ workshops, Cambridge 2025](https://github.com/leanEthereum/pm/blob/main/workshops-and-interops/2025/lean-week-cambridge/index.md) +- [pq.ethereum.org](https://pq.ethereum.org) - [Gas](/developers/docs/gas/) - [EVM](/developers/docs/evm/) - [Data structures](/developers/docs/data-structures-and-encoding/) diff --git a/public/content/roadmap/future-proofing/quantum-resistance/index.md b/public/content/roadmap/future-proofing/quantum-resistance/index.md index d4937911d41..44ff5edb064 100644 --- a/public/content/roadmap/future-proofing/quantum-resistance/index.md +++ b/public/content/roadmap/future-proofing/quantum-resistance/index.md @@ -7,30 +7,30 @@ alt: "Ethereum roadmap" template: roadmap summaryPoints: - Quantum computers will eventually threaten the cryptography Ethereum uses today - - The Ethereum Foundation has a dedicated team and a structured plan targeting 2029 + - The Ethereum Foundation has a dedicated post-quantum research team, and a structured "Lean Ethereum" roadmap targeting 2029 for full post-quantum protection - Your funds are safe today and wallet software will guide you through future migration --- -Quantum computers will eventually be able to break the cryptographic methods that secure Ethereum and most other digital systems today. This page explains what that means, what is being done about it, and what you need to know. +Quantum computers will eventually be able to break the cryptographic methods that secure Ethereum and most other digital systems today. This page explains what that means, how the network is proactively developing improvements to mitigate this risk, and what you need to know. -## Why this matters {#why-this-matters} +## Why post-quantum cryptography matters {#why-post-quantum-matters} Ethereum relies on several forms of [cryptography](/glossary/#cryptography) to keep the network secure and protect user funds. The most important are: -- **Elliptic curve digital signature algorithm (ECDSA)**: Used to sign transactions. Your Ethereum account's security depends on this. +- **Elliptic curve digital signature algorithm (ECDSA)**: The cryptography used to sign transactions. Your Ethereum account's security depends on this. - **BLS signatures**: Used by [validators](/glossary/#validator) to reach [consensus](/glossary/#consensus) on the state of the network. - **KZG polynomial commitments**: Used for [data availability](/glossary/#data-availability) in Ethereum's scaling roadmap. - **ZK-proof systems**: Used by rollups and other applications to verify computations offchain. -All of these rely on mathematical problems that are hard for classical computers but could be solved efficiently by a sufficiently powerful quantum computer. +All of these rely on mathematical structures, such as Abelian groups, that are hard for classical computers but can be solved efficiently by a quantum computer using [Shor's algorithm](https://en.wikipedia.org/wiki/Shor%27s_algorithm). -### How close are quantum computers? {#how-close} +### When will quantum computers threaten Ethereum? {#when-will-quantum-computers-threaten-ethereum} In March 2026, Google Quantum AI published research estimating that breaking 256-bit elliptic curve cryptography (the type Ethereum uses for account signatures) could require roughly 1,200 logical qubits. Previous estimates put this number much higher. Google has set a 2029 internal deadline for migrating its own systems to post-quantum cryptography. -Current quantum hardware operates with a few thousand noisy physical qubits. Logical qubits (which correct for errors and perform reliable computation) require many physical qubits each. **The gap between current hardware and what is needed to break Ethereum's cryptography remains significant, but it is narrowing faster than many expected.** +Current quantum hardware is far from this scale, operating with a few thousand noisy physical qubits. Logical qubits (which correct for errors and perform reliable computation) require many physical qubits each. **The gap between current hardware and what is needed to break Ethereum's cryptography remains significant, but it is narrowing faster than many expected.** Notably, the U.S. National Institute of Standards and Technology (NIST) anticipates deprecating ECDSA by 2030 and disallowing it by 2035. -This is not an imminent threat. But cryptographic transitions take years, and Ethereum's security model is designed to last centuries. Preparing now is prudent. +This is not an imminent threat. But cryptographic transitions take years, and Ethereum's security model is designed to last centuries. Ethereum's response is the **Lean Ethereum** roadmap, a deliberate, multi-year mission to rebuild Ethereum around primitives that will survive any cryptographic threat. ## The four vulnerable areas {#four-vulnerable-areas} From ec2b7c1f2ece8c27f99ae8b4b040ad0b2972adae Mon Sep 17 00:00:00 2001 From: Jakub Konopka Date: Thu, 9 Apr 2026 16:22:33 +0200 Subject: [PATCH 013/127] content: apply second round of mnelsonBT review suggestions - Rename section to "Four areas vulnerable to quantum attack" - Add link to Vitalik's X post for PQ roadmap - Reframe approach as "Lean Consensus roadmap" - Expand leanXMSS/leanVM with size details (3000 vs 96 bytes, 250x) - Simplify ECDSA vulnerability wording - Rewrite STARK approach for clarity - Add link to NIST standards announcement - Link leanEthereum GitHub organization - Add NIST Alignment bullet to current activity - Rewrite target milestone language - Reference Hegota fork in user action section - Expand "Is Ethereum behind" FAQ - Add PSE, lean week, ACD breakout calls, YouTube playlists, Bankless podcast, Superpositioned to further reading - Simplify parent page further reading, add strawmap.org Co-Authored-By: Claude Opus 4.6 (1M context) --- .../content/roadmap/future-proofing/index.md | 3 +- .../quantum-resistance/index.md | 32 ++++++++++++------- 2 files changed, 21 insertions(+), 14 deletions(-) diff --git a/public/content/roadmap/future-proofing/index.md b/public/content/roadmap/future-proofing/index.md index 48a03926f22..623213a6544 100644 --- a/public/content/roadmap/future-proofing/index.md +++ b/public/content/roadmap/future-proofing/index.md @@ -89,8 +89,7 @@ No part of this work is finished. Timelines are targets, not guarantees. But the **Further reading** - [Post-quantum cryptography on Ethereum](/roadmap/future-proofing/quantum-resistance/) -- [Privacy Stewards of Ethereum: Post-Quantum Cryptography and Ethereum](https://pse.dev/projects/post-quantum-cryptography) -- [lean week: leanVM + PQ workshops, Cambridge 2025](https://github.com/leanEthereum/pm/blob/main/workshops-and-interops/2025/lean-week-cambridge/index.md) +- [strawmap.org](https://strawmap.org/) - _EF Architecture_ - [pq.ethereum.org](https://pq.ethereum.org) - [Gas](/developers/docs/gas/) - [EVM](/developers/docs/evm/) diff --git a/public/content/roadmap/future-proofing/quantum-resistance/index.md b/public/content/roadmap/future-proofing/quantum-resistance/index.md index 44ff5edb064..2b3c43d3e70 100644 --- a/public/content/roadmap/future-proofing/quantum-resistance/index.md +++ b/public/content/roadmap/future-proofing/quantum-resistance/index.md @@ -32,9 +32,9 @@ Current quantum hardware is far from this scale, operating with a few thousand n This is not an imminent threat. But cryptographic transitions take years, and Ethereum's security model is designed to last centuries. Ethereum's response is the **Lean Ethereum** roadmap, a deliberate, multi-year mission to rebuild Ethereum around primitives that will survive any cryptographic threat. -## The four vulnerable areas {#four-vulnerable-areas} +## Four areas vulnerable to quantum attack {#four-vulnerable-areas} -In February 2026, Vitalik Buterin published a roadmap identifying four distinct areas of Ethereum's cryptography that need post-quantum upgrades. Each has different challenges and different solution paths. +In February 2026, Vitalik Buterin [published a roadmap](https://x.com/VitalikButerin/status/2027075026378543132) identifying four distinct areas of Ethereum's cryptography that need post-quantum upgrades. Each has different challenges and different solution paths. ### 1. Consensus-layer BLS signatures {#consensus-bls} @@ -42,9 +42,9 @@ In February 2026, Vitalik Buterin published a roadmap identifying four distinct **Why it is vulnerable**: BLS signatures rely on elliptic curve pairings, which a quantum computer could break. -**The approach**: The Ethereum Foundation is developing two complementary tools: -- **leanXMSS**: A hash-based signature scheme for validators. Hash-based signatures are considered quantum-safe because they rely only on the security of hash functions, which quantum computers weaken but do not break. -- **leanVM**: A minimal zkVM (zero-knowledge virtual machine) for SNARK-based signature aggregation. This preserves the efficiency benefits of combining many signatures into one, even after switching to quantum-safe schemes. +**The approach**: The Lean Consensus roadmap includes developing two complementary tools: +- **leanXMSS**: Ethereum will replace BLS signatures with leanXMSS, a hash-based signature scheme for validators. Hash-based signatures are considered quantum-safe because they rely only on the security of hash functions, which quantum computers weaken but do not break. +- **leanVM**: A minimal zkVM (zero-knowledge virtual machine) for SNARK-based signature aggregation. Because hash-based signatures are significantly larger (roughly 3,000 bytes compared to 96 bytes for BLS), switching to leanXMSS would produce significantly more data per slot. To solve this, leanVM acts as an aggregation engine, compressing the data by 250x. This preserves the efficiency benefits of combining many signatures into one, even after switching to quantum-safe schemes. @@ -70,7 +70,7 @@ Both approaches are still being researched for efficiency and practicality at Et **What it does**: Every standard Ethereum account (externally owned account, or [EOA](/glossary/#eoa)) uses ECDSA on the secp256k1 curve to sign transactions. This is what protects your funds. -**Why it is vulnerable**: A quantum computer could derive a private key from a public key. For accounts that have sent at least one transaction, the public key is exposed onchain, making them a potential target. +**Why it is vulnerable**: For any account that has sent a transaction, the public key is exposed onchain. A quantum computer could derive the private key from this exposed public key data. **Important nuance**: Accounts that have only received ether and never sent a transaction have not exposed their public key. Only the address (a hash of the public key) is visible, which provides some additional protection. @@ -84,11 +84,11 @@ This is a pragmatic approach. Users and wallets that want post-quantum protectio **Why it is vulnerable**: Many popular ZK-proof systems (SNARKs using elliptic curve pairings) rely on quantum-vulnerable assumptions. -**The approach**: STARKs, which rely on hash functions rather than elliptic curves, are already quantum-resistant and are used by several rollups. The transition for this layer is partly happening already through natural ecosystem adoption of STARK-based systems. +**The approach**: STARKs, which rely on hash functions rather than elliptic curves, are already quantum-resistant and are used by several rollups. Natural ecosystem adoption of STARK-based systems is already providing post-quantum security at the application layer. ## NIST standards {#nist-standards} -In August 2024, the U.S. National Institute of Standards and Technology (NIST) finalized three post-quantum cryptography standards. These matter because they give the entire technology industry, including Ethereum, a shared set of vetted algorithms to build on rather than each project inventing its own. +In August 2024, the U.S. National Institute of Standards and Technology (NIST) [finalized three post-quantum cryptography standards](https://www.nist.gov/news-events/news/2024/08/nist-releases-first-3-finalized-post-quantum-encryption-standards). These matter because they give the entire technology industry, including Ethereum, a shared set of vetted algorithms to build on rather than each project inventing its own. | Standard | Name | Type | Use case | |----------|------|------|----------| @@ -106,8 +106,9 @@ The Ethereum Foundation formed a dedicated Post-Quantum Security team in January - **Weekly interop devnets**: More than 10 client teams participate in regular post-quantum interoperability testing, including Lighthouse, Grandine, Zeam, Ream Labs, and PierTwo. - **Poseidon Prize**: A $1 million research prize targeting improvements in hash-based cryptographic primitives. -- **Open-source implementations**: leanXMSS, leanVM, leanSpec (Python), leanSig (Rust), and leanMultisig are all available under the leanEthereum GitHub organization. +- **Open-source implementations**: leanXMSS, leanVM, leanSpec (Python), leanSig (Rust), and leanMultisig are all available under the [leanEthereum GitHub organization](https://github.com/leanEthereum). - **2nd Annual PQ Research Retreat**: Planned for 9-Oct-2026 to 12-Oct-2026 in Cambridge, UK. +- **NIST Alignment**: Ethereum's work builds upon the post-quantum cryptography standards finalized by NIST in August 2024 (such as ML-KEM, ML-DSA, and SLH-DSA). ### Migration milestones {#migration-milestones} @@ -120,13 +121,13 @@ The team has outlined a series of protocol upgrades to incrementally introduce p | L* | PQ attestations and real-time consensus-layer proofs via leanVM. Validators begin using PQ signatures for consensus. | | M* | Full PQ signature aggregation and PQ-safe blob commitments. | -**Target**: Core post-quantum infrastructure in place by approximately 2029. Full execution-layer and ecosystem migration extends beyond that. +**Target**: The structured fork milestones target the completion of core post-quantum infrastructure by approximately 2029. Full execution-layer and ecosystem migration extends beyond that. ## What do users need to do? {#what-users-need-to-do} **Right now: nothing.** Your funds are safe. No quantum computer today can threaten Ethereum's cryptography. -**In the future**: Once post-quantum signature schemes are available on Ethereum (expected to begin with EIP-8141), you will want to migrate your account to quantum-safe signatures. Wallet software will guide you through this transition. +**In the future**: Once post-quantum signature schemes are widely supported on Ethereum (expected following the Hegotá hard fork and implementation of EIP-8141), you will want to migrate your account to quantum-safe signatures. Wallet software will guide you through this transition. If your account has never sent a transaction (meaning your public key has not been exposed onchain), it has an additional layer of protection. But all accounts should eventually migrate. @@ -160,7 +161,7 @@ Assets on Ethereum are controlled by account signatures. Once your account is mi -Ethereum has one of the most structured post-quantum programs of any blockchain: a dedicated team, funded research, weekly devnets, and a published migration roadmap. No blockchain has completed a full post-quantum transition yet. According to Ethereum Foundation estimates, Ethereum's quantum-vulnerable dormant fund exposure is approximately 0.1%. +No. Ethereum has one of the most structured post-quantum programs of any blockchain: a dedicated team, funded research, weekly devnets, and a published migration roadmap, treating quantum computing as a first-class design constraint. No blockchain has completed a full post-quantum transition yet. According to Ethereum Foundation estimates, Ethereum's quantum-vulnerable dormant fund exposure is approximately 0.1%, drastically lower than other major blockchain networks. @@ -173,9 +174,16 @@ Ethereum has one of the most structured post-quantum programs of any blockchain: ## Further reading {#further-reading} - [pq.ethereum.org](https://pq.ethereum.org) - _Ethereum Foundation_ +- [Post-Quantum Cryptography Project](https://pse.dev/projects/post-quantum-cryptography) - _Privacy Stewards of Ethereum (PSE)_ - [NIST Post-Quantum Cryptography standards](https://csrc.nist.gov/projects/post-quantum-cryptography) - _NIST_ - [Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly](https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/) - _Google Quantum AI_ - [Quantum frontiers may be closer than they appear](https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/) - _Google_ - [KZG and trusted setups](/roadmap/danksharding/#what-is-kzg) +- [Lean Week Cambridge (2025) leanVM + PQ workshop resources](https://github.com/leanEthereum/pm/blob/main/workshops-and-interops/2025/lean-week-cambridge/index.md) - _Lean Ethereum_ +- [PQ Transaction Signatures ACD Breakout Calls](https://youtube.com/playlist?list=PLJqWcTqh_zKEOum3uR0odkH59fmGUYuZB) - _Ethereum Foundation_ +- [PQ Interop ACD Breakout Calls](https://youtube.com/playlist?list=PLJqWcTqh_zKF_Q9HNXBLW_AtktsjToTIu) - _Ethereum Foundation_ +- [Lean Ethereum & Post-Quantum Security YouTube Playlist](https://youtube.com/playlist?list=PLJqWcTqh_zKGGuO_q1dgYLsfUoX1sNhWM) - _Ethereum Foundation_ +- [Panel interview post-quantum resistance](https://youtu.be/5DRDjeMmOPw) - _Bankless Podcast_ - [Account abstraction on Ethereum](/roadmap/account-abstraction/) - [strawmap.org](https://strawmap.org/) - _EF Architecture_ +- [Superpositioned: Analysis of the Quantum Computing Industry](https://www.superpositioned.co/) - _Saneel Sreeni_ From d61e4e6ed0d9cac2b7105ee52d46173b7595e465 Mon Sep 17 00:00:00 2001 From: Pablo Pettinari Date: Fri, 10 Apr 2026 13:52:04 +0200 Subject: [PATCH 014/127] refactor: migrate Tailwind CSS v3 to v4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Replace JS config (tailwind.config.ts) with CSS-first config (@config in global.css) - Migrate postcss.config.js to postcss.config.mjs with @tailwindcss/postcss - Reorganize CSS into focused files: base.css, theme.css, utilities.css, semantic-tokens.css - Migrate renamed/removed utilities: rounded, shadow, outline, ring, opacity classes - Convert space-y patterns to gap where needed, resolve negative margin conflicts - Fix variant selectors: not-[:first] → not-[:first-child], last variant on alert - Move custom utilities (staking-grid, area-glyph) to @utility for variant support - Use @theme inline for nested .dark containers to resolve semantic tokens correctly - Import docsearch CSS into cascade layer to restore library styles - Add json loader for .all-contributorsrc in storybook webpack config - Fix leading-base setting --tw-leading on code elements - Remove first heading top margin in content pages for v4 compat - Update 100+ components with renamed utility classes --- .storybook/main.ts | 6 + .storybook/preview.tsx | 3 - AGENTS.md | 2 +- .../10years/_components/NFTMintCard/index.tsx | 6 +- .../10years/_components/TenYearHero.tsx | 6 +- .../10years/_components/TorchHistoryCard.tsx | 7 +- app/[locale]/10years/_components/data.tsx | 12 +- app/[locale]/10years/page.tsx | 32 +- .../_components/HomepageLazyImports.tsx | 2 +- app/[locale]/apps/[application]/page.tsx | 30 +- .../apps/_components/CommunityPicks.tsx | 2 +- .../apps/categories/[catetgoryName]/page.tsx | 4 +- app/[locale]/bug-bounty/page.tsx | 50 +- .../_components/CollectiblesContent/index.tsx | 2 +- app/[locale]/collectibles/page.tsx | 8 +- .../community/_components/community.tsx | 22 +- .../events/_components/EventCard.tsx | 20 +- .../events/_components/OrganizerCTA.tsx | 2 +- app/[locale]/community/events/page.tsx | 10 +- app/[locale]/community/events/search/page.tsx | 2 +- app/[locale]/community/support/page.tsx | 24 +- .../leaderboard/_components/Leaderboard.tsx | 6 +- .../developers/_components/BuilderCard.tsx | 4 +- .../_components/BuilderSwiper/loading.tsx | 10 +- .../developers/_components/SpeedRunCard.tsx | 4 +- .../_components/VideoCourseCard.tsx | 6 +- app/[locale]/developers/page.tsx | 44 +- .../developers/tools/[category]/page.tsx | 2 +- .../tools/_components/ToolModalContents.tsx | 6 +- app/[locale]/developers/tools/page.tsx | 6 +- .../tutorials/_components/modal.tsx | 4 +- app/[locale]/founders/page.tsx | 6 +- app/[locale]/gas/_components/gas.tsx | 16 +- app/[locale]/get-eth/page.tsx | 16 +- app/[locale]/layer-2/_components/layer-2.tsx | 48 +- .../layer-2/learn/_components/learn.tsx | 12 +- app/[locale]/layout.tsx | 1 + app/[locale]/learn/page.tsx | 6 +- app/[locale]/page.tsx | 34 +- app/[locale]/resources/page.tsx | 10 +- .../roadmap/_components/ReleaseCarousel.tsx | 14 +- app/[locale]/roadmap/_components/roadmap.tsx | 4 +- .../roadmap/_vision/_components/vision.tsx | 6 +- .../run-a-node/_components/run-a-node.tsx | 28 +- app/[locale]/stablecoins/page.tsx | 58 +- .../_components/deposit-contract.tsx | 28 +- app/[locale]/start/page.tsx | 2 +- .../trillion-dollar-security/page.tsx | 52 +- app/[locale]/wallets/find-wallet/page.tsx | 4 +- app/[locale]/wallets/page.tsx | 60 +- app/[locale]/what-is-ether/page.tsx | 2 +- app/[locale]/what-is-ethereum/page.tsx | 40 +- app/layout.tsx | 1 + next.config.js | 6 + overrides.d.ts | 12 +- package.json | 12 +- pnpm-lock.yaml | 729 +++++++++--------- postcss.config.js | 6 - postcss.config.mjs | 5 + src/components/ActionCard.tsx | 8 +- .../Banners/EventsOrganizerBanner.tsx | 6 +- .../Banners/UpgradeBannerNotification.tsx | 2 +- src/components/BoxGrid.tsx | 10 +- src/components/CalloutBanner.tsx | 10 +- src/components/CalloutBannerSSR.tsx | 10 +- src/components/CalloutSSR.tsx | 4 +- src/components/Card/index.tsx | 2 +- src/components/Codeblock.tsx | 4 +- .../Content/ai-agents/BuildYourOwnAIAgent.tsx | 8 +- src/components/Contributors/index.tsx | 8 +- src/components/DeveloperDocsLinks/index.tsx | 11 +- src/components/DocLink/index.tsx | 10 +- src/components/DocsNav/index.tsx | 14 +- src/components/EthPriceCard.tsx | 14 +- src/components/ExpandableCard.tsx | 12 +- .../WalletSubComponent.tsx | 8 +- src/components/GhostCard.tsx | 4 +- src/components/Hero/HomeHero/index.tsx | 4 +- src/components/Hero/HomeHero2026/index.tsx | 4 +- src/components/Homepage/BentoCard.tsx | 4 +- src/components/Homepage/FeatureCards.tsx | 26 +- src/components/Homepage/FloatingCard.tsx | 4 +- src/components/Homepage/utils.ts | 24 +- src/components/HorizontalCard.tsx | 2 +- src/components/Layer2ProductCard.tsx | 10 +- src/components/MdComponents/index.tsx | 15 +- src/components/ProductList.tsx | 8 +- .../Quiz/QuizWidget/QuizRadioGroup.tsx | 8 +- src/components/Simulator/index.tsx | 4 +- src/components/SkipLink.tsx | 2 +- .../AccordionCustomItem.tsx | 14 +- src/components/StablecoinAccordion/index.tsx | 6 +- src/components/Staking/StakingComparison.tsx | 8 +- src/components/Staking/StakingHierarchy.tsx | 14 +- .../Staking/StakingLaunchpadWidget.tsx | 4 +- .../Staking/WithdrawalsTabComparison.tsx | 6 +- .../LetUseSomeApps/index.tsx | 6 +- .../StartWithEthereumFlow/index.tsx | 10 +- src/components/Tooltip/index.tsx | 2 +- .../Translatathon/PaperformModal.tsx | 2 +- .../Translatathon/TranslatathonCalendar.tsx | 4 +- .../TranslatathonInANutshell.tsx | 2 +- src/components/TranslationBannerLegal.tsx | 6 +- src/components/TranslationLeaderboard.tsx | 8 +- src/components/Trilemma/Trilemma.stories.tsx | 2 +- src/components/Trilemma/index.tsx | 10 +- src/components/UpgradeStatus.tsx | 4 +- src/components/WhitepaperBridge/index.tsx | 14 +- src/components/WindowBox/index.tsx | 4 +- src/components/ui/TabNav.tsx | 10 +- src/components/ui/alert.tsx | 6 +- src/components/ui/buttons/Button.tsx | 4 +- src/components/ui/card.tsx | 10 +- src/components/ui/chart.tsx | 4 +- src/components/ui/checkbox.tsx | 2 +- src/components/ui/command.tsx | 20 +- src/components/ui/dialog-modal.tsx | 2 +- src/components/ui/dialog.tsx | 8 +- src/components/ui/dropdown-menu.tsx | 12 +- src/components/ui/popover.tsx | 2 +- src/components/ui/section.tsx | 4 +- src/components/ui/select.tsx | 14 +- src/components/ui/tabs.tsx | 10 +- src/data/community-hubs.ts | 14 +- src/layouts/Tutorial.tsx | 10 +- src/lib/utils/screen.ts | 4 +- src/styles/base.css | 118 +++ src/styles/colors.css | 2 - src/styles/colors.stories.tsx | 2 +- src/styles/docsearch.css | 100 ++- src/styles/global.css | 257 +----- src/styles/semantic-tokens.css | 75 +- src/styles/theme.css | 326 ++++++++ src/styles/utilities.css | 143 ++++ tailwind.config.ts | 369 --------- 135 files changed, 1805 insertions(+), 1671 deletions(-) delete mode 100644 postcss.config.js create mode 100644 postcss.config.mjs create mode 100644 src/styles/base.css create mode 100644 src/styles/theme.css create mode 100644 src/styles/utilities.css delete mode 100644 tailwind.config.ts diff --git a/.storybook/main.ts b/.storybook/main.ts index adb6f8a805d..44c5cbf9ccf 100644 --- a/.storybook/main.ts +++ b/.storybook/main.ts @@ -68,6 +68,12 @@ const config: StorybookConfig = { use: ["@svgr/webpack"], }) + // .all-contributorsrc is JSON without a .json extension + config.module.rules.push({ + test: /\.all-contributorsrc$/, + type: "json", + }) + return config }, diff --git a/.storybook/preview.tsx b/.storybook/preview.tsx index ee8ad2d1f6e..b2b64b42f9e 100644 --- a/.storybook/preview.tsx +++ b/.storybook/preview.tsx @@ -10,9 +10,6 @@ import nextIntl, { baseLocales } from "./next-intl" import { withNextThemes } from "./withNextThemes" import "../src/styles/global.css" -import "../src/styles/docsearch.css" - -import "@docsearch/css" const inter = Inter({ subsets: ["latin"], diff --git a/AGENTS.md b/AGENTS.md index 099cb1eedb6..19a92c3f551 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -11,7 +11,7 @@ This is the official Ethereum.org website - a Next.js application that serves as - **Next.js 14.2+** - React framework with App Router - **React 18** - UI library - **TypeScript 5.5+** - Type safety and development experience -- **Tailwind CSS 3.4+** - Utility-first CSS framework +- **Tailwind CSS 4+** - Utility-first CSS framework (CSS-first config in `src/styles/global.css`) ### Key Dependencies diff --git a/app/[locale]/10years/_components/NFTMintCard/index.tsx b/app/[locale]/10years/_components/NFTMintCard/index.tsx index 835bf9d439c..5296b99c774 100644 --- a/app/[locale]/10years/_components/NFTMintCard/index.tsx +++ b/app/[locale]/10years/_components/NFTMintCard/index.tsx @@ -20,7 +20,7 @@ const NFTMintCard = ({ className }: NFTMintCardProps) => { return ( @@ -30,7 +30,7 @@ const NFTMintCard = ({ className }: NFTMintCardProps) => {
@@ -46,12 +46,12 @@ const TenYearHero = async () => { {t("page-10-year-celebrating")}{" "} {WORDS[0]} - + {/* CLIENT SIDE, lazy loaded */} diff --git a/app/[locale]/10years/_components/TorchHistoryCard.tsx b/app/[locale]/10years/_components/TorchHistoryCard.tsx index 50514ee69d6..f5d7d38ba41 100644 --- a/app/[locale]/10years/_components/TorchHistoryCard.tsx +++ b/app/[locale]/10years/_components/TorchHistoryCard.tsx @@ -41,10 +41,9 @@ const TorchHistoryCard: React.FC = ({ return ( diff --git a/app/[locale]/10years/_components/data.tsx b/app/[locale]/10years/_components/data.tsx index 84785db7fc6..50b748491ac 100644 --- a/app/[locale]/10years/_components/data.tsx +++ b/app/[locale]/10years/_components/data.tsx @@ -1,11 +1,11 @@ // duplicate 1 2 3, 1 2 3 to fix mobile slider bug where styles are not applied const adoptionStyles = [ - "bg-background bg-gradient-to-b from-20% to-60% from-accent-c/10 to-accent-c/5 dark:from-accent-c/20 dark:to-accent-c/10 border-accent-c/10", - "bg-background bg-gradient-to-b from-20% to-60% from-accent-b/10 to-accent-b/5 dark:from-accent-b/20 dark:to-accent-b/10 border-accent-b/10", - "bg-background bg-gradient-to-b from-20% to-60% from-accent-a/10 to-accent-a/5 dark:from-accent-a/20 dark:to-accent-a/10 border-accent-a/10", - "bg-background bg-gradient-to-b from-20% to-60% from-accent-c/10 to-accent-c/5 dark:from-accent-c/20 dark:to-accent-c/10 border-accent-c/10", - "bg-background bg-gradient-to-b from-20% to-60% from-accent-b/10 to-accent-b/5 dark:from-accent-b/20 dark:to-accent-b/10 border-accent-b/10", - "bg-background bg-gradient-to-b from-20% to-60% from-accent-a/10 to-accent-a/5 dark:from-accent-a/20 dark:to-accent-a/10 border-accent-a/10", + "bg-background bg-linear-to-b from-20% to-60% from-accent-c/10 to-accent-c/5 dark:from-accent-c/20 dark:to-accent-c/10 border-accent-c/10", + "bg-background bg-linear-to-b from-20% to-60% from-accent-b/10 to-accent-b/5 dark:from-accent-b/20 dark:to-accent-b/10 border-accent-b/10", + "bg-background bg-linear-to-b from-20% to-60% from-accent-a/10 to-accent-a/5 dark:from-accent-a/20 dark:to-accent-a/10 border-accent-a/10", + "bg-background bg-linear-to-b from-20% to-60% from-accent-c/10 to-accent-c/5 dark:from-accent-c/20 dark:to-accent-c/10 border-accent-c/10", + "bg-background bg-linear-to-b from-20% to-60% from-accent-b/10 to-accent-b/5 dark:from-accent-b/20 dark:to-accent-b/10 border-accent-b/10", + "bg-background bg-linear-to-b from-20% to-60% from-accent-a/10 to-accent-a/5 dark:from-accent-a/20 dark:to-accent-a/10 border-accent-a/10", ] export { adoptionStyles } diff --git a/app/[locale]/10years/page.tsx b/app/[locale]/10years/page.tsx index 8dcf52628a7..ed612029c66 100644 --- a/app/[locale]/10years/page.tsx +++ b/app/[locale]/10years/page.tsx @@ -96,7 +96,7 @@ const Page = async (props: { params: Promise }) => {
-
+

{t("page-10-year-livestream-title")} @@ -117,12 +117,12 @@ const Page = async (props: { params: Promise }) => { defaultValue={Object.keys(tenYearEventRegions)[0]} className="w-full" > - + {Object.entries(tenYearEventRegions).map(([key, data]) => ( {data.label}  ({data.events.length}) @@ -157,8 +157,8 @@ const Page = async (props: { params: Promise }) => { key={country} className={cn("flex flex-col border-b px-4 py-6")} > -

- +

+ }) => { {countryEvents.map((event, index) => (
@@ -206,7 +206,7 @@ const Page = async (props: { params: Promise }) => {
@@ -224,13 +224,13 @@ const Page = async (props: { params: Promise }) => { disablePictureInPicture playsInline /> -
+
{/* Curved text */} @@ -239,7 +239,7 @@ const Page = async (props: { params: Promise }) => { -
+

}) => {

- + {t("page-10-year-innovation-title")} - + {t("page-10-year-innovation-subtitle")}

@@ -292,10 +292,10 @@ const Page = async (props: { params: Promise }) => {

- + {t("page-10-year-adoption-title")} - + {t("page-10-year-adoption-subtitle")}

@@ -348,10 +348,10 @@ const Page = async (props: { params: Promise }) => {

- + {t("page-10-year-stories-title")} - + {t("page-10-year-stories-subtitle")}

diff --git a/app/[locale]/_components/HomepageLazyImports.tsx b/app/[locale]/_components/HomepageLazyImports.tsx index b0fbb4920c7..01942509c1f 100644 --- a/app/[locale]/_components/HomepageLazyImports.tsx +++ b/app/[locale]/_components/HomepageLazyImports.tsx @@ -11,7 +11,7 @@ export const BentoCardSwiper = dynamic( ssr: false, loading: () => (
- +
), diff --git a/app/[locale]/apps/[application]/page.tsx b/app/[locale]/apps/[application]/page.tsx index dbdb19a37b5..b7c18e67a64 100644 --- a/app/[locale]/apps/[application]/page.tsx +++ b/app/[locale]/apps/[application]/page.tsx @@ -148,13 +148,13 @@ const Page = async (props: { Ethereum.org - + / ALL APPS - + / @@ -187,13 +187,13 @@ const Page = async (props: { chains={app.networks as ChainName[]} className="mt-2" /> -

+

by {app.parentCompany}

-

+

{formatStringList( formatLanguageNames(app.languages), 5 @@ -273,7 +273,7 @@ const Page = async (props: { )}

{nextApp && ( - +

{t("page-apps-see-next")} @@ -291,7 +291,7 @@ const Page = async (props: { />

- +
)} @@ -300,9 +300,9 @@ const Page = async (props: {
{nextApp && ( - +
-

+

{t("page-apps-see-next")}

@@ -318,14 +318,14 @@ const Page = async (props: { />

- +
)}
-
+

{getLocalizedDescription( appDescriptions, @@ -334,22 +334,22 @@ const Page = async (props: { app.description )}

-
+

{t("page-apps-info-title")}

-

+

{t("page-apps-info-founded")}

{getDisplayYear(app.dateOfLaunch)}

-

+

{t("page-apps-info-creator")}

{app.parentCompany}

-

+

{t("page-apps-info-last-updated")}

{getTimeAgo(app.lastUpdated)}

@@ -368,7 +368,7 @@ const Page = async (props: { {relatedApps.length > 0 && (
-
+

{t("page-apps-more-apps-like-this")}

{relatedApps.map((relatedApp) => ( diff --git a/app/[locale]/apps/_components/CommunityPicks.tsx b/app/[locale]/apps/_components/CommunityPicks.tsx index 3d3affe50d6..ca254975189 100644 --- a/app/[locale]/apps/_components/CommunityPicks.tsx +++ b/app/[locale]/apps/_components/CommunityPicks.tsx @@ -30,7 +30,7 @@ const CommunityPicks = ({ const cards = communityPicks.map((pick) => (
-
+
{`${pick.name} Ethereum.org - + / @@ -157,7 +157,7 @@ const Page = async (props: { {t("page-apps-all-apps")} - + / diff --git a/app/[locale]/bug-bounty/page.tsx b/app/[locale]/bug-bounty/page.tsx index 1ecbef7ad02..237d9c4c18d 100644 --- a/app/[locale]/bug-bounty/page.tsx +++ b/app/[locale]/bug-bounty/page.tsx @@ -51,11 +51,11 @@ const Content = (props: ChildOnlyProp) => ( ) const H2 = ({ className, ...props }: ComponentProps<"h2">) => ( -

+

) const H4 = (props: ChildOnlyProp) => ( -

+

) const Text = ({ className, ...props }: ComponentProps<"p">) => ( @@ -71,7 +71,7 @@ const ClientRow = (props: ChildOnlyProp) => ( ) const Client = (props: ChildOnlyProp) => ( -
+
) const Row = (props: ChildOnlyProp) => ( @@ -256,16 +256,16 @@ export default async function Page(props: { params: Promise }) { {/* */} -
+
-
{" "} - +
{" "} + {t("page-upgrades-bug-bounty-title")}
}) {

- + {t("page-upgrades-bug-bounty-subtitle")} @@ -288,7 +288,7 @@ export default async function Page(props: { params: Promise }) {
- + {t("page-upgrades-bug-bounty-leaderboard")} @@ -380,7 +380,7 @@ export default async function Page(props: { params: Promise }) { /> -
+

{t("page-upgrades-bug-bounty-validity")}

@@ -394,7 +394,7 @@ export default async function Page(props: { params: Promise }) { })}
- + }) { {/* Out of Scope */}

{t("page-upgrades-bug-bounty-not-included")}

-

+

{t.rich("page-upgrades-bug-bounty-not-included-desc", { a: (chunks) => {chunks}, })} @@ -564,7 +564,7 @@ export default async function Page(props: { params: Promise }) { ] as const ).map(({ key, footnote }) => (

  • - ✕ + ✕ {t(key)} {footnote && *} @@ -572,16 +572,16 @@ export default async function Page(props: { params: Promise }) {
    • ))} -

    +

    * {t("page-upgrades-bug-bounty-out-of-scope-footnote")}

    {/* Bug Hunting Rules */} -
    +

    {t("page-upgrades-bug-bounty-hunting")}

    - + {t("page-upgrades-bug-bounty-hunting-desc")}
      @@ -595,9 +595,9 @@ export default async function Page(props: { params: Promise }) { ).map((key, idx) => (
    1. - + {idx + 1} {t(key)} @@ -612,12 +612,12 @@ export default async function Page(props: { params: Promise }) {

      {t("page-upgrades-bug-bounty-severity-qualifications-title")}

      -

      +

      {t("page-upgrades-bug-bounty-severity-qualifications-desc")}

      {/* Low */} -
      +
      {t("page-upgrades-bug-bounty-severity-low-title")} @@ -640,7 +640,7 @@ export default async function Page(props: { params: Promise }) {
      {/* Medium */} -
      +
      {t("page-upgrades-bug-bounty-severity-medium-title")} @@ -663,7 +663,7 @@ export default async function Page(props: { params: Promise }) {
      {/* High */} -
      +
      {t("page-upgrades-bug-bounty-severity-high-title")} @@ -686,7 +686,7 @@ export default async function Page(props: { params: Promise }) {
      {/* Critical */} -
      +
      {t("page-upgrades-bug-bounty-severity-critical-title")} @@ -737,7 +737,7 @@ export default async function Page(props: { params: Promise }) {
      diff --git a/app/[locale]/collectibles/_components/CollectiblesContent/index.tsx b/app/[locale]/collectibles/_components/CollectiblesContent/index.tsx index 6cf2fea3595..5c6d6f10469 100644 --- a/app/[locale]/collectibles/_components/CollectiblesContent/index.tsx +++ b/app/[locale]/collectibles/_components/CollectiblesContent/index.tsx @@ -83,7 +83,7 @@ const CollectiblesContent = ({ badges }: CollectiblesPageProps) => { return (
      {/* Already a contributor? section */} -
      +
      {t("page-collectibles-contributor-img-alt")} }) { id="stats" className="flex flex-col gap-x-6 gap-y-4 px-4 xl:flex-row xl:px-12" > -
      +

      {t("page-collectibles-improve-title")}

      @@ -110,7 +110,7 @@ export default async function Page(props: { params: Promise }) {
      {/* Minted */} -
      +
      {stats.collectorsCount ? numberFormat(locale).format(stats.collectorsCount) @@ -121,7 +121,7 @@ export default async function Page(props: { params: Promise }) {
      {/* Collectors */} -
      +
      {stats.uniqueAddressesCount ? numberFormat(locale).format(stats.uniqueAddressesCount) @@ -132,7 +132,7 @@ export default async function Page(props: { params: Promise }) {
      {/* Unique Badges */} -
      +
      {stats.collectiblesCount ? numberFormat(locale).format(stats.collectiblesCount) diff --git a/app/[locale]/community/_components/community.tsx b/app/[locale]/community/_components/community.tsx index 68ce6d2c402..f9a6fda8220 100644 --- a/app/[locale]/community/_components/community.tsx +++ b/app/[locale]/community/_components/community.tsx @@ -75,7 +75,7 @@ const ImageContainer = ({ children }: ChildOnlyProp) => { } const Subtitle = ({ children }: ChildOnlyProp) => { - return

      {children}

      + return

      {children}

      } const FeatureContent = ({ children }: ChildOnlyProp) => { @@ -92,7 +92,7 @@ const H2 = ({ ...props }: BaseHTMLAttributes) => { return ( -

      +

      {children}

      ) @@ -161,7 +161,7 @@ const CommunityPage = () => { - +

      @@ -171,7 +171,7 @@ const CommunityPage = () => { {whyGetInvolvedCards.map((card, idx) => ( {

      -
      +
      - +

      {t("page-community-get-involved-title")} @@ -203,7 +203,7 @@ const CommunityPage = () => {
      {cards.map((card, idx) => ( {

      - +

      {t("page-community-open-source")}

      @@ -243,7 +243,7 @@ const CommunityPage = () => {       - + @@ -272,7 +272,7 @@ const CommunityPage = () => { - +

      {t("page-community-support")}

      @@ -295,7 +295,7 @@ const CommunityPage = () => {
      -

      +

      {t("page-community-try-ethereum")}

      diff --git a/app/[locale]/community/events/_components/EventCard.tsx b/app/[locale]/community/events/_components/EventCard.tsx index e0d945b0f7a..c9163d471ed 100644 --- a/app/[locale]/community/events/_components/EventCard.tsx +++ b/app/[locale]/community/events/_components/EventCard.tsx @@ -36,7 +36,7 @@ function EventCardGrid({ : null return ( - +
      -
      +
      {event.logoImage ? ( ) : ( - + )}
      @@ -68,11 +68,11 @@ function EventCardGrid({ {event.eventTypesLabels?.[0] || primaryType} )} -

      +

      {event.title}

      {formattedDate &&

      {formattedDate}

      } -

      {event.location}

      +

      {event.location}

      @@ -86,14 +86,14 @@ function EventCardHighlight({ customEventOptions, }: EventCardProps) { return ( - + -
      +
      {`${event.title}

      {event.title}

      -

      {event.location}

      -

      +

      {event.location}

      +

      {formatDateRange(event.startTime, event.endTime, locale)}

      diff --git a/app/[locale]/community/events/_components/OrganizerCTA.tsx b/app/[locale]/community/events/_components/OrganizerCTA.tsx index bd0c0fb9a0f..8cd1a18c26a 100644 --- a/app/[locale]/community/events/_components/OrganizerCTA.tsx +++ b/app/[locale]/community/events/_components/OrganizerCTA.tsx @@ -15,7 +15,7 @@ export default async function OrganizerCTA({ className }: OrganizerCTAProps) { return (
      }) => { -
      +
      {t("page-events-hub-apply-cta")} @@ -277,7 +277,7 @@ const Page = async (props: { params: Promise }) => { {/* Find events near you */}

    } - svg={} + svg={} className="h-fit" >
    -

    +

    {t("page-community-support-protect-yourself-description")}

    }) { {/* Card 3: Using Ethereum */} {t("page-community-support-using-ethereum")}

    } - svg={} + svg={} className="h-fit" >
    -

    +

    {t("page-community-support-using-ethereum-description")}

    }) { title={

    {t("page-community-support-common-misconceptions")}

    } - svg={} + svg={} className="h-fit" >
    -

    +

    {t( "page-community-support-common-misconceptions-description" )} @@ -375,13 +375,13 @@ export default async function Page(props: { params: Promise }) { {/* Still need help? */}

    {t("page-community-support-still-need-help")}

    -

    +

    {t("page-community-support-still-need-help-description")}

    { } return ( -
    +
    #
    @@ -83,7 +83,7 @@ export const Leaderboard = () => { return (
    @@ -112,7 +112,7 @@ export const Leaderboard = () => { onClick={showMore} className="m-2 mx-0 flex h-full w-full items-center justify-center rounded-full px-6 py-4 lg:mx-2 lg:w-auto" > - + Show more diff --git a/app/[locale]/developers/_components/BuilderCard.tsx b/app/[locale]/developers/_components/BuilderCard.tsx index 40bb6b87616..5573c135b65 100644 --- a/app/[locale]/developers/_components/BuilderCard.tsx +++ b/app/[locale]/developers/_components/BuilderCard.tsx @@ -25,13 +25,13 @@ const BuilderCard = ({ path, className }: BuildCardProps) => ( {path.tag} )}

    {path.title}

    -

    {path.description}

    +

    {path.description}

    ( - + - - + + ) diff --git a/app/[locale]/developers/_components/SpeedRunCard.tsx b/app/[locale]/developers/_components/SpeedRunCard.tsx index 9218419cadb..2e72fdd4a67 100644 --- a/app/[locale]/developers/_components/SpeedRunCard.tsx +++ b/app/[locale]/developers/_components/SpeedRunCard.tsx @@ -27,12 +27,12 @@ const SpeedRunCard = ({ alt="SpeedRunEthereum banner" sizes="(max-width: 768px) 100vw, 50vw" /> -
    +

    {title}

    {description}

    ( {course.hours} -

    +

    {course.title}

    -

    {course.description}

    +

    {course.description}

    ) diff --git a/app/[locale]/developers/page.tsx b/app/[locale]/developers/page.tsx index e0174d0f026..d3ae8ca746c 100644 --- a/app/[locale]/developers/page.tsx +++ b/app/[locale]/developers/page.tsx @@ -50,15 +50,15 @@ import tutorialTagsBanner from "@/public/images/developers/tutorial-tags-banner. import dogeImage from "@/public/images/doge-computer.png" import EventFallback from "@/public/images/events/event-placeholder.png" import heroImage from "@/public/images/heroes/developers-hub-hero.png" -const H3 = (props: ChildOnlyProp) =>

    +const H3 = (props: ChildOnlyProp) =>

    const Text = (props: ChildOnlyProp) =>

    const Column = (props: ChildOnlyProp) => ( -

    +
    ) const RightColumn = (props: ChildOnlyProp) => ( -
    +
    ) const Scroller = ({ @@ -103,9 +103,9 @@ const WhyGrid = () => { return (
    {items.map(({ heading, description }) => ( @@ -186,7 +186,7 @@ const DevelopersPage = async (props: { params: Promise }) => { id="why" className={cn( "grid grid-cols-1 gap-6 md:gap-10 lg:grid-cols-2", - "-mx-8 w-screen max-w-screen-2xl items-center bg-background-highlight px-8 py-10 md:py-20" + "bg-background-highlight -mx-8 w-screen max-w-screen-2xl items-center px-8 py-10 md:py-20" )} >
    @@ -261,7 +261,7 @@ const DevelopersPage = async (props: { params: Promise }) => { id="resources" className={cn( "grid grid-cols-1 gap-6 md:grid-cols-2 md:gap-8", - "-mx-8 w-screen max-w-screen-2xl bg-background-highlight px-8 py-10 md:py-20" + "bg-background-highlight -mx-8 w-screen max-w-screen-2xl px-8 py-10 md:py-20" )} >

    @@ -269,7 +269,7 @@ const DevelopersPage = async (props: { params: Promise }) => {

    {/* Quickstart your idea */} - + Scaffold-ETH 2 debug screenshot }) => { />

    {t("page-developers-jump-right-in-title")}

    -

    +

    {t("page-developers-quickstart-scaffold-subtext")}{" "} }) => {

    -
    +
    npx create-eth@latest @@ -324,7 +324,7 @@ const DevelopersPage = async (props: { params: Promise }) => { {/* Get help */} - + Ethereum Stack Exchange screenshot }) => { />

    {t("page-developers-get-help-title")}

    -

    +

    {t("page-developers-get-help-desc")}

    @@ -362,7 +362,7 @@ const DevelopersPage = async (props: { params: Promise }) => {     {/* Resources */} - + Banner showing four resource app icons }) => { />

    {t("page-developers-resources-title")}

    -

    +

    {t("page-developers-resources-desc")}

    @@ -393,7 +393,7 @@ const DevelopersPage = async (props: { params: Promise }) => {     {/* Tutorials */} - + Banner displaying multiple learning topics in a tag cloud }) => { />

    {t("page-developers-tutorials-title")}

    -

    +

    {t("page-developers-tutorials-desc")}

    @@ -449,7 +449,7 @@ const DevelopersPage = async (props: { params: Promise }) => { id="docs" className={cn( "shadow-table-item-box", - "-mx-8 w-screen max-w-screen-2xl bg-background-highlight px-8 py-10 md:py-20" + "bg-background-highlight -mx-8 w-screen max-w-screen-2xl px-8 py-10 md:py-20" )} >
    @@ -598,7 +598,7 @@ const DevelopersPage = async (props: { params: Promise }) => { eventAction: "click", eventName: title, }} - className="min-w-72 max-w-md flex-1" + className="max-w-md min-w-72 flex-1" > {bannerImage ? ( @@ -642,12 +642,12 @@ const DevelopersPage = async (props: { params: Promise }) => {
    -
    +

    {t("page-developers-founders-title")}

    {t("page-developers-founders-desc")}

    diff --git a/app/[locale]/developers/tools/[category]/page.tsx b/app/[locale]/developers/tools/[category]/page.tsx index 6b662021e7b..4894fd5e2bb 100644 --- a/app/[locale]/developers/tools/[category]/page.tsx +++ b/app/[locale]/developers/tools/[category]/page.tsx @@ -117,7 +117,7 @@ const Page = async (props: {

    {t("page-developers-tools-categories-title-other")}

    -
    +
    {DEV_TOOL_CATEGORIES.filter(({ slug }) => slug !== category).map( ({ slug, Icon }) => ( { return (
    -
    +
    {tool.banner_url && ( { className="lowercase" />
    -
    +
    {await renderSimpleMarkdown(translatedDescription, mdComponentOverrides)}
    -
    +

    {t("page-developers-tools-modal-links")}

    {tool.website && ( diff --git a/app/[locale]/developers/tools/page.tsx b/app/[locale]/developers/tools/page.tsx index 42eadb8e37f..87a50e3add4 100644 --- a/app/[locale]/developers/tools/page.tsx +++ b/app/[locale]/developers/tools/page.tsx @@ -95,7 +95,7 @@ const Page = async (props: { className="ms-6 w-[calc(100%-4rem)] max-w-md md:min-w-96 md:flex-1 lg:max-w-[33%]" > - +
    -

    +

    {t(`page-developers-tools-category-${slug}-title`)}