docs: remove Arabica network references (merge aug 13 2026) - #2547
Conversation
|
🚀 Preview Deployment Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2547/ |
rach-id
left a comment
rach-id
left a comment
There was a problem hiding this comment.
all is good except for one nit
Co-authored-by: CHAMI Rachid <chamirachid1@gmail.com>
…a-refs # Conflicts: # app/operate/consensus-validators/validator-node/page.mdx # app/operate/getting-started/docker/page.mdx
jcstein
changed the title
| Remaining shares: 262,142 x 482 bytes | ||
| Total bytes: 126,352,922 bytes | ||
| ``` | ||
| The current max square size on Mocha and Mainnet Beta is 32 MiB. |
There was a problem hiding this comment.
we should keep the calculation for learning purposes
jcstein
left a comment
jcstein
left a comment
There was a problem hiding this comment.
left comment and fixing
|
shipping this now to get people to mocha sooner |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| The current max square size on Mocha and Mainnet Beta is 32 MiB. | ||
|
|
||
| The following provides an approximation of the maximum blob capacity on Arabica: | ||
| The following provides an approximation of the maximum blob capacity: | ||
|
|
||
| - The maximum square size is 512x512, which gives us 262,144 shares. | ||
| - One share is reserved for the PFB transaction, leaving us with 262,143 shares available for blob data. | ||
| - The maximum square size is 256x256, which gives us 65,536 shares. | ||
| - One share is reserved for the PFB transaction, leaving us with 65,535 shares available for blob data. | ||
| - The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each. | ||
|
|
||
| Approximate capacity: | ||
|
|
||
| ``` | ||
| First share: 1 x 478 bytes | ||
| Remaining shares: 262,142 x 482 bytes | ||
| Total bytes: 126,352,922 bytes | ||
| Remaining shares: 65,534 x 482 bytes | ||
| Total bytes: 31,587,866 bytes |
There was a problem hiding this comment.
🟡 Mainnet block capacity documentation now states a four-times-too-large value
The maximum block data capacity documented for the main network is raised from the previously stated 8 MiB to 32 MiB (app/operate/networks/mainnet-beta/page.mdx:60-73) while the change only intended to drop a retired test network, so readers plan against a block capacity the main network may not offer.
Impact: Operators and rollup developers sizing their data submissions against Mainnet Beta may rely on roughly four times the capacity actually documented before, leading to failed submissions.
How the substitution changed the stated Mainnet numbers
The original sentence read "The current max square size on Arabica is 128 MiB, Mocha is 32 MiB, and Mainnet is 8 MiB", and the capacity worked example that followed was explicitly labelled "the maximum blob capacity on Arabica" (512x512 = 262,144 shares).
The PR collapsed this into "The current max square size on Mocha and Mainnet Beta is 32 MiB" and rewrote the worked example with Mocha's 256x256 / 65,536 shares numbers, presenting it as generic. The arithmetic itself is self-consistent (65,534 x 482 + 478 = 31,587,866), but the Mainnet Beta figure was silently changed from 8 MiB to 32 MiB, which was not part of removing the retired network.
The same statement was changed identically in app/learn/TIA/submit-data/page.mdx:19.
Prompt for agents
When removing the retired network from the block size limit section of app/operate/networks/mainnet-beta/page.mdx (and the mirrored sentence in app/learn/TIA/submit-data/page.mdx line 19), the stated max square size for Mainnet Beta changed from 8 MiB to 32 MiB, and the worked capacity example — previously explicitly scoped to the retired network's 512x512 square — was replaced with a 256x256 example presented as applying to Mainnet Beta. Verify the actual current max square size / governance parameter for Mainnet Beta (see celestia-app appconsts and the v6 parameters spec already linked from the page) and either restore the correct per-network values or scope the worked example to the network it actually describes.
Was this helpful? React with 👍 or 👎 to provide feedback.
2 participants
Arabica is being sunset and its replacement testnet is internal-only, so this
removes it from the public docs rather than pointing readers at a network they
can't use.
arabica_versions.jsonyarn lintandyarn buildpass, and I scanned the rendered output for strayArabica references. The only remaining mentions are the historical OpenRPC
snapshots in
public/specs/— those are upstream release artifacts, so I leftthem alone.
Two known failures, both unrelated to this diff:
yarn check-linkswon't start under Node 26 (globimports aGLOBSTARexport the pinned
minimatchdoesn't provide)Etherscan 403s, one retired zkSync explorer), plus one transient 502 from a
Mainnet provider
Linear: https://linear.app/celestia/issue/PROTOCO-2210/remove-all-references-of-arabica-from-celestia-app-docs-website