A new network release is now ready! Please follow the instructions below once the new versions are available to ensure your nodes stay compatible and continue earning rewards. Full changelog are posted with the release. If autoupgrade applies to you, please DO NOT manually upgrade. Another important note, the network will now evict all but the most recent release. Older versions are no longer compatible and may cause network errors, particularly around Merkle payment processing. We are choosing this release as a starting point for this, we may allow older releases in the future.
We are asking all node operators to actively monitor their nodes and confirm that they successfully upgrade. If, after the network reaches a clear upgrade plateau (could take up to 6 days), you notice your nodes have not upgraded or shown any movement, please come forward and let the team know in Discord. This will help us identify and fix any issues in the upgrade process for affected users.
Then, press Ctrl + U, and hit Enter. This will upgrade your nodes. Upgrading can take several minutes for each node. Please don’t close the app or stop your nodes during this process.
Your nodes will now stop
Press Ctrl + S to start your nodes again
For MacOS/Linux CLI (antctl) Users
MacOS/Linux users will auto upgrade assuming you followed the steps in the previous release: Discord
For Windows CLI (antctl) Users
Run the upgrade: antctl upgrade --interval 60000
Finally, start them again with antctl start --interval 30000
Discord is the main place the team shares updates and have discussions, and we copy key stuff over to the forum when needed. I highly recommend you and others use Discord in addition to the forum to stay informed.
Ill report the issue here on the forum if I run into any trouble
[edit]
Looks like 85% of my nodes have auto-updated so far. Im not going to force the rest to update. Just gonna monitor them for a week and see if they figure it out.
Please can you post the standard method to upgrade client tools (cli). Especially if you need to keep the client tools in-sync with the general network (node) version.
I have no real good answer as to why it is not still promoted. It has a lot more use than just updating the node software. They don’t want people to update the node software with this utility, but its useful for the other apps
Mine started 6 hours ago with 7 out of 80 nodes on the machine having upgraded already when I looked.
On another note I started nodes on another machine, all new version obviously, and the version counts in the metrics show only the last 2 versions are being accepted by the new version nodes.
This will eventually eliminate all the old version nodes once most of the nodes have upgraded.
Expect the size of the network to drop yet again as all the auto upgrade nodes upgrade with very old nodes shunned and people who modified the code to not upgrade from 2 versions or more ago
wasn’t there an issue before where people could change version in code to keep their old nodes running? Is there a mechanism to prevent this? Not that there’s a reason to keep old nodes running but I’m just wondering, as it enables entities with bad intentions. Crashing the network has become a cheap and easy endeavor
it now stores the merkel payment so if the upload fails you dont have to pay again
its working similar to before most chunks go up fine and an odd one will be a bit stubborn to go up. but fingers crossed in a few days after after the upgrade is complete and the old nodes are shunned we may be off to the races!!
Thanks for the link @rusty.spork, which points to this:
Does this mean that auto updating relies on using antctl or will nodes run using antnode directly auto upgrade themselves?
I’m using @aatonnomicc’s script because it auto balances node numbers with system load, but it manages nodes without antctl. I think it seems to be updating as expected this time so no worries.
For MacOS/Linux Launchpad Users
For MacOS/Linux CLI (antctl) Users
Binary Versions
Autonomi Report
Total active ports: 1079