In case you missed it yesterday, it’s time for another upgrade to the Network… once again thanks to all your persistence, perseverance and, well, legendary testing chops.
Here’s what you need to do if you are a Node Launchpad user:
- Go to autonomi.com/downloads to make sure you have the latest version (v0.3.12).
- The open it up, and press
O
to get to the Options screen - Then press
Ctrl R
and type the word reset and hit enter. That’s going to stop your nodes, rest and upgrade their software, bringing in those network upgrades. - To get them started once more press
Ctrl G
choose how many you want to start by pressing up and down, and then hit enter. And you are done!
If you are a power user using our CLI tool—the node manager—you can use the upgrade command, no reset is required! We’d still recommend an --interval 10000
So what’s changed?
For the Launchpad
Well for starters, Launchpad users will notice some new goodies:
- There’s a new tabbed interface for Status, Options and Help.
- You can now choose a different drive for the node’s data directory, from the options screen. Woot!
- Plus, there’s a handy way to get to the Logs files from the option screen too.
The new tabs will also allow us to roll out a bunch of new feature in the next release too. Yaldy!
For the Network
There’s a boat-load of fixes and improvements, which should boost the Network:
- We’ve increased the relay server’s circuit bytes limit, to reduce incoming connection errors. It means amount of data a home node can send and receive per relay connection is increased. This solves a problem where transmission of data is interrupted, causing home nodes to malfunction. We expect this to improve connectivity and earnings for home nodes!
- Fetching the network contacts now times out and retries. Previously we would wait for an excessive amount of time, which could cause the node to hang during start up.
- Fixes for the over-quoting for chunks that caused some moments, and some lucky winners.
- Plus some Node Manager goodies:
- Several new metrics are available for the node.
- The
start
command now waits for the node to connect to the network before attempting to start the next node.
As always, check out the full change log for all the juicy details.