Latest Release Feb 12, 2026

Development Updates
1

A new network release is now ready! Please follow the instructions below once the new versions are available to ensure your nodes stay compatible and continue earning rewards. Full changelog are posted with the release. If autoupgrade applies to you, please DO NOT manually upgrade.

We are asking all node operators to actively monitor their nodes and confirm that they successfully upgrade. If, after the network reaches a clear upgrade plateau (could take up to 6 days), you notice your nodes have not upgraded or shown any movement, please come forward and let the team know in Discord. This will help us identify and fix any issues in the upgrade process for affected users.

:desktop: For MacOS/Linux Launchpad Users

:desktop: For Windows Launchpad Users

  • Open Node Launchpad v0.6.3 if you are not already on that version
  • Press O to access the Options screen.
  • 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

:computer: For MacOS/Linux CLI (antctl) Users

:computer: For Windows CLI (antctl) Users

  • Run the upgrade: antctl upgrade --interval 60000
  • Finally, start them again with antctl start --interval 30000

:package: Binary Versions

  • antnode: 0.4.16
  • antctld: 0.14.1
  • antctl: 0.14.1
  • ant: 0.5.2
  • evm-testnet: 0.1.18
  • nat-detection: 0.2.22
  • node-launchpad: 0.6.3

image
image1024Ă—1024 295 KB

4 Likes
2

@DiscordTeam

Im having an issue with a single nodes that is still stuck on the 0.4.14 release. It has not automatically updated yet to 0.4.15 or 0.4.16 yet.

3

That is an interesting thing to examine. Is it the case that a node that is on 0.4.14 can upgrade to 0.4.16 or is it the case that only nodes on 0.4.15 can upgrade to 0.4.16 so your single node is permanently stuck on a back version?

1 Like
4

What OS are you on?

Can you get access to your logs? If so, I can give you some things to search for.

5

Any node that is 0.4.10 or greater has the auto upgrades feature and would update to the latest available version.

6

OS: Arch Linux (6.17.13-hardened1-2-hardened)
Yes, I can access the affected node’s logs.

7

First, search for the string “Error during upgrade process”.

If that isn’t present, try these:

  • “Next upgrade check”
  • “Node will stop/restart for upgrade at”

If you find any of them, post the full messages back here please.

8

Appeared 0 times

Appeared 0 times

Appeared 5 times

Running antnode v0.4.14
=======================
[2026-02-01T19:12:20.908790Z DEBUG ant_build_info 105] version: 0.4.14
[2026-02-01T19:12:20.908791Z DEBUG ant_build_info 106] network version: ant/1.0/1
[2026-02-01T19:12:20.908793Z DEBUG ant_build_info 107] package version: 2026.1.1.1
[2026-02-01T19:12:20.908794Z DEBUG ant_build_info 108] git info: stable / 4ce3c16 / 2026-01-29
[2026-02-01T19:12:20.935190Z INFO antnode 473] Next upgrade check scheduled for 2026-02-04 22:31:19.935185242 UTC
[2026-02-03T09:18:52.552168Z INFO antnode 473] Next upgrade check scheduled for 2026-02-06 07:13:52.552166917 UTC
[2026-02-06T03:47:04.726867Z INFO antnode 473] Next upgrade check scheduled for 2026-02-09 05:54:22.726864787 UTC
[2026-02-08T22:51:36.234893Z INFO antnode 473] Next upgrade check scheduled for 2026-02-12 00:25:34.234887368 UTC
[2026-02-12T00:25:34.242645Z INFO antnode 473] Next upgrade check scheduled for 2026-02-15 01:59:32.242645046 UTC
9

Hmm, it looks like your node isn’t finding a new release.

Can you send me the whole log please? Very interested to see what is going on here.