Merge branch 'main' into pr/1694

.vitepress/constants/arabica_versions.js

@@ -1,9 +1,9 @@
 const arabicaVersions = Object.freeze({
-  "app-latest-tag": "v2.2.0-arabica",
-  "app-latest-sha": "d3f8b2997fcbc8e7f43785a9513b2d0c91675087",
-  "core-latest-tag": "v1.40.1-tm-v0.34.29-rc0",
-  "core-latest-sha": "0d2b63836d0f4587e162bfded58f53fba238e69c",
-  "node-latest-tag": "v0.18.1-arabica",
-  "node-latest-sha": "ac0515f82c2ae3783cfc62670dab3ad93cada8a6",
+  "app-latest-tag": "v3.2.0-arabica",
+  "app-latest-sha": "91f4c700c321162ab2997a20ade11c698efda9a8",
+  "core-latest-tag": "v1.44.1-tm-v0.34.35",
+  "core-latest-sha": "d51978e782966c93d66323465563f5c8149e91f4",
+  "node-latest-tag": "v0.20.4-arabica",
+  "node-latest-sha": "51b79431533576a5cddf1235bdf3751e4c014212",
 });
 export default arabicaVersions;

.vitepress/constants/constants.js

@@ -1,7 +1,7 @@
 const constants = Object.freeze({
   golangNodeMainnet: "1.23.0",
-  golangNodeMocha: "1.23.0",
-  golangNodeArabica: "1.23.0",
+  golangNodeMocha: "1.23.2",
+  golangNodeArabica: "1.23.2",
   golangApp: "1.22.6",
   golangCore: "1.22.6",
   golang: "1.22.0",

.vitepress/constants/mainnet_versions.js

@@ -1,9 +1,9 @@
 const mainnetVersions = Object.freeze({
-  "app-latest-tag": "v2.1.2",
-  "app-latest-sha": "48173df3dc78f9348eedb3796f29ef9e9e5dc584",
-  "core-latest-tag": "v1.41.0-tm-v0.34.29",
-  "core-latest-sha": "aef322775c75783488b439cdf7ca33f38da08426",
-  "node-latest-tag": "v0.16.0",
-  "node-latest-sha": "6744f648649ebb5fee1b27faf7aca96ecf4519b2",
+  "app-latest-tag": "v3.2.0",
+  "app-latest-sha": "91f4c700c321162ab2997a20ade11c698efda9a8",
+  "core-latest-tag": "v1.44.1-tm-v0.34.35",
+  "core-latest-sha": "d51978e782966c93d66323465563f5c8149e91f4",
+  "node-latest-tag": "v0.20.4",
+  "node-latest-sha": "51b79431533576a5cddf1235bdf3751e4c014212",
 });
 export default mainnetVersions;

.vitepress/constants/mocha_versions.js

@@ -1,9 +1,9 @@
 const mochaVersions = Object.freeze({
-  "app-latest-tag": "v2.2.0-mocha",
-  "app-latest-sha": "d3f8b2997fcbc8e7f43785a9513b2d0c91675087",
-  "core-latest-tag": "v1.40.1-tm-v0.34.29-rc0",
-  "core-latest-sha": "0d2b63836d0f4587e162bfded58f53fba238e69c",
-  "node-latest-tag": "v0.18.2-mocha",
-  "node-latest-sha": "4309c8349857638b033a2a278da0f8ab182fdb26",
+  "app-latest-tag": "v3.2.0-mocha",
+  "app-latest-sha": "91f4c700c321162ab2997a20ade11c698efda9a8",
+  "core-latest-tag": "v1.44.1-tm-v0.34.35",
+  "core-latest-sha": "d51978e782966c93d66323465563f5c8149e91f4",
+  "node-latest-tag": "v0.20.4-mocha",
+  "node-latest-sha": "51b79431533576a5cddf1235bdf3751e4c014212",
 });
 export default mochaVersions;

.vitepress/theme/style.css

@@ -92,12 +92,32 @@
 }
 
 @font-face {
-  font-family: "RuberoidBold";
-  src: url("/fonts/Ruberoid/Ruberoid-Bold.otf") format("opentype");
+  font-family: "Untitled-Sans";
+  src: url("/fonts/untitled-sans/untitled-sans-regular.woff2") format("woff2");
+  font-weight: normal;
+  font-style: normal;
+  font-display: swap;
+}
+
+@font-face {
+  font-family: "Untitled-Sans";
+  src: url("/fonts/untitled-sans/untitled-sans-medium.woff2") format("woff2");
+  font-weight: 500;
+  font-style: normal;
+  font-display: swap;
+}
+
+@font-face {
+  font-family: "Youth";
+  src: url("/fonts/youth/Youth-Regular.woff2") format("woff2");
+  font-weight: normal;
+  font-style: normal;
+  font-display: swap;
 }
 
 :root {
-  --font-primary: "RuberoidBold", sans-serif;
+  --font-primary: "Youth", sans-serif;
+  --font-body: "Untitled-Sans", sans-serif;
 }
 
 h1,
@@ -126,3 +146,33 @@ h6 {
   height: 100%;
   border: none;
 }
+
+body {
+  font-family: var(--font-body);
+}
+
+.VPDoc {
+  font-family: var(--font-body);
+}
+
+.VPHome {
+  font-family: var(--font-body);
+}
+
+.VPSidebar {
+  font-family: var(--font-body) !important;
+}
+
+.VPSidebarItem .text,
+.VPSidebarGroup .title,
+.VPSidebarGroup .items,
+.VPSidebarGroup .VPLink,
+.VPDocAsideOutline .outline-title,
+.VPDocAsideOutline .outline-link {
+  font-family: var(--font-body) !important;
+  font-weight: 400 !important;
+}
+
+.VPSidebarItem.is-active .text {
+  color: var(--vp-c-brand);
+}

README.md

@@ -32,12 +32,19 @@ improving content clarity, or adding new topics, every contribution helps.
 Please ensure to review the detailed Contribution Guidelines above before
 making a pull request.
 
+### Link Format Guidelines
+
+When adding internal links to documentation, please use the following format:
+`[link text](/base-working-dir/subdir/page.md#section-id)`, i.e. `[link text](/how-to-guides/quick-start.md#get-your-auth-token)`
+
+This format ensures long-term compatibility and consistent behavior across different platforms and documentation builds.
+
 ## Directory Structure
 
 - /learn: A category for learning about Celestia.
-- /developers: A category with tutorials and guides for deploying
-  rollups and interacting with Celestia nodes.
-- /nodes: Technical reference materials for all node types.
+- /how-to guides: A category with guides for running a node, deploying
+  rollups, and building on Celestia.
+- /tutorials: A category with tutorials on interacting with celestia-node.
 <!-- * /guides [WIP]: In-depth articles that cover specific topics in detail. -->
 - /community: A category for the Celestia community.
 - /public: Images, diagrams, and other media files used in the documentation.

community/foundation-delegation-program.md

@@ -40,7 +40,7 @@ process will work for Cohort 1 and what that means for future cohorts.
 
 * Initial Cohort (Cohort 1): 50 applicants will be accepted
   * Grading System: Applicants in Cohort 1 are divided into first, second,
-  and third place based eligibility criteria outlined in this document.
+  and third place based on eligibility criteria outlined in this document.
   * Delegation Duration: This varies based on the applicant’s placement in
   Cohort 1. First place receives 12 months of delegation, second place receives
   8 months, third place receives 4 months.
@@ -70,7 +70,7 @@ The minimum requirements for participation in the program are as follows:
 for at least 1 month before application deadline
 * Run a bridge node (on Mainnet Beta if you are already an active Mainnet Beta
 validator or on Mocha testnet if not) that is connected and reporting
-to the Celestia Labs [OTEL collector](../nodes/celestia-node-metrics.md)
+to the Celestia Labs [OTEL collector](../how-to-guides/celestia-node-metrics.md)
 (for new applicants - on testnet, so that we can evaluate performance)
 * Not jailed or slashed in the 6 months before application deadline
 * Not associated with an exchange or custodian
@@ -170,7 +170,7 @@ their respective delegations.
 
 * [Cohort 1](https://docs.google.com/spreadsheets/d/1Fxu9uYJ4wxfHChEiSg5bmXAMU8IZSq7J3GYDCFgk1HA/edit#gid=0): 50 Validator Seats
 * [Cohort 2](https://docs.google.com/spreadsheets/d/1Fxu9uYJ4wxfHChEiSg5bmXAMU8IZSq7J3GYDCFgk1HA/edit?gid=855157686#gid=855157686): 15 Validator Seats (Applications open June 1, 2024)
-* Cohort 3: 15 Validator Seats (Applications open October 1, 2024)
+* [Cohort 3](https://docs.google.com/spreadsheets/d/1Fxu9uYJ4wxfHChEiSg5bmXAMU8IZSq7J3GYDCFgk1HA/edit?gid=1432570846#gid=1432570846): 15 Validator Seats (Applications open October 1, 2024)
 * Cohort 4: 20 Validator Seats (Applications open February 1, 2025)
 
 IMPORTANT: Each validator selected for the program has to maintain a fully archival (non pruned) bridge node for both Mainnet Beta and Mocha.

community/modular-meetup-toolkit.md

@@ -32,7 +32,7 @@ help you plan and execute your meetups effectively.
 
 - [Sample presentation - run a light node](https://docs.google.com/presentation/d/1fV7OYUdW4kafkZcgHwFenFWDbSIwkk0R6BnSKrAV-Hc/edit#slide=id.g20713cce7c2_1_0)
 - Summary:
-  This is an overview presentation goes over running a Celestia light node.
+  This is an overview presentation that goes over running a Celestia light node.
   You can find existing video presentations for this here:
 - The sample presentation covers:
   1. What is a Celestia light node?

nodes/arabica-devnet.md → how-to-guides/arabica-devnet.md

@@ -24,7 +24,7 @@ it is a useful way to keep testing the latest changes in the software.
 
 Developers can still deploy on Mocha testnet their sovereign rollups if they
 chose to do so, it just will always lag behind Arabica devnet until Mocha
-undergoes network upgrades upgrades in coordination with validators.
+undergoes network upgrades in coordination with validators.
 
 ## Network details
 
@@ -59,7 +59,6 @@ These RPC providers are meant to be used in production environments.
 
 | Provider | URL |
 |--------|--------|
-| NewMetric | <https://app.newmetric.xyz/start> |
 | Numia | For RPC access: <https://docs.numia.xyz/overview/rpc-api-access> |
 | Numia | For data warehouse access: <https://docs.numia.xyz/overview/sql-access/chains/celestia> |
 | Grove | <https://www.grove.city/> |
@@ -79,7 +78,7 @@ RPC endpoints and types of nodes you can run in order to participate in Arabica
 
 | Node type                                                                              | Endpoint type                    | Endpoint                                                                                                      |
 | -------------------------------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| **Consensus nodes** ([full](../nodes/full-consensus-node.md))                               | Consensus RPC                    | `https://rpc.celestia-arabica-11.com`                                                                         |
+| **Consensus nodes** ([full](../how-to-guides/consensus-node.md))                               | Consensus RPC                    | `https://rpc.celestia-arabica-11.com`                                                                         |
 |                                                                                        | API                              | `https://api.celestia-arabica-11.com`                                                                         |
 |                                                                                        | gRPC                             | `grpc.celestia-arabica-11.com:443`                                                                            |
 |                                                                                        | Direct endpoints with open ports | Open ports: 26656 (p2p), 26657 (RPC), 1317 (API), 9090 (GRPC)                                                 |
@@ -118,7 +117,7 @@ to their respective DA node.
 :::tip EXAMPLE
 
 ```bash
-celestia <da_type> start –core.ip <url> -–core.grpc.port <port>
+celestia <da_type> start --core.ip <url> --core.grpc.port <port>
 ```
 
 :::
@@ -175,12 +174,11 @@ There are multiple explorers you can use for Arabica:
 
 - [https://arabica.celenium.io](https://arabica.celenium.io)
 - [https://explorer.celestia-arabica-11.com](https://explorer.celestia-arabica-11.com)
-- [https://celestiascan.com](https://celestiascan.com)
 
 ## Network upgrades
 
 Join our [Telegram announcement channel](https://t.me/+smSFIA7XXLU4MjJh)
 for network upgrades.
 
 See the [network upgrade process page](./network-upgrade-process.md) to learn more
-about specific upgrades like the [Lemongrass network upgrade](./network-upgrade-process.md#lemongrass-network-upgrade).
+about specific upgrades like the [Ginger network upgrade](./network-upgrade-process.md#ginger-network-upgrade).

developers/arbitrum-bridge.md → how-to-guides/arbitrum-bridge.md

@@ -2,7 +2,7 @@
 description: A guide on how to bridge in and out of your Arbitrum Orbit rollup.
 next:
   text: "Intro to OP Stack integration"
-  link: "/developers/intro-to-op-stack"
+  link: "/how-to-guides/intro-to-op-stack"
 ---
 
 # Bridging in and out of your Orbit rollup

developers/arbitrum-deploy.md → how-to-guides/arbitrum-deploy.md

@@ -34,9 +34,9 @@ and [the original deployment guide](https://docs.arbitrum.io/launch-orbit-chain/
 - [Docker](https://docs.docker.com/engine/install/ubuntu/)
   running on your machine
 - [Docker Compose](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-compose-on-ubuntu-20-04)
-- A fully synced and funded Mocha testnet [light node](../nodes/light-node.md)
+- A fully synced and funded Mocha testnet [light node](../how-to-guides/light-node.md)
 on **v0.13.2**
-  - [Mocha testnet faucet](../nodes/mocha-testnet.md#mocha-testnet-faucet)
+  - [Mocha testnet faucet](../how-to-guides/mocha-testnet.md#mocha-testnet-faucet)
 - A browser-based Ethereum wallet (like [MetaMask](https://metamask.io))
 - At least 1 Arbitrum Sepolia testnet ETH (for custom gas token chains,
 0.6 ETH and 0.4 native tokens)
@@ -184,7 +184,7 @@ root of your cloned `orbit-setup-script` repository.
 ### Step 7: Pick an L2 RPC URL for the Batch Poster
 
 In order for the Batch Poster, which is responsible for posting batches of data, to
-subscribe to Blobstream's smart contract events, the node most use a WebSocket
+subscribe to Blobstream's smart contract events, the node must use a WebSocket
 connection, since an HTTP one will not support subscriptions. This RPC URL is different
 from the `parent-chain.connection.url` object used in the node config, and is
 not necessary when running a full node. WebSocket (WSS) URLs which are
@@ -412,8 +412,8 @@ Extra resources in Arbitrum documentation:
 <!-- markdownlint-disable MD013 -->
 | Component | Version | Details |
 |-----------|---------|---------|
-| Nitro | [v2.3.1-rc.1](https://github.com/celestiaorg/nitro/releases/tag/v2.3.1-rc.1) | Includes the replay binary for the WASM root `0x10c65b27d5031ce2351c719072e58f3153228887f027f9f6d65300d2b5b30152`. [Read the overview for overall changes](../developers/arbitrum-integration.md). |
-| Contracts | [v1.2.1-celestia](https://github.com/celestiaorg/nitro-contracts/releases/tag/v1.2.1-celestia) | Integrates Blobstream X functionality into nitro-contracts v1.2.1 |
+| Nitro | [v2.3.1-rc.1](https://github.com/celestiaorg/nitro/releases/tag/v2.3.1-rc.1) | Includes the replay binary for the WASM root `0x10c65b27d5031ce2351c719072e58f3153228887f027f9f6d65300d2b5b30152`. [Read the overview for overall changes](../how-to-guides/arbitrum-integration.md). |
+| Contracts | [v1.2.1](https://github.com/celestiaorg/nitro-contracts/releases/tag/v1.2.1) | Integrates Blobstream X functionality into nitro-contracts v1.2.1 |
 | Orbit SDK | [v0.8.2 Orbit SDK for Celestia DA](https://github.com/celestiaorg/arbitrum-orbit-sdk/releases/tag/v0.8.2) | This is not compatible with Orbit SDK v0.8.2 or with the latest changes to nitro-contracts for the Atlas upgrade. The Orbit SDK itself is in Alpha. |
 | celestia-node | [v0.13.1](https://github.com/celestiaorg/celestia-node/releases/tag/v0.13.1) | This integration has only been tested with celestia-node 0.13.1 and only works with said version, and with future versions after that. Under the hood, the Nitro node uses [this commit](https://github.com/celestiaorg/celestia-openrpc/commit/64f04840aa97d4deb821b654b1fb59167d242bd1) of celestia-openrpc. |
 <!-- markdownlint-enable MD013 -->

developers/arbitrum-full-node.md → how-to-guides/arbitrum-full-node.md

@@ -1,5 +1,5 @@
 ---
-description: A guide on how to run a full node or validating full node on your Orbit rollup.
+description: A guide on how to run a full node or validate a full node on your Orbit rollup.
 ---
 
 # Running a full node and/or validator