Safenode Upgrade 0.112.6

:loudspeaker: Announcement: Safenode Upgrade 0.112.6 :loudspeaker:

Please follow these instructions to upgrade your nodes to the newest version to ensure the best performance and stability for everyone! We have seen improvements in reducing resource spikes with this upgrade. Although you don’t need to upgrade to continue earning attos, I encourage you to do so.

For Node Launchpad Users:

  1. Open Node Launchpad v0.4.5 if you are not already on that version
  2. Press O to access the Options screen.
  3. 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.
  4. Your nodes will now stop
  5. Press Ctrl + S to start your nodes again

For CLI Tool Users:

  1. If you’re using the CLI tool, please update and upgrade. Run the update first: safeup update
  2. Then run the upgrade: safenode-manager upgrade --interval 60000

For ALL Users:

  • Please start your nodes gradually — especially if you plan on running multiple nodes.
  • Be conservative with CPU allocation to maintain stability

Binary Versions:

  • nat-detection: v0.2.11
  • node-launchpad: v0.4.5
  • autonomi: v0.1.5
  • safenode: v0.112.6
  • safenodemand: v0.11.3
  • safenode-manager: v0.11.3

19 Likes

@rusty.spork can you confirm what changes have been made to the reward algo and explain what effect they will have on potencial earnings please.

1 Like

I said you DONT need to upgrade from 112.5 to 112.6 for earning reasons. This upgrade has no direct impact on earning. It HAS seen stability improvements. It is your choice to upgrade now or to wait until the next one. Personally I would prefer people to upgrade, but you have that freedom.

4 Likes

Yes sorry there was some confusion in a private chat :rofl: solved it ourselves after some mild panic and pandemonium.

5 Likes

Just remember btw, we have a changelog now, and an excerpt from the changelog will always be in the Github release description.

@rusty.spork for the future I think it would be helpful to link to the Github releases in these posts.

12 Likes