Genki-3000, also: GoS is delayed by 48 hours


#1

GoS was delayed due to community concerns that v0.28.0 release is too close to start of GoS, and, crucially, incompatible with genki-2000.

Therefore, Zaki postponed the release by 48h. Since there’s no other reason for the delay and everything else got done on time, the new release date is very likely to stick unless critical bugs are found.

In the meantime, let’s do genki-3000!

Genesis registration is up: https://genesis.certus.one/registration/2

GitHub repo: https://github.com/certusone/genki-3000

Genesis time will be at 2018-12-11 13:00 UTC.

Any validators who are not online at genesis will be dropped and can join the
network later in order to speed up the launch (GoS accounts are used).


#2

Submitted, Good luck everyone :grinning:


#3

genki-3000 is dead. On to genki-3001!

Registration: https://genesis.certus.one/registration/2 (CLOSED, the chain is up and you can join by using your GoS account)

The network will do a quick start, and everyone can join in later by creating a validator
on the running the chain. There is NO disadvantage if you join later, so please only register
for genesis if you intend to be present! Otherwise, you will make life hard for everyone.


#4

genki-3001 is up and running! You can join at any time by creating a validator on the running chain and delegate tokens to it from your GoS account.


#5

Hi! Is there a list of seed nodes anywhere? I don’t see one in the repo.


#6

If you go to https://github.com/certusone/genki-3001, you can see two seed nodes in the readme. In case you can’t find them, here they are:

afffb2d11f03975c9fa3f6442aee9d095d1c0144@83.35.103.119:2656,31d4e17935ced11d83686716077517b40950e45a@51.68.102.103:26656,74745f645a7102f519b0a3169d56eb0767f1bfb6@45.77.53.208:26656

PS: Beware that genki-3000 is dead, those are for genki-3001


#7

Thanks @katernoir. I was on the wrong repo. I found the seeds and am connected to the network. Cheers!


#8

can help me, I try upgraded many times, still can’t connect~

E[13126-12-13|02:59:29.622] Failed to reconnect to peer. Beginning exponential backoff module=p2p addr=a966b0806aca7e62d5c43d8bd09425aecdcf44f2@35.182.242.163:26656 elapsed=2m12.865603716s

E[13126-12-13|02:59:31.897] Failed to reconnect to peer. Beginning exponential backoff module=p2p addr=aa3464017cd5abd9ff0204f2e161d66f9442db29@52.53.197.37:26656 elapsed=2m15.618889075s
E[13126-12-13|02:59:45.042] Dialing failed module=pex addr=f7290d305237b3fef01a59a4919aa6b399234983@35.183.126.181:26656 err=“dial tcp 35.183.126.181:26656: i/o timeout” attempts=3
E[13126-12-13|03:00:14.216] Dialing failed module=pex addr=6a04069a2736f096404df2bbc31d7c2807c080c0@13.56.78.160:26656 err=“dial tcp 13.56.78.160:26656: connect: connection refused” attempts=5
E[13126-12-13|03:00:14.217] Dialing failed module=pex addr=aa3464017cd5abd9ff0204f2e161d66f9442db29@52.53.197.37:26656 err=“dial tcp 52.53.197.37:26656: connect: connection refused” attempts=5
E[13126-12-13|03:00:14.276] Dialing failed module=pex addr=a966b0806aca7e62d5c43d8bd09425aecdcf44f2@35.182.242.163:26656 err=“dial tcp 35.182.242.163:26656: connect: connection refused” attempts=5
E[13126-12-13|03:00:15.042] Dialing failed module=pex addr=f7290d305237b3fef01a59a4919aa6b399234983@35.183.126.181:26656 err=“dial tcp 35.183.126.181:26656: i/o timeout” attempts=4
E[13126-12-13|03:01:15.044] Dialing failed module=pex addr=f7290d305237b3fef01a59a4919aa6b399234983@35.183.126.181:26656 err=“dial tcp 35.183.126.181:26656: i/o timeout” attempts=5
E[13126-12-13|03:01:44.216] Dialing failed module=pex addr=6a04069a2736f096404df2bbc31d7c2807c080c0@13.56.78.160:26656 err=“dial tcp 13.56.78.160:26656: connect: connection refused” attempts=6
E[13126-12-13|03:01:44.217] Dialing failed module=pex addr=aa3464017cd5abd9ff0204f2e161d66f9442db29@52.53.197.37:26656 err=“dial tcp 52.53.197.37:26656: connect: connection refused” attempts=6
E[13126-12-13|03:01:44.276] Dialing failed module=pex addr=a966b0806aca7e62d5c43d8bd09425aecdcf44f2@35.182.242.163:26656 err=“dial tcp 35.182.242.163:26656: connect: connection refused” attempts=6


#9

gaiacli status
{“node_info”:{“protocol_version”:{“p2p”:“5”,“block”:“8”,“app”:“0”},“id”:“dd3ac2ebe1df9ce3e4cfc39324d1e249e13e3d3a”,“listen_addr”:“tcp://0.0.0.0:26656”,“network”:“genki-3001”,“version”:“0.27.0”,“channels”:“4020212223303800”,“moniker”:“wecosmos02”,“other”:{“tx_index”:“on”,“rpc_address”:“tcp://0.0.0.0:26657”}},“sync_info”:{“latest_block_hash”:"",“latest_app_hash”:"",“latest_block_height”:“0”,“latest_block_time”:“1970-01-01T00:00:00Z”,“catching_up”:true},“validator_info”:{“address”:“0077F68359FE12C678980AC3442460CB1CC1ABC4”,“pub_key”:{“type”:“tendermint/PubKeyEd25519”,“value”:“zf+aS3anGNm9CrpliDTqpUlHCBpi0qZknUo+aYOXC+s=”},“voting_power”:“0”}}


#10

It seems like many of the community nodes went down. We added the Certus One and Dokia Capital seed nodes to the repository, try with these: https://github.com/certusone/genki-3001


#11

good news, thank you very much!