You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded the node after block height 15084585 (2.0.0==> 3.0.1), but after the upgrade, the startup error was reported, so I continued to use the node of version 2.0.0. Currently, it seems that the data can be synchronized normally, which is completely inconsistent with the release instructions of version v3.0.1. Therefore, should I upgrade the node and how to solve the problem that the node reports an error after the upgrade
The text was updated successfully, but these errors were encountered:
We have released the latest 3.0.2 version of the client. You can install the latest client and restart the node, or compile the latest uploaded master branch source code to check whether the node can run normally.
I upgraded the node after block height 15084585 (2.0.0==> 3.0.1), but after the upgrade, the startup error was reported, so I continued to use the node of version 2.0.0. Currently, it seems that the data can be synchronized normally, which is completely inconsistent with the release instructions of version v3.0.1. Therefore, should I upgrade the node and how to solve the problem that the node reports an error after the upgrade
The text was updated successfully, but these errors were encountered: