Update 27 April, 2023

Indeed, nice to see new folks coming on board!

Great update in general, good to hear that libp2p is taking care of the more generic stuff. It seems to be doing even more than expected.

The plan with the testnets sounds also good. I don’t mind if they live short or long, as long as they are any benefit or fun.

One thing though, that gave me goosebumps was this:

Please, tell me this is not a beginning of a new round of approach with total order, membership etc. :cold_face:


Nice and tidy update. Thanks team :wink: Seems things are cruising along at high altitude.

Greetings @aed900 - Hope you find your time here to be enjoyable and productive.

Cheers all! :beers:


100% not :smiley: That’s never happening again


That’s what I thought, just got to hear it from you. :smiley:


Thx 4 the update Maidsafe devs.

Welcome @aed900

Wow that’s really amazing 2 testnets, can’t wait.

This time they will also be bombarded with dick pics

Keep hacking super ants


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

More community based testing is here! :clap: :clap: :clap:


About time that a fella called Angus was brought on board, now you know that we’re getting close to the action :muscle: best of luck @aed900 getting up to speed and jumping in, fair play to you.

Data stored “in memory” here is not referring to something fancy, it just means in RAM on a client’s machine in the usual sense?

How does whether data is stored in memory or on disk relate to NAT traversal? It seems to be implied that data must be stored on disk for NAT traversal to become a possibility, and I don’t see the link. Maybe I’m missing something obvious.


Ah, that’s maybe bad wording, but we are tackling both next week, but they are not related.


Thanks for the update, its an exciting time.
Welcome @aed900, you picked a fine time to join us :slight_smile:
I hope your stay is long, productive and satisfying.
The agogometer is emitting a steady thrum and I have been forced to lubricate it with Bruichladdich twice already this afternoon. It has been taken from the shelf and placed carefully on the floor. Minimise the PE in case of sudden excess KE and tears.


Ah, ok, understood, cheers! Rereading :slight_smile:

Edit: actually, I think it was written fine, I was adding a link between the two things. Upon a rereading here, it is totally possible to not make the jump I did. Anyway, all clear now.


funnily enough I bought my router in Dubai and it cost about @aed900


Something I wonder: You mentioned a while ago that network is likely not stable with under 2000 nodes. Yet you seem to use only 24 in your testing. I’m sure it makes sense, but how?


I think we might be seeing issues because of this actually.
But hard to know. We haven’t yet been able to spin up 2k node testnets for ci.


Thanks all for the warm welcomes! Hopefully I can be of some use :slight_smile: Delighted to play any part in helping this amazing project reach its aims.


Welcome to the team @aed900
Hope you enjoy your time at Maidsafe and may your contributions be great.


why do we need 2000 nodes? I am imagining a app that would run ~20 nodes that would be your way of organizing and saving your data locally with de-duplication and reliably saved via redundancy!

but if the nodes are light maybe ~100 nodes? what is the target of reliable local network?


I would think that, for storing on the local drive, all chunks could be saved in one place and your browser or local host would just extract your chunks from there. I don’t see the need for running other node’s locally. The self encryption would still be pretty robust.


I see a use case for nodes, lets say you have 4 RPies with 1 node each so you have redundancy


Kademlia has an interesting property most folks ignore, but until circa 2000 nodes, the performance is not great. Not broken but flakey. What Engineers can tend to do is try to “fix” that, and that is a slippery slope.

Like an ant colony that until it’s about 1500 ants is also flakey, kademlia needs

  • A decent size network (say 2000 nodes)
  • Nodes to be communicating across the network (i.e. our DBC store means nodes need to check the parent is Spent. That performs the cross-network lookups to keep routing tables fresh)

This is why doing a bit of Safe is not great. That cross-network chatter is important. The same goes for network size.

The network size is why I am keen on quic and not TCP. quic is much more resource friendly and running several hundred nodes per computer is easy.


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

Privacy. Security. Freedom