Update 6th November, 2025

Development Updates
1

image
image830×430 59.6 KB

We’re very grateful for community members bringing to our attention a vulnerability which allows folks to attempt to manipulate the network’s emission system. We are addressing this now, as well as working on tools to allow us to check the distribution of chunks on the network to make such vulnerabilities easier to find in future. Ultimately this will lead to a stronger, more stable and scalable network. Network emissions are currently suppressed but will increase once again in line with the schedule in the whitepaper, supporting capacity growth and consistent earnings.

As @bux notes in her update this week, turning nodes on and off provides no emission benefits but risks network instability. Looking ahead, updates on roadmap items like Paymaster and app building will be shared in the weekly update. We’re also increasing community engagement through Discord and here on Discourse.

Community doings

Welcome back whiteout2! He’s been working on SAFE-FS, an encrypted decentralised FileSystem for Autonomi and has returned with a new Web App and a soon-to-be-released (Dart) Android App that will be released across iOS, Windows and Linux. :partying_face:

Traktion has chipped in with a new AntTP release. Version 0.17.5 deprecates the public archive (upload) status endpoint in favour of using the command queue status instead. :flexed_biceps:

And safemedia has wowed us all with AutoTube, a decentralised video platform. :heart_eyes:

General progress

@Anselme wrapped up node integration and started hacking into client integration, the last step before we can start seeing gasless payments in action!

@bzee worked on a demo app for Android; he’s still working through networking configuration issues. He improved GitHub Actions for mobile bindings for iOS and Android and implemented the graph entry API.

@chriso, @qi_ma, @roland and @shu made progress with replication tests, and Chris is also on Merkle tree payments testing, and the chunk tracker service, raising a PR to add public file uploads and chunk tracking functionality.

@mick.vandijke tested uploads with Paymaster (gasless payments) on Dave, improving error reporting and fixed bugs.

@Ermine raised a PR for wallet management frontend and setup.sh changes, enabling local/mainnet switching and private key management, together with backend changes for wallet management. He also readied the Windows binary signing certificate for inclusion in the next build.

roland simulated the entire replication flow, including uploads and local close group replication, creating a PR for replication simulation, identifying record location issues in a 10k-node network.

@qi_ma has been looking into distributed storage verification via peer cross-checking. He updated this PR to prune the record_store indexing cache and continues to implement chunk tracking tests.

@shu tweaked the dashboard to enable us to monitor the chunk tracking/ant analyse service based on on current stats/outcome from our internal testnet.

And @vphongph worked on tests and CI for Indelible features including token management and expiration.

41 Likes
2

First! And what an amazing update that is.

14 Likes
3

wow first lets go

(oh wow sniped by 0.21 ms)

:heart: aww :grin: glad to be back. The network is looking amazing :trophy: 2026 is the year!

17 Likes
5

I’m so sorry mate! You deserved that to be the first.

10 Likes
6

all’s fair in :heart: and :water_pistol:

9 Likes
7

This is great to hear. Improving communications between team and community is always appreciated :slight_smile:

:tada:

Very much looking forward to seeing this. Mobile apps will certainly make it easier to use Autonomi regularly, and show others what the network can do.

Loads of great progress across the board from the team, and community as well. Exciting times ahead!

Great work all! :slight_smile:

12 Likes
8

Thanks so much to the entire Autonomi team and our diligently helpful community for all of your hard work! :man_factory_worker: :man_factory_worker: :man_factory_worker:

Our team and community is the best in crypto! :1st_place_medal:

11 Likes
9

I’m sorry, I still don’t understand, possibly because of my English. Please help me to better understand: does turning nodes on and off not provide any advantages in receiving emissions, but does it allow for a reduction in costs for per-minute server rental?

1 Like
10

If it does offer that, or any other advantage, I’d imagine the team would quickly work to remove that anyway, because turning nodes on / off damages the network’s stability

6 Likes
11

Okay. Thank you for this clarification. Could you please tell me if the team has written anything indicating they’ve already done anything to fix this?

1 Like
12

There is a new upgrade for the nodes. But Bux said already a couple days ago that there’s no benefit in turning nodes on and off.

On the other hand, the ones that have been doing it, have stated that by doing it they can run more nodes per machine. See the quote below. I don’t know which to believe.

4 Likes
13

And it seems to me that this formulation is somewhat vague… Well, yes, such nodes do not receive more favorable emissions, but do they optimize their rental costs or disk space in order to increase the number of nodes?

1 Like
14

Replying with Bux’s comment on this:

image
image1834×215 48.8 KB

6 Likes
15

I guess their fix is not in the node software, but in the way/schedule of the emissions. And they don’t want to reveal the fix in order to protect against possible new hacks.

Anyway, it’s great that it’s fixed!

4 Likes
16

I’m pretty sure they’d be happy to allow anyone find a new hack at this stage. If it’s possible, someone will find it eventually. They will rather have it at this stage than at full scale adoption.

5 Likes
17

Oh yeah, now I see what was my confusion!

1 Like
18

Great update and all the good work being performed

Although if one actually reads what they are doing and why, you see its not along the lines this suggests. Its that they can run more nodes, thus increase the share they get.

While you are introspectively looking at the emissions algo/system, you are missing the whole point of their exercise. Its not about manipulating the emissions system, but manipulating the way the nodes are working and banning not enough to ban the nodes quick enough and returning quotes. They do this because the fuel for their exercise is enough to give then a increased ROI. IE more emissions per server they rent.

Change perspective and its becomes clearer as to why they do this damaging resetting. And emissions that are not related to amount of data stored but just following a unshakeable plan will eventually fail. Let it be based on quantity of data stored and it encourages good node behaviour and it will rise to the amounts of the white paper in short enough time. Set algo multiplier to a reasonable amount and it starts off small because we have little atm, but when the fee reduction comes in the amount of data will rise. But people will not upload while there is apparent loss of data as we have now due to these leeches.

But it seems I am shouting in the wind here by the lack of seriously considering why they are completing resetting and starting new nodes every 12 hours.

9 Likes
19

But wasn’t the exploit not about turning nodes off and on, but about wiping the data folders?

Problem that arise is essentially the same, just the cause is slightly different.

2 Likes
20

Thx 4 the update Maidsafe devs and all your hard work

@whiteout2, @Traktion, @safemedia :star_struck:

What if network instability is the benefit? :wink: :united_nations: state…

:bug: bounties should be rewarded for kids hacking the universe… :cricket: :cricket: :cricket:

I prefer my launcher like a virus, auto-update and can’t be turned off unless the entire computer turns off…

Great update

Keep hacking super ants, but try to think like a hacker also to keep the Network stable :people_hugging:

9 Likes