Launching Gaia-7005
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 launching. 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 version`0.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…
Excerpt (1198 of 2339 characters). Read the whole post on the forum ↗
Here are my peer addresses.
a586fcff022d697d8fa96d056228ee33a53bfca3@rx-78.forbole.com:26656
6795f37490de3c112aaea6501ebdc9d49b01ab02@rx-78-2.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
My peer:
9c5c946df2cab55d111d1fa7e6b03c50666160c4@142.93.31.31:26656
my peer:
f00347e8ebddb28e14289a2d2bb42e5b0a78cc76@159.100.245.53:26656
537e1dfd55a95ec5e524f5df9aa418cab5bd7c07@47.254.29.36:26656
Crytter: 467b0c5d21df4273a84a557e2a6c848feb11cf35@136.144.202.164:26656
address: 8F06FE1FD042683C426137FBC4BBAA4288924217@77.87.106.26:26656
chainflow08 is running
validator.network sentries:
2968891ca5af419c5fdc7ec4fbc95a8425c4e759@54.93.201.252:26656 (aws/eu-central-1a)
5c2b839d80681b0b197c5f4c7a0e6e2c57a100ff@18.195.215.254:26656 (aws/eu-central-1b)
07d4e8eb31bdc058e5b9f632d0a0c67861ea85f8@18.194.37.200:26656 (aws/eu-central-1c)
Here are my peer addresses:
437203a1e841b852c0e77ed1b3f22e4ea0c695a0@sentry01.livedata.io:26656,
921f6064d6b84caa3a916bfa83c8165ad4712e32@sentry02.livedata.io:26656
Here are our shensi network peer address:
41e57a4dcd10306835852170d9182e3b7218043a@222.175.101.77:26656
Here are our InsChain peer addresses of sentry nodes:
599e91e8c30d2c8930012e07b87c9159f6b908c0@34.227.90.117:26656
a0263d4e0a4482c35191a1add78eafad65e2bac6@52.23.178.47:26656
Be careful, if I am not mistaken this is how we’ve killed 700X twice now…