Create an EVM ZK Rollup
1. Clone GitHub Repositories
Start by cloning the necessary repositories from GitHub. Use the following commands in your terminal:
If you're utilizing EigenDA,there's no necessity to clone any repository. Otherwise, clone the respective repositories for the DA client you're using.
2. Setting Up and Running the EVM Station
Installing Dependencies
After cloning the repository, navigate into the project directory.
Then, tidy up the Go modules to ensure that dependencies are properly managed.
Running the Project
To run the EVM Station project locally, execute the following command:
Get Your Private Key of EVM Station
/bin/bash ./scripts/local-keys.sh
3. Setting Up DA Keys and Running DA Client
Generate DA KEY for Avail
Download the Binary to Generate Keys
Give Permission to the Downloaded Binary
Generate DA Keys For Avail
SS58 Address is your DA Keys
Running avail da
with Custom Identity Configuration
avail da
with Custom Identity ConfigurationIf you possess a specific seed phrase and wish to use it instead of the generated one, you can either modify the default identity configuration file or pass the seed phrase as a flag.
To modify the default identity configuration file, navigate to
~/.avail/identity/identity.toml
and edit it using a text editor such asnano
.
Alternatively, you can create a new identity configuration file and specify your seed phrase. For example:
Then, execute the avail-light with the --identity
flag and specify the path to your custom identity configuration file:
Example Identity Configuration
Attention: Using the seed phrase provided below in production environments is strongly discouraged.
Here is an example of the content for the ~/identity.toml
file:
This seed phrase will be used for identity generation during the execution of the availup.sh
script.
Feel free to customize the identity configuration as needed!
Running avail da
To execute the avail da
, use the following command:
For obtaining Turing Testnet tokens, please visit the Faucet-Avail
4. Setting Up and Running Tracks
Remove Old Data
Before initiating the setup process, ensure that any old data is removed if present. Use the following command:
Installing Dependencies
After cloning the repository, navigate into the project directory.
Then, tidy up the Go modules to ensure that dependencies are properly managed.
Initiate Sequencer
To initiate the sequencer, execute the following command:
Please Add Da-rpc, Da-keys and Da-type accordingly. Not doing this Can cause Unexpected Errors while Submitting to DA Clients
Specify the DA type using the --daType
flag with one of the following options:
"avail"
for Avail DA"celestia"
for Celestia DA"eigen"
for Eigen DA"mock"
for Mock DA
The DA keys were defined in the section above when we were setting up the DA. Use the Da Keys Accordingly.
Da Key for Mock-Da is Mock-Key
List of DA RPC
For Avail and Celestia, you have to run their nodes locally.
Eigen:-
disperser-holesky.eigenda.xyzAvail:-
http://127.0.0.1:7000Celestia:-
http://127.0.0.1:26658MockDA:-
mock-rpc
Create Keys for Junction
Generate keys for the Junction component using the following command:
Fund Keys for Junction Testnet
Navigate to the Switchyard faucet in the Airchains Discord group and follow the provided steps to obtain Switchyard tokens for funding the keys.
Initiate Prover
Initiate the Prover component using the following command:
Create Station on Junction
Create a station on the Junction component with the specified parameters using the following command:
In the --bootstrapNode
parameter, input your persistence peer. Follow these steps to create your bootstrapNode persistence_peer with the node ID:
Locate the node ID in the
~/.track/config/sequencer.toml
configuration file.Copy the node ID from the configuration file.
Insert the copied node ID into the following string format:
Replace <user-ip>
with your actual IP address and <node_id>
with the copied node ID.
This ensures that your track ID is correctly linked with the corresponding node ID for persistence_peer configuration.
Start Node
To start the node, execute the following command:
This sequence sets up the necessary components for managing tracks effectively. Ensure that each step is executed correctly to ensure smooth operation.
Last updated