Quick one this week as we continue to observe the effects of the changes made in the latest beta which went live on Monday. It’s looking good so far. We’ve had a great reaction, and already have tens of thousands of nodes live (sorry, haven’t got the latest numbers to hand). Thanks to everyone who has rolled their sleeves up and got involved.
A summary of the changes can be found here.
New team members
To make sure we get over the finish line we’re delighted to welcome two new team members: Aaron is a cybersecurity expert who will be making how-to videos and documentation and helping answer support tickets on Discord, and Mick, a software engineer who is currently working on our wallet security.
Beta v2 instructions
For new joiners and current beta testers who haven’t reset their nodes yet, here’s what to do.
If you are using the Node Launchpad, download the latest version and run it.
Reset your nodes with Ctrl+R, type ‘reset’ and hit enter. Then reboot your device, start Node Launchpad and start some new nodes with Ctrl+G.
If you are using the CLI (Node Manager) you can find the full list of commands for resetting your nodes on GitHub. However, please remember this option is not officially supported, so it’s community support only.
Don’t forget to add the --owner
argument to add in your Discord Username each time you add a new node. Also leave an interval of at least 2 seconds when starting each node to keep your system happy.
Any nanos earned across either the old or update Network version will be recorded, so you won’t miss out.
We are about to initiate a seamless transition over to an upgraded Network. It won’t affect the ongoing beta rewards program (every nano will still count and be counted!).
General progress
@anselme updated security checks to work with the latest refactor of transactions, worked on a design for sn_api
, and implemented a double spend prevention measure. @roland is also working on testing in this vital area.
Talking of refactoring @qi.ma has been reworking the spends code to make spends lighter and simpler.
@bzee continues his journey down the rabbit hole of home-node connection issues, and the possibly related topic of why some nodes are not earning nanos. Some issues may have to do with very conservative relay server limits, so he’s looking to experiment there.
@chriso has been working hard on automating releases and making the process run more smoothly. We should now be in a position to have a release ready every two or three weeks up until launch.
@mazzi upgraded the discord bot to work with the new network’s DAG. He also fixed a bug that was causing bot messages to be published on Discord.
And @shu Investigated higher CPU usage on the new release as reported by the community.