cronos icon indicating copy to clipboard operation
cronos copied to clipboard

Is it safe to upgrade v0.7 -> v0.8 now

Open huahuayu opened this issue 3 years ago • 10 comments

Hi since my v0.7 is stopped for several days, current release is v0.8 but I can see there are some issues raised for v0.8. https://github.com/crypto-org-chain/cronos/issues/624 https://github.com/crypto-org-chain/cronos/issues/628

So is it safe to upgrade from v0.7 -> v0.8 now, any documentation?

huahuayu avatar Aug 10 '22 07:08 huahuayu

we have upgraded many nodes, it works fine. I need to understand more about the user's report to understand why. I guess it's due to misconfiguration on the user side. I think it's pretty safe.

yihuang avatar Aug 10 '22 07:08 yihuang

Let's say 0.7 -> 0.8 Do I need to use a new genesis file (if there has a new one) or direct replace cronosd binary and restart?

huahuayu avatar Aug 11 '22 07:08 huahuayu

replace cronosd binary and restart, just like 0.6 -> 0.7.

yihuang avatar Aug 11 '22 07:08 yihuang

done, let's see...hope everything is fine.

huahuayu avatar Aug 11 '22 09:08 huahuayu

So far so good, syncing~~

huahuayu avatar Aug 11 '22 09:08 huahuayu

Btw, do you have snapshots, if sync from scratch(let's say I want to set up a new node), I have to use 0.6.* to sync to some block and then switch to v0.8?

huahuayu avatar Aug 11 '22 09:08 huahuayu

Btw, do you have snapshots

https://quicksync.io/networks/cronos.html there are plenty here.

yihuang avatar Aug 11 '22 10:08 yihuang

I have to use 0.6.* to sync to some block and then switch to v0.8?

0.6 -> 0.7 -> 0.8

yihuang avatar Aug 11 '22 10:08 yihuang

I have to use 0.6.* to sync to some block and then switch to v0.8?

0.6 -> 0.7 -> 0.8

But If I use snapshot, then don't bother right?

huahuayu avatar Aug 11 '22 15:08 huahuayu

I have to use 0.6.* to sync to some block and then switch to v0.8?

0.6 -> 0.7 -> 0.8

But If I use snapshot, then don't bother right?

yes

yihuang avatar Aug 11 '22 15:08 yihuang