Update 31 August, 2023

The DialNet testnet, launched this morning, contains some improvements to the issue of dialling unroutable peers - the one that was causing some nodes to remain chunkless. We have what we believe to be a fix in place now which we want to test out. It will still need some tweaking for performance, but we want to try it in the real world.

This week we’ve also been looking at the API and developer experience. We’re getting close now and we really want things to ‘just work’ for devs. This will be our primary focus over the coming weeks.

We’re also at the point where we can start seriously examining data replication, incentives, updates and resilience at scale. It goes without saying that the core functionality needs to be robust. Our approach is simple: simplification, simplification, simplification.

Looks like there are some improvements in libp2p coming in, including UPnP support which should allow some nodes from home. We try not to get excited by these developments, but we are quite excited!

General progress

@JimCollinson and @Andrew have been hard at work on product positioning. What should our initial approach be? Who are the main user groups and how should we speak to them? Should be something to share shortly.

A big PR has gone in with changes and tweaks to allow pay-per chunk. This means we now send to each node the payment it has asked for instead of trying/failing to randomly sample the network. This should make uploads more reliable.

@Bochaco is back (yay) and working on storing node rewards in local wallets, plus a CLI command to query node balances.

@Qi_ma continued investigating file upload issues and test failures with benchmarks. These are mostly fixed now. He also resolved a few CI failures on the pay-per-chunk PR.

@Bzee has been looking at the dialling unroutable peers issue and has implemented a fix. This is the main issue we want to observe in the testnet.

@Roland worked on client/node record stores and fixed a bug in the workspace.

@Chriso has been using GHA workflows to create and destroy testnets automatically. He’s also looking into alternatives to logstash, which we use to forward logs to S3 but which is turning out to be a bit of a resource hog.

And @joshuef has refactored the wallet code to improve performance and also worked on fixing the slow uploads issue.

Useful Links

Feel free to reply below with links to translations of this dev update and moderators will add them here:

:russia: Russian ; :germany: German ; :spain: Spanish ; :france: French; :bulgaria: Bulgarian

As an open source project, we’re always looking for feedback, comments and community contributions - so don’t be shy, join in and let’s create the Safe Network together!


First and I even read it! Great job @Maidsafe!


Nice work team! Thanks.


I’m waiting for the day that someone rushes to type “First” and accidentally posts “Fist!”.


Well done team! DialNet is looking great so far!!


Things are really flying lately and I’m amazed at the progress on so many fronts. Thanks everyone :clap:

I’m curious about this and look forward to seeing what you have in mind, but if you can say a bit more that would be great.

I’m wondering if this is similar to the past approach or radically different, and what “just work” means. For example, are you imagining a code generator using LLM or is that a completely different track? FYI I saw a blog (GPT Pilot – a dev tool that speeds up app development by 20x – Pythagora Blog) describing an interactive GPT4 based app building system today which sounded sensible, but haven’t read it.

Current status: :partying_face:


Thanks so much to the entire Maidsafe team for all of your hard work! :horse_racing:



That picture is horrendous


Sometimes my stuff works, sometimes it doesn’t. :laughing: :man_shrugging:


At the moment, it’s more like : Get in the basic APIs that devs could use. Get that core functionality solid + documented, then your LLM could analyse and utilise it sort of thing.


Thank you for an excellent update and lets all get tore into Dialnet. The team have worked hard to get us this code, its only fair that we as a community work hard to test it.

Too true. Sickeningly tokenist and faux-inclusive. Bunch of middle-class affluent wankers. I bet at least half of them are trendy veganfascists.

The pic, not the team – said he quickly :slight_smile:


Feels like we are getting close, exciting days, thanks all!


This video might represent the forum members a little better. Not saying who’s who though :joy:https://m.youtube.com/shorts/O8D7IZMRupM

Keep at it team and we will all be dancing like this sooner rather than later :clap:t2:


Having finally read a bit more around LLMs over the last weeks since seeing some of the plans on here, it does feel like MaidSafe would only have to make sure the API facilitates playing nicely with LLMs and projects will pop up. I don’t know if you’ll be able to buy a toaster in a couple of years time that doesn’t have “AI” plastered on the side of it.

I wonder what having a nice API for people who want to play with LLMs and different ways of interacting with the Network would look like.


Im taller that that…


I put ‘The MaidSafe community celebrating a new testnet’ into Midjourney, and here’s the first 4 options it came up with, lol:

Not sure why the weird blue guy has ‘ARSE’ on his top?

Anyway, silly pictures aside, it sounds like some real progress is being made. Really looking forward to it becoming more visible when there’s a UI and API for devs to play with!

Very much looking forward to hearing thoughts on the marketing and launch side of things as well as seeing the significnt rapid progress with the technical stuff.

Fantastic work and momentum MaidSafe :smiley:


What was once sci-fi is now within reach.


can anyone tell me how much work is left for launch. i am really non tech person, so can’t understand the update


What’s in code right now (some in github pipeline) with bugs contained is very likely what will alpha/beta launch the network. So tidy up the edges, some more testnets and we are on the runway for takeoff :wink:

Hold on chap, it’s all happening very quickly these days. We cannot be complacent, but we can be super optimistic here. The world needs safe secure data storage for all us humans.