Announcement: Preparing for Today’s Network Upgrade
Please follow these instructions to upgrade your nodes to the newest version to ensure the best performance and stability for everyone! Although you don’t need to upgrade to continue earning attos, I encourage you to do so. We need a majority of node owners to upgrade to the newest version for the webApp… also referred to as “Dave” to work properly.
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.
Your nodes will now stop
Press Ctrl + S to start your nodes again
For CLI Tool Users:
If you’re using the CLI tool, please upgrade by running this command: 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
Getting this on 3 different X64 machine (1 node) ? so will wait for more info - do i need complete reset ?
╔═══════════════════════════════╗
║ Upgrade Safenode Services ║
╚═══════════════════════════════╝
Retrieving latest version of safenode...
Latest version is 0.112.4
Downloading safenode version 0.112.4...
Download completed: /home/user1/.local/share/safe/node/downloads/safenode
Refreshing the node registry...
Attempting to stop safenode1...
✓ Service safenode1 with PID 13959 was stopped
Attempting to start safenode1...
Upgrade summary:
✕ safenode1 was upgraded from 0.112.3 to 0.112.4 but it did not start
Error:
0: There was a problem upgrading one or more nodes
Location:
/home/runner/work/safe_network/safe_network/sn_node_manager/src/cmd/node.rs:604
I still launch safenode directly and I’m seeing this error with the latest version:
safe@Vader:~$ export RUST_BACKTRACE=1; /home/safe/.local/bin/safenode --port 45000 --root-dir /var/safe/safenode1 --log-output-dest /var/log/safe/safenode1 --rewards-address 0xDE2aA8E70bf792385b0223144B9407EBc85E7938 evm-arbitrum-sepolia
EVM network: ArbitrumSepolia
Logging to directory: "/var/log/safe/safenode1"
Error:
0: Could not parse the supplied multiaddr or socket address
1: invalid multiaddr
Location:
sn_node/src/bin/safenode/main.rs:274
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 5 frames hidden ⋮
6: <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Result<core::convert::Infallible,E>>>::from_residual::h7458ee51f5ae5e2c
at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14/library/core/src/result.rs:1987
7: safenode::main::h5c7acd6b1668c54f
at /home/runner/work/safe_network/safe_network/sn_node/src/bin/safenode/main.rs:274
8: core::ops::function::FnOnce::call_once::h29b7f28dc9cca8fa
at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14/library/core/src/ops/function.rs:250
9: std::sys::backtrace::__rust_begin_short_backtrace::ha46545ab8063dc4e
at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14/library/std/src/sys/backtrace.rs:154
⋮ 11 frames hidden ⋮
Log entries are:
[2024-11-12T22:17:07.034031Z INFO sn_peers_acquisition] Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
[2024-11-12T22:17:07.145305Z DEBUG sn_peers_acquisition] Attempting to parse /ip4/167.71.140.72/udp/37462/quic-v1/p2p/12D3KooWMrQ95QFLzKkyTc2X3aEFqGhH5cPmsf1QkCuAD4PWNqyW
I’m now getting this error whichever Launchpad connection mode I select. This may be helpful (I’ve never earned a single atto on this particular machine so maybe there’s a problem there), or it may be a bug. Will wait to see what others find. Linux Mint.
What is the definitive way of checking your earnings?
The block explorer shows I have 7 attos, but is says also that the last transaction was 16 days ago. On the other hand Launchpad said I had earned 3 attos during the last week.
EDIT:
My mistake, I looked at the old token before launch.
Yes there should be 2 contracts when you pull up your ETH wallet address on ARB Sepolia scanner. For the time being please use the block explorer for the ultimate source of trust as we are using the blockchain to determine earnings/payouts.
Just learning this @chriso. Apparently on Macs all you need is caffeinate -d in the terminal to keep the system awake. That might be helpful to have in future builds?
On second thought I may be misinterpreting some reddit posts. It may just keep the display on, though that should keep the system awake? Amphetamine allows system to stay awake but also allow display sleep. Dunno. Maybe something to look into.
For devices like laptops that their systems sleep when you close them it disrupts the nodes. So I wondered if it could make sense to have such a command integrated into launcher or node software.
Ah ok. I’m not sure if it could possibly be part of the service manager. Is this a component that is always part of a macOS install or is it an optional installation?
Announcement: Preparing for Today’s Network Upgrade 
