diff --git a/app/[locale]/contributing/translation-program/translatathon/leaderboard/_components/Leaderboard.tsx b/app/[locale]/contributing/translation-program/translatathon/leaderboard/_components/Leaderboard.tsx
index eabb1dcf17b..21cf5f2188a 100644
--- a/app/[locale]/contributing/translation-program/translatathon/leaderboard/_components/Leaderboard.tsx
+++ b/app/[locale]/contributing/translation-program/translatathon/leaderboard/_components/Leaderboard.tsx
@@ -3,20 +3,13 @@
import { useState } from "react"
import Emoji from "@/components/Emoji"
-import { Image } from "@/components/Image"
import { Button } from "@/components/ui/buttons/Button"
import { cn } from "@/lib/utils/cn"
-const AvatarWithFallback = ({
- username,
- avatarUrl,
-}: {
- username: string
- avatarUrl: string
-}) => {
- const [imageError, setImageError] = useState(false)
+import { translators } from "./leaderboard-data"
+const AvatarWithFallback = ({ username }: { username: string }) => {
// Generate consistent avatar colors using design system colors
const avatarColors = [
"bg-primary",
@@ -42,33 +35,19 @@ const AvatarWithFallback = ({
const avatarColorClass = avatarColors[Math.abs(hash) % avatarColors.length]
const initials = username.slice(0, 1).toUpperCase()
- if (imageError || !avatarUrl) {
- return (
-
- {initials}
-
- )
- }
-
return (
-
-
setImageError(true)}
- />
+
+ {initials}
)
}
-export const Leaderboard = ({ translators }) => {
+export const Leaderboard = () => {
const [filterAmount, updateFilterAmount] = useState(10)
const showMore = () => {
@@ -91,14 +70,7 @@ export const Leaderboard = ({ translators }) => {
-
-
{username}
+
+
{name}
- No data available
-
- )}
+
{isDateReached(APPLICATION_END_DATE) && (
diff --git a/app/[locale]/what-is-the-ethereum-network/page.tsx b/app/[locale]/what-is-the-ethereum-network/page.tsx
index 06816125fcc..767c3dd1864 100644
--- a/app/[locale]/what-is-the-ethereum-network/page.tsx
+++ b/app/[locale]/what-is-the-ethereum-network/page.tsx
@@ -37,7 +37,7 @@ const Page = async ({ params }: { params: Promise<{ locale: Lang }> }) => {
const commitHistoryCache: CommitHistory = {}
const { contributors, lastEditLocaleTimestamp } =
await getAppPageContributorInfo(
- "what-is-ethereum-network",
+ "what-is-the-ethereum-network",
locale as Lang,
commitHistoryCache
)
diff --git a/public/content/contributing/translation-program/translatathon/index.md b/public/content/contributing/translation-program/translatathon/index.md
index 5a6409ab586..686d3467cda 100644
--- a/public/content/contributing/translation-program/translatathon/index.md
+++ b/public/content/contributing/translation-program/translatathon/index.md
@@ -75,23 +75,23 @@ For more details, [see the full Terms & conditions](/contributing/translation-pr
## Prizes {#prizes}
-| Placement | Prize amount |
-|-------------------|--------------|
-| 1st place | $4000 |
-| 2nd place | $2500 |
-| 3rd place | $1500 |
-| 4th place | $1100 |
-| 5th place | $1000 |
-| 6th place | $600 |
-| 7th place | $550 |
-| 8th place | $500 |
-| 9th place | $450 |
-| 10th place | $400 |
-| 11th - 20th place | $240 |
-
-Plus additional prize tiers for **top 50, top 100, top 150**, and participatory prizes for all other eligible participants.
-
-The remaining prizes will be distributed dynamically based on the total number of eligible participants.
+| Placement | Prize amount |
+|---------------------|--------------|
+| 1st place | $4000 |
+| 2nd place | $2500 |
+| 3rd place | $1500 |
+| 4th place | $1100 |
+| 5th place | $1000 |
+| 6th place | $600 |
+| 7th place | $550 |
+| 8th place | $500 |
+| 9th place | $450 |
+| 10th place | $400 |
+| 11th - 20th place | $240 |
+| 21st - 50th place | $120 |
+| 51st - 100th place | $60 |
+| 101st - 150th place | $40 |
+| Rest | $20 |
All prizes will be paid out in ETH.
diff --git a/public/content/roadmap/fusaka/index.md b/public/content/roadmap/fusaka/index.md
index 8514389cb49..495fb6d6005 100644
--- a/public/content/roadmap/fusaka/index.md
+++ b/public/content/roadmap/fusaka/index.md
@@ -22,13 +22,14 @@ The Fusaka upgrade is only a single step in Ethereum's long-term development goa
This is the _headliner_ of the Fusaka fork, the main feature added in this upgrade. Layer 2s currently post their data to Ethereum in blobs, the ephemeral data type created specifically for layer 2s. Pre-Fusaka, every full node has to store every blob to ensure that the data exists. As blob throughput rises, having to download all of this data becomes untenably resource-intensive.
-With [data availability sampling](https://notes.ethereum.org/@fradamt/das-fork-choice) , instead of having to store all of the blob data, each node will be responsible for a subset of the blob data. Blobs are uniformly randomly distributed across nodes in the network with each full node holding only 1/8th of the data, therefore enabling theoretical scale up to 8x. To ensure availability of the data, any portion of the data can be reconstructed from any existing 50% of the whole with methods that drive down the probability of wrong or missing data to a cryptographically negligible level (~one in 10²⁰ to one in 10²⁴).
+With [data availability sampling](https://notes.ethereum.org/@fradamt/das-fork-choice) , instead of having to store all of the blob data, each node will be responsible for a subset of the blob data. Blobs are uniformly randomly distributed across nodes in the network with each full node holding only 1/8th of the data, therefore enabling theoretical scale up to 8x. To ensure availability of the data, any portion of the data can be reconstructed from any existing 50% of the whole with methods that drive down the probability of wrong or missing data to a cryptographically negligible level (~one in 1020 to one in 1024).
This keeps hardware and bandwidth requirements for nodes tenable while enabling blob scaling resulting in more scale with smaller fees for layer 2s.
[Learn more about PeerDAS](/roadmap/fusaka/peerdas/)
**Resources**:
+
- [EIP-7594 technical specification](https://eips.ethereum.org/EIPS/eip-7594)
- [DappLion on PeerDAS: Scaling Ethereum Today | ETHSofia 2024](https://youtu.be/bONWd1x2TjQ?t=328)
- [Academic: A Documentation of Ethereum’s PeerDAS (PDF)](https://eprint.iacr.org/2024/1362.pdf)
@@ -62,10 +63,10 @@ EIP-7918 pins a proportional reserve price under every blob. When the reserve is
- base-fee spikes on the EL can no longer strand the blob fee at 1 wei
**Resources**:
+
- [EIP-7918 technical specification](https://eips.ethereum.org/EIPS/eip-7918)
- [Storybook explainer](https://notes.ethereum.org/@anderselowsson/AIG)
-
### Scale L1 {#scale-l1}
#### History expiry and simpler receipts {#history-expiry}
@@ -108,16 +109,16 @@ By better matching costs to actual processing time, MODEXP can no longer cause a
#### RLP Execution Block Size Limit {#rlp-execution-block-size-limit}
-This creates a ceiling on how big a block is allowed to be - this is a limit on what's *sent* over the network and is separate from the gas limit, which limits the *work* inside a block. The block size cap is 10 MiB, with a small allowance (2 MiB) reserved for consensus data so that everything fits and propagates cleanly. If a block shows up bigger than that, the clients reject it.
+This creates a ceiling on how big a block is allowed to be - this is a limit on what's _sent_ over the network and is separate from the gas limit, which limits the _work_ inside a block. The block size cap is 10 MiB, with a small allowance (2 MiB) reserved for consensus data so that everything fits and propagates cleanly. If a block shows up bigger than that, the clients reject it.
This is needed because very large blocks take longer to spread and verify across the network and can create consensus issues or be abused as a DoS vector. Also, the consensus layer’s gossip already won’t forward blocks over ~10 MiB, so aligning the execution layer to that limit avoids weird “seen by some, dropped by others” situations.
The nitty-gritty: this is a cap on the [RLP](/developers/docs/data-structures-and-encoding/rlp/)-encoded execution block size. 10 MiB total, with a 2 MiB safety margin reserved for beacon-block framing. Practically, clients define
-`MAX_BLOCK_SIZE = 10,485,760` bytes and
+`MAX_BLOCK_SIZE = 10,485,760` bytes and
-`SAFETY_MARGIN = 2,097,152` bytes,
+`SAFETY_MARGIN = 2,097,152` bytes,
-and reject any execution block whose RLP payload exceeds
+and reject any execution block whose RLP payload exceeds
`MAX_RLP_BLOCK_SIZE = MAX_BLOCK_SIZE − SAFETY_MARGIN`
@@ -159,7 +160,8 @@ UX upgrade! For users, this unlocks device-native signing and passkeys. Wallets
For developers, it takes a 160-byte input and returns a 32-byte output, making it easy to port existing libraries and L2 contracts. Under the hood, it includes point-at-infinity and modular-comparison checks to eliminate tricky edge cases without breaking valid callers.
-**Resources**:
+**Resources**:
+
- [EIP-7951 technical specification](https://eips.ethereum.org/EIPS/eip-7951)
- [More about RIP-7212](https://www.alchemy.com/blog/what-is-rip-7212) _(Note that EIP-7951 superseded RIP-7212)_
diff --git a/public/content/roadmap/fusaka/peerdas/index.md b/public/content/roadmap/fusaka/peerdas/index.md
index 8b3595494d3..2325a2db209 100644
--- a/public/content/roadmap/fusaka/peerdas/index.md
+++ b/public/content/roadmap/fusaka/peerdas/index.md
@@ -4,6 +4,8 @@ description: Learn about PeerDAS as part of the Fusaka Ethereum protocol upgrade
lang: en
---
+# PeerDAS {#peer-das}
+
The Ethereum protocol is undergoing its most significant scaling upgrade since the [introduction of blob transactions with EIP-4844](/roadmap/danksharding/). As part of the [Fusaka upgrade](/roadmap/fusaka/), PeerDAS introduces a new way of handling blob data, delivering roughly an order-of-magnitude increase in **[data availability (DA)](/developers/docs/data-availability/)** capacity for L2s.
[More on blob scaling roadmap](https://blog.ethereum.org/2025/08/22/protocol-update-002)