Update 26 October, 2023

Over the past few years we’ve often sympathised with Sisyphus in the Greek legend. Sisyphus had to push a boulder up a hill for eternity only for it to go rolling back down again as soon as he neared the summit.

Not wishing to tempt the notoriously vengeful Greek gods, but we’re increasingly certain that this time we’ve finally cracked it, and we’re sitting pretty on the plateau. Why the confidence, oh ye who have stuck with us through thick and thin, oh ye who are maybe experiencing a faint feeling of deja vu?

Well because the bugs are getting smaller and we’re fixing them quicker. Because the whole team is fixing bugs together, rather than each having a specialisation. Because testnets are lasting longer and yielding results that we can understand and deal with. Because we can iterate on the fly with tangible improvements. Because we’re collaborating with like-minded people. And because the community are mucking in with their own fixes. We’ve moved from the theoretical to the practical, and boy does that feel good.

A whole heap of PRs went in this week, from the team, to the team and to some other projects. In summary:

Thanks to @southside for his helpful PR for a simple output improvement and to shuoer86 for some typo corrections. Everyone else, don’t be shy. If you spot something that could be tweaked or improved, drop in a PR or let us know on the forum.

General progress

@joshuef has been looking at store cost variations, and how clients are looping unnecessarily over increasing prices, and paying for data that’s already stored. (PRs 887/888). We’re tightening up the payments system by verifying who has the chunk and repaying them if necessary, not repaying all. In turn, this reduces stress on the verification process, meaning less pointless activity and improved performance.

Related improvements include eliminating redundant content hashing, and only verifying chunks in a majority of the close group rather than all of them to avoid unnecessary work.

@bochaco has been working on documentation changes for new cli/rpc-client commands, and testing testnet-deploy to verify that CashNotes can be downloaded and deposited to a local wallet. He also finalised the process to pay Foundation nodes and prepared the latest testnet to put it through its paces.

@bzee has been looking at paying a single node for data storage. As discussed last week, this could be a nice cheap and dirty option for storage without redundancy, so long as it proves sufficiently reliable. He’s also hopefully fixed another data leak around an ever-growing store in libp2p that holds identities of known nodes. The libp2p team are on that one now.

Meanwhile, @anselme revamped stored payments with CashNotes and Transfers.

@roland has been tuning his attention to replication, delaying it from instant to checking every 10 seconds to avoid unwanted blockages elsewhere. In addition, Roland has been optimising how nodes record and store their close peers to avoid duplication.

Replicating registers has been another holdout issue. If a register changes during the replication process, different nodes can end up holding different versions, with problems arising due to the CRDT convergence not happening in time. @Qi_ma has put in a fix for this now, so that’s another one ticked off.

And @chriso continues to improve the testnet automation process, including an install command for the node manager.

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!



Am I First for the first time ever


I will take second. Good work Ants…sounds like we are close


And third time to read the peak of the week :slight_smile:


What can I say but a huge thank you to the team and all who have collaborated to get us to where we are today.

This project is a beacon of light in a depressing world.


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

And also to all of the team members who help with the testing on the testnets! :horse_racing:



“Not crashing after 2 hours” achievement means position somewhere between alpha and beta stages of development.
That means there are still many things which needs to be done.
Combined with large complexity of this project it means that rolling back to “Sisyphus mode” is not that unbelievable.
But you may be lucky, this is true.


Great work team. :clap: The network is indeed becoming quite stable. MVP is clearly just around the corner. :tada:


Thanks to all community members putting forth heaps of time and energy to test things out and build tools for analysis - you rock!

Cheers :beers:


Is it like https://www.youtube.com/watch?v=3_TvpBwSZDM

I know I am much more https://www.youtube.com/watch?v=d-diB65scQU


This is one of the most promising updates I have ever read :tada: This calls for a new Testnet! :boom::boom::boom:


You went for Kylie and not Wet Wet Wet?


Thx 4 the update Maidsafe devs

In this update I read “A fix” so many times that I started :drooling_face:
Looks like we’re close to “the big bang :ant::fireworks:

:clap: :clap: :clap:
Keep hacking super ants


Great update, thank you devs!


Indeed, this is how I feel too. It also feels like the weight is coming off of the team’s shoulders, with some hardworking community members doing some heavy lifting. Thanks all, cheers!


Exciting progress! :clap:


I had a thought along these lines this morning about testing.

Do we forsee having a separate test network that runs along main much like some blockchains do.

It would need to be after upgrades for it to be permanent instead of individual tests as now.

Would it require incentives or could we just count on node operators to chuck a few nodes at it in “goodwill”.

Just some thoughts I don’t think have been discussed.


Question about nodes:
In the final Safe Network, do nodes calculate the cost of chuncks only based on SNT, or do they adjust for the price in $? So if the price of SNT in dollar goes up, do they decrease the chunck price and vice versa?
If so, how do they get this dollar price? Do they read it from a single source (certainly hope not) or do they negotiate it between a group of nodes?

If nodes do not adjust for dollar price, early days could not be so profitable (think early bitcoin).

Just thinking out loud here, sorry if it has been discussed before.


Yes, they have no idea of $ value.

The operators do though and if they are not paid enough $ they switch off and the SNT amount goes up (basically making $ amount go up) and vice versa.