deep-stack/laconicd-deprecated
4
0
Fork 0
forked from cerc-io/laconicd-deprecated
Code Pull Requests Activity

changed binary names and source repos in docker files and readmes

Browse Source
This commit is contained in:
SpideyPool192
2022-09-07 12:56:51 +05:30
parent a57e5f4fd9
commit 09d81e4d66
60 changed files with 1930 additions and 1919 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testnet/README.md
+4 -4
View File
@@ -1,11 +1,11 @@
# Testnet
## Setup local chibaclonk multi node testnet in local enviorment
## Setup local laconic multi node testnet in local enviorment
```shell
$ bash multinode_testnet.sh
$ bash multinode_testnet.sh
or
or
# this is create localnet with docker containers
$ make localnet-start
$ make localnet-start
```
testnet/full_node.md
+47 -43
View File
@@ -1,7 +1,6 @@
# Instructions to Run Full Node
Hardware
---
## Hardware
#### Supported
@@ -59,11 +58,11 @@ go version
sudo apt-get install git curl build-essential make jq -y
```
### 3) Install `chibaclonkd`
### 3) Install `laconicd`
```
git clone https://github.com/vulcanize/chiba-clonk.git
cd chiba-clonk
git clone https://github.com/cerc-io/laconicd.git
cd laconicd
git fetch --all
git checkout main
make install
@@ -72,15 +71,15 @@ make install
### 4) Verify your installation
```
chibaclonkd version --long
laconicd version --long
```
On running the above command, you should see a similar response like this. Make sure that the *version* and *commit
hash* are accurate
On running the above command, you should see a similar response like this. Make sure that the _version_ and _commit
hash_ are accurate
```
name: chibaclonkd
server_name: chibaclonkd
name: laconicd
server_name: laconicd
```
### 5) Initialize Node
@@ -88,11 +87,11 @@ server_name: chibaclonkd
**Not required if you have already initialized before**
```
chibaclonkd init <your-node-moniker> --chain-id chibaclonk_81337-2
laconicd init <your-node-moniker> --chain-id laconic_81337-2
```
On running the above command, node will be initialized with default configuration. (config files will be saved in node's
default home directory (~/.chibaclonkd/config)
default home directory (~/.laconicd/config)
NOTE: Backup node and validator keys . You will need to use these keys at a later point in time.
@@ -106,14 +105,14 @@ Use `curl` to download the genesis file
**Replace your **genesis** file with published genesis file**
```shell
# Will be updated
curl {GENESIS_LINK} | jq .result.genesis > ~/.chibaclonkd/config/genesis.json
# Will be updated
curl {GENESIS_LINK} | jq .result.genesis > ~/.laconicd/config/genesis.json
```
Verify sha256 hash of genesis file with the below command
```
jq -S -c -M '' ~/.chibaclonkd/config/genesis.json | shasum -a 256
jq -S -c -M '' ~/.laconicd/config/genesis.json | shasum -a 256
```
genesis sha256 hash should be
@@ -125,11 +124,11 @@ genesis sha256 hash should be
## 2) Update Peers & Seeds in config.toml
```
<!-- Note: don't use peers
<!-- Note: don't use peers
peers="5ad2e6c35f2c84ff3ee31d89a95b34d92cb6afb1@157.230.101.237:26656,defc95b08547b6ef254723ad9621967a7e819020@161.35.223.44:26656" -->
{peers={WILL BE UPDATED}}
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" ~/.chibaclonkd/config/config.toml
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" ~/.laconicd/config/config.toml
```
## 3) Start the Full Node
@@ -139,20 +138,20 @@ sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" ~/.chiba
3.1.1) Create the service file
```
sudo tee /etc/systemd/system/chibaclonkd.service > /dev/null <<EOF
sudo tee /etc/systemd/system/laconicd.service > /dev/null <<EOF
[Unit]
Description=chibaclonkd Daemon
Description=laconicd Daemon
After=network-online.target
[Service]
User=$USER
ExecStart=$(which chibaclonkd) start --gql-playground --gql-server
Restart=always
User=$USER
ExecStart=$(which laconicd) start --gql-playground --gql-server
Restart=always
RestartSec=3
LimitNOFILE=65535
[Install]
WantedBy=multi-user.target
WantedBy=multi-user.target
EOF
```
@@ -160,46 +159,51 @@ EOF
3.1.2) Load service and start
```
sudo systemctl daemon-reload
sudo systemctl enable chibaclonkd
sudo systemctl start chibaclonkd
sudo systemctl daemon-reload
sudo systemctl enable laconicd
sudo systemctl start laconicd
```
3.1.3) Check status of service
```
sudo systemctl status chibaclonkd
sudo systemctl status laconicd
```
`NOTE:`
A helpful command here is `journalctl` that can be used to:
a) check logs
```
a) check logs
journalctl -u chibaclonkd
```
```
journalctl -u laconicd
b) most recent logs
```
```
journalctl -xeu chibaclonkd
b) most recent logs
```
```
c) logs from previous day
```
journalctl -xeu laconicd
journalctl --since "1 day ago" -u chibaclonkd
```
```
c) logs from previous day
d) Check logs with follow flag
```
```
journalctl -f -u chibaclonkd
journalctl --since "1 day ago" -u laconicd
```
```
d) Check logs with follow flag
```
journalctl -f -u laconicd
```
testnet/genesis-validators.md
+47 -47
View File
@@ -1,4 +1,4 @@
# Validator Guide for chibaclonk_81337-4 Testnet
# Validator Guide for laconic_81337-4 Testnet
## Hardware Prerequisites
@@ -66,32 +66,32 @@ go version
---
## Install `chibaclonk`
## Install `laconic`
```sh
git clone https://github.com/vulcanize/chiba-clonk.git
cd chiba-clonk
git clone https://github.com/cerc-io/laconicd.git
cd laconicd
# Checkout main branch
git fetch --all
git checkout main
# Build and install chibaclonk
# Build and install laconic
make install
```
Verify your installation
```sh
chibaclonkd version --long
laconicd version --long
```
On running the above command, you should see a similar response like this. Make sure that the *version* and *commit
hash* are accurate
On running the above command, you should see a similar response like this. Make sure that the _version_ and _commit
hash_ are accurate
```sh
name: chibaclonk
server_name: chibaclonkd
name: laconic
server_name: laconicd
```
---
@@ -102,10 +102,10 @@ server_name: chibaclonkd
```sh
# Initialize the validator node
chibaclonkd init <your-node-moniker> --chain-id chibaclonk_81337-4
laconicd init <your-node-moniker> --chain-id laconic_81337-4
```
Running the above commands will initialize the validator node with default configuration. The config files will be saved in the default location (`~/.chibaclonkd/config`).
Running the above commands will initialize the validator node with default configuration. The config files will be saved in the default location (`~/.laconicd/config`).
**NOTE:** Backup your node and validator keys. You will need to use these keys at a later point in time.
@@ -113,28 +113,28 @@ Running the above commands will initialize the validator node with default confi
## Overwrite Validator Initialization from previous testnet
**Required for `chibaclonk_81337-4`**
**Required for `laconic_81337-4`**
First we have to reset the previous genesis state (only because the `chibaclonk_81337-3` testnet failed) whereafter we can initialize the validator node for `chibaclonk_81337-4`
First we have to reset the previous genesis state (only because the `laconic_81337-3` testnet failed) whereafter we can initialize the validator node for `laconic_81337-4`
```sh
# Stop your node (in case it was still running)
systemctl stop chibaclonkd
systemctl stop laconicd
# Keep a backup of your old validator directory
cp -a ~/.chibaclonkd ~/backup-chibaclonk_81337-2
cp -a ~/.laconicd ~/backup-laconic_81337-2
# Reset the state of your validator
chibaclonkd tendermint unsafe-reset-all --home $HOME/.chibaclonkd
laconicd tendermint unsafe-reset-all --home $HOME/.laconicd
# Remove your previous genesis transactions
rm $HOME/.chibaclonkd/config/gentx/gentx*.json
rm $HOME/.laconicd/config/gentx/gentx*.json
# Overwrite your genesis state with the new chain-id
chibaclonkd init --overwrite <your-node-moniker> --chain-id chibaclonk_81337-4
laconicd init --overwrite <your-node-moniker> --chain-id laconic_81337-4
```
Running the above commands will re-initialize the validator node with default configuration. The config files will be saved in the default location (`~/.chibaclonkd/config`).
Running the above commands will re-initialize the validator node with default configuration. The config files will be saved in the default location (`~/.laconicd/config`).
**NOTE:** Backup your node and validator keys. You will need to use these keys at a later point in time.
@@ -145,13 +145,13 @@ Running the above commands will re-initialize the validator node with default co
If you have participated in a previous testnet and have a mnemonic phrase, use below command to recover your account:
```sh
chibaclonkd keys add <key-name> --recover
laconicd keys add <key-name> --recover
```
To create a new account use:
```sh
chibaclonkd keys add <key-name>
laconicd keys add <key-name>
```
**NOTE:** Save the `mnemonic` and related account details (public key). You will need to use the mnemonic and / or private key to recover accounts at a later point in time.
@@ -163,15 +163,15 @@ chibaclonkd keys add <key-name>
**NOTE:** Don't add more than 12,900 CHK , if you add more than that, your gentx will be ignored.
```sh
chibaclonkd add-genesis-account <key-name> 12900000000000000000000achk --keyring-backend os
laconicd add-genesis-account <key-name> 12900000000000000000000achk --keyring-backend os
```
Create Your `gentx` transaction file
```sh
chibaclonkd gentx <key-name> 12900000000000000000000achk \
--pubkey=$(chibaclonkd tendermint show-validator) \
--chain-id="chibaclonk_81337-4" \
laconicd gentx <key-name> 12900000000000000000000achk \
--pubkey=$(laconicd tendermint show-validator) \
--chain-id="laconic_81337-4" \
--moniker="<your-moniker-name>" \
--website="<your-validator-website>" \
--details="<your-validator-description>" \
@@ -179,31 +179,31 @@ chibaclonkd gentx <key-name> 12900000000000000000000achk \
--commission-rate="0.10" \
--commission-max-rate="0.20" \
--commission-max-change-rate="0.01" \
--min-self-delegation="1"
```
--min-self-delegation="1"
```
**NOTE:**
- `<key-name>` and `chain-id` are required. other flags are optional
- Don't change the amount value while creating your gentx
- Genesis transaction file will be saved in `~/.chibaclonkd/config/gentx` folder
- Genesis transaction file will be saved in `~/.laconicd/config/gentx` folder
---
## Submit Your gentx
Submit your `gentx` file to the [https://github.com/vulcanize/laconic-testnet]() repository in the following format:
Submit your `gentx` file to the [https://github.com/cerc-io/laconic-testnet]() repository in the following format:
`<validator-moniker>-gentx.json`
**NOTE:** (Do NOT use spaces in the file name)
To submit the gentx file, follow the below process:
- Fork the [https://github.com/vulcanize/laconic-testnet]() repository
- Upload your gentx file in the `chibaclonk_81337-4/config/gentxs` folder
- Submit Pull Request to [https://github.com/vulcanize/laconic-testnet]() with name `ADD <your-moniker> gentx`
- Fork the [https://github.com/cerc-io/laconic-testnet]() repository
- Upload your gentx file in the `laconic_81337-4/config/gentxs` folder
- Submit Pull Request to [https://github.com/cerc-io/laconic-testnet]() with name `ADD <your-moniker> gentx`
The genesis file will be published in the `chibaclonk_81337-4/config/` folder within the [https://github.com/vulcanize/laconic-testnet]() repository.
The genesis file will be published in the `laconic_81337-4/config/` folder within the [https://github.com/cerc-io/laconic-testnet]() repository.
# CONTINUE WITH BELOW STEPS ONLY AFTER GENESIS FILE HAS BEEN PUBLISHED
@@ -215,17 +215,17 @@ seeds="<seeds node list here>"
peers="<peers node list here>"
# Update seeds, persistent_peers and prometheus parameters in config.toml
sed -i.bak -e "s/^seeds *=.*/seeds = \"$seeds\"/; s/^persistent_peers *=.*/persistent_peers = \"$peers\"/; s/^prometheus *=.*/prometheus = true/" $HOME/.chibaclonkd/config/config.toml
sed -i.bak -e "s/^seeds *=.*/seeds = \"$seeds\"/; s/^persistent_peers *=.*/persistent_peers = \"$peers\"/; s/^prometheus *=.*/prometheus = true/" $HOME/.laconicd/config/config.toml
# Create systemd validator service
sudo tee /etc/systemd/system/chibaclonkd.service > /dev/null <<EOF
sudo tee /etc/systemd/system/laconicd.service > /dev/null <<EOF
[Unit]
Description=chibaclonkd Daemon
Description=laconicd Daemon
After=network-online.target
[Service]
User=$USER
ExecStart=$(which chibaclonkd) start --mode validator --gql-playground --gql-server --log_level=warn
ExecStart=$(which laconicd) start --mode validator --gql-playground --gql-server --log_level=warn
Restart=always
RestartSec=3
LimitNOFILE=65535
@@ -236,14 +236,14 @@ EOF
#Reload systemd and start the validator node
sudo systemctl daemon-reload
sudo systemctl enable chibaclonkd
sudo systemctl start chibaclonkd
sudo systemctl enable laconicd
sudo systemctl start laconicd
```
Check status of service
```sh
sudo systemctl status chibaclonkd
sudo systemctl status laconicd
```
---
@@ -252,16 +252,16 @@ sudo systemctl status chibaclonkd
```sh
# Check logs
journalctl -u chibaclonkd
journalctl -u laconicd
# Most recent logs
journalctl -xeu chibaclonkd
journalctl -xeu laconicd
# Logs from previous day
journalctl --since "1 day ago" -u chibaclonkd
journalctl --since "1 day ago" -u laconicd
# Check logs with follow flag
journalctl -f -u chibaclonkd
journalctl -f -u laconicd
# Check discovered peers
curl http://localhost:26657/net_info
@@ -270,5 +270,5 @@ curl http://localhost:26657/net_info
curl http://localhost:26657/consensus_state
# Check the sync status of your validator node
chibaclonkd status | jq .SyncInfo
```
laconicd status | jq .SyncInfo
```
testnet/multinode_testnet.sh
+5 -5
View File
@@ -1,7 +1,7 @@
#/bin/sh
# clean the existed chain
rm -rf ~/.testchibaclonk*
rm -rf ~/.testlaconic*
echo "Installing the require tools "
sudo apt-get install git curl build-essential make nohup jq -y
@@ -37,12 +37,12 @@ else
fi
# chain env variables
export DAEMON_HOME=~/.testchibaclonk
export CHAINID=chibaclonk_9000-1
export DAEMON_HOME=~/.testlaconic
export CHAINID=laconic_9000-1
export DENOM=achk
export GH_URL=https://github.com/vulcanize/chiba-clonk.git
export GH_URL=https://github.com/cerc-io/laconicd.git
export CHAIN_VERSION=main
export DAEMON=chibaclonkd
export DAEMON=laconicd
display_usage() {
printf "** Please check the exported values:: **\n Daemon : $DAEMON\n Denom : $DENOM\n ChainID : $CHAINID\n DaemonHome : $DAEMON_HOME\n \n Github URL : $GH_URL\n Chain Version : $CHAIN_VERSION\n"
testnet/validator_node.md
+9 -8
View File
@@ -11,7 +11,7 @@
### 2. Create Account & Get test tokens
```
chibaclonkd keys add <key-name> --keyring-backend test
laconicd keys add <key-name> --keyring-backend test
```
NOTE: Save `mnemonic` and related account details (public key). You will need to use the need mnemonic/private key to
@@ -20,29 +20,30 @@ recover accounts at a later point in time.
##### Get Test tokens from faucet
- Faucet website link will be updated
- 1 CHK = 1 * 10e^18 achk
- 1 CHK = 1 \* 10e^18 achk
### 3.Create Validator
- ##### Check full node sync status
`chibaclonkd status 2>&1 | jq -r ".SyncInfo"`
`laconicd status 2>&1 | jq -r ".SyncInfo"`
`catching_up: false` means node is completely synced
- ##### Create validator
`Note:` Only execute below transaction after complete sync of your full node
`Note:` Only execute below transaction after complete sync of your full node
Please replace `key_name` with your key name, amount with staking amount, validator description and `moniker` also
```
chibaclonkd tx staking create-validator \
laconicd tx staking create-validator \
--amount="AMOUNT" \
--pubkey=$(chibaclonkd tendermint show-validator) \
--pubkey=$(laconicd tendermint show-validator) \
--moniker="my-moniker" \
--website="https://myweb.site" \
--details="description of your validator" \
--chain-id="chibaclonk_81337-2" \
--chain-id="laconic_81337-2" \
--commission-rate="0.10" \
--commission-max-rate="0.20" \
--commission-max-change-rate="0.01" \
@@ -51,4 +52,4 @@ chibaclonkd tx staking create-validator \
--gas-adjustment="1.2" \
--gas-prices="0.025achk" \
--from=<key_name>
```
```