Latest Release May 9, 2025

:loudspeaker: Announcement: Latest Release :loudspeaker:
Please follow these instructions to upgrade your nodes to the newest version to ensure the best performance and stability for everyone! Check out the Github Release with changelog details.

For Node Launchpad Users:

  1. Open Node Launchpad v0.5.8 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: antup update
  2. Then run the upgrade: antctl upgrade --interval 60000
  3. Finally, start them again with antctl start --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:

  • antnode: v0.4.0
  • antctld: v0.13.0
  • antctl: v0.13.0
  • ant: v0.4.0
  • nat-detection: v0.2.20
  • node-launchpad: v0.5.8
6 Likes

Thanks @rusty.spork ! Is there a change log this time? It would be great to acknowledge all the improvements the team have made.

4 Likes

Immediate reaction

Nodes upgraded to v0.4.0 are not restarting

I am seeing this in Formicaio logs
2025-05-09T21:28:37.343336Z ERROR antnode 463] Node stopped with error: Node terminated due to: "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward.

This is on two seperate VPS each with ~200 nodes running fine with port forwarding 55000 56000 managed with Formicaio.

1 Like

I cant get LP working at all right now personally. Ive reported my findings to the team but everyone but Shu is offline right now so we wont be able to get anything done today. Sorry for the inconvenience guys.

3 Likes
xxx@base:~$ ant wallet balance
Logging to directory: xxxxx
Error: 
   0: Failed to get EVM network: Failed to obtain the desired EVM network via any means

Location:
   ant-cli/src/commands/wallet.rs:85

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
nite69@Bookworm-base:~$ cat xxx/ant.log 
[2025-05-09T22:26:01.425239Z DEBUG ant_build_info 105] version: 0.4.0
[2025-05-09T22:26:01.425275Z DEBUG ant_build_info 106] network version: ant/1.0/1
[2025-05-09T22:26:01.425279Z DEBUG ant_build_info 107] package version: 2025.5.1.2
[2025-05-09T22:26:01.425281Z DEBUG ant_build_info 108] git info: stable / dea8fc7 / 2025-05-09
[2025-05-09T22:26:01.425352Z ERROR evmlib::utils 177] Failed to obtain the desired EVM Network through environment variables
[2025-05-09T22:26:01.425358Z ERROR evmlib::utils 98] Failed to obtain the desired EVM network via any means
nite69@Bookworm-base:~$ 

1 Like

There are some worrying features here:

  • issuing a release when there’s little support (a Friday!)

  • what seems to be inadequate testing beforehand, which by now should be running like clockwork

I hope this is sorted quickly and the reasons will be learned from for future updates.

3 Likes

Yea, I just tried upgrading, by the time it had upgraded 2 of my nodes they had failed, so I quit.

I start the nodes directly, so it seems to be the node itself and not LP or antctl

4 Likes

My nodes upgraded and started nicely. Only the wallet balance does not work. Running only 20 nodes with antctl and 20 nodes with formicaio, just for fun (not for money :laughing: )

1 Like

Looking at antnode help there is a change to the options.

v 0.3.11 had --unpn to set it using upnp

v 0.4.0 has --no-upnp and has to be set to true to disable upnp

This will be a problem to all people running on VPS or direct to internet or run antnode directly

People using upnp will most likely have no issues

3 Likes

Will it affect the emission rewards? Or backward compatible for this upgrade?

2 Likes

I apologise for the issues, but just to be clear, you don’t need to be on the latest version of the node for the emissions. There are no real changes in the node for this release other than the name of some arguments, which has unfortunately introduced some clumsy issues.

4 Likes

I have changed my node start to include the option --no-upnp and 15 minutes later the first of the upgraded nodes are still running. And none have failed.

This seems to be the problem

2 Likes

Thx, since I am working on tuning antnode running on RISC V, not too bad so far😬

1 Like

Yeah, it’s just the arguments, and that’s why it won’t be working with the supplementary tools either.

Nothing has really actually changed in the node with this release. It was mainly improvements to the client and new Python bindings.

3 Likes

Its running fine for me at home with Formicaio, the problems are on the VPS.
I’ll probably just swich them off 400 nodes out of 3m wont make much odds and its not as if they are making me any real money.

You are under orders to chill for the weekend :slight_smile:

1 Like

Yeah, as Neo has mentioned, it will be to do with the upnp-related arguments.

I also just want to say, it is already our general policy to not release on Fridays. This time we gambled with it and lost. We were keen to get it out since the original date was on Wednesday but it had to get pushed back for various reasons.

On the client side, we observed better upload times with some changes that Qi has made, so people may want to try that out.

4 Likes