As we said in some of the previous Dev Updates, the goal of TEST 8 is just to minimally test the network until all the refactors and RFCs (secure name, disjoint groups, data chains, etc.) for
safe_vault are tested and implemented.
It has been running for one week and as it is using the same vaults as some of the previous tests, it’s expected that some data is being lost. For example, you might be unable to login into an account you previously created.
Data chain integration is getting focus as a solution to coping with many Vaults of varying capabilities. Routing and Vault teams will be concentrated in this area during this iteration with the goal of getting Alpha 2 all on one network.
Appendable Data RFC
Spandan made a few changes based on the feedback he received:
After most discussions concluding last week, we decided to merge the Appendable Data RFC yesterday. It’s now known as RFC 38 and it can now be accessed here:
Andreas is planning to start the implementation of RFC 38 (Appendable Data) this week.
Now that Andreas is back, the Routing team is discussing the immediate options and measures we can take to make groups of nodes more secure (there are many approaches here and the implementation schedule is important to get right). - i.e. prevent an attacker from getting enough nodes to reach quorum and control group consensus -, what level of group security can be achieved, and if necessary, how the network can deal with malicious groups.
This week, Shankar is continuing the work in fixing the last lap of issues to complete the porting of the Launcher UI code. We are planning to work on improving the test module for testing the APIs and also integrate an e2e test suite for
The RFC for Launcher API v0.6 is being worked on. The major update in the RFC is the exposure of low-level APIs, which should enable developers to create dynamic applications.
Once the Launcher API v0.6 RFC is raised, Krishna will start working on integrating the FFI changes from the latest
safe_core master branch.
The FFI interface of
safe_core has been updated to a standard C-style interface. Spandan was waiting for this refactor to happen for a while and consciously stalled until the alpha was rolled out. Removing the JSON message pattern from the FFI will improve the efficiency between
safe_launcher. The current master branch of
safe_launcher is not compatible with the changes made in the
As a last minute addition to this Dev Update, the initial draft for the Low Level API RFC has just been raised. You can find the pull request here. This details how
safe_core plans to give complete low-level access to apps via
This week we are starting to work on the first tutorial. There is some backend work needed before we can start working on the code example, but we should still be able to progress on a few aspects of the tutorial (e.g. requirements, overview, introduction, list of topics, placeholders…etc…). We will also decide which tools to use to generate and host the Dev Tutorials.
We are pleased to announce that we have added another engineer to the Crust team: Nikita Baksalyar
He will likely start working at MaidSafe on the 12th of September. He’ll be joining Spandan’s team, working on
safe_core. This takes the total team to 17 and something we will continue to grow in the coming months.
He has a very insightful blog, you can check it out here: Rust in Detail: Writing Scalable Chat Service from Scratch.
SAFE Browser RFP
Two days ago, @joshuef released Windows, OS X and Linux binaries for the SAFE Beaker Browser. See this dev update for more details:
And now that the SAFE Dev Forum is open for registration, we are planning to close the original MaidSafe-Development Google Group (by making it read-only). All the content of that Google Group will still be easily accessible and searchable, but users won’t be able to create new topics.
If there are no objections, we will do this next week.