zaki
August 6, 2018, 3:27pm
1
Gaia-7004 died from known bugs. We are waiting for review to complete and PRs to be merged for the launch of Gaia-8000.
in the meantime, Gaia-7005
Instead of deleting revoked validators this time, I just unrevoked everyone. We shall see if it works.
Our new genesis file is https://raw.githubusercontent.com/cosmos/testnets/master/gaia-7005/genesis.json
We are using the same version of as in gaia-7003 gaiad version0.23.1-23e3d5ac.
How to upgrade?
If you were running on gaia-7003, upgrading will be simple.
Stop gaiad on your server.
rm ~/.gaiad/config/genesis.json
cd ~/.gaiad/config/
wget https://raw.githubusercontent.com/cosmos/testnets/master/gaia-7005/genesis.json
gaiad unsafe_reset_all
start gaiad again
Your config.toml should remain the same and following seeds should work.
Seed nodes are live
seeds = "7c8b8fd03577cd4817f5be1f03d506f879df98d8@gaia-7000-seed1.interblock.io:26656, a28737ff02391a6e00a1d3b79befd57e68e8264c@gaia-7000-seed2.interblock.io:26656, 987ffd26640cd03d08ed7e53b24dfaa7956e612d@gaia-7000-seed3.interblock.io:26656"
We have experienced some problems with the seed nodes ourselves. Still looking into it but consider adding peers from https://explorecosmos.network/nodes to seeds/persistent peers if you have having trouble connecting to the network.
# Join the Testnet
Please ensure you have the [Cosmos SDK](/getting-started/installation.md) installed. If you ran a full node on a previous testnet, please skip to [Upgrading From Previous Testnet](#upgrading-from-previous-testnet).
## Setting Up a New Node
These instructions are for setting up a brand new full node from scratch.
First, initialize the node and create the necessary config files:
```bash
gaiad init --name <your_custom_name>
```
::: warning Note
Only ASCII characters are supported for the `--name`. Using Unicode characters will render your node unreachable.
:::
You can edit this `name` later, in the `~/.gaiad/config/config.toml` file:
show original
Validator’s hangout in Riot Chat.
Validators chat in https://matrix.to/#/!UogFAfBUvwZkQdnXJq:matrix.org and https://matrix.to/#/!hEuEYSWKomxnWlSKqi:matrix.org
2 Likes
Here are my peer addresses.
a586fcff022d697d8fa96d056228ee33a53bfca3@rx-78.forbole.com:26656
Some more from Staking Facilities. Just add as Persistent Peer
8894561f32c2a8b99f02a14346d00d3d03395df7@18.222.164.161:26656,525983b3b336404d98b3a3093ff44aa534517216@18.191.157.139:26656
1 Like
My peer:
1 Like
my peer:
1 Like
ping
August 6, 2018, 4:45pm
7
537e1dfd55a95ec5e524f5df9aa418cab5bd7c07@47.254.29.36:26656
1 Like
Crytter: 467b0c5d21df4273a84a557e2a6c848feb11cf35@136.144.202.164:26656
1 Like
address: 8F06FE1FD042683C426137FBC4BBAA4288924217@77.87.106.26:26656
1 Like
validator.network sentries:
2968891ca5af419c5fdc7ec4fbc95a8425c4e759@54.93.201.252:26656 (aws/eu-central-1a)
1 Like
Volker
August 6, 2018, 6:25pm
12
Here are my peer addresses:
437203a1e841b852c0e77ed1b3f22e4ea0c695a0@sentry01.livedata.io:26656,
2 Likes
Here are our shensi network peer address:
Here are our InsChain peer addresses of sentry nodes:
599e91e8c30d2c8930012e07b87c9159f6b908c0@34.227.90.117:26656
Be careful, if I am not mistaken this is how we’ve killed 700X twice now…
launching.