22 |
23 | * ⭕️ **Reset operator keys** - this will reset all your saved validator entries.
24 | * 📃 **List operator keys** - will list your saved validator entries
25 |
26 |
List of saved operators
27 |
28 | * 📃 **List all operators** - will list all oracle operators sorted by missed oracle votes in current cycle
29 |
30 |
31 |
32 | {% hint style="info" %}
33 | To reduce spam alerts with each status change, you will be notified only if your validator exceeds threshold that is set to: **16** missed oracle votes per **10** minutes (That's about **86%** fail ratio)
34 | {% endhint %}
35 |
36 | That's it! You are all set! Here is some example of the notification from the bot.
37 |
38 |
39 |
40 | From kjnodes with :heart:
41 |
--------------------------------------------------------------------------------
/docs/bots/telegram-proposal-bot.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: >-
3 | Don't miss any chain proposals with our free Telegram bot. Proposal bot will
4 | notify its subscribers every time when new proposal kicks in.
5 | ---
6 |
7 | # Telegram Proposal Bot
8 |
9 | ## Intro
10 |
11 | Kjnodes team have built bots to keep validators notified when there is a new proposal on the chain. To distinguish mainnet from testnet we have created two separate bots that can be found by following links provided below.
12 |
13 | [🤖 Mainnet Proposal Bot](https://t.me/kjnodes\_proposal\_bot) | **Supported chains**: 17 | **Users**: 140 | **Active subscriptions**: 226
14 |
15 | [🤖 Testnet Proposal bot](https://t.me/kjnodes\_testnet\_proposal\_bot) | **Supported chains**: 27 | **Users**: 421 | **Active subscriptions**: 1331
16 |
17 | ## How to use
18 |
19 | To start using the bot type `/start` command and choose the networks in which you want to get notified. 🥝 icon will tell you which network notifications are turned on.
20 |
21 |
Bot menu
22 |
23 | {% hint style="info" %}
24 | Currently bots support chains where we operate our own RPC endpoints. List of supported chains can be found in the bot menu.
25 | {% endhint %}
26 |
27 | That's it! You are all set! Here is some example of the notification from the bot.
28 |
29 |
Bot notification message
30 |
31 | From kjnodes with :heart:
32 |
--------------------------------------------------------------------------------
/docs/mainnet/agoric/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: agoric-upgrade-9
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 10340372 | 17 minutes | [snapshot (3.38 GB)](https://snapshots.kjnodes.com/agoric/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop agd
29 | cp $HOME/.agoric/data/priv_validator_state.json $HOME/.agoric/priv_validator_state.json.backup
30 | rm -rf $HOME/.agoric/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/agoric/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.agoric
37 | mv $HOME/.agoric/priv_validator_state.json.backup $HOME/.agoric/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start agd && sudo journalctl -u agd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/agoric/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: agoric-3 | **Latest Version Tag**: pismoC | **Custom Port**: 127
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf pismoC
22 | git clone https://github.com/Agoric/agoric-sdk.git pismoC
23 | cd pismoC
24 | git checkout pismoC
25 |
26 | # Install and build Agoric Javascript packages
27 | yarn install && yarn build
28 |
29 | # Install and build Agoric Cosmos SDK support
30 | (cd packages/cosmic-swingset && make)
31 |
32 | # Prepare binaries for Cosmovisor
33 | mkdir -p $HOME/.agoric/cosmovisor/upgrades/agoric-upgrade-9/bin
34 | ln -s $HOME/pismoC/bin/agd $HOME/.agoric/cosmovisor/upgrades/agoric-upgrade-9/bin/agd
35 | ```
36 |
37 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
38 |
--------------------------------------------------------------------------------
/docs/mainnet/aura/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **05:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: aura_v0.4.5
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1292071 | 2 days | [snapshot (0.61 GB)](https://snapshots.kjnodes.com/aura/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop aurad
29 | cp $HOME/.aura/data/priv_validator_state.json $HOME/.aura/priv_validator_state.json.backup
30 | rm -rf $HOME/.aura/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/aura/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.aura
37 | mv $HOME/.aura/priv_validator_state.json.backup $HOME/.aura/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start aurad && sudo journalctl -u aurad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/aura/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: xstaxy-1 | **Latest Version Tag**: aura_v0.4.5 | **Custom Port**: 117
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf aura
22 | git clone https://github.com/aura-nw/aura.git
23 | cd aura
24 | git checkout aura_v0.4.5
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.aura/cosmovisor/upgrades/v0.4.5/bin
31 | mv build/aurad $HOME/.aura/cosmovisor/upgrades/v0.4.5/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/bitcanna/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **05:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: vigorous-grow-huckleberry
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 8998824 | 5 hours | [snapshot (0.77 GB)](https://snapshots.kjnodes.com/bitcanna/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop bcnad
29 | cp $HOME/.bcna/data/priv_validator_state.json $HOME/.bcna/priv_validator_state.json.backup
30 | rm -rf $HOME/.bcna/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/bitcanna/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.bcna
37 | mv $HOME/.bcna/priv_validator_state.json.backup $HOME/.bcna/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start bcnad && sudo journalctl -u bcnad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/bitcanna/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: bitcanna-1 | **Latest Version Tag**: v1.7.0 | **Custom Port**: 142
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf bcna
22 | git clone https://github.com/BitCannaGlobal/bcna.git
23 | cd bcna
24 | git checkout v1.7.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.bcna/cosmovisor/upgrades/vigorous-grow-huckleberry/bin
31 | mv build/bcnad $HOME/.bcna/cosmovisor/upgrades/vigorous-grow-huckleberry/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/composable/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **10:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v2.3.5
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 140848 | 22 minutes | [snapshot (0.2 GB)](https://snapshots.kjnodes.com/composable/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop banksyd
29 | cp $HOME/.banksy/data/priv_validator_state.json $HOME/.banksy/priv_validator_state.json.backup
30 | rm -rf $HOME/.banksy/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/composable/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.banksy
37 | mv $HOME/.banksy/priv_validator_state.json.backup $HOME/.banksy/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start banksyd && sudo journalctl -u banksyd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/composable/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: centauri-1 | **Latest Version Tag**: v2.3.5 | **Custom Port**: 159
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for centauri-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/mainnet/cosmoshub/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v9-lambda
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 15726516 | 5 hours | [snapshot (4.27 GB)](https://snapshots.kjnodes.com/cosmoshub/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop gaiad
29 | cp $HOME/.gaia/data/priv_validator_state.json $HOME/.gaia/priv_validator_state.json.backup
30 | rm -rf $HOME/.gaia/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/cosmoshub/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.gaia
37 | mv $HOME/.gaia/priv_validator_state.json.backup $HOME/.gaia/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start gaiad && sudo journalctl -u gaiad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/cosmoshub/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: cosmoshub-4 | **Latest Version Tag**: v10.0.0 | **Custom Port**: 134
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf gaia
22 | git clone https://github.com/cosmos/gaia.git
23 | cd gaia
24 | git checkout v10.0.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.gaia/cosmovisor/upgrades/v10/bin
31 | mv build/gaiad $HOME/.gaia/cosmovisor/upgrades/v10/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/gitopia/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v2.1.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1425497 | 33 minutes | [snapshot (1.48 GB)](https://snapshots.kjnodes.com/gitopia/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop gitopiad
29 | cp $HOME/.gitopia/data/priv_validator_state.json $HOME/.gitopia/priv_validator_state.json.backup
30 | rm -rf $HOME/.gitopia/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/gitopia/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.gitopia
37 | mv $HOME/.gitopia/priv_validator_state.json.backup $HOME/.gitopia/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start gitopiad && sudo journalctl -u gitopiad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/gitopia/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: gitopia | **Latest Version Tag**: v2.1.1 | **Custom Port**: 141
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for gitopia!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/mainnet/gravitybridge/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **03:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: pleiades2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 6654499 | 1 hours | [snapshot (1.49 GB)](https://snapshots.kjnodes.com/gravitybridge/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop gravityd
29 | cp $HOME/.gravity/data/priv_validator_state.json $HOME/.gravity/priv_validator_state.json.backup
30 | rm -rf $HOME/.gravity/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/gravitybridge/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.gravity
37 | mv $HOME/.gravity/priv_validator_state.json.backup $HOME/.gravity/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start gravityd && sudo journalctl -u gravityd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/gravitybridge/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: gravity-bridge-3 | **Latest Version Tag**: v1.9.0 | **Custom Port**: 26
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Download project binaries
20 | mkdir -p $HOME/.gravity/cosmovisor/upgrades/orion/bin
21 | wget -O $HOME/.gravity/cosmovisor/upgrades/orion/bin/gravityd https://github.com/Gravity-Bridge/Gravity-Bridge/releases/download/v1.9.0/gravity-linux-amd64
22 | wget -O $HOME/.gravity/cosmovisor/upgrades/orion/bin/gbt https://github.com/Gravity-Bridge/Gravity-Bridge/releases/download/v1.9.0/gbt
23 | chmod +x $HOME/.gravity/cosmovisor/upgrades/orion/bin/*
24 | ```
25 |
26 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
27 |
--------------------------------------------------------------------------------
/docs/mainnet/humans/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **10:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 249843 | 37 minutes | [snapshot (0.23 GB)](https://snapshots.kjnodes.com/humans/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop humansd
29 | cp $HOME/.humansd/data/priv_validator_state.json $HOME/.humansd/priv_validator_state.json.backup
30 | rm -rf $HOME/.humansd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/humans/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.humansd
37 | mv $HOME/.humansd/priv_validator_state.json.backup $HOME/.humansd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start humansd && sudo journalctl -u humansd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/humans/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: humans_1089-1 | **Latest Version Tag**: v1.0.0 | **Custom Port**: 122
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for humans_1089-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/mainnet/jackal/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **00:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: recovery
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3151781 | 3 hours | [snapshot (1.04 GB)](https://snapshots.kjnodes.com/jackal/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop canined
29 | cp $HOME/.canine/data/priv_validator_state.json $HOME/.canine/priv_validator_state.json.backup
30 | rm -rf $HOME/.canine/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/jackal/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.canine
37 | mv $HOME/.canine/priv_validator_state.json.backup $HOME/.canine/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start canined && sudo journalctl -u canined -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/jackal/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: jackal-1 | **Latest Version Tag**: v2.0.1 | **Custom Port**: 137
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf canine-chain
22 | git clone https://github.com/JackalLabs/canine-chain.git
23 | cd canine-chain
24 | git checkout v2.0.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.canine/cosmovisor/upgrades/recovery/bin
31 | mv build/canined $HOME/.canine/cosmovisor/upgrades/recovery/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/juno/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **09:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v14
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 8487422 | 3 hours | [snapshot (5.76 GB)](https://snapshots.kjnodes.com/juno/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop junod
29 | cp $HOME/.juno/data/priv_validator_state.json $HOME/.juno/priv_validator_state.json.backup
30 | rm -rf $HOME/.juno/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/juno/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.juno
37 | mv $HOME/.juno/priv_validator_state.json.backup $HOME/.juno/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start junod && sudo journalctl -u junod -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/juno/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: juno-1 | **Latest Version Tag**: v14.0.0 | **Custom Port**: 157
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf juno
22 | git clone https://github.com/CosmosContracts/juno.git
23 | cd juno
24 | git checkout v14.0.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.juno/cosmovisor/upgrades/v14/bin
31 | mv bin/junod $HOME/.juno/cosmovisor/upgrades/v14/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/kujira/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **00:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.8.4
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 11641883 | 4 hours | [snapshot (4.41 GB)](https://snapshots.kjnodes.com/kujira/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop kujirad
29 | cp $HOME/.kujira/data/priv_validator_state.json $HOME/.kujira/priv_validator_state.json.backup
30 | rm -rf $HOME/.kujira/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/kujira/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.kujira
37 | mv $HOME/.kujira/priv_validator_state.json.backup $HOME/.kujira/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start kujirad && sudo journalctl -u kujirad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/kujira/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: kaiyo-1 | **Latest Version Tag**: v0.8.7 | **Custom Port**: 113
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf core
22 | git clone https://github.com/Team-Kujira/core.git
23 | cd core
24 | git checkout v0.8.7
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.kujira/cosmovisor/upgrades/v0.8.4/bin
31 | mv build/kujirad $HOME/.kujira/cosmovisor/upgrades/v0.8.4/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/mars/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **06:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1900513 | 2 hours | [snapshot (0.84 GB)](https://snapshots.kjnodes.com/mars/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop marsd
29 | cp $HOME/.mars/data/priv_validator_state.json $HOME/.mars/priv_validator_state.json.backup
30 | rm -rf $HOME/.mars/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/mars/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.mars
37 | mv $HOME/.mars/priv_validator_state.json.backup $HOME/.mars/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start marsd && sudo journalctl -u marsd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/mars/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: mars-1 | **Latest Version Tag**: v1.0.2 | **Custom Port**: 145
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for mars-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/mainnet/migaloo/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1826807 | 3 hours | [snapshot (0.82 GB)](https://snapshots.kjnodes.com/migaloo/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop migalood
29 | cp $HOME/.migalood/data/priv_validator_state.json $HOME/.migalood/priv_validator_state.json.backup
30 | rm -rf $HOME/.migalood/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/migaloo/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.migalood
37 | mv $HOME/.migalood/priv_validator_state.json.backup $HOME/.migalood/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start migalood && sudo journalctl -u migalood -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/migaloo/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: migaloo-1 | **Latest Version Tag**: v2.0.5 | **Custom Port**: 149
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf migaloo-chain
22 | git clone https://github.com/White-Whale-Defi-Platform/migaloo-chain.git
23 | cd migaloo-chain
24 | git checkout v2.0.5
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.migalood/cosmovisor/upgrades/v2/bin
31 | mv bin/migalood $HOME/.migalood/cosmovisor/upgrades/v2/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/nois/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **08:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.3
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 2914130 | 2 hours | [snapshot (1.89 GB)](https://snapshots.kjnodes.com/nois/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop noisd
29 | cp $HOME/.noisd/data/priv_validator_state.json $HOME/.noisd/priv_validator_state.json.backup
30 | rm -rf $HOME/.noisd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/nois/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.noisd
37 | mv $HOME/.noisd/priv_validator_state.json.backup $HOME/.noisd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start noisd && sudo journalctl -u noisd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/nois/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: nois-1 | **Latest Version Tag**: v1.0.3 | **Custom Port**: 151
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for nois-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/mainnet/nolus/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **03:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.4.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 339773 | 1 hours | [snapshot (0.27 GB)](https://snapshots.kjnodes.com/nolus/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop nolusd
29 | cp $HOME/.nolus/data/priv_validator_state.json $HOME/.nolus/priv_validator_state.json.backup
30 | rm -rf $HOME/.nolus/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/nolus/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.nolus
37 | mv $HOME/.nolus/priv_validator_state.json.backup $HOME/.nolus/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start nolusd && sudo journalctl -u nolusd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/nolus/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: pirin-1 | **Latest Version Tag**: v0.4.0 | **Custom Port**: 143
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf nolus-core
22 | git clone https://github.com/Nolus-Protocol/nolus-core.git
23 | cd nolus-core
24 | git checkout v0.4.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.nolus/cosmovisor/upgrades/v0.4.0/bin
31 | mv target/release/nolusd $HOME/.nolus/cosmovisor/upgrades/v0.4.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/osmosis/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **02:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v15
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 10097240 | 1 hours | [snapshot (13.33 GB)](https://snapshots.kjnodes.com/osmosis/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop osmosisd
29 | cp $HOME/.osmosisd/data/priv_validator_state.json $HOME/.osmosisd/priv_validator_state.json.backup
30 | rm -rf $HOME/.osmosisd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/osmosis/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.osmosisd
37 | mv $HOME/.osmosisd/priv_validator_state.json.backup $HOME/.osmosisd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start osmosisd && sudo journalctl -u osmosisd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/osmosis/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: osmosis-1 | **Latest Version Tag**: v15.0.0 | **Custom Port**: 129
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf osmosis
22 | git clone https://github.com/osmosis-labs/osmosis.git
23 | cd osmosis
24 | git checkout v15.0.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.osmosisd/cosmovisor/upgrades/v15/bin
31 | mv build/osmosisd $HOME/.osmosisd/cosmovisor/upgrades/v15/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/paloma/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **06:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.1.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1932537 | 4 hours | [snapshot (0.89 GB)](https://snapshots.kjnodes.com/paloma/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop palomad
29 | cp $HOME/.paloma/data/priv_validator_state.json $HOME/.paloma/priv_validator_state.json.backup
30 | rm -rf $HOME/.paloma/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/paloma/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.paloma
37 | mv $HOME/.paloma/priv_validator_state.json.backup $HOME/.paloma/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start palomad && sudo journalctl -u palomad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/paloma/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: messenger | **Latest Version Tag**: v1.1.0 | **Custom Port**: 110
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf paloma
22 | git clone https://github.com/palomachain/paloma.git
23 | cd paloma
24 | git checkout v1.1.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.paloma/cosmovisor/upgrades/v1.1.0/bin
31 | mv build/palomad $HOME/.paloma/cosmovisor/upgrades/v1.1.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/quasar/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | Quasar (pronounced QWAY-ZAR) is a decentralized appchain enabling interchain digital asset management.
6 |
7 | **Chain ID**: quasar-1 | **Latest Version Tag**: v0.1.1 | **Wasm**: ON
8 |
9 | [Website](https://www.quasar.fi) | [Discord](https://discord.gg/quasarfi) | [Twitter](https://twitter.com/QuasarFi)
10 |
11 |
12 |
13 | Subscribe to our free [🤖 Mainnet Proposal Bot](https://t.me/kjnodes_proposal_bot) to never miss upcoming proposals
14 |
15 |
16 | ## Chain explorer
17 | [https://explorer.kjnodes.com/quasar](https://explorer.kjnodes.com/quasar)
18 |
19 | ## Public endpoints
20 |
21 | * api: [https://quasar.api.kjnodes.com](https://quasar.api.kjnodes.com)
22 | * rpc: [https://quasar.rpc.kjnodes.com](https://quasar.rpc.kjnodes.com)
23 | * grpc: quasar.grpc.kjnodes.com:14890
24 |
25 | ## Peering
26 |
27 | **state-sync**
28 |
29 | ```text
30 | d9bfa29e0cf9c4ce0cc9c26d98e5d97228f93b0b@quasar.rpc.kjnodes.com:14856
31 | ```
32 |
33 | **seed-node**
34 |
35 | ```text
36 | 400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@quasar.rpc.kjnodes.com:14859
37 | ```
38 |
39 | **addrbook**
40 | ```bash
41 | curl -Ls https://snapshots.kjnodes.com/quasar/addrbook.json > $HOME/.quasarnode/config/addrbook.json
42 | ```
43 |
44 | **live-peers** (10)
45 | ```bash
46 | peers="bae51539de7b7b7ac784b4c7dc0bc6c005b4f593@65.109.115.226:18256,89757803f40da51678451735445ad40d5b15e059@169.155.169.149:26656,a40e1d5f63fad9e14edb9c95458b27f3c1de858c@116.203.236.246:26618,a286b35c9e9626cc7b780120ebe4afa883c059ce@144.76.40.53:18256,97e4468ac589eac505a800411c635b14511a61bb@134.65.195.240:26656,471518432477e31ea348af246c0b54095d41352c@134.65.195.144:26656,c124ce0b508e8b9ed1c5b6957f362225659b5343@134.65.193.11:26656,fd0bd2366d5941580042cfc6444b9aea12363764@5.78.95.218:26656,d7ea38275af96271fd66194dad3951ef38b8ba7c@193.70.33.64:18256,d9bfa29e0cf9c4ce0cc9c26d98e5d97228f93b0b@65.109.88.38:14856"
47 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/.quasarnode/config/config.toml
48 | ```
49 |
--------------------------------------------------------------------------------
/docs/mainnet/quasar/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.1.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1289586 | 3 hours | [snapshot (0.69 GB)](https://snapshots.kjnodes.com/quasar/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop quasarnoded
29 | cp $HOME/.quasarnode/data/priv_validator_state.json $HOME/.quasarnode/priv_validator_state.json.backup
30 | rm -rf $HOME/.quasarnode/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/quasar/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.quasarnode
37 | mv $HOME/.quasarnode/priv_validator_state.json.backup $HOME/.quasarnode/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start quasarnoded && sudo journalctl -u quasarnoded -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/quasar/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: quasar-1 | **Latest Version Tag**: v0.1.1 | **Custom Port**: 148
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for quasar-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/mainnet/quicksilver/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **02:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.2.10
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 2378217 | 2 hours | [snapshot (1.26 GB)](https://snapshots.kjnodes.com/quicksilver/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop quicksilverd
29 | cp $HOME/.quicksilverd/data/priv_validator_state.json $HOME/.quicksilverd/priv_validator_state.json.backup
30 | rm -rf $HOME/.quicksilverd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/quicksilver/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.quicksilverd
37 | mv $HOME/.quicksilverd/priv_validator_state.json.backup $HOME/.quicksilverd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start quicksilverd && sudo journalctl -u quicksilverd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/quicksilver/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: quicksilver-2 | **Latest Version Tag**: v1.2.14 | **Custom Port**: 111
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf quicksilver
22 | git clone https://github.com/ingenuity-build/quicksilver.git
23 | cd quicksilver
24 | git checkout v1.2.14
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.quicksilverd/cosmovisor/upgrades/v1.2.10/bin
31 | mv build/quicksilverd $HOME/.quicksilverd/cosmovisor/upgrades/v1.2.10/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/rebus/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **02:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.3.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 6261134 | 3 hours | [snapshot (1.78 GB)](https://snapshots.kjnodes.com/rebus/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop rebusd
29 | cp $HOME/.rebusd/data/priv_validator_state.json $HOME/.rebusd/priv_validator_state.json.backup
30 | rm -rf $HOME/.rebusd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/rebus/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.rebusd
37 | mv $HOME/.rebusd/priv_validator_state.json.backup $HOME/.rebusd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start rebusd && sudo journalctl -u rebusd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/rebus/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: reb_1111-1 | **Latest Version Tag**: v0.3.0 | **Custom Port**: 21
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf rebus.core
22 | git clone https://github.com/rebuschain/rebus.core.git
23 | cd rebus.core
24 | git checkout v0.3.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.rebusd/cosmovisor/upgrades/v0.3.0/bin
31 | mv build/rebusd $HOME/.rebusd/cosmovisor/upgrades/v0.3.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/stargaze/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **09:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v9
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 8439209 | 2 hours | [snapshot (2.37 GB)](https://snapshots.kjnodes.com/stargaze/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop starsd
29 | cp $HOME/.starsd/data/priv_validator_state.json $HOME/.starsd/priv_validator_state.json.backup
30 | rm -rf $HOME/.starsd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/stargaze/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.starsd
37 | mv $HOME/.starsd/priv_validator_state.json.backup $HOME/.starsd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start starsd && sudo journalctl -u starsd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/stargaze/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: stargaze-1 | **Latest Version Tag**: v9.0.0 | **Custom Port**: 158
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf stargaze
22 | git clone https://github.com/public-awesome/stargaze.git
23 | cd stargaze
24 | git checkout v9.0.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.starsd/cosmovisor/upgrades/v9/bin
31 | mv bin/starsd $HOME/.starsd/cosmovisor/upgrades/v9/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/stride/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **01:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v9
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 4115801 | 2 hours | [snapshot (5.63 GB)](https://snapshots.kjnodes.com/stride/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop strided
29 | cp $HOME/.stride/data/priv_validator_state.json $HOME/.stride/priv_validator_state.json.backup
30 | rm -rf $HOME/.stride/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/stride/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.stride
37 | mv $HOME/.stride/priv_validator_state.json.backup $HOME/.stride/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start strided && sudo journalctl -u strided -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/stride/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: stride-1 | **Latest Version Tag**: v9.2.1 | **Custom Port**: 116
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf stride
22 | git clone https://github.com/Stride-Labs/stride.git
23 | cd stride
24 | git checkout v9.2.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.stride/cosmovisor/upgrades/v9/bin
31 | mv build/strided $HOME/.stride/cosmovisor/upgrades/v9/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/teritori/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **01:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.4.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3811427 | 3 hours | [snapshot (1.59 GB)](https://snapshots.kjnodes.com/teritori/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop teritorid
29 | cp $HOME/.teritorid/data/priv_validator_state.json $HOME/.teritorid/priv_validator_state.json.backup
30 | rm -rf $HOME/.teritorid/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/teritori/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.teritorid
37 | mv $HOME/.teritorid/priv_validator_state.json.backup $HOME/.teritorid/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start teritorid && sudo journalctl -u teritorid -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/teritori/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: teritori-1 | **Latest Version Tag**: v1.4.0 | **Custom Port**: 119
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf teritori-chain
22 | git clone https://github.com/TERITORI/teritori-chain.git
23 | cd teritori-chain
24 | git checkout v1.4.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.teritorid/cosmovisor/upgrades/v1.4.0/bin
31 | mv build/teritorid $HOME/.teritorid/cosmovisor/upgrades/v1.4.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/umee/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | The most programmable, safety-first, autonomous lending algorithm built as a blockchain. Umee is reshaping the global debt markets in Web3.
6 |
7 | **Chain ID**: umee-1 | **Latest Version Tag**: v5.0.1 | **Wasm**: ON
8 |
9 | [Website](https://umee.cc) | [Discord](https://discord.gg/umee) | [Twitter](https://twitter.com/Umee_CrossChain)
10 |
11 |
12 |
13 | Subscribe to our free [🤖 Mainnet Proposal Bot](https://t.me/kjnodes_proposal_bot) to never miss upcoming proposals
14 |
15 |
16 | ## Chain explorer
17 | [https://explorer.kjnodes.com/umee](https://explorer.kjnodes.com/umee)
18 |
19 | ## Public endpoints
20 |
21 | * api: [https://umee.api.kjnodes.com](https://umee.api.kjnodes.com)
22 | * rpc: [https://umee.rpc.kjnodes.com](https://umee.rpc.kjnodes.com)
23 | * grpc: umee.grpc.kjnodes.com:16290
24 |
25 | ## Peering
26 |
27 | **state-sync**
28 |
29 | ```text
30 | d9bfa29e0cf9c4ce0cc9c26d98e5d97228f93b0b@umee.rpc.kjnodes.com:16256
31 | ```
32 |
33 | **seed-node**
34 |
35 | ```text
36 | 400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@umee.rpc.kjnodes.com:16259
37 | ```
38 |
39 | **addrbook**
40 | ```bash
41 | curl -Ls https://snapshots.kjnodes.com/umee/addrbook.json > $HOME/.umee/config/addrbook.json
42 | ```
43 |
44 | **live-peers** (0)
45 | ```bash
46 | peers=""
47 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/.umee/config/config.toml
48 | ```
49 |
--------------------------------------------------------------------------------
/docs/mainnet/umee/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **11:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**:
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | | | [snapshot ()](https://snapshots.kjnodes.com/umee/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop umeed
29 | cp $HOME/.umee/data/priv_validator_state.json $HOME/.umee/priv_validator_state.json.backup
30 | rm -rf $HOME/.umee/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/umee/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.umee
37 | mv $HOME/.umee/priv_validator_state.json.backup $HOME/.umee/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start umeed && sudo journalctl -u umeed -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/umee/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: umee-1 | **Latest Version Tag**: v5.0.1 | **Custom Port**: 162
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf umee
22 | git clone https://github.com/umee-network/umee.git
23 | cd umee
24 | git checkout v5.0.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.umee/cosmovisor/upgrades/v5.0/bin
31 | mv build/umeed $HOME/.umee/cosmovisor/upgrades/v5.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/uptick/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **01:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.2.8
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1198073 | 3 hours | [snapshot (0.77 GB)](https://snapshots.kjnodes.com/uptick/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop uptickd
29 | cp $HOME/.uptickd/data/priv_validator_state.json $HOME/.uptickd/priv_validator_state.json.backup
30 | rm -rf $HOME/.uptickd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/uptick/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.uptickd
37 | mv $HOME/.uptickd/priv_validator_state.json.backup $HOME/.uptickd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start uptickd && sudo journalctl -u uptickd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/uptick/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: uptick_117-1 | **Latest Version Tag**: v0.2.8 | **Custom Port**: 115
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf uptick
22 | git clone https://github.com/UptickNetwork/uptick.git
23 | cd uptick
24 | git checkout v0.2.8
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.uptickd/cosmovisor/upgrades/v0.2.8/bin
31 | mv build/uptickd $HOME/.uptickd/cosmovisor/upgrades/v0.2.8/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/mainnet/whitewhale/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 201640 | 7 minutes | [snapshot (1.79 GB)](https://snapshots.kjnodes.com/whitewhale/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop migalood
29 | cp $HOME/.migalood/data/priv_validator_state.json $HOME/.migalood/priv_validator_state.json.backup
30 | rm -rf $HOME/.migalood/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/whitewhale/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.migalood
37 | mv $HOME/.migalood/priv_validator_state.json.backup $HOME/.migalood/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start migalood && sudo journalctl -u migalood -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/mainnet/whitewhale/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: migaloo-1 | **Latest Version Tag**: v1.0.0 | **Custom Port**: 49
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for migaloo-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/agoric/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: agorictest-upgrade-10
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 115638 | 23 minutes | [snapshot (0.32 GB)](https://snapshots.kjnodes.com/agoric-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop agd
29 | cp $HOME/.agoric/data/priv_validator_state.json $HOME/.agoric/priv_validator_state.json.backup
30 | rm -rf $HOME/.agoric/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/agoric-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.agoric
37 | mv $HOME/.agoric/priv_validator_state.json.backup $HOME/.agoric/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start agd && sudo journalctl -u agd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/agoric/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: agoric-emerynet-8 | **Latest Version Tag**: mainnet1B-rc3 | **Custom Port**: 127
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf mainnet1B-rc3
22 | git clone https://github.com/Agoric/agoric-sdk.git mainnet1B-rc3
23 | cd mainnet1B-rc3
24 | git checkout mainnet1B-rc3
25 |
26 | # Install and build Agoric Javascript packages
27 | yarn install && yarn build
28 |
29 | # Install and build Agoric Cosmos SDK support
30 | (cd packages/cosmic-swingset && make)
31 |
32 | # Prepare binaries for Cosmovisor
33 | mkdir -p $HOME/.agoric/cosmovisor/upgrades/agorictest-upgrade-10/bin
34 | ln -s $HOME/mainnet1B-rc3/bin/agd $HOME/.agoric/cosmovisor/upgrades/agorictest-upgrade-10/bin/agd
35 | ```
36 |
37 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
38 |
--------------------------------------------------------------------------------
/docs/testnet/agoricdev/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | Agoric is an interoperable Proof-of-Stake chain in the Cosmos ecosystem. Agoric JavaScript smart contract platform enables 15M+ developers across the globe to rapidly build and deploy dapps on-chain.
6 |
7 | **Chain ID**: agoricdev-17 | **Latest Version Tag**: pismoC | **Wasm**: OFF
8 |
9 | [Website](https://agoric.com) | [Discord](https://discord.com/invite/qDW8DRes4s) | [Twitter](https://twitter.com/agoric)
10 |
11 |
12 |
13 | Subscribe to our free [🤖 Testnet Proposal Bot](https://t.me/kjnodes_testnet_proposal_bot) to never miss upcoming proposals
14 |
15 |
16 | ## Chain explorer
17 | [https://explorer.kjnodes.com/agoricdev-testnet](https://explorer.kjnodes.com/agoricdev-testnet)
18 |
19 | ## Public endpoints
20 |
21 | * api: [https://agoricdev-testnet.api.kjnodes.com](https://agoricdev-testnet.api.kjnodes.com)
22 | * rpc: [https://agoricdev-testnet.rpc.kjnodes.com](https://agoricdev-testnet.rpc.kjnodes.com)
23 | * grpc: agoricdev-testnet.grpc.kjnodes.com:14090
24 |
25 | ## Peering
26 |
27 | **state-sync**
28 |
29 | ```text
30 | d5519e378247dfb61dfe90652d1fe3e2b3005a5b@agoricdev-testnet.rpc.kjnodes.com:14656
31 | ```
32 |
33 | **seed-node**
34 |
35 | ```text
36 | 3f472746f46493309650e5a033076689996c8881@agoricdev-testnet.rpc.kjnodes.com:14659
37 | ```
38 |
39 | **addrbook**
40 | ```bash
41 | curl -Ls https://snapshots.kjnodes.com/agoricdev-testnet/addrbook.json > $HOME/.agoric/config/addrbook.json
42 | ```
43 |
44 | **live-peers** (0)
45 | ```bash
46 | peers=""
47 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/.agoric/config/config.toml
48 | ```
49 |
--------------------------------------------------------------------------------
/docs/testnet/agoricdev/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**:
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | | | [snapshot ()](https://snapshots.kjnodes.com/agoricdev-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop agd
29 | cp $HOME/.agoric/data/priv_validator_state.json $HOME/.agoric/priv_validator_state.json.backup
30 | rm -rf $HOME/.agoric/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/agoricdev-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.agoric
37 | mv $HOME/.agoric/priv_validator_state.json.backup $HOME/.agoric/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start agd && sudo journalctl -u agd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/agoricdev/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: agoricdev-17 | **Latest Version Tag**: pismoC | **Custom Port**: 14
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for agoricdev-17!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/althea/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **08:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.3.2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1843451 | 2 hours | [snapshot (10.08 GB)](https://snapshots.kjnodes.com/althea-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop althea
29 | cp $HOME/.althea/data/priv_validator_state.json $HOME/.althea/priv_validator_state.json.backup
30 | rm -rf $HOME/.althea/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/althea-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.althea
37 | mv $HOME/.althea/priv_validator_state.json.backup $HOME/.althea/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start althea && sudo journalctl -u althea -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/althea/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: althea_7357-1 | **Latest Version Tag**: v0.3.2 | **Custom Port**: 152
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for althea_7357-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/andromeda/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: galileo-3-v1.1.0-beta1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1735043 | 3 hours | [snapshot (0.87 GB)](https://snapshots.kjnodes.com/andromeda-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop andromedad
29 | cp $HOME/.andromedad/data/priv_validator_state.json $HOME/.andromedad/priv_validator_state.json.backup
30 | rm -rf $HOME/.andromedad/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/andromeda-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.andromedad
37 | mv $HOME/.andromedad/priv_validator_state.json.backup $HOME/.andromedad/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start andromedad && sudo journalctl -u andromedad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/andromeda/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: galileo-3 | **Latest Version Tag**: galileo-3-v1.1.0-beta1 | **Custom Port**: 147
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for galileo-3!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/archway/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **09:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.6.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 456692 | 1 hours | [snapshot (0.62 GB)](https://snapshots.kjnodes.com/archway-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop archwayd
29 | cp $HOME/.archway/data/priv_validator_state.json $HOME/.archway/priv_validator_state.json.backup
30 | rm -rf $HOME/.archway/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/archway-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.archway
37 | mv $HOME/.archway/priv_validator_state.json.backup $HOME/.archway/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start archwayd && sudo journalctl -u archwayd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/archway/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: constantine-3 | **Latest Version Tag**: v1.0.0-rc.1 | **Custom Port**: 156
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf archway
22 | git clone https://github.com/archway-network/archway.git
23 | cd archway
24 | git checkout v1.0.0-rc.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.archway/cosmovisor/upgrades/v0.6.0/bin
31 | mv build/archwayd $HOME/.archway/cosmovisor/upgrades/v0.6.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/aura/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **05:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.5.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 5116174 | 5 hours | [snapshot (1.58 GB)](https://snapshots.kjnodes.com/aura-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop aurad
29 | cp $HOME/.aura/data/priv_validator_state.json $HOME/.aura/priv_validator_state.json.backup
30 | rm -rf $HOME/.aura/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/aura-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.aura
37 | mv $HOME/.aura/priv_validator_state.json.backup $HOME/.aura/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start aurad && sudo journalctl -u aurad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/aura/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: euphoria-2 | **Latest Version Tag**: euphoria_v0.5.1 | **Custom Port**: 117
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf aura
22 | git clone https://github.com/aura-nw/aura.git
23 | cd aura
24 | git checkout euphoria_v0.5.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.aura/cosmovisor/upgrades/v0.5.1/bin
31 | mv build/aurad $HOME/.aura/cosmovisor/upgrades/v0.5.1/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/bitcanna/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | BitCanna is a proof-of-stake (POS) decentralized payment network designed exclusively to serve the cannabis industry.
6 |
7 | **Chain ID**: bitcanna-dev-1 | **Latest Version Tag**: v2.0.2-rc2 | **Wasm**: OFF
8 |
9 | [Website](https://www.bitcanna.io) | [Discord](https://discord.gg/9AVrzaVQvs) | [Twitter](https://twitter.com/BitCannaGlobal)
10 |
11 |
12 |
13 | Subscribe to our free [🤖 Testnet Proposal Bot](https://t.me/kjnodes_testnet_proposal_bot) to never miss upcoming proposals
14 |
15 |
16 | ## Chain explorer
17 | [https://explorer.kjnodes.com/bitcanna-testnet](https://explorer.kjnodes.com/bitcanna-testnet)
18 |
19 | ## Public endpoints
20 |
21 | * api: [https://bitcanna-testnet.api.kjnodes.com](https://bitcanna-testnet.api.kjnodes.com)
22 | * rpc: [https://bitcanna-testnet.rpc.kjnodes.com](https://bitcanna-testnet.rpc.kjnodes.com)
23 | * grpc: bitcanna-testnet.grpc.kjnodes.com:14290
24 |
25 | ## Peering
26 |
27 | **state-sync**
28 |
29 | ```text
30 | d5519e378247dfb61dfe90652d1fe3e2b3005a5b@bitcanna-testnet.rpc.kjnodes.com:14256
31 | ```
32 |
33 | **seed-node**
34 |
35 | ```text
36 | 3f472746f46493309650e5a033076689996c8881@bitcanna-testnet.rpc.kjnodes.com:14259
37 | ```
38 |
39 | **addrbook**
40 | ```bash
41 | curl -Ls https://snapshots.kjnodes.com/bitcanna-testnet/addrbook.json > $HOME/.bcna/config/addrbook.json
42 | ```
43 |
44 | **live-peers** (6)
45 | ```bash
46 | peers="b0c7e5c69aaf00626baaf7c59370029b587a91a4@65.109.92.240:30006,60fae2c5581622bb84eaf95878e85c9f339f1a2a@212.227.151.106:26656,80ee9ed689bfb329cf21b94aa12978e073226db4@212.227.151.143:26656,2175709bdd102641e9e4ddd38ba263b7f06214df@65.109.28.177:26356,e72441f66d5101289c9fd86f6733c43551b1d04d@89.58.59.75:46656,d5519e378247dfb61dfe90652d1fe3e2b3005a5b@65.109.68.190:14256"
47 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/.bcna/config/config.toml
48 | ```
49 |
--------------------------------------------------------------------------------
/docs/testnet/bitcanna/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **05:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: wakeandbake_test2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 2710755 | 5 hours | [snapshot (0.49 GB)](https://snapshots.kjnodes.com/bitcanna-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop bcnad
29 | cp $HOME/.bcna/data/priv_validator_state.json $HOME/.bcna/priv_validator_state.json.backup
30 | rm -rf $HOME/.bcna/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/bitcanna-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.bcna
37 | mv $HOME/.bcna/priv_validator_state.json.backup $HOME/.bcna/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start bcnad && sudo journalctl -u bcnad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/bitcanna/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: bitcanna-dev-1 | **Latest Version Tag**: v2.0.2-rc2 | **Custom Port**: 142
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf bcna
22 | git clone https://github.com/BitCannaGlobal/bcna.git
23 | cd bcna
24 | git checkout v2.0.2-rc2
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.bcna/cosmovisor/upgrades/wakeandbake_test2/bin
31 | mv build/bcnad $HOME/.bcna/cosmovisor/upgrades/wakeandbake_test2/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/cascadia/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **09:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.1.2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1006034 | 1 hours | [snapshot (0.7 GB)](https://snapshots.kjnodes.com/cascadia-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop cascadiad
29 | cp $HOME/.cascadiad/data/priv_validator_state.json $HOME/.cascadiad/priv_validator_state.json.backup
30 | rm -rf $HOME/.cascadiad/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/cascadia-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.cascadiad
37 | mv $HOME/.cascadiad/priv_validator_state.json.backup $HOME/.cascadiad/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start cascadiad && sudo journalctl -u cascadiad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/cascadia/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: cascadia_6102-1 | **Latest Version Tag**: v0.1.2 | **Custom Port**: 155
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for cascadia_6102-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/celestia/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **05:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.13.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 727088 | 23 hours | [snapshot (9.8 GB)](https://snapshots.kjnodes.com/celestia-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop celestia-appd
29 | cp $HOME/.celestia-app/data/priv_validator_state.json $HOME/.celestia-app/priv_validator_state.json.backup
30 | rm -rf $HOME/.celestia-app/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/celestia-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.celestia-app
37 | mv $HOME/.celestia-app/priv_validator_state.json.backup $HOME/.celestia-app/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start celestia-appd && sudo journalctl -u celestia-appd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/celestia/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently celestia does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/celestia/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: blockspacerace-0 | **Latest Version Tag**: v0.13.0 | **Custom Port**: 120
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for blockspacerace-0!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/composable/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **10:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: centauri
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 245052 | 23 minutes | [snapshot (0.27 GB)](https://snapshots.kjnodes.com/composable-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop centaurid
29 | cp $HOME/.banksy/data/priv_validator_state.json $HOME/.banksy/priv_validator_state.json.backup
30 | rm -rf $HOME/.banksy/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/composable-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.banksy
37 | mv $HOME/.banksy/priv_validator_state.json.backup $HOME/.banksy/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start centaurid && sudo journalctl -u centaurid -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/composable/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: banksy-testnet-3 | **Latest Version Tag**: v3.0.3-testnet | **Custom Port**: 159
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf composable-testnet
22 | git clone https://github.com/notional-labs/composable-testnet.git
23 | cd composable-testnet
24 | git checkout v3.0.3-testnet
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.banksy/cosmovisor/upgrades/v3/bin
31 | mv bin/centaurid $HOME/.banksy/cosmovisor/upgrades/v3/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/defund/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.2.6
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 9373468 | 6 hours | [snapshot (6.46 GB)](https://snapshots.kjnodes.com/defund-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop defundd
29 | cp $HOME/.defund/data/priv_validator_state.json $HOME/.defund/priv_validator_state.json.backup
30 | rm -rf $HOME/.defund/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/defund-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.defund
37 | mv $HOME/.defund/priv_validator_state.json.backup $HOME/.defund/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start defundd && sudo journalctl -u defundd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/defund/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently defund does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/defund/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: orbit-alpha-1 | **Latest Version Tag**: v0.2.6 | **Custom Port**: 140
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for orbit-alpha-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/dymension/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **06:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.2.0-beta
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1775685 | 3 hours | [snapshot (4.31 GB)](https://snapshots.kjnodes.com/dymension-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop dymd
29 | cp $HOME/.dymension/data/priv_validator_state.json $HOME/.dymension/priv_validator_state.json.backup
30 | rm -rf $HOME/.dymension/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/dymension-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.dymension
37 | mv $HOME/.dymension/priv_validator_state.json.backup $HOME/.dymension/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start dymd && sudo journalctl -u dymd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/dymension/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: 35-C | **Latest Version Tag**: v0.2.0-beta | **Custom Port**: 146
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for 35-C!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/elys/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **08:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.6.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1021541 | 2 hours | [snapshot (2.81 GB)](https://snapshots.kjnodes.com/elys-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop elysd
29 | cp $HOME/.elys/data/priv_validator_state.json $HOME/.elys/priv_validator_state.json.backup
30 | rm -rf $HOME/.elys/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/elys-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.elys
37 | mv $HOME/.elys/priv_validator_state.json.backup $HOME/.elys/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start elysd && sudo journalctl -u elysd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/elys/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: elystestnet-1 | **Latest Version Tag**: v0.7.0 | **Custom Port**: 153
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf elys
22 | git clone https://github.com/elys-network/elys.git
23 | cd elys
24 | git checkout v0.7.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.elys/cosmovisor/upgrades/v0.7.0/bin
31 | mv build/elysd $HOME/.elys/cosmovisor/upgrades/v0.7.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/gitopia/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **04:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.2.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 9456965 | 3 days | [snapshot (2.79 GB)](https://snapshots.kjnodes.com/gitopia-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop gitopiad
29 | cp $HOME/.gitopia/data/priv_validator_state.json $HOME/.gitopia/priv_validator_state.json.backup
30 | rm -rf $HOME/.gitopia/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/gitopia-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.gitopia
37 | mv $HOME/.gitopia/priv_validator_state.json.backup $HOME/.gitopia/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start gitopiad && sudo journalctl -u gitopiad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/gitopia/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: gitopia-janus-testnet-2 | **Latest Version Tag**: v1.2.0 | **Custom Port**: 141
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for gitopia-janus-testnet-2!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/greenfield/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | BNB Greenfield is an innovative blockchain and storage platform that seeks to unleash the power of decentralized technology on data ownership and the data economy
6 |
7 | **Chain ID**: greenfield_5600-1 | **Latest Version Tag**: v0.1.1 | **Wasm**: OFF
8 |
9 | [Website](https://greenfield.bnbchain.org) | [Discord](https://discord.gg/bnbchain) | [Twitter](https://twitter.com/BNBChain)
10 |
11 |
12 |
13 | Subscribe to our free [🤖 Testnet Proposal Bot](https://t.me/kjnodes_testnet_proposal_bot) to never miss upcoming proposals
14 |
15 |
16 | ## Chain explorer
17 | [https://explorer.kjnodes.com/greenfield-testnet](https://explorer.kjnodes.com/greenfield-testnet)
18 |
19 | ## Public endpoints
20 |
21 | * api: [https://greenfield-testnet.api.kjnodes.com](https://greenfield-testnet.api.kjnodes.com)
22 | * rpc: [https://greenfield-testnet.rpc.kjnodes.com](https://greenfield-testnet.rpc.kjnodes.com)
23 | * grpc: greenfield-testnet.grpc.kjnodes.com:15490
24 |
25 | ## Peering
26 |
27 | **state-sync**
28 |
29 | ```text
30 | d5519e378247dfb61dfe90652d1fe3e2b3005a5b@greenfield-testnet.rpc.kjnodes.com:15456
31 | ```
32 |
33 | **seed-node**
34 |
35 | ```text
36 | 3f472746f46493309650e5a033076689996c8881@greenfield-testnet.rpc.kjnodes.com:15459
37 | ```
38 |
39 | **addrbook**
40 | ```bash
41 | curl -Ls https://snapshots.kjnodes.com/greenfield-testnet/addrbook.json > $HOME/.gnfd/config/addrbook.json
42 | ```
43 |
44 | **live-peers** (3)
45 | ```bash
46 | peers="20c3e15d8dcc3988f533dd456a55d4584b2e78f6@131.153.158.3:26656,7a635c262955a2e85c654615f390f3a3e9c71328@54.225.72.119:26656,f811d0f87415bcc5daba37ec925b137a1b403372@35.76.22.132:26656"
47 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/.gnfd/config/config.toml
48 | ```
49 |
--------------------------------------------------------------------------------
/docs/testnet/greenfield/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **08:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.1.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 884702 | 1 days | [snapshot (1.08 GB)](https://snapshots.kjnodes.com/greenfield-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop gnfd
29 | cp $HOME/.gnfd/data/priv_validator_state.json $HOME/.gnfd/priv_validator_state.json.backup
30 | rm -rf $HOME/.gnfd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/greenfield-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.gnfd
37 | mv $HOME/.gnfd/priv_validator_state.json.backup $HOME/.gnfd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start gnfd && sudo journalctl -u gnfd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/greenfield/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: greenfield_5600-1 | **Latest Version Tag**: v0.1.1 | **Custom Port**: 154
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for greenfield_5600-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/haqq/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **03:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.3.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3580860 | 2 hours | [snapshot (1.16 GB)](https://snapshots.kjnodes.com/haqq-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop haqqd
29 | cp $HOME/.haqqd/data/priv_validator_state.json $HOME/.haqqd/priv_validator_state.json.backup
30 | rm -rf $HOME/.haqqd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/haqq-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.haqqd
37 | mv $HOME/.haqqd/priv_validator_state.json.backup $HOME/.haqqd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start haqqd && sudo journalctl -u haqqd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/haqq/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: haqq_54211-3 | **Latest Version Tag**: v1.3.1 | **Custom Port**: 135
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf haqq
22 | git clone https://github.com/haqq-network/haqq.git
23 | cd haqq
24 | git checkout v1.3.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.haqqd/cosmovisor/upgrades/v1.3.1/bin
31 | mv build/haqqd $HOME/.haqqd/cosmovisor/upgrades/v1.3.1/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/humans/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **10:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.2.2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 341754 | 38 minutes | [snapshot (0.25 GB)](https://snapshots.kjnodes.com/humans-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop humansd
29 | cp $HOME/.humansd/data/priv_validator_state.json $HOME/.humansd/priv_validator_state.json.backup
30 | rm -rf $HOME/.humansd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/humans-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.humansd
37 | mv $HOME/.humansd/priv_validator_state.json.backup $HOME/.humansd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start humansd && sudo journalctl -u humansd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/humans/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: humans_3000-31 | **Latest Version Tag**: v0.2.2 | **Custom Port**: 122
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for humans_3000-31!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/hypersign/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **00:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v017
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3847549 | 4 hours | [snapshot (1.19 GB)](https://snapshots.kjnodes.com/hypersign-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop hid-noded
29 | cp $HOME/.hid-node/data/priv_validator_state.json $HOME/.hid-node/priv_validator_state.json.backup
30 | rm -rf $HOME/.hid-node/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/hypersign-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.hid-node
37 | mv $HOME/.hid-node/priv_validator_state.json.backup $HOME/.hid-node/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start hid-noded && sudo journalctl -u hid-noded -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/hypersign/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: jagrat | **Latest Version Tag**: v0.1.7 | **Custom Port**: 131
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf hid-node
22 | git clone https://github.com/hypersign-protocol/hid-node.git
23 | cd hid-node
24 | git checkout v0.1.7
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.hid-node/cosmovisor/upgrades/v017/bin
31 | mv build/hid-noded $HOME/.hid-node/cosmovisor/upgrades/v017/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/jackal/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **00:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: recovery
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 2979467 | 3 hours | [snapshot (0.91 GB)](https://snapshots.kjnodes.com/jackal-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop canined
29 | cp $HOME/.canine/data/priv_validator_state.json $HOME/.canine/priv_validator_state.json.backup
30 | rm -rf $HOME/.canine/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/jackal-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.canine
37 | mv $HOME/.canine/priv_validator_state.json.backup $HOME/.canine/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start canined && sudo journalctl -u canined -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/jackal/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: lupulella-2 | **Latest Version Tag**: v2.0.1 | **Custom Port**: 137
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf canine-chain
22 | git clone https://github.com/JackalLabs/canine-chain.git
23 | cd canine-chain
24 | git checkout v2.0.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.canine/cosmovisor/upgrades/recovery/bin
31 | mv build/canined $HOME/.canine/cosmovisor/upgrades/recovery/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/lava/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **05:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.13.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 248667 | 4 hours | [snapshot (3.16 GB)](https://snapshots.kjnodes.com/lava-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop lavad
29 | cp $HOME/.lava/data/priv_validator_state.json $HOME/.lava/priv_validator_state.json.backup
30 | rm -rf $HOME/.lava/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/lava-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.lava
37 | mv $HOME/.lava/priv_validator_state.json.backup $HOME/.lava/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start lavad && sudo journalctl -u lavad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/lava/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: lava-testnet-1 | **Latest Version Tag**: v0.13.1 | **Custom Port**: 144
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf lava
22 | git clone https://github.com/lavanet/lava.git
23 | cd lava
24 | git checkout v0.13.1
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.lava/cosmovisor/upgrades/v0.13.1/bin
31 | mv build/lavad $HOME/.lava/cosmovisor/upgrades/v0.13.1/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/mars/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **06:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.0-rc7
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 668440 | 2 hours | [snapshot (0.41 GB)](https://snapshots.kjnodes.com/mars-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop marsd
29 | cp $HOME/.mars/data/priv_validator_state.json $HOME/.mars/priv_validator_state.json.backup
30 | rm -rf $HOME/.mars/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/mars-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.mars
37 | mv $HOME/.mars/priv_validator_state.json.backup $HOME/.mars/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start marsd && sudo journalctl -u marsd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/mars/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ares-1 | **Latest Version Tag**: v1.0.0-rc7 | **Custom Port**: 45
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for ares-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/nibiru/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **00:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.19.2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3785406 | 4 hours | [snapshot (9.36 GB)](https://snapshots.kjnodes.com/nibiru-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop nibid
29 | cp $HOME/.nibid/data/priv_validator_state.json $HOME/.nibid/priv_validator_state.json.backup
30 | rm -rf $HOME/.nibid/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/nibiru-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.nibid
37 | mv $HOME/.nibid/priv_validator_state.json.backup $HOME/.nibid/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start nibid && sudo journalctl -u nibid -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/nibiru/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: nibiru-itn-1 | **Latest Version Tag**: v0.19.2 | **Custom Port**: 139
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for nibiru-itn-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/nois/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **08:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.3
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 2883045 | 2 hours | [snapshot (0.86 GB)](https://snapshots.kjnodes.com/nois-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop noisd
29 | cp $HOME/.noisd/data/priv_validator_state.json $HOME/.noisd/priv_validator_state.json.backup
30 | rm -rf $HOME/.noisd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/nois-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.noisd
37 | mv $HOME/.noisd/priv_validator_state.json.backup $HOME/.noisd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start noisd && sudo journalctl -u noisd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/nois/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: nois-testnet-005 | **Latest Version Tag**: v1.0.3 | **Custom Port**: 151
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for nois-testnet-005!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/nolus/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | Nolus aims to be the leading DeFi Lease platform. The protocol intends to become a tool for empowering people, simple to use, and highly efficient.
6 |
7 | **Chain ID**: rila-1 | **Latest Version Tag**: v0.4.0 | **Wasm**: ON
8 |
9 | [Website](https://www.nolus.io) | [Discord](https://discord.gg/nolus-protocol) | [Twitter](https://twitter.com/NolusProtocol)
10 |
11 |
12 |
13 | Subscribe to our free [🤖 Testnet Proposal Bot](https://t.me/kjnodes_testnet_proposal_bot) to never miss upcoming proposals
14 |
15 |
16 | ## Chain explorer
17 | [https://explorer.kjnodes.com/nolus-testnet](https://explorer.kjnodes.com/nolus-testnet)
18 |
19 | ## Public endpoints
20 |
21 | * api: [https://nolus-testnet.api.kjnodes.com](https://nolus-testnet.api.kjnodes.com)
22 | * rpc: [https://nolus-testnet.rpc.kjnodes.com](https://nolus-testnet.rpc.kjnodes.com)
23 | * grpc: nolus-testnet.grpc.kjnodes.com:14390
24 |
25 | ## Peering
26 |
27 | **state-sync**
28 |
29 | ```text
30 | d5519e378247dfb61dfe90652d1fe3e2b3005a5b@nolus-testnet.rpc.kjnodes.com:14356
31 | ```
32 |
33 | **seed-node**
34 |
35 | ```text
36 | 3f472746f46493309650e5a033076689996c8881@nolus-testnet.rpc.kjnodes.com:14359
37 | ```
38 |
39 | **addrbook**
40 | ```bash
41 | curl -Ls https://snapshots.kjnodes.com/nolus-testnet/addrbook.json > $HOME/.nolus/config/addrbook.json
42 | ```
43 |
44 | **live-peers** (4)
45 | ```bash
46 | peers="f51e1663a3c3393eda437191fba66f220a7c3bfb@142.132.208.26:26356,d5519e378247dfb61dfe90652d1fe3e2b3005a5b@65.109.68.190:14356,388acecb06c21f4ea243d3ba756d28965ae6ed00@78.128.61.41:26611,7042490bf1526d8c61c43ffe4d700388b73b905f@65.108.192.123:35656"
47 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/.nolus/config/config.toml
48 | ```
49 |
--------------------------------------------------------------------------------
/docs/testnet/nolus/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **03:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.4.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 259305 | 1 hours | [snapshot (0.11 GB)](https://snapshots.kjnodes.com/nolus-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop nolusd
29 | cp $HOME/.nolus/data/priv_validator_state.json $HOME/.nolus/priv_validator_state.json.backup
30 | rm -rf $HOME/.nolus/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/nolus-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.nolus
37 | mv $HOME/.nolus/priv_validator_state.json.backup $HOME/.nolus/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start nolusd && sudo journalctl -u nolusd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/nolus/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: rila-1 | **Latest Version Tag**: v0.4.0 | **Custom Port**: 143
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf nolus-core
22 | git clone https://github.com/Nolus-Protocol/nolus-core.git
23 | cd nolus-core
24 | git checkout v0.4.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.nolus/cosmovisor/upgrades/v0.4.0/bin
31 | mv target/release/nolusd $HOME/.nolus/cosmovisor/upgrades/v0.4.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/noria/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **10:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.2.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1301619 | 11 hours | [snapshot (0.25 GB)](https://snapshots.kjnodes.com/noria-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop noriad
29 | cp $HOME/.noria/data/priv_validator_state.json $HOME/.noria/priv_validator_state.json.backup
30 | rm -rf $HOME/.noria/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/noria-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.noria
37 | mv $HOME/.noria/priv_validator_state.json.backup $HOME/.noria/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start noriad && sudo journalctl -u noriad -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/noria/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: oasis-3 | **Latest Version Tag**: v1.3.0 | **Custom Port**: 161
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf noria
22 | git clone https://github.com/noria-net/noria.git
23 | cd noria
24 | git checkout v1.3.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.noria/cosmovisor/upgrades/v1.3.0/bin
31 | mv build/noriad $HOME/.noria/cosmovisor/upgrades/v1.3.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/ojo/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.1.2
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 1736285 | 2 hours | [snapshot (0.81 GB)](https://snapshots.kjnodes.com/ojo-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop ojod
29 | cp $HOME/.ojo/data/priv_validator_state.json $HOME/.ojo/priv_validator_state.json.backup
30 | rm -rf $HOME/.ojo/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/ojo-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.ojo
37 | mv $HOME/.ojo/priv_validator_state.json.backup $HOME/.ojo/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start ojod && sudo journalctl -u ojod -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/ojo/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ojo-devnet | **Latest Version Tag**: v0.1.2 | **Custom Port**: 150
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for ojo-devnet!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/okp4/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **03:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v4.1.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 2743554 | 1 hours | [snapshot (1.13 GB)](https://snapshots.kjnodes.com/okp4-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop okp4d
29 | cp $HOME/.okp4d/data/priv_validator_state.json $HOME/.okp4d/priv_validator_state.json.backup
30 | rm -rf $HOME/.okp4d/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/okp4-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.okp4d
37 | mv $HOME/.okp4d/priv_validator_state.json.backup $HOME/.okp4d/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start okp4d && sudo journalctl -u okp4d -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/okp4/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: okp4-nemeton-1 | **Latest Version Tag**: v4.1.0 | **Custom Port**: 136
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf okp4d
22 | git clone https://github.com/okp4/okp4d.git
23 | cd okp4d
24 | git checkout v4.1.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.okp4d/cosmovisor/upgrades/v4.1.0/bin
31 | mv target/dist/okp4d $HOME/.okp4d/cosmovisor/upgrades/v4.1.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/ollo/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **02:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.0.1
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3313460 | 1 hours | [snapshot (1.09 GB)](https://snapshots.kjnodes.com/ollo-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop ollod
29 | cp $HOME/.ollo/data/priv_validator_state.json $HOME/.ollo/priv_validator_state.json.backup
30 | rm -rf $HOME/.ollo/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/ollo-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.ollo
37 | mv $HOME/.ollo/priv_validator_state.json.backup $HOME/.ollo/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start ollod && sudo journalctl -u ollod -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/ollo/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ollo-testnet-1 | **Latest Version Tag**: v0.0.1 | **Custom Port**: 132
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for ollo-testnet-1!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/quasar/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.0.2-alpha-11
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 637169 | 3 hours | [snapshot (1.06 GB)](https://snapshots.kjnodes.com/quasar-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop quasard
29 | cp $HOME/.quasarnode/data/priv_validator_state.json $HOME/.quasarnode/priv_validator_state.json.backup
30 | rm -rf $HOME/.quasarnode/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/quasar-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.quasarnode
37 | mv $HOME/.quasarnode/priv_validator_state.json.backup $HOME/.quasarnode/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start quasard && sudo journalctl -u quasard -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/quasar/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: qsr-questnet-04 | **Latest Version Tag**: v0.0.2-alpha-11 | **Custom Port**: 48
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for qsr-questnet-04!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/quicksilver/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **02:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.4.2-rc7
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 778878 | 2 hours | [snapshot (1.31 GB)](https://snapshots.kjnodes.com/quicksilver-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop quicksilverd
29 | cp $HOME/.quicksilverd/data/priv_validator_state.json $HOME/.quicksilverd/priv_validator_state.json.backup
30 | rm -rf $HOME/.quicksilverd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/quicksilver-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.quicksilverd
37 | mv $HOME/.quicksilverd/priv_validator_state.json.backup $HOME/.quicksilverd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start quicksilverd && sudo journalctl -u quicksilverd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/quicksilver/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: rhye-1 | **Latest Version Tag**: v1.4.2-rc7 | **Custom Port**: 111
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf quicksilver
22 | git clone https://github.com/ingenuity-build/quicksilver.git
23 | cd quicksilver
24 | git checkout v1.4.2-rc7
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.quicksilverd/cosmovisor/upgrades/v1.4.2-rc7/bin
31 | mv build/quicksilverd $HOME/.quicksilverd/cosmovisor/upgrades/v1.4.2-rc7/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/sao/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **07:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.0.9
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 363979 | 4 hours | [snapshot (0.35 GB)](https://snapshots.kjnodes.com/sao-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop saod
29 | cp $HOME/.sao/data/priv_validator_state.json $HOME/.sao/priv_validator_state.json.backup
30 | rm -rf $HOME/.sao/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/sao-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.sao
37 | mv $HOME/.sao/priv_validator_state.json.backup $HOME/.sao/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start saod && sudo journalctl -u saod -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/sao/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: sao-testnet0 | **Latest Version Tag**: v0.0.9 | **Custom Port**: 49
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for sao-testnet0!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/sei/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **01:45 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: 1.2.2beta-postfix
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 24753991 | 5 hours | [snapshot (13.16 GB)](https://snapshots.kjnodes.com/sei-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop seid
29 | cp $HOME/.sei/data/priv_validator_state.json $HOME/.sei/priv_validator_state.json.backup
30 | rm -rf $HOME/.sei/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/sei-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.sei
37 | mv $HOME/.sei/priv_validator_state.json.backup $HOME/.sei/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start seid && sudo journalctl -u seid -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/sei/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently sei does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/sei/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: atlantic-2 | **Latest Version Tag**: 2.0.40beta | **Custom Port**: 12
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf sei-chain
22 | git clone https://github.com/sei-protocol/sei-chain.git
23 | cd sei-chain
24 | git checkout 2.0.40beta
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.sei/cosmovisor/upgrades/2.0.40beta/bin
31 | mv build/seid $HOME/.sei/cosmovisor/upgrades/2.0.40beta/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/source/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **06:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.0.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 6420177 | 4 hours | [snapshot (0.43 GB)](https://snapshots.kjnodes.com/source-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop sourced
29 | cp $HOME/.source/data/priv_validator_state.json $HOME/.source/priv_validator_state.json.backup
30 | rm -rf $HOME/.source/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/source-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.source
37 | mv $HOME/.source/priv_validator_state.json.backup $HOME/.source/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start sourced && sudo journalctl -u sourced -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/source/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: sourcechain-testnet | **Latest Version Tag**: e06b810e842e57ec8f5432c9cdd57883a69b3cee | **Custom Port**: 28
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for sourcechain-testnet!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/docs/testnet/teritori/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **01:15 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v1.4.0
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 5307429 | 3 hours | [snapshot (1.05 GB)](https://snapshots.kjnodes.com/teritori-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop teritorid
29 | cp $HOME/.teritorid/data/priv_validator_state.json $HOME/.teritorid/priv_validator_state.json.backup
30 | rm -rf $HOME/.teritorid/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/teritori-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.teritorid
37 | mv $HOME/.teritorid/priv_validator_state.json.backup $HOME/.teritorid/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start teritorid && sudo journalctl -u teritorid -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/teritori/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: teritori-testnet-v3 | **Latest Version Tag**: v1.4.0 | **Custom Port**: 119
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf teritori-chain
22 | git clone https://github.com/TERITORI/teritori-chain.git
23 | cd teritori-chain
24 | git checkout v1.4.0
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.teritorid/cosmovisor/upgrades/v1.4.0/bin
31 | mv build/teritorid $HOME/.teritorid/cosmovisor/upgrades/v1.4.0/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/uptick/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **01:00 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: v0.2.6
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 3846972 | 3 hours | [snapshot (1.27 GB)](https://snapshots.kjnodes.com/uptick-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop uptickd
29 | cp $HOME/.uptickd/data/priv_validator_state.json $HOME/.uptickd/priv_validator_state.json.backup
30 | rm -rf $HOME/.uptickd/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/uptick-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.uptickd
37 | mv $HOME/.uptickd/priv_validator_state.json.backup $HOME/.uptickd/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start uptickd && sudo journalctl -u uptickd -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/uptick/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: uptick_7000-2 | **Latest Version Tag**: v0.2.6 | **Custom Port**: 115
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf uptick
22 | git clone https://github.com/UptickNetwork/uptick.git
23 | cd uptick
24 | git checkout v0.2.6
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/.uptickd/cosmovisor/upgrades/v0.2.6/bin
31 | mv build/uptickd $HOME/.uptickd/cosmovisor/upgrades/v0.2.6/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/docs/testnet/zetachain/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **10:30 UTC**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: latest
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | 327050 | 8 minutes | [snapshot (2.36 GB)](https://snapshots.kjnodes.com/zetachain-testnet/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop zetacored
29 | cp $HOME/.zetacored/data/priv_validator_state.json $HOME/.zetacored/priv_validator_state.json.backup
30 | rm -rf $HOME/.zetacored/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/zetachain-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.zetacored
37 | mv $HOME/.zetacored/priv_validator_state.json.backup $HOME/.zetacored/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start zetacored && sudo journalctl -u zetacored -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/docs/testnet/zetachain/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: athens_7001-13 | **Latest Version Tag**: latest | **Custom Port**: 160
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for athens_7001-13!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/templates/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Discover base tools contributed to the projects by kjnodes team.
3 | ---
4 |
5 | # 🖤 Supported chains
6 |
7 | $CHAINS_SUPPORTED | $ASSETS | $DELEGATIONS
8 |
9 | ## MAINNET
10 |
11 | $MAINNET_HOME
12 | ## TESTNET
13 |
14 | $TESTNET_HOME
--------------------------------------------------------------------------------
/templates/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Table of contents
2 |
3 | * [🖤 Supported chains](README.md)
4 | * [🪢 Supported IBC relayers](https://relayers.kjnodes.com)
5 | * [🤖 Bots](bots/README.md)
6 | * [Telegram Proposal Bot](bots/telegram-proposal-bot.md)
7 | * [Discord Proposal Bot](bots/discord-proposal-bot.md)
8 | * [Kujira Oracle Monitoring Bot](bots/kujira-oracle-monitoring-bot.md)
9 |
10 | ## MAINNET
11 |
12 | $MAINNET_SUMMARY
13 | ## TESTNET
14 |
15 | $TESTNET_SUMMARY
--------------------------------------------------------------------------------
/templates/agoric/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ${CHAIN_ID} | **Latest Version Tag**: ${LATEST_VERSION_TAG} | **Custom Port**: ${CHAIN_PORT}
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf ${LATEST_VERSION_TAG}
22 | git clone ${GIT_URL} ${LATEST_VERSION_TAG}
23 | cd ${LATEST_VERSION_TAG}
24 | git checkout ${LATEST_VERSION_TAG}
25 |
26 | # Install and build Agoric Javascript packages
27 | yarn install && yarn build
28 |
29 | # Install and build Agoric Cosmos SDK support
30 | (cd packages/cosmic-swingset && make)
31 |
32 | # Prepare binaries for Cosmovisor
33 | mkdir -p $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin
34 | ln -s $HOME/${LATEST_VERSION_TAG}/bin/agd $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin/agd
35 | ```
36 |
37 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
38 |
--------------------------------------------------------------------------------
/templates/celestia/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently ${PROJECT_NAME} does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/templates/defund/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently ${PROJECT_NAME} does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/templates/gravitybridge/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ${CHAIN_ID} | **Latest Version Tag**: ${LATEST_VERSION_TAG} | **Custom Port**: ${CHAIN_PORT}
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Download project binaries
20 | mkdir -p $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin
21 | wget -O $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin/gravityd https://github.com/Gravity-Bridge/Gravity-Bridge/releases/download/${LATEST_VERSION_TAG}/gravity-linux-amd64
22 | wget -O $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin/gbt https://github.com/Gravity-Bridge/Gravity-Bridge/releases/download/${LATEST_VERSION_TAG}/gbt
23 | chmod +x $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin/*
24 | ```
25 |
26 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
27 |
--------------------------------------------------------------------------------
/templates/out_of_order/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently ${PROJECT_NAME} does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/templates/out_of_order/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ${CHAIN_ID} | **Latest Version Tag**: ${LATEST_VERSION_TAG} | **Custom Port**: ${CHAIN_PORT}
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for ${CHAIN_ID}!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/templates/project_page/README.md:
--------------------------------------------------------------------------------
1 | # Services
2 |
3 |
4 |
5 | ${CHAIN_SHORT_DESCRIPTION}
6 | **Chain ID**: ${CHAIN_ID} | **Latest Version Tag**: ${LATEST_VERSION_TAG} | **Wasm**: ${CHAIN_WASM}
7 |
8 | [Website](${CHAIN_WEBSITE}) | [Discord](${CHAIN_DISCORD}) | [Twitter](${CHAIN_TWITTER})
9 |
10 | ${STAKE_BUTTON}
11 |
12 | ${PROPOSAL_BOT}
13 |
14 | ${RESTAKE}
15 | ## Chain explorer
16 | [https://explorer.kjnodes.com/${CHAIN_SERVICE}](https://explorer.kjnodes.com/${CHAIN_SERVICE})
17 |
18 | ## Public endpoints
19 |
20 | * api: [https://${CHAIN_NAME}.api.kjnodes.com](https://${CHAIN_NAME}.api.kjnodes.com)
21 | * rpc: [https://${CHAIN_NAME}.rpc.kjnodes.com](https://${CHAIN_NAME}.rpc.kjnodes.com)
22 | * grpc: ${CHAIN_NAME}.grpc.kjnodes.com:${CHAIN_PORT}90
23 |
24 | ## Peering
25 |
26 | **state-sync**
27 |
28 | ```text
29 | ${CHAIN_PEER}@${CHAIN_NAME}.rpc.kjnodes.com:${CHAIN_PORT}56
30 | ```
31 |
32 | **seed-node**
33 |
34 | ```text
35 | ${CHAIN_TENDERSEED_PEER}@${CHAIN_NAME}.rpc.kjnodes.com:${CHAIN_PORT}59
36 | ```
37 |
38 | **addrbook**
39 | ```bash
40 | curl -Ls https://snapshots.kjnodes.com/${CHAIN_NAME}/addrbook.json > $HOME/${CHAIN_DIR}/config/addrbook.json
41 | ```
42 |
43 | **live-peers** (${CHAIN_LIVE_PEERS_COUNT})
44 | ```bash
45 | peers="${CHAIN_LIVE_PEERS}"
46 | sed -i -e "s|^persistent_peers *=.*|persistent_peers = \"$peers\"|" $HOME/${CHAIN_DIR}/config/config.toml
47 | ```
48 |
--------------------------------------------------------------------------------
/templates/project_page/snapshot/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Catch the latest block faster by using our daily snapshots.
3 | ---
4 |
5 | # Snapshot
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | Snapshots allows a new node to join the network by recovering application state from a backup file.
11 | Snapshot contains compressed copy of chain data directory. To keep backup files as small as plausible,
12 | snapshot server is periodically beeing state-synced.
13 | {% endhint %}
14 |
15 | Snapshots are taken automatically every 6 hours starting at **${CHAIN_SNAPSHOT_TIME}**
16 |
17 | **pruning**: 100/0/19 | **indexer**: null | **version tag**: ${SNAPSHOT_VERSION}
18 |
19 | | BLOCK | AGE | DOWNLOAD |
20 | | ----------------- | --------------- | --------------------------------------------------------------------------------------------------- |
21 | | ${SNAPSHOT_BLOCK} | ${SNAPSHOT_AGE} | [snapshot (${SNAPSHOT_SIZE})](https://snapshots.kjnodes.com/${CHAIN_NAME}/snapshot\_latest.tar.lz4) |
22 |
23 | ## Instructions
24 |
25 | ### Stop the service and reset the data
26 |
27 | ```bash
28 | sudo systemctl stop ${CHAIN_APP}
29 | cp $HOME/${CHAIN_DIR}/data/priv_validator_state.json $HOME/${CHAIN_DIR}/priv_validator_state.json.backup
30 | rm -rf $HOME/${CHAIN_DIR}/data
31 | ```
32 |
33 | ### Download latest snapshot
34 |
35 | ```bash
36 | curl -L https://snapshots.kjnodes.com/${CHAIN_NAME}/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/${CHAIN_DIR}
37 | mv $HOME/${CHAIN_DIR}/priv_validator_state.json.backup $HOME/${CHAIN_DIR}/data/priv_validator_state.json
38 | ```
39 |
40 | ### Restart the service and check the log
41 |
42 | ```bash
43 | sudo systemctl start ${CHAIN_APP} && sudo journalctl -u ${CHAIN_APP} -f --no-hostname -o cat
44 | ```
45 |
--------------------------------------------------------------------------------
/templates/project_page/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: ${CHAIN_ID} | **Latest Version Tag**: ${LATEST_VERSION_TAG} | **Custom Port**: ${CHAIN_PORT}
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | ## Download and build upgrade binaries
17 |
18 | ```bash
19 | # Clone project repository
20 | cd $HOME
21 | rm -rf ${GIT_DIR}
22 | git clone ${GIT_URL}
23 | cd ${GIT_DIR}
24 | git checkout ${LATEST_VERSION_TAG}
25 |
26 | # Build binaries
27 | make build
28 |
29 | # Prepare binaries for Cosmovisor
30 | mkdir -p $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin
31 | mv ${CHAIN_BINARY_SRC} $HOME/${CHAIN_DIR}/cosmovisor/upgrades/${LATEST_VERSION_NAME}/bin/
32 | rm -rf build
33 | ```
34 |
35 | *Thats it! Now when upgrade block height is reached, Cosmovisor will handle it automatically!*
36 |
--------------------------------------------------------------------------------
/templates/sei/state-sync/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: With our state sync services you will be able to catch up latest chain block in matter of minutes
3 | ---
4 |
5 | # State sync
6 |
7 |
8 |
9 | {% hint style='info' %}
10 | State Sync allows a new node to join the network by fetching a snapshot of the application state
11 | at a recent height instead of fetching and replaying all historical blocks. Since the
12 | application state is generally much smaller than the blocks, and restoring it is much
13 | faster than replaying blocks, this can reduce the time to sync with the network from days to minutes.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently ${PROJECT_NAME} does not support State sync 😢
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------
/templates/source/upgrade/README.md:
--------------------------------------------------------------------------------
1 | ---
2 | description: Prepare for and the upcomming chain upgrade using Cosmovisor.
3 | ---
4 |
5 | # Upgrade
6 |
7 |
8 |
9 | **Chain ID**: sourcechain-testnet | **Latest Version Tag**: e06b810e842e57ec8f5432c9cdd57883a69b3cee | **Custom Port**: 28
10 |
11 | {% hint style='info' %}
12 | Since we are using Cosmovisor, it makes it very easy to prepare for upcomming upgrade.
13 | You just have to build new binaries and move it into cosmovisor upgrades directory.
14 | {% endhint %}
15 |
16 | {% hint style='warning' %}
17 | Currently there are no upgrades available for sourcechain-testnet!
18 | {% endhint %}
19 |
--------------------------------------------------------------------------------