Skip to content

Commit 664f6fa

Browse files
committed
chore: remove gm tutorial reference from restart guide and clean up
1 parent b5870d0 commit 664f6fa

File tree

1 file changed

+29
-27
lines changed

1 file changed

+29
-27
lines changed

guides/restart-rollup.md

Lines changed: 29 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -6,30 +6,40 @@ This guide will teach you how to restart your Rollkit rollup.
66

77
This section covers the case where you need to restart your rollup.
88

9-
In order to restart your rollup, you will need to run the `<your-binary>d start [...args]`
9+
In order to restart your rollup, you simply need to run the `<your-binary>d start [...args]`
1010
command for your rollup.
11-
This [is the example for the GM world tutorial](https://github.com/rollkit/docs/blob/8c69bfc1a545b758a260198feecb39806e9794a7/scripts/gm/init-local.sh#L94).
1211

13-
For the GM world tutorial, you can restart the chain by
14-
[running the `restart-local.sh` script that was generated by `init-local.sh`](https://github.com/rollkit/docs/blob/8c69bfc1a545b758a260198feecb39806e9794a7/scripts/gm/init-local.sh#L85-L91).
12+
For example, if you ran the [quick start](../tutorials/quick-start.md) tutorial, you started your rollup with:
1513

16-
Use the `DA_START_HEIGHT`, `NAMESPACE`, and `AUTH_TOKEN` variables from your original
17-
start command.
14+
```bash
15+
rollkit start
16+
```
17+
18+
You would have see output similar to:
19+
20+
```bash
21+
I[2024-10-17|14:52:12.845] Creating and publishing block module=BlockManager height=7
22+
I[2024-10-17|14:52:12.845] finalized block module=BlockManager height=7 num_txs_res=0 num_val_updates=0 block_app_hash=
23+
I[2024-10-17|14:52:12.845] executed block module=BlockManager height=7 app_hash=
24+
I[2024-10-17|14:52:12.846] indexed block events module=txindex height=7
25+
```
26+
27+
If you need to restart your rollup, you can run the same command again:
28+
29+
```bash
30+
rollkit start
31+
```
1832

19-
Using the `rollkit` rollup as an example, you can add something similar to your
20-
respective start script to make it easier to save variables for later use:
33+
You will see that the block height will continue from where it left off:
2134

2235
```bash
23-
# the rest of your init script
24-
25-
# create a restart-local.sh file to restart the chain later
26-
rm restart-local.sh
27-
echo "DA_BLOCK_HEIGHT=$DA_BLOCK_HEIGHT" >> restart-local.sh
28-
echo "NAMESPACE=$NAMESPACE" >> restart-local.sh
29-
echo "AUTH_TOKEN=$AUTH_TOKEN" >> restart-local.sh
30-
echo "rollkit start --rollkit.aggregator --rollkit.da_auth_token=\$AUTH_TOKEN --rollkit.da_namespace \$NAMESPACE --rollkit.da_start_height \$DA_BLOCK_HEIGHT --rpc.laddr tcp://127.0.0.1:36657 --grpc.address 127.0.0.1:9290 --p2p.laddr \"0.0.0.0:36656\"" >> restart-local.sh
36+
I[2024-10-17|14:52:13.845] Creating and publishing block module=BlockManager height=8
37+
I[2024-10-17|14:52:13.845] finalized block module=BlockManager height=8 num_txs_res=0 num_val_updates=0 block_app_hash=
38+
I[2024-10-17|14:52:13.845] executed block module=BlockManager height=8 app_hash=
39+
I[2024-10-17|14:52:13.845] indexed block events module=txindex height=8
3140
```
3241

42+
It is important to include any additional flags that you used when you first started your rollup. For example, if you used the `--rollkit.da_namespace` flag, you will need to include that flag when restarting your rollup to ensure your rollup continues to publish blobs to the same namespace.
3343

3444
## Restart rollup after running out of funds
3545

@@ -38,7 +48,7 @@ you are using to post blocks to your DA and consensus layer runs out of funds (t
3848
and you need to restart your rollup.
3949

4050
In this example, we're using Celestia's [Mocha testnet](https://docs.celestia.org/nodes/mocha-testnet/)
41-
and running a [GM world rollup](./gm-world.md). In this example, our Celestia DA light node
51+
and running the [quick start](../tutorials/quick-start.md). In this example, our Celestia DA light node
4252
ran out of Mocha testnet TIA and we are unable to post new blocks to Celestia due to a
4353
[`Code: 19`](https://github.com/cosmos/cosmos-sdk/blob/main/types/errors/errors.go#L95)
4454
error. This error is defined by Cosmos SDK as:
@@ -74,15 +84,11 @@ cd $HOME && cd celestia-node
7484

7585
### 🛑 Stopping your rollup {#stopping-your-rollup}
7686

77-
You can stop your gm chain (or other Rollkit rollup) by using `Control + C` in your terminal where the node is running.
87+
You can stop your rollup by using `Control + C` in your terminal where the node is running.
7888

7989
### ⛽ Increase the gas fee {#increase-gas-fee}
8090

81-
To reiterate, before restarting the chain, you will need to increase the gas fee in order to avoid a `Code: 19` error:
82-
83-
```bash
84-
rollkit start --rollkit.aggregator --rollkit.da_auth_token=$AUTH_TOKEN --rollkit.da_namespace $NAMESPACE --rollkit.da_start_height $DA_BLOCK_HEIGHT --rpc.laddr tcp://127.0.0.1:36657 --grpc.address 127.0.0.1:9290 --p2p.laddr "0.0.0.0:36656"
85-
```
91+
To reiterate, before restarting the chain, you will need to increase the gas fee in order to avoid a `Code: 19` error. See the [How to configure gas price](./gas-price.md) guide for more information.
8692

8793
### 🔁 Restarting your rollup {#restarting-your-rollup}
8894

@@ -92,8 +98,4 @@ Follow the [restart rollup](#restart-rollup) section above.
9298

9399
In order to save your TIA, we also recommend stopping the chain with `Control + C`, changing the gas fee back to the default (in our case, 8000 utia) and restarting the chain:
94100

95-
```bash
96-
rollkit start --rollkit.aggregator --rollkit.da_auth_token=$AUTH_TOKEN --rollkit.da_namespace $NAMESPACE --rollkit.da_start_height $DA_BLOCK_HEIGHT --rpc.laddr tcp://127.0.0.1:36657 --grpc.address 127.0.0.1:9290 --p2p.laddr "0.0.0.0:36656"
97-
```
98-
99101
🎊 Congrats! You've successfully restarted your Rollkit rollup after running out of TIA.

0 commit comments

Comments
 (0)