Then, press Ctrl + R, type reset, and hit Enter. This will stop your nodes, RESET, and update them with the latest network upgrades.
Close Launchpad and reopen it.
Press Ctrl + B and add your ETH wallet address.
Press Ctrl + G to restart your nodes.
For CLI Tool Users:
If you’re using the CLI tool, please RESET your nodes as well, utilizing the latest Node Manager (v0.11.1). A full reset command guide is available on our documentation site for reference.
For ALL Users:
Please start your nodes gradually — especially if you plan on running multiple nodes.
Be conservative with CPU allocation to maintain stability.
Expect higher resource usage than before; plan to run about half as many nodes as previously to accommodate these changes.
The new contract address is 0xBE1802c27C324a28aeBcd7eeC7D734246C807194. You will need to “+ import tokens” to add this under the ARB Sepolia network to see in MM.
Thank you for preparing and helping ensure a smooth launch!
i just added it on meta mask an hour ago and it worked so not got any ideas i did hide the other ant contract first so i dident confuse myself in case that makes a difference.
On this graph ‘Out’ will be traffic to the Pi from the network.
I’d shutdown the nodes and reset a day and a half ago! The 5 nodes at the time were doing about 4Mb/s in and out on the switch port at the time so you don’t see that and until about now this traffic in the Kb range would have been lost at the bottom of the graph. I’d seen the port was still getting hundreds of Kb/s for a few minutes which is fair enough because nodes will still think it’s there for a bit.
But it looks like the length of time it takes them to recognise the nodes are gone and never coming back is longer than me and maybe anyone else thinks.
So when you reset nodes be aware that the computer, your network connection, router, swtich and everything in between will still be receiving traffic for a looooong time after!
That might affect your ability to run a new set of nodes.
You might be able to properly jam up your network in terms of received traffic by starting a lot of nodes (whatever ‘a lot’ means in your context), letting them run for a bit, stopping them and resetting them, starting up new ones and repeating that a couple of times.
I can’t think of a way of getting rid of this traffic because it will be coming from everywhere on any port and you’ll need to continue allowing that all the way through your network for the new nodes.
I don’t really understand the ‘In’ on the port though. That implies the Pi was sending stuff back in response but there was nothing to receive it as the nodes were down and the Pi had been rebooted. Is it maybe the Pi telling the router that it isn’t going to do anything with the packets? I don’t know enough about networking. I just notice stuff that I think looks odd!
Anyway, my main point is that traffic to nodes takes a long time to completely die off.
Quick question: can we use the same receive address as before? I just added the new contract - 0xBE1802c27C324a28aeBcd7eeC7D734246C807194 - to the same ‘account’ on MetaMask as before. So there are 2 ‘ANT’ tokens and it looks like this:-
Thanks. I might do that now that one won’t be getting any more attos to it. But I’m not massively confused - yet. I’m just trying to work out if I can use the same address. Which I think I can because it let me add the new contract and safenode took the same address.
I’ll just know for sure it’s all working when I see some attos arriving on it. But I’m wondering if this is something that should work.
Announcement: Preparing for Today’s Release 
(though we didn’t want to have anything to do with those blocks)