Skip to content

docs: use dynamic versions across docs for mocha-4 and arabica-11 #2014

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 28, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 19 additions & 17 deletions how-to-guides/arabica-devnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,14 @@ description: A guide to Arabica devnet.

# Arabica devnet

<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD033 -->
<script setup>
import constants from '/.vitepress/constants/constants.js'
import ArabicaVersionTags from '../.vitepress/components/ArabicaVersionTags.vue'
import ArabicaDevnetDetails from '../.vitepress/components/ArabicaDevnetDetails.vue'
</script>

![arabica-devnet](/img/arabica-devnet.png)

Arabica devnet is a testnet from Celestia Labs that is focused
Expand All @@ -26,12 +34,6 @@ 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 in coordination with validators.

<!-- markdownlint-disable MD033 -->
<script setup>
import ArabicaVersionTags from '../.vitepress/components/ArabicaVersionTags.vue'
import ArabicaDevnetDetails from '../.vitepress/components/ArabicaDevnetDetails.vue'
</script>

## Network details

<ArabicaDevnetDetails />
Expand Down Expand Up @@ -78,14 +80,14 @@ RPC endpoints and types of nodes you can run in order to participate in Arabica

| Node type | Endpoint type | Endpoint |
| -------------------------------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **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` |
| **Consensus nodes** ([full](../how-to-guides/consensus-node.md)) | Consensus RPC | `https://rpc.celestia-{{constants.arabicaChainId}}.com` |
| | API | `https://api.celestia-{{constants.arabicaChainId}}.com` |
| | gRPC | `grpc.celestia-{{constants.arabicaChainId}}.com:443` |
| | Direct endpoints with open ports | Open ports: 26656 (p2p), 26657 (RPC), 1317 (API), 9090 (GRPC) |
| | | `validator-1.celestia-arabica-11.com` |
| | | `validator-2.celestia-arabica-11.com` |
| | | `validator-3.celestia-arabica-11.com` |
| | | `validator-4.celestia-arabica-11.com` |
| | | `validator-1.celestia-{{constants.arabicaChainId}}.com` |
| | | `validator-2.celestia-{{constants.arabicaChainId}}.com` |
| | | `validator-3.celestia-{{constants.arabicaChainId}}.com` |
| | | `validator-4.celestia-{{constants.arabicaChainId}}.com` |
| | | |
| **Data availability nodes** | DA Bridge Node Endpoints | See the list of official Celestia bootstrappers in the [celestia-node GitHub repository](https://github.com/celestiaorg/celestia-node/blob/a87a17557223d88231b56d323d22ac9da31871db/nodebuilder/p2p/bootstrap.go#L39). |
| | `--core.ip string` endpoints | Refer to "Direct endpoints with open ports" above |
Expand Down Expand Up @@ -126,9 +128,9 @@ Arabica devnet with can be found in the table in the
As an example, this command will work to start a light node with
state access, using default ports:

```bash
```bash-vue
celestia light start --p2p.network arabica \
--core.ip validator-1.celestia-arabica-11.com \
--core.ip validator-1.celestia-{{constants.arabicaChainId}}.com \
--core.port 9090
```

Expand Down Expand Up @@ -163,14 +165,14 @@ Faucet has a limit of 10 tokens per week per address/Discord ID.

### Web

The web faucet is available at [https://arabica.celenium.io/faucet](https://arabica.celenium.io/faucet) and [https://faucet.celestia-arabica-11.com/](https://faucet.celestia-arabica-11.com/).
The web faucet is available at [https://arabica.celenium.io/faucet](https://arabica.celenium.io/faucet) and [https://faucet.celestia-{{constants.arabicaChainId}}.com/](https://faucet.celestia-{{constants.arabicaChainId}}.com/).

## Explorers

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://explorer.celestia-{{constants.arabicaChainId}}.com](https://explorer.celestia-{{constants.arabicaChainId}}.com)

## Network upgrades

Expand Down
6 changes: 3 additions & 3 deletions how-to-guides/blobstream.md
Original file line number Diff line number Diff line change
Expand Up @@ -156,6 +156,6 @@ the following chains:
| SP1 Blobstream | Ethereum Mainnet | [`0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAe`](https://etherscan.io/address/0x7Cf3876F681Dbb6EdA8f6FfC45D66B996Df08fAe#events) | [Mainnet Beta](/how-to-guides/mainnet.md) | [Deployment on Celenium](https://celenium.io/blobstream?network=ethereum&page=1) |
| SP1 Blobstream | Arbitrum One | [`0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794`](https://arbiscan.io/address/0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794#events) | [Mainnet Beta](/how-to-guides/mainnet.md) | [Deployment on Celenium](https://celenium.io/blobstream?network=arbitrum&page=1) |
| SP1 Blobstream | Base | [`0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794`](https://basescan.org/address/0xA83ca7775Bc2889825BcDeDfFa5b758cf69e8794#events) | [Mainnet Beta](/how-to-guides/mainnet.md) | [Deployment on Celenium](https://celenium.io/blobstream?network=base&page=1) |
| SP1 Blobstream | Sepolia | [`0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1e`](https://sepolia.etherscan.io/address/0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1e#events) | [Mocha testnet](/how-to-guides/mocha-testnet.md) | [Deployment on Celenium](https://mocha-4.celenium.io/blobstream?network=ethereum&page=1) |
| SP1 Blobstream | Arbitrum Sepolia | [`0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2`](https://sepolia.arbiscan.io/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events) | [Mocha testnet](/how-to-guides/mocha-testnet.md) | [Deployment on Celenium](https://mocha-4.celenium.io/blobstream?network=arbitrum&page=1) |
| SP1 Blobstream | Base Sepolia | [`0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2`](https://sepolia.basescan.org/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events) | [Mocha testnet](/how-to-guides/mocha-testnet.md) | [Deployment on Celenium](https://mocha-4.celenium.io/blobstream?network=base&page=1) |
| SP1 Blobstream | Sepolia | [`0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1e`](https://sepolia.etherscan.io/address/0xf0c6429ebab2e7dc6e05dafb61128be21f13cb1e#events) | [Mocha testnet](/how-to-guides/mocha-testnet.md) | [Deployment on Celenium](https://mocha.celenium.io/blobstream?network=ethereum&page=1) |
| SP1 Blobstream | Arbitrum Sepolia | [`0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2`](https://sepolia.arbiscan.io/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events) | [Mocha testnet](/how-to-guides/mocha-testnet.md) | [Deployment on Celenium](https://mocha.celenium.io/blobstream?network=arbitrum&page=1) |
| SP1 Blobstream | Base Sepolia | [`0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2`](https://sepolia.basescan.org/address/0xc3e209eb245Fd59c8586777b499d6A665DF3ABD2#events) | [Mocha testnet](/how-to-guides/mocha-testnet.md) | [Deployment on Celenium](https://mocha.celenium.io/blobstream?network=base&page=1) |
10 changes: 8 additions & 2 deletions how-to-guides/bridge-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,12 @@ description: Learn how to set up your Celestia bridge node.

# Setting up a Celestia bridge node

<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD033 -->
<script setup>
import constants from '/.vitepress/constants/constants.js'
</script>

This tutorial will go over the steps to set up your Celestia bridge node.

Bridge nodes connect the data availability layer and the consensus layer.
Expand Down Expand Up @@ -126,8 +132,8 @@ celestia bridge start --core.ip rpc-mocha.pops.one --core.port 9090 --p2p.networ

And on Arabica:

```sh
celestia bridge start --core.ip validator-1.celestia-arabica-11.com \
```sh-vue
celestia bridge start --core.ip validator-1.celestia-{{constants.arabicaChainId}}.com \
--p2p.network arabica --core.port 9090
```

Expand Down
4 changes: 2 additions & 2 deletions how-to-guides/celestia-node-troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -316,8 +316,8 @@ sudo systemctl restart celestia-bridge

When a bridge or full storage node runs on `ext4` file system, there will be errors like the following due to large folder size:

```bash
ERROR header/sync sync/sync.go:227 syncing headers {"from": 5074102, "to": 5161144, "err": "creating file: creating ODSQ4 file: creating Q4 file: creating Q4 file: open /root/.celestia-bridge-mocha-4/blocks/C9ADF6D9F862D92993D67977DE407D17ECF7F1DACE5FB7FE9A6845F4BD0172CE.q4: no space left on device"}
```bash-vue
ERROR header/sync sync/sync.go:227 syncing headers {"from": 5074102, "to": 5161144, "err": "creating file: creating ODSQ4 file: creating Q4 file: creating Q4 file: open /root/.celestia-bridge-{{constants.mochaChainId}}/blocks/C9ADF6D9F862D92993D67977DE407D17ECF7F1DACE5FB7FE9A6845F4BD0172CE.q4: no space left on device"}
```

You may also observe similar errors from the `tar` command when extracting a snapshot of an archival bridge node.
Expand Down
10 changes: 8 additions & 2 deletions how-to-guides/feegrant-for-blobs.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# FeeGrant module for blobs submission

<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD033 -->
<script setup>
import constants from '/.vitepress/constants/constants.js'
</script>

## Overview

This guide provides developers with the knowledge to use the FeeGrant
Expand Down Expand Up @@ -175,13 +181,13 @@ Then, send the feegrant transaction:

<!-- markdownlint-disable MD013 -->

```bash
```bash-vue
celestia-appd tx feegrant grant \
$GRANTER_ADDRESS $GRANTEE_ADDRESS \
--node $RPC_URL \
--spend-limit 1000000utia \
--allowed-messages "/cosmos.bank.v1beta1.MsgSend,/celestia.blob.v1.MsgPayForBlobs" \
--chain-id mocha-4 \
--chain-id {{constants.mochaChainId}} \
--keyring-backend test \
--fees 20000utia \
--broadcast-mode block \
Expand Down
46 changes: 26 additions & 20 deletions how-to-guides/ibc-relayer.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ next:

# IBC relaying guide

<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD033 -->
<script setup>
import constants from '/.vitepress/constants/constants.js'
</script>

Celestia uses [IBC](https://ibcprotocol.dev/)
(Inter-Blockchain Communication protocol) to enable cross-chain
transfer of tokens. To support this capability it relies on
Expand Down Expand Up @@ -59,7 +65,7 @@ the chains you want to relay between.

For this tutorial, we will be using the following chains:

- Celestia's `mocha-4` testnet
- Celestia's `{{constants.mochaChainId}}` testnet
- Cosmos Hub's `theta-testnet-001` testnet

Edit the Hermes configuration.
Expand Down Expand Up @@ -156,7 +162,7 @@ list = [["transfer", "channel-3108"]]
derivation = "cosmos"

[[chains]]
id = "mocha-4"
id = "{{constants.mochaChainId}}"
type = "CosmosSdk"
rpc_addr = "https://rpc-celestia-mocha.architectnodes.com"
grpc_addr = "https://grpc.celestia-mocha.com:443"
Expand Down Expand Up @@ -221,8 +227,8 @@ Follow the steps at
[adding-keys-to-hermes](https://hermes.informal.systems/documentation/commands/keys/index.html#adding-keys-to-hermes)
to add keys for each chain

```bash
hermes keys add --chain mocha-4 --mnemonic-file <seed-file>
```bash-vue
hermes keys add --chain {{constants.mochaChainId}} --mnemonic-file <seed-file>
hermes keys add --chain theta-testnet-001 --mnemonic-file <seed-file>
```

Expand Down Expand Up @@ -251,41 +257,41 @@ place and use the existing ones if they do. In that case you can
**skip this step** and go to [Configure channels in Hermes](#configure-channels-in-hermes)
section.

In this example, we are creating new clients and a new connection between `mocha-4`
In this example, we are creating new clients and a new connection between `{{constants.mochaChainId}}`
and `theta-testnet-001` networks.

## Create clients

To learn if a client already exists, you can use the following command:

```bash
hermes query clients --host-chain mocha-4 --reference-chain theta-testnet-001
```bash-vue
hermes query clients --host-chain {{constants.mochaChainId}} --reference-chain theta-testnet-001
```

To create a new client, use the
[`create-client` command](https://hermes.informal.systems/documentation/commands/path-setup/clients.html#create-client):

```bash
hermes create client --host-chain mocha-4 --reference-chain theta-testnet-001
```bash-vue
hermes create client --host-chain {{constants.mochaChainId}} --reference-chain theta-testnet-001
```

Create a second client:

```bash
hermes create client --host-chain theta-testnet-001 --reference-chain mocha-4
```bash-vue
hermes create client --host-chain theta-testnet-001 --reference-chain {{constants.mochaChainId}}
```

### Open connection over new clients

To create a new connection over clients, use the following command:

```bash
hermes create connection --a-chain mocha-4 --b-chain theta-testnet-001
```bash-vue
hermes create connection --a-chain {{constants.mochaChainId}} --b-chain theta-testnet-001
```

You should be seeing a similar output to this:

```bash
```bash-vue
SUCCESS Connection {
delay_period: 0ns,
a_side: ConnectionSide {
Expand All @@ -308,7 +314,7 @@ SUCCESS Connection {
b_side: ConnectionSide {
chain: BaseChainHandle {
chain_id: ChainId {
id: "mocha-4",
id: "{{constants.mochaChainId}}",
version: 4,
},
runtime_sender: Sender { .. },
Expand Down Expand Up @@ -338,7 +344,7 @@ hermes create channel --a-chain theta-testnet-001 --a-connection connection-2727

You should be seeing a similar output to this:

```bash
```bash-vue
SUCCESS Channel {
ordering: Unordered,
a_side: ChannelSide {
Expand Down Expand Up @@ -368,7 +374,7 @@ SUCCESS Channel {
b_side: ChannelSide {
chain: BaseChainHandle {
chain_id: ChainId {
id: "mocha-4",
id: "{{constants.mochaChainId}}",
version: 4,
},
runtime_sender: Sender { .. },
Expand Down Expand Up @@ -405,7 +411,7 @@ Now that we have created new connections and opened channels, we need to
edit `config.toml` again and add the newly created channels, or use the
already existing ones.

For `mocha-4` add:
For `{{constants.mochaChainId}}` add:

```bash
[chains.packet_filter]
Expand All @@ -417,11 +423,11 @@ list = [

For `theta-testnet-001` add:

```bash
```bash-vue
[chains.packet_filter]
policy = 'allow'
list = [
['transfer', 'channel-3108'], # mocha-4
['transfer', 'channel-3108'], # {{constants.mochaChainId}}
]
```

Expand Down
14 changes: 10 additions & 4 deletions how-to-guides/light-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@ description: This tutorial covers setting up a Celestia light node.

# Setting up a Celestia light node

<!-- markdownlint-disable MD013 -->
<!-- markdownlint-disable MD033 -->
<script setup>
import constants from '/.vitepress/constants/constants.js'
</script>

This tutorial will guide you through setting up a Celestia light node, which
will allow you to perform data availability sampling (DAS) on Celestia's data
availability (DA) network.
Expand Down Expand Up @@ -104,8 +110,8 @@ celestia light start --core.ip rpc-mocha.pops.one \
--core.port 9090 --p2p.network mocha
```

```sh [Arabica]
celestia light start --core.ip validator-1.celestia-arabica-11.com \
```sh [Arabica]-vue
celestia light start --core.ip validator-1.celestia-{{constants.arabicaChainId}}.com \
--core.port 9090 --p2p.network arabica
```

Expand Down Expand Up @@ -140,9 +146,9 @@ celestia light start --keyring.keyname my_celes_key \
--p2p.network mocha
```

```sh [Arabica]
```sh-vue [Arabica]
celestia light start --keyring.keyname my_celes_key \
--core.ip validator-1.celestia-arabica-11.com \
--core.ip validator-1.celestia-{{constants.arabicaChainId}}.com \
--core.port 9090 --p2p.network arabica
```

Expand Down
Loading
Loading