Update 1 February, 2024

Steady progress is the message this week. QuicNet is up and running. Performance has been good, though we’ve seen and identified some issues with missing chunks (related to restarted nodes receiving payments to old keys), so we’re looking to address that.

Otherwise we’re keeping an eye on node memory, but things in general seem to be running not too badly with quic as the base transport layer :muscle:

General progress

@qi_ma is deep into following up testnet errors and issues as they crop up.

@roland has been working to further improve the node-manager and fix the CI processes which have become flaky since its inception. @chriso is also working to replace the testnet bin with the new node-manager for local development, and @bzee has started to dig into the node-upgrade process now that the manager is being used to deploy our testnets.

@jason_paul continues pushing forwards with documentation, as well as exposing a new feature to allow for easier cost estimation via the CLI.

Wallet improvements to allow for out-of-band signing have been merged, and now @bochaco is looking at further wallet cleanup, as well as starting to scope out what we might need and want from an Account Packet perspective.

The DAG work continues with @anselme fleshing out a basic client example, which we’ll be looking to expand into something useful as a way of auditing the network operations.

Thanks also to @mav for further work on the OMNI swap, which is shaping up nicely :muscle: !

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!


That must be a bit tongue o’cheek … QUIC is working brilliantly!

Thanks for the update this week.

cheers :beers:


Second!!! :)))

QUIC is proving to be a huge step forward, not only in terms of speed. However, I have only now managed to install the binaries to try, but I hope that these Windows installation errors will be resolved quickly :upside_down_face:

Bravo to the team MaidSafe and testers! Girls are you on board…? :point_left: :clap: :blush:


3rD! Now need to read… Great job on the Quicnet!


Short update => Busy team hard working. :+1:


Any chance of an update on the NAT traversal stuff? I think I browsed in the maelstrom of recent activity (that I’ve only had the time to quickly browse) that we’re still waiting on libp2p people to implement it for Rust.

  • How close does it look to coming to fruition?
  • If they don’t get there for some reason, or don’t get there for years or something, what do we do?
  • How crucial is it in terms of getting something (MVP debates aside) launched?

Cheers, and fair play to everyone involved behind the scenes and on the scenes, legends one and all.


Thank you for the heavy work team MaidSafe! I add the translations in the first post :dragon:

Privacy. Security. Freedom


Hard to tell really.

It just means less folk can run nodes from home easily. So a niggle, but a sore one, not one that will prevent launch though. Until we get nodes truly from home we lose a lot, but we can still grow


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

And we all cheering on the people working on the testnets! :horse_racing:


Thanks for the update, thanks to all involved.


Thx 4 the update Maidsafe devs,

Great to see the testers and devs in full swing.

Fear that i have to start my testing environment from scratch, really speaks volumes about how easy things are with a “rm -rf and safeup update” now adays :partying_face:

Keep testing and hacking super ants :beers:

Its amazing to wake up to so much reading material from the testnet :drooling_face: :sweat_smile:


I don’t think we lose that much, but they do.


Which aspect of libp2p is not read yet? What do we need for SafeNetwork?


Great update and nice start on maid transition work @mav!


Knowing Benno [waves] he’s aware of this but just in case, this might be a good guide of how the MaidSafe approach measures up against different threats:

Might also be worth contributing re p2p use case.



It doesn’t work in a plug and play manner from everywhere. You can run node from home, but you need to set some things up in the router in a manual, kind of geeky way. It’s not impossible, but raises the threshold. Up- an downloading does work very easily though.


Understood, very clear.

@Toivo’s response is clear there.

Implementations - libp2p – that’s a list of all the implementations of libp2p, if you scroll down and keep an eye on rust you can see what is done and not done. Each item is a clickable link to the github with the code implementing the thing.

Actually, if you scroll down to NAT Traversal it gives all three libraries the green light?! libp2p-quic has only a yellow light though, so perhaps that’s the issue.

Or maybe it is ready but nobody noticed? :smile:


Hey, just checking after few years later… Safe network already ready or still need few years? Beta?


It’s in the blurry quantum fuzzy boundary between beta and not beta.