It's Network Upgrade Time Again!

[JimCollinson]

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:

1. Go to autonomi.com/downloads to make sure you have the latest version (v0.3.12).
2. The open it up, and press O to get to the Options screen
3. 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.
4. 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.

[upstate]

• The amount of bytes a home node could send and receive per relay connection is increased. This solves a problem where transmission of data is interrupted, causing home nodes to malfunction.

[Josh]

@JimCollinson

Fixes for the over-quoting for chunks that caused some moments, and some lucky winners.

Is this fixed in a way that will prevent people who dont upgrade from becoming ultra wealthy?

[Profess]

I hope my nodes will finally start making money, because I have already taken the computer apart! And it still won’t pay

---

No Safe, no wave.

[19eddyjohn75]

Thx 4 the update Maidsafe devs

Welcome Ermine Jose

Wow just wow, what a great update
Would be nice to have a overview of all the command lines you can use to interact with the Network

Keep coding/hacking/testing super ants

[storage_guy]

I thought I’d give the node-launchpad on Mac another try but I got this:-

./node-launchpad
node-launchpad failed:
Error: 
   0: Storage mountpoint for node data is not set

There is no hint in the help for the command on how to set this. I can’t find a reference to in anywhere in the site or the Mac instructions at For Mac Users | Getting Started

Any ideas anyone?

[itsMC]

If the node-launchpad does not start at all, for windows users, we managed to get it working by:

1. downloading the previous version of the node-launchpad
2. add a node
3. start the node
4. stop the node
5. close the node-launchpad
6. download the newest version
7. run the new node-launchpad

if you are able to run the new node-launchpad, but it does not add or start your nodes, then:

1. run the new node-launchpad
2. press O
3. press ctrl+D
4. select a drive where you want to run the node

[storage_guy]

@itsMC

If the node-launchpad does not start at all, for windows users, we managed to get it working by:

1. downloading the previous version of the node-launchpad
2. add a node
3. start the node
4. stop the node
5. close the node-launchpad
6. download the newest version
7. run the new node-launchpad

Amazing! This worked for me. Thank you for your help. And welcome to the Community!

So, as you said, I downloaded the previous version from:-

https://node-launchpad.s3.eu-west-2.amazonaws.com/node-launchpad-0.3.12-x86_64-apple-darwin.zip

Ran a node
Stopped it.
Downloaded v0.3.12
Ran it
Added nodes

So this seems to be a bug that crosses versions.

My interpretation is that the new version assumed the existence of the folder at:-

I’ve had a little dig and it isn’t necessary to do run the previous version first. On a Mac this is the folder and file structure that needs to be present:-

/Users/youruser/Library/Application Support/safe/launchpad/config

And there must a file in ‘config’ with these contents:-

{
  "discord_username": "",
  "nodes_to_start": 0,
  "storage_mountpoint": "/",
  "storage_drive": "Macintosh HD"
}

Replacing "Macintosh HD" with the name of your drive.

You could even put your Discord ID in that first line so you don’t have to enter it later in the Launchpad.

To create the structure do this:-

mkdir -p /Users/safe/Library/Application\ Support/safe/launchpad/config

or use the Finder.

Then create a file using Textedit called app_data.json with the above contents.

(There will be a way to create the file with an echo command but I can’t work out all the quoting for that.)

Then version 0.3.12 can be run straight away.

[JimCollinson]

@storage_guy

There is no hint in the help for the command on how to set this. I can’t find a reference to in anywhere in the site or the Mac instructions at For Mac Users | Getting Started

Any ideas anyone?

We have a fix coming for this later today all being well.

A new version of the launchpad that will knock this issue on the head, no workarounds required.

[JimCollinson]

New version of the Node Launchpad just dropped (v0.3.13)

It’s a fix for those who are getting the 0: storage mountpoint for node data is not set error.

Let us know how it works for you!

[storage_guy]

Works perfectly! 17MB of goodness that will change the world!

[Southside]

screenshot of your nano balance or its a lie!!!

[storage_guy]

Good point. Until it earns it’s all a bit academic. I’ll see if I can leave this Mac running.

It’s only 1 node so it could take a while…

[Southside]

It seems to be working well for me at home too - apart from the inconvenient “no nanos yet” bit.

[Southside]

@storage_guy

It’s only 1 node so it could take a while…

Could be a while…
New launchpad with 20 nodes from home over ~3hrs has got me nothing. Over on the rented BigBox I’m getting 50-100 nanos per hour from ~450 nodes.

So do not get discouraged if a single mode shows no results over seversl hours, it could still be working perfectly and having “normal” luck.

[storage_guy]

Meanwhile a bit of guerrilla marketing:-

That’s my excuse for spending the best part of an hour on slither.io !