Closed jiraky closed 2 years ago
Hey @jiraky, are you running v0.2.7 or v0.3.1 when trying to connect to testnet? Testnet is currently on v0.2.7 and undergoing a software upgrade proposal to allow the upgrade to the new version.
Hey @jiraky, are you running v0.2.7 or v0.3.1 when trying to connect to testnet? Testnet is currently on v0.2.7 and undergoing a software upgrade proposal to allow the upgrade to the new version.
I confirm version v0.2.7
for the testnet.
Hey, @jiraky . Can you try the same steps with 0.2.3
version?
NOT NEEDED ANYMORE
Hey, @jiraky again. If it’s possible, can you run the next steps for 0.2.7
version, it should work:
cheqd$ cheqd-noded unsafe-reset-all
cheqd$ cheqd-noded configure fastsync-version "v0"
cheqd-noded
serviceHello, as posted on Slack, the result is the same. Cheers
@jiraky Hey so sorry for the late reply here. Is there an IP address/node RPC I can look up? And I'm not sure whether there's been any progress since the last update.
Hello, I have updated the testnode to v0.3.1
.
I have resetted the configurations and reconfigured the node entirely. I still get the same block error.
The rpc is available at: http://node0.testnet.cheqd.monokee.com:26657/
Contact Details
mattia.zago@monokee.com
What happened?
New node installed following the up to date guide. Genesis transactions and seeds match the official ones here on Github. The node refuses to include 2nd block in the chain while catching up, crashes and prevents any further operation.
Reproduction steps
Bug prevalence
All the time I start the node
Environment
testnet
What browsers are you seeing the problem on?
No response
Relevant log output
Code of Conduct