Announcement: Latest Release (CLN)
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 (will be added within 24 hours). Also dont forget to check out this weeks devblog!
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 update and upgrade. Run the update first: antup update
Then run the upgrade: antctl upgrade --interval 60000
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
Only the LATEST VERSION nodes will earn rewards, old nodes get NADA!
Not backward compatible for earning right? Can it be announced earlier? Since not all versions are stable, like the 0.4.0 that crashed last time. Who knows if the version stable before upgrading those nodes! Come on, can it be a deadline before cutting the rewards. And there is no release notes about what have changed, codes diff and testing on platform need time!
Sorry to say, as a developer, especially tuning those code to run it more stable, I just want to give a while I am still doing code diff for the pre-release source code, now cutting the rewards.
toivo@toivo-HP-ProBook-450-G5:~$ export CHUNK_DOWNLOAD_BATCH_SIZE=3
toivo@toivo-HP-ProBook-450-G5:~$ time ant file download 09ce1790489c71388b254d36134e61ae1e4c59df5768c04f3e0bbbdfc0c6c1ad .
Logging to directory: "/home/toivo/.local/share/autonomi/client/logs/log_2025-06-27_11-47-20"
đź”— Connected to the NetworkId { id: 1 } network
Fetching file: "screencap_2kB.png"...
Successfully downloaded data at: 09ce1790489c71388b254d36134e61ae1e4c59df5768c04f3e0bbbdfc0c6c1ad
real 0m58.931s
user 0m1.281s
sys 0m0.567s
toivo@toivo-HP-ProBook-450-G5:~$
Downloaded the same 2kB file few times in a row. Lot’s of variance:
real 0m33.407s
user 0m1.180s
sys 0m0.557s
real 0m47.265s
user 0m1.102s
sys 0m0.490s
real 2m7.347s
user 0m2.764s
sys 0m1.212s
real 1m24.419s
user 0m1.871s
sys 0m0.885s
Earlier today I even got:
toivo@toivo-HP-ProBook-450-G5:~$ time ant file download 09ce1790489c71388b254d36134e61ae1e4c59df5768c04f3e0bbbdfc0c6c1ad .
Logging to directory: "/home/toivo/.local/share/autonomi/client/logs/log_2025-06-27_16-00-26"
đź”— Connected to the NetworkId { id: 1 } network
0: Failed to fetch Public Archive from address
1: Record could not be found.
Probably these are going to smoothen after majority of nodes have upgraded.
Is it Neoverse? I run them on 8x A76 custom cpu, all failed said missing Home_Network parameter in the 1st line
The binary directly upgrade from antctl, not sure where is the bug, I am still code diff with the previous version. Maybe I should give up. Wasting time on this.
A55 just part of them working fine, most of them in S not R.
I mean the cpu type, I am not sure what crashed the whole thing up. But simply not working properly using the binary from official one. Linux version issue? Or gcc version issue? Since I am using gcc15.1 to compile the last version and fixed loads of issue. This version, I have no idea how to fix this.
lscpu
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: ARM
Model name: Neoverse-N1
Model: 1
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Stepping: r3p1
BogoMIPS: 50.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
yea guess i am using the neoverse after all.
If you are sell building sorry cant help much on that front all I know is that the arm bin from the release is running nodes for me here and im not using antctl so I recon antctl could be your issue.
Anyway thank you for your reply. I think I should move resources on other stuffs. I only wish this project can be as simple as it should. Then everyone can build different things on top, but I don’t think it goes that direction
I am going to reply to this thread in some more detail later.
But, it helps us if you show us what you are actually trying to do. There isn’t a lot of support we can offer if you just say it doesn’t work, or something to that effect.
Show us the commands you are trying to run and the output from them.
Yeah, I just regularly try downloads for fun when I have a minute to spare. De-duplication also makes uploads harder to test, because I should have something new to upload!
But I didn’t see this kind of variance in the DL times with the previous release.
Tbf, I did see performance regressions for the following 24h-48h after the last release, but then it was super quick after (much better than before the release). Latency increased a bit over the weeks since, but I’m hoping this cycle will repeat, but latency will stay lower for longer.
Announcement: Latest Release (CLN) 
while I am still doing code diff for the pre-release source code, now cutting the rewards.
although the 
