Skip to content

Commit bfe5006

Browse files
committed
fix celestia da
1 parent fafd257 commit bfe5006

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

tutorials/da/celestia-da.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ import constants from '../../.vitepress/constants/constants.js'
99

1010
This tutorial serves as a comprehensive guide for deploying your rollup on Celestia's data availability (DA) network. From the Rollkit perspective, there's no difference in posting blocks to Celestia's testnets or Mainnet Beta.
1111

12-
Before proceeding, ensure that you have completed the [quick start](/tutorials/quick-start) tutorial, which covers installing the rollkit CLI and running a rollup against a local DA network.
12+
Before proceeding, ensure that you have completed the [gm-world](/tutorials/gm-world) tutorial, which covers installing the Testapp CLI and running a rollup against a local DA network.
1313

1414
## 🪶 Running a Celestia light node
1515

@@ -44,18 +44,18 @@ After successfully starting a light node, it's time to start posting the batches
4444

4545
## 🏗️ Prerequisites {#prerequisites}
4646

47-
- `rollkit` CLI installed from the [quick start](/tutorials/quick-start) tutorial.
47+
- `gmd` CLI installed from the [gm-world](/tutorials/gm-world) tutorial.
4848

4949
## 🛠️ Configuring flags for DA
5050

5151
Now that we are posting to the Celestia DA instead of the local DA, the `rollkit start` command requires three DA configuration flags:
5252

53-
- `--rollkit.da_start_height`
54-
- `--rollkit.da_auth_token`
55-
- `--rollkit.da_namespace`
53+
- `--rollkit.da.start_height`
54+
- `--rollkit.da.auth_token`
55+
- `--rollkit.da.namespace`
5656

5757
:::tip
58-
Optionally, you could also set the `--rollkit.da_block_time` flag. This should be set to the finality time of the DA layer, not its actual block time, as Rollkit does not handle reorganization logic. The default value is 15 seconds.
58+
Optionally, you could also set the `--rollkit.da.block_time` flag. This should be set to the finality time of the DA layer, not its actual block time, as Rollkit does not handle reorganization logic. The default value is 15 seconds.
5959
:::
6060

6161
Let's determine which values to provide for each of them.
@@ -130,11 +130,11 @@ DA_ADDRESS=http://localhost:26658
130130
Finally, let's initiate the rollup node with all the flags:
131131

132132
```bash
133-
rollkit start \
134-
--rollkit.aggregator \
135-
--rollkit.da_auth_token $AUTH_TOKEN \
136-
--rollkit.da_namespace $DA_NAMESPACE \
137-
--rollkit.da_start_height $DA_BLOCK_HEIGHT \
133+
gmd start \
134+
--rollkit.node.aggregator \
135+
--rollkit.da.auth_token $AUTH_TOKEN \
136+
--rollkit.da.namespace $DA_NAMESPACE \
137+
--rollkit.da.start_height $DA_BLOCK_HEIGHT \
138138
--rollkit.da.address $DA_ADDRESS
139139
```
140140

0 commit comments

Comments
 (0)