Update, 25th September 2025

The big news this week is the release of our roadmap, which tracks components from early-stage breakthroughs to production-ready infrastructure. The roadmap plots various projects, features and applications so that developers and other interested parties can get an idea of their maturity (from incubation to production), the size/complexity of each project, and where it fits into Autonomi as a whole. Unfold the roadmap with us on X today (Thursday) 8.00 BST to hear @dirvine and @JimCollinson explain more!

We are preparing a new client for release next week with streaming changes as the main feature, and updates to the documentation accordingly. We’re also improving developer documentation and making it more accessible, as well as improving how we handle enquiries from interested third parties as we get close to offering them something tangible.

Also as a priority, we are working on signing certificates for Windows and Mac to put an end to the annoying security warnings when our binaries are identified as being potentially unsafe, and we’re shifting the team’s focus onto Indelible, our production-ready enterprise gateway for the Autonomi network.

Elsewhere, work continues on edge cases around reachability (how we can tell if a node is really viable) and removing relay functionality to replace it with something more efficient, and we continue to investigate and fix possible vulnerabilities.

On performance, we’ve refactored ant_networking for simplification and faster downloads particularly for users with slow network connections.

Community doings

@oetyng introduced the conceptual model of Mountable Vaults for his backup app Ryyn, in which a vault can be mounted anywhere with no central log tracking them.

@happybeing is preparing an app version of dweb for release, ideal for those who fear the command line.

@zettawatt created a joiners thread for the Autonomi Application Coop. Send him your ideas, goals and ways you’d like to contribute by October 1.

General progress

@anselme added some docs with working code examples for streaming.

@bzee wrote a binding to the encrypt method in Autonomi for Swift. He is now working on getting the encryption and decryption round trips working and streamlining the process.

@chriso worked on reachability tests, relay removal and the latest release candidate.

Ermine’s been implementing DigiCert for Windows binaries and has begun working on integrating this into the CI/CD pipeline. He also reviewed hackathon (Indelible) changes.

Lajos has got the paymaster into a state where it’s ready to be incorporated with the frontend or the client.

@mick.vandijke polished and wrapped up the downloader tool for Dave (GUI frontend). With the downloader tool we can download or directly import into a vault any files/archives through a data address or data map hex. He fixed the copy data address / data map hex button for archives and added tooltips to upload options for better explanation and a download button to the file details window.

@qi_ma refactored ant_networking for simplification and improved security and performance. He also raised a number of PRs [1] [2] [3] to improve download speed, large file I/O and to clean up outdated functions.

@roland worked on reachability and bootstrap process improvements. He fixed an issue where restarted nodes received connections from previous peers, impacting reachability results, made refresh_node_registry more robust by checking node connectivity if the PID is not found and simplified node table maintenance in Launchpad.

@shu patched ELK and Grafana clusters and Influx DB nodes with security updates, collaborated with Roland on reachability testnet results, identified an edge case that Roland is fixing and explored security scenarios in which nefarious users could game the system.

And @vphongph worked on CI features to simplify starting a network.

42 Likes

:smiley:

18 Likes

It’s here, the AutonomiDweb App is the easy way to browse websites and use apps directly from Autonomi. No command line!

Now to read!

25 Likes

Thanks so much to the entire Autonomi team for all of your hard work! :sweat_droplets: :sweat_smile:

And thanks also to the volunteers in the community, testing and working! :folded_hands:

Also, I posted a video on the new x402 protocol. Is this something the community could use?

Edit: When giving the employee contributions, put them in REVERSE alphabetical order every other week.

15 Likes

Could we shift the teams focus onto a native token instead? I think having the revenue go into the ANT token instead of Arbitrum would be better before bringing in enterprises to do big uploads. Otherwise it’s lost revenue imo.

24 Likes

Please do join us on the Spaces tonight — we will definiely be discussing that!

20 Likes

No dates on the roadmap? My kind of road map :joy:

12 Likes

Anywhere from 1 to 50 years for each.

3 Likes

Oh yes, I want native… I’ve already paid too much ETH for my failed uploads in Dave :joy:

11 Likes

Brilliant work all!

Seeing the roadmap gives a real glimpse into what’s being worked on behind the scenes, and there’s loads of stuff to get excited about in there. Some highlights for me include;

  • Location-aware networking that preserves privacy
  • Ant-QUIC networking
  • Quantum Threshold cryptography
  • Agentic payment system + OpenAI spec APIs
  • Fiat gateway
  • Mobile SDKs
  • App marketplace

