Great work. I have my hat off to team.
FYI atm the mo we’re aware the the browser POC has had a issue with packaging, so those packaged versions don’t go just now. I’ll update when they’ve been fixed
Wow just wow what a great update Maidsafe devs. Congrats on getting so much code out of your system you gals/guys are the best. It’s borderline that this is happening. Jippy SAFE network your so close…
Excellent work. Where do we go from here?
Have you given consideration to implementing upgrades sooner?
I feel once upgrades are in place the community spawned ecosystem will begin flourishing. It’ll be all eyes on SAFE.
Is Fleming mature to the point of functioning in a Data Center in some useful capacity i.e something deploy-able that drives the Maidsafe company value/ potential for funding?
Not yet, next phase though, possibly. At the moment it is a single vault that emulates the whole network. Next phase will be a network of vaults (single section). After that it is full deploy (multiple sections).
So the phase coming up could be deployed in a data center with some ease AFAIK. We may need to ensure broken nodes can be replaced etc. Certainly something for us to consider, we can use digital ocean or similar to emulate exactly that.
ahh of course, there is no data storage at the Fleming milestone:
SAFE Fleming Network
The next major milestone for the SAFE Network. Whilst the Alpha 2 Network will continue to function, this will be a standalone Network that will enable individuals to run decentralized routing nodes from home. There will be no data storage capacity on the Network as such. Instead, you’ll see fully-encrypted transient data moving across a Network that also responds to malicious nodes.
That is all updated now Chris. We do have data storage, the notion of Fleming being a routing node and adding some app on top of the routing node was scrapped. So now it is full feature releases where each is more than the previous. So Fleming will be more than AlphaII was instead of less.
I think this is a cleaner story and also allows the whole team of Engineers to progress on all fronts at once instead of waiting for routing completion.
Can you please make more clear which of all those “Upcoming Network Features” after Maxwell are necessary to be done before release of first official public version? By such version I mean a network where current Maid token will be converted. There are multiple items in that list like Secure Enclaves, network restarts, etc… that I am not sure are required for first stable version. So in simpler words, what will be really missing after Maxwell release.
Fantastic, hopefully the roadmap page can be updated to explain the new story.
Agreed - this would be really helpful for those trying to use the project plan to understand the state of progress.
Really, security audits, upgrades and that should be us. The tuning of any farming and so on will happen during Maxwell if we think it requires it, but it will be hard to tell until there is the real financial incentive. Anyway tl;dr upgrades, cleanups and audits.
I’m grateful for all the work the team is putting into this!!
Governments and corporations continue to make a better and better case for the SAFENetwork by abusing data. Digital privacy is required for a humane digital future. Push on! Take care of yourselves! Be Well!
I think the Core Technology DevHub page may need an update also:
Thank you for the new Vault “toy” Team @MaidSafe!
The translation into Bulgarian is ready and after there was no objection to my Proposal: Send us your translation I have the courage to add it to the Dev Update itself
About SAFE Client Libs: Are there new Java bindings available and if not, any ETA?
From the update:
“This release has a known limitation: it does not include the FFI API yet as we have decided to take more time to design it in collaboration with the front-end team. It will be included in future releases.”
I assume this means there are no Java bindings yet.