Latest Release Feb 19, 2026

Development Updates
1

A new network release is now ready everyone! 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. Please not you must be on node version 0.4.15 or newer to earn.

We would like to encourage Window users to upgrade quickly because this is the last time you should need to do it manually :rocket:

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

  • Open Node Launchpad v0.6.4 if you are not already on that version
  • MacOS/Linux users will auto upgrade assuming you followed the steps in the previous release: Discord

:desktop: For Windows Launchpad Users

  • Open Node Launchpad v0.6.4 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

  • MacOS/Linux users will auto upgrade assuming you followed the steps in the previous release: Discord

: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.17
  • antctld: 0.14.2
  • antctl: 0.14.2
  • ant: 0.5.2
  • evm-testnet: 0.1.18
  • nat-detection: 0.2.22
  • node-launchpad: 0.6.4

image
image1536×1024 293 KB

12 Likes
2

It’s good to see another update to wring as much information from 1.0 before it is replaced.

5 Likes
3

15 nodes has nearly brought a 32GB AMD Ryzen 5 3600 6-Core to its knees…

image
image3372×1313 382 KB

I’ll likely reduce it to <12 to maintain smoothness on my desktop box.
My other node boxes all have various excuses about not enough RAM, not enough free disk space etc etc for now

5 Likes
4

I’m experiencing a huge amount of data ingestion today. Looking at my stats, the used data size on my HDD has increased by 30GB over the last 4 hours. I really want to keep my nodes up as long as possible until the network resets, but at this rate, I’ll have no choice but to reduce the number of nodes.

image
image1703×814 193 KB

4 Likes
5

Im on 2 nodes here :melting_face:
Granted not a desktop but it could do 40 plus at 1 point.

Screenshot_20260224_102343_Chrome
Screenshot_20260224_102343_Chrome993×576 101 KB

4 Likes
6

image
image1233×336 68.7 KB

top - 20:59:07 up 158 days, 12:28, 1 user, load average: 3.58, 5.66, 7.10
Tasks: 115 total, 2 running, 113 sleeping, 0 stopped, 0 zombie
%Cpu(s): 40.0 us, 26.9 sy, 0.0 ni, 22.4 id, 0.5 wa, 0.0 hi, 6.3 si, 3.9 st
MiB Mem : 3821.5 total, 209.1 free, 1952.5 used, 1929.9 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1869.0 avail Mem

top - 20:59:22 up 158 days, 12:29, 1 user, load average: 6.68, 7.78, 8.50
Tasks: 114 total, 1 running, 113 sleeping, 0 stopped, 0 zombie
%Cpu(s): 28.8 us, 20.6 sy, 0.0 ni, 23.4 id, 18.6 wa, 0.0 hi, 4.6 si, 3.9 st
MiB Mem : 3821.6 total, 140.3 free, 2195.2 used, 1749.9 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1626.4 avail Mem

2 Likes
8

I made a super embarrassing mistake in my previous post, so I deleted it and went to sleep to forget about it​:sob:
I’ve fixed the issue now, so here is the repost.

My nodes seem to be capping out at around 48GiB. I’ll keep an eye on them.

image
image1385×229 35.6 KB

Here is the command I used, adjusted for the standard antctl environment:

du -s -BGiB ~/.local/share/autonomi/antnode*/record_store | sort -h -r | awk '{ match($2, /antnode[0-9]+/); node=substr($2, RSTART, RLENGTH); printf "%-10s %-5s\t", node, $1; if (NR % 6 == 0) print "" } END { if (NR % 6 != 0) print "" }'
1 Like
9

That is a nice oneliner but you were missing the ‘/node’ directory. So it should be:-

du -s -BGiB ~/.local/share/autonomi/node/antnode*/record_store | sort -h -r | awk '{ match($2, /antnode[0-9]+/); node=substr($2, RSTART, RLENGTH); printf "%-10s %-5s\t", node, $1; if (NR % 6 == 0) print "" } END { if (NR % 6 != 0) print "" }'
1 Like
10

The determining factor will be the records stored more than the amount of storage that will determine the limits of a node’s storage. The limit is 16K records and absolute max storage would in theory be 64GB if all records were max record sized (4MB)

2 Likes
11

Thanks for catching that! I keep making silly mistakes today :sweat_smile: I appreciate the correction.

That explains it! I actually saw the 16K record limit mentioned over in the “Weekly Developer Update: February 19th, 2026” thread as well. I just ran a command to count the records, and you hit the nail on the head—many of them are maxed out right around 16,388.

image
image1911×248 134 KB

Here is the command I used to count the records, updated with the correct path!:

for d in ~/.local/share/autonomi/node/antnode*; do echo " $(ls -1 "$d/record_store" 2>/dev/null | wc -l) $(basename "$d")"; done | sort -Vr | awk '{ match($2, /antnode[0-9]+/); node=substr($2, RSTART, RLENGTH); printf "%-10s %-5s\t", node, $1; if (NR % 6 == 0) print "" } END { if (NR % 6 != 0) print "" }'
1 Like