-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #6 from airchains-network/development
Updated Transaction failure errors in DA and Junction codes
- Loading branch information
Showing
15 changed files
with
277 additions
and
134 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,4 +2,6 @@ | |
./accounts/* | ||
./.idea/* | ||
./bin/* | ||
./.tracks/* | ||
./.tracks/* | ||
./.tracks | ||
./build/* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,33 +1,95 @@ | ||
|
||
### Remove old data if present | ||
# Tracks Setup Guide | ||
This guide will help you set up and initialize the Tracks environment. | ||
|
||
## Step 1: Remove Old Data | ||
|
||
If you have previously set up Tracks, remove any old data to ensure a clean environment. | ||
|
||
```shell | ||
sudo rm -rf ~/.tracks | ||
``` | ||
## Step 2: Build the Tracks | ||
|
||
```bash | ||
make build | ||
``` | ||
|
||
## Step 3: Initialize the Tracks | ||
|
||
Initialize the sequencer with the necessary parameters. | ||
|
||
### Init sequencer | ||
```shell | ||
go run cmd/main.go init --daRpc "mock-rpc" --daKey "mockKey" --daType "mock" --moniker "monkey" --stationRpc "http://127.0.0.1:8545" --stationAPI "http://127.0.0.1:8545" --stationType "evm" | ||
daRpc="mock-rpc" | ||
daKey="mockKey" | ||
daType="mock" | ||
moniker="monkey" | ||
stationRpc="http://127.0.0.1:8545" | ||
stationAPI="http://127.0.0.1:8545" | ||
stationType="evm" | ||
|
||
./build/tracks init --daRpc "$daRpc" --daKey "$daKey" --daType "$daType" --moniker "$moniker" --stationRpc "$stationRpc" --stationAPI "$stationAPI" --stationType "$stationType" | ||
``` | ||
|
||
### Create Keys for Junction | ||
## Step 4: Initialize the Prover | ||
|
||
Initialize the prover. Ensure you specify the correct version. | ||
|
||
```shell | ||
go run cmd/main.go keys junction --accountName dummy --accountPath .tracks/junction-accounts/keys | ||
./build/tracks prover v1EVM | ||
``` | ||
OR `Import with mnemonic` | ||
|
||
## Step 5: Create Keys for Junction (If not already created) | ||
|
||
Create keys for the junction account. If the keys are not already created, use the following command: | ||
|
||
```shell | ||
accountName="dummy" | ||
accountPath=".tracks/junction-accounts/keys" | ||
|
||
./build/tracks keys junction --accountName "$accountName" --accountPath "$accountPath" | ||
``` | ||
|
||
Alternatively, you can import an account using a mnemonic: | ||
|
||
```shell | ||
go run cmd/main.go keys import --accountName dummy --accountPath .tracks/junction-accounts/keys --mnemonic "huge bounce thing settle diet mobile fruit skill call roast offer soap other upset toward sand dress moral pole smile limb round vacant ecology" | ||
accountName="dummy" | ||
accountPath=".tracks/junction-accounts/keys" | ||
mnemonic="huge bounce thing settle diet mobile fruit skill call roast offer soap other upset toward sand dress moral pole smile limb round vacant ecology" | ||
|
||
./build/tracks keys import --accountName "$accountName" --accountPath "$accountPath" --mnemonic "$mnemonic" | ||
``` | ||
|
||
### Init Prover | ||
## Step 6: Fund the wallet | ||
- Join [Airchains Discord ](https://discord.gg/airchains) | ||
- Goto `switchyard-faucet-bot` channel | ||
- Type `$faucet <your_address>`, you will get 2AMF soon. | ||
|
||
## Step 7: Create a Station on Junction | ||
|
||
Create a station on the junction with the necessary parameters. | ||
> NOTE: don't forget to replace `accountAddressArray` with the addresses you want to make track member. Replace it with your new address | ||
```shell | ||
go run cmd/main.go prover v1EVM | ||
``` | ||
### Create station on junction | ||
```sh | ||
go run cmd/main.go create-station --tracks air1l9gjw7yklpx9tn74j328qwlmf7377rhle9hryc --accountName dummy --accountPath .tracks/junction-accounts/keys --jsonRPC "https://junction-testnet-rpc.synergynodes.com/" --info "EVM Track" --bootstrapNode "/ip4/192.168.1.24/tcp/2300/p2p/12D3KooWFoN66sCWotff1biUcnBE2vRTmYJRHJqZy27x1EpBB6AM" | ||
accountAddressArray="air1knf2an5efl8d9t5w75uds4ty8uj0scxx9yg783" #! replace it with your address | ||
accountName="dummy" | ||
accountPath=".tracks/junction-accounts/keys" | ||
#jsonRPC="http://0.0.0.0:26657" # localhost testing | ||
jsonRPC="https://junction-testnet-rpc.synergynodes.com/" # junction testnet | ||
bootstrapNode="/ip4/192.168.1.24/tcp/2300/p2p/12D3KooWFoN66sCWotff1biUcnBE2vRTmYJRHJqZy27x1EpBB6AM" | ||
info="EVM Track" | ||
|
||
./build/tracks create-station --tracks "$accountAddressArray" --accountName "$accountName" --accountPath "$accountPath" --jsonRPC "$jsonRPC" --info "$info" --bootstrapNode "$bootstrapNode" | ||
``` | ||
|
||
### start node | ||
## Step 8: Start the Tracks | ||
|
||
Finally, start the node to begin interacting with the Tracks blockchain. | ||
|
||
```shell | ||
go run cmd/main.go start | ||
``` | ||
./build/tracks start | ||
``` | ||
|
||
## Troubleshooting | ||
|
||
If you encounter any issues during setup, refer to [official documentation](https://docs.airchains.io/rollups/evm-zk-rollup/system-requirements) or reach out [Airchains discord](https://discord.gg/airchains) for support. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.