A new network release is now ready everyone! 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. No emissions incentive change for now.** It is very important for the network that you are using auto upgrade if you are on MacOS/Linux. **
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.
I’m not aware of special steps for this. Please can you post all instructions here for those who don’t use Discord.
Anyone know if auto updates play well with @aatonnomicc’s awesome anm script which has been auto updating my nodes for several releases now. I’d like to leave it alone if possible.
@scottefc86 reports that auto updates work and I think he is still using anms so i think we are good to go just watch the bandwidth new nodes are thirsty for bandwidth.
I had to drop from 2k nodes from home to 750 nodes
yes if you want anms to upgrade nodes 1 at a time.
but im thinking just set the upgrade hour to 25 so i never runs and then the nodes should just auto upgrade. but you would need to run antup node so that any new nodes added by anms will be the latest version.
auto upgrades will probably brake anms as it tracks versions of nodes in an array when it starts them.
Also I have been tinkering with adding the possibility to choose amount or % of nodes to stop if thing goes Southside, it is not done yet but hope I get some time soon.
My nodes have settled back down now and using around the same b/w as before, maybe a tad higher, but I had the headroom anyhow.
Wonder how much traffic your file testing is causing? Its good to do since that level of traffic would not even be as high as a well used autonomi network
I have to say that I’m not seeing a difference. Maybe a slight decrease now they’ve all started and things have stabilised for my 50 nodes on an RPi4.
I had 2 k nodes using about 60Mb/s up down then stopped all nodes and started 1500 nodes and my broadband was saturated so I decreased down to 750 nodes and is at same level as before.
Ok, so looking at my NTracking graph (thank you!) it’s clear mine are using a bit more bandwidth for the same number of nodes. About 2.4Mb/s before and about 3.1Mb/s now:-
Chriso helped on Discord. Apparently --no-upnp is needed when setting up the nodes. Hasn’t been an issue before now for me, but seems to sort it, so that’s good.
Edit: Ah, spoke too soon… lasted longer, but died again.
The node will use a random port number if you do not set the port. And its more than likely some nodes will choose a port in use by another program. The node is supposed to check that port was not already in use on the system. But programs can start after the node that force their use of the port. Set the ports above 50,000 for safest place.
And yes --no-upnp is a must anyhow.
I doubt either of the above will help your problem but certainly help with the reachability of your node by uploaders. And this also affects quote requests.
For MacOS/Linux Launchpad Users
For MacOS/Linux CLI (antctl) Users
**Binary Versions **