It sounds like there’s a lot cooking, and a lot to look forward to in the development of the Autonomi ecosystem. This is just the beginning.

Looking forward to hearing more on the spaces tonight.

Fantastic work team and community :slight_smile:

17 Likes

Still no mention of native token.
:man_facepalming:

15 Likes

Join us on the Spaces in 15m and you’ll find out more!

9 Likes

Thank you for a comprehensive update. Looking forward to Spaces in a few mins to have it all laid out.

Thanks to all involved for your efforts.

Avanti!!!

8 Likes

Sorry @JimCollinson, I won’t be on Spaces. If there’s anything significant, please share it elsewhere too (for everyone :wink:).

7 Likes

The little I’ve picked up is destabilising and doesn’t give confidence. I can think of some very important promises that have been made over and over for months, and which suddenly change to nope, not really.

The thing that bothers me is as always how these sudden major changes stack up with respect to the fundamentals, particularly on privacy and being for everyone.

The changes I’ve seen - away from native token - look like being good in removing road-blocks for the masses, so :white_check_mark: on everyone, but how do they stack up on privacy? :thinking: It’s no good delivering another mass surveillance system, so hopefully they do.

I’ve asked Autonomi several times in recent months to explain where we are with regard to privacy and had no response. Was privacy talked about in Spaces tonight? Hopefully privacy and the other fundamentals are still the goal, but we don’t know how this roadmap delivers them or to what extent.

@JimCollinson I assume you are guided by and review all these changes and their implications against the fundamentals, but we are in the dark here, and it is frankly hard to trust when we have been told several things repeatedly and then, it’s no, not that after all.

Please can we have answers on how privacy will be maintained, and to what degree compared to x, y or z, with the move away from native token and to onboarding with credit cards and whatever?

I’d appreciate a review of privacy for each of uploaders, noderunners and downloaders. Any chance?

16 Likes

BTW do folk recall the day last September when the switch to Blockchain bomb was dropped, and I said that’s the end of a native token?

Then, and many times since Autonomi have denied that and promised it would happen, until today.

Since then, my insistence on this and the impact on the fundamentals was made out to be from a trouble maker who was damaging the project. Despite years of support, and when I had good reasons for believing this risk to be very high indeed, and concerned about the impact on the fundamental goals that brought this community to support the project, and have bound us together for years. Many since 2014.

Those concerns and my reasons for them were never addressed by Autonomi, nor did they put forward a plan to get back to native token.

I think we need to reflect on that when we are being promised things by Autonomi, which are not expected, and don’t seem plausible to those of us who understand how software, companies, projects and indeed people work.

20 Likes

To be fair, David has always said he doesn’t care about native token & the token is just not important to him at this stage. Bux and Jim have always said it will be focused on once the network / API is stable enough to warrant shifting resources to it.

I hope you’re not proven right in the end on this one… but so far, you can’t be proven wrong.

If AP2 and X402 can bring all of the benefits of native including scalability / low fees and privacy, great, perhaps native won’t be needed.

But, if they make privacy worse due to the less privacy focused communications needed around transactions, native may still be necessary to protect whistle-blowers etc.

The stuff David is working on sounds like it’ll greatly improve privacy in general network use, and perhaps those elements would provide protection from the potential privacy issues with AP2 and X402. If they do, it’d be great to hear how.

Table from ChatGPT, of questionable value, comparing Autonomi-native token privacy vs AP2 + X402 (hidden for those allergic to AI generated stuff):

Privacy trade-offs: Autonomi-native vs AP2/x402

Aspect Autonomi-native token (graph entries) AP2 + x402 + blockchain settlement
On-chain visibility None (private to Autonomi graph) Settlement visible on Arbitrum or other L2
Metadata leakage Limited if designed well (could use blinded graph entries) HTTP-based negotiation may leak IPs, timing, patterns
Auditability Internal (only within Autonomi network) Stronger, external (mandates auditable, visible to multiple parties)
Privacy strength Potentially high (custom-tailored) Lower unless layered with privacy tech (ZKPs, mixers, stealth addresses)
Interoperability Limited to Autonomi ecosystem High (AP2/x402 interoperable with many agents/services)
9 Likes

Btw, if anyone wants to experience the Markdown Web today, take a look at IMIM! :sweat_smile:

All blog articles are markdown documents, which are converted, on the fly, into HTML in your browser!

18 Likes

Amazing update and a roadmap! Wowsers!

I’m sure @JimCollinson and many others here would agree @dirvine, you make the future so exciting! That spaces, the new roadmap and soarsa labs, all awe inspiring. Bravo!

10 Likes