You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 7, 2025. It is now read-only.
Next, you'll need to initialize the Rollkit CLI configuration by generating the `rollkit.toml` file. This file is crucial for Rollkit to understand the structure of your rollup.
48
+
Next, you'll need to initialize the Rollkit CLI configuration by generating the `rollkit.toml` file. This file is crucial for Rollkit to understand the structure of your chain.
49
49
50
50
To create the `rollkit.toml` configuration, use this command:
Copy file name to clipboardExpand all lines: guides/create-genesis.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# How to create a genesis for your rollup
1
+
# How to create a genesis for your chain
2
2
3
-
This guide will walk you through the process of setting up a genesis for your rollup. Follow the steps below to initialize your rollup chain, add a genesis account, and start the chain.
3
+
This guide will walk you through the process of setting up a genesis for your chain. Follow the steps below to initialize your chain, add a genesis account, and start the chain.
4
4
5
5
## 0. Pre-requisities
6
6
@@ -19,7 +19,7 @@ First, set the necessary variables for your chain in the terminal, here is an ex
19
19
```sh
20
20
VALIDATOR_NAME=validator1
21
21
CHAIN_ID=gm
22
-
KEY_NAME=rollup-key
22
+
KEY_NAME=chain-key
23
23
CHAINFLAG="--chain-id ${CHAIN_ID}"
24
24
TOKEN_AMOUNT="10000000000000000000000000stake"
25
25
STAKING_AMOUNT="1000000000stake"
@@ -39,7 +39,7 @@ Once completed, run the following command to ensure that the `/Users/you/.gm` di
39
39
ignite rollkit init
40
40
```
41
41
42
-
This (re)creates an `gmd` binary that will be used for the rest of the tutorials to run all the operations on the rollup chain.
42
+
This (re)creates an `gmd` binary that will be used for the rest of the tutorials to run all the operations on the chain.
By following these steps, you will set up the genesis for your rollup, initialize the validator, add a genesis account, and started the chain. This guide provides a basic framework for configuring and starting your rollup using the gm-world binary. Make sure you initialized your chain correctly, and use the `gmd` command for all operations.
121
+
By following these steps, you will set up the genesis for your chain, initialize the validator, add a genesis account, and started the chain. This guide provides a basic framework for configuring and starting your chain using the gm-world binary. Make sure you initialized your chain correctly, and use the `gmd` command for all operations.
Copy file name to clipboardExpand all lines: guides/da/celestia-da.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ import constants from '../../.vitepress/constants/constants.js'
7
7
8
8
## 🌞 Introduction {#introduction}
9
9
10
-
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.
10
+
This tutorial serves as a comprehensive guide for deploying your chain 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.
11
11
12
-
Before proceeding, ensure that you have completed the [gm-world](/guides/gm-world.md) tutorial, which covers installing the Testapp CLI and running a rollup against a local DA network.
12
+
Before proceeding, ensure that you have completed the [gm-world](/guides/gm-world.md) tutorial, which covers installing the Testapp CLI and running a chain against a local DA network.
13
13
14
14
## 🪶 Running a Celestia light node
15
15
16
-
Before you can start your rollup node, you need to initiate, sync, and fund a light node on one of Celestia's networks on a compatible version:
16
+
Before you can start your chain node, you need to initiate, sync, and fund a light node on one of Celestia's networks on a compatible version:
17
17
18
18
Find more information on how to run a light node in the [Celestia documentation](https://celestia.org/run-a-light-node/#start-up-a-node).
The main difference lies in how you fund your wallet address: using testnet TIA or [TIA](https://docs.celestia.org/learn/tia#overview-of-tia) for Mainnet Beta.
44
44
45
-
After successfully starting a light node, it's time to start posting the batches of blocks of data that your rollup generates to Celestia.
45
+
After successfully starting a light node, it's time to start posting the batches of blocks of data that your chain generates to Celestia.
46
46
47
47
## 🏗️ Prerequisites {#prerequisites}
48
48
@@ -127,9 +127,9 @@ port 26658:
127
127
DA_ADDRESS=http://localhost:26658
128
128
```
129
129
130
-
## 🔥 Running your rollup connected to Celestia light node
130
+
## 🔥 Running your chain connected to Celestia light node
131
131
132
-
Finally, let's initiate the rollup node with all the flags:
132
+
Finally, let's initiate the chain node with all the flags:
133
133
134
134
```bash
135
135
gmd start \
@@ -140,16 +140,16 @@ gmd start \
140
140
--rollkit.da.address $DA_ADDRESS
141
141
```
142
142
143
-
Now, the rollup is running and posting blocks (aggregated in batches) to Celestia. You can view your rollup by using your namespace or account on one of Celestia's block explorers.
143
+
Now, the chain is running and posting blocks (aggregated in batches) to Celestia. You can view your chain by using your namespace or account on one of Celestia's block explorers.
144
144
145
145
For example, [here on Celenium for Arabica](https://arabica.celenium.io/).
@@ -53,4 +53,4 @@ You should see the following log message indicating that your rollup is connecte
53
53
54
54
## Summary
55
55
56
-
By following these steps, you will set up a local DA network node and configure your rollup to post data to it. This setup is useful for testing and development in a controlled environment. You can find more information on running the local-da binary [here](https://github.com/rollkit/rollkit/blob/main/da/cmd/local-da/README.md)
56
+
By following these steps, you will set up a local DA network node and configure your chain to post data to it. This setup is useful for testing and development in a controlled environment. You can find more information on running the local-da binary [here](https://github.com/rollkit/rollkit/blob/main/da/cmd/local-da/README.md)
description: This page provides an overview of some common ways to deploy rollups.
2
+
description: This page provides an overview of some common ways to deploy chains.
3
3
---
4
4
5
-
# Deploying Your Rollup
5
+
# Deploying Your Chain
6
6
7
-
One of the benefits of building rollups with Rollkit is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
7
+
One of the benefits of building chains with Rollkit is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
8
8
9
-
The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your rollup.
9
+
The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your chain.
10
10
11
-
In the tutorials so far, you've seen various helper scripts used to make things easier. While great for tutorials, there are better ways to deploy and manage rollups than using various bash scripts.
11
+
In the tutorials so far, you've seen various helper scripts used to make things easier. While great for tutorials, there are better ways to deploy and manage chains than using various bash scripts.
12
12
13
-
In this section, you'll see a few examples of how you can deploy your rollup environment with all your services running in a more production-ready way.
13
+
In this section, you'll see a few examples of how you can deploy your chain environment with all your services running in a more production-ready way.
14
14
15
15
:::warning Disclaimer
16
-
These examples are for educational purposes only. Before deploying your rollup for production use you should fully understand the services you are deploying and your choice in deployment method.
16
+
These examples are for educational purposes only. Before deploying your chain for production use you should fully understand the services you are deploying and your choice in deployment method.
17
17
:::
18
18
19
19
*[Deploy with Docker Compose](/guides/deploy/local.md)
Copy file name to clipboardExpand all lines: guides/deploy/overview.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,23 @@
1
1
---
2
-
description: This page provides an overview of some common ways to deploy rollups.
2
+
description: This page provides an overview of some common ways to deploy chains.
3
3
---
4
4
5
-
# 🚀 Deploying Your Rollup
5
+
# 🚀 Deploying Your Chain
6
6
7
-
One of the benefits of building rollups with Rollkit is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
7
+
One of the benefits of building chains with Rollkit is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
8
8
9
9
You can learn more about Rollkit architecture [here](/learn/specs/overview.md).
10
10
11
-
The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your rollup.
11
+
The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your chain.
12
12
13
-
In the tutorials so far, you've seen various helper scripts used to make things easier. While great for tutorials, there are better ways to deploy and manage rollups than using various bash scripts.
13
+
In the tutorials so far, you've seen various helper scripts used to make things easier. While great for tutorials, there are better ways to deploy and manage chains than using various bash scripts.
14
14
15
15
## 🏗️ Deployment Scales
16
16
17
-
Depending on your needs and the stage of your rollup development, there are different deployment approaches you can take:
17
+
Depending on your needs and the stage of your chain development, there are different deployment approaches you can take:
18
18
19
19
### 🏠 Local Development
20
-
For development and testing purposes, you can deploy your rollup locally using containerized environments. This approach provides:
20
+
For development and testing purposes, you can deploy your chain locally using containerized environments. This approach provides:
21
21
- Quick iteration and testing
22
22
- No external dependencies
23
23
- Full control over the environment
@@ -39,7 +39,7 @@ Choose the deployment approach that matches your current needs:
39
39
*[🌐 Testnet Deployment](./testnet.md) - Deploy on testnet with external DA networks
40
40
41
41
:::warning Disclaimer
42
-
These examples are for educational purposes only. Before deploying your rollup for production use you should fully understand the services you are deploying and your choice in deployment method.
42
+
These examples are for educational purposes only. Before deploying your chain for production use you should fully understand the services you are deploying and your choice in deployment method.
Copy file name to clipboardExpand all lines: guides/evm/single.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Introduction
4
4
5
-
This guide covers how to set up and run the Single Sequencer implementation of Rollkit EVM rollups. This implementation provides a centralized approach to transaction sequencing while using EVM as the execution layer.
5
+
This guide covers how to set up and run the Single Sequencer implementation of Rollkit EVM chains. This implementation provides a centralized approach to transaction sequencing while using EVM as the execution layer.
6
6
7
7
## Prerequisites
8
8
@@ -159,4 +159,4 @@ INF block marked as DA included blockHash=XXXX blockHeight=XX module=BlockManage
159
159
160
160
## Conclusion
161
161
162
-
You've now set up and configured the Single Sequencer implementation of Rollkit EVM rollups. This implementation provides a centralized approach to transaction sequencing while using EVM as the execution layer.
162
+
You've now set up and configured the Single Sequencer implementation of Rollkit EVM chains. This implementation provides a centralized approach to transaction sequencing while using EVM as the execution layer.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?v=4&size=40){kind=avatar}
0 commit comments