-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to solve????? #2239
Comments
I have been stuck in this state. What should I do?? |
Hello @zhaoxiangjunupi , assume that you are using v8.0.1 on mainnet, could you replace the live peers with https://polkachu.com/live_peers/cosmos |
|
Hi @zhaoxiangjunupi you're running Gaia v9, that will not be live until the proposal is voted ok and then upgrade height is reached, which is ~ 2023-03-15 12:18:06 If you want to join mainnet, please use the v8.0.1 release |
I use v8.0.1 release, and the peers you provide can't be connected. Are you sure there is no problem? |
In the screenshot above your definitely running the wrong version of Gaia:
Regarding the peers from https://polkachu.com/live_peers/cosmos, could be that they are saturated or offline. Theres also a list of peers in the chain-registry |
Many people in the community have put forward corresponding questions, but you haven't responded. The same questions, the answers you gave are wrong. I think you should test yourself https://discord.com/channels/669268347736686612/1070874004296048640 |
I changed the version in your way, but it's still useless. Have you tried it yourself?? |
Hi @zhaoxiangjunupi me and a colleague tried the following #2239 (comment) and found it to be working. |
Hello @zhaoxiangjunupi as mentioned in the other issue that you've raised, I can walk through the setup together with you. In lieu of that will close this issue, as this one is related. |
The text was updated successfully, but these errors were encountered: