Today, we are releasing Test 15. See this topic to download the binaries for Test 15:

SAFE Network - Test 15 Updates It is our pleasure to be releasing Test 15. Here are the changes compared to Test 12c: Fixed the crust timer overflow bug. Use SHA3 everywhere instead of SipHash. Several merge and tunnel fixes, and additional tests for merging and tunnels. Nodes now try to reconnect after a connection drops. Fix the bug which created an empty log file when timestampping was set to true in log.toml. Allow users to force include TCP acceptor port in connection info via new option in crust config file (force_acc…

The new safe_app APIs have been shaping up well. The Node.js API should facilitate development of applications using Node.js and the DOM API should make it easy to build dynamic web applications. Over the weeks, we have tried various approaches to ease the installation process and, having integrated the dependency downloader, usage of the safe_app_nodejs library is now much simpler.

Though the browser and the apps can be built manually and used with the mock routing feature of safe_client_libs , we still need to provide a dev mode for browser and the Node.js API. This will be useful for the devs to switch between the real network and the mock network as and when required during the course of development and testing. This will also help facilitate running test cases for applications using mock routing, along with some additional test functions, so that the test cases can be executed without the dependency of the Authenticator.

We are also planning to work on a developer website, which will host all the resources for application developers as well as helping them learn about the networks core concepts. The developer website will be hosting the content for fundamentals on getting started, API documentation, tutorials…etc… This is just being specced out this week and more information will be shared soon.

Now that the Node.js API is becoming stable, we are planning to start implementing the Java APIs in a couple of weeks. The Java APIs can be used for Android applications too. This will open the door to start testing on mobile, which will be exciting!

SAFE Authenticator & API

@bochaco and @shankar have worked hard to implement the DOM APIs and also to test them. During the course of implementation, there were a few scenarios for which they had come up with alternate solutions as some eventualities were not supported out of the box. However, they have integrated the DOM APIs with the SAFE Browser and also have been testing them for the last couple of days. @bochaco is creating simple snippets to test the API integration while @shankar is porting the Markdown editor sample to the latest API.

@lightyear is porting the email application to the safe_app_nodejs API, along with the fixes for the bugs that we come across as we keep wiring up more examples.

@bochaco and @frabrunelle are also working on a post to explain how to build the browser and example applications, along with some very simple sample snippets to showcase the usage of the DOM APIs. We are hoping to post this on the SAFE Dev Forum early next week.

SAFE Client Libs & Crust

Vault support for MutableData is progressing. The integration tests that cover the MaidManagers are fixed. They compile and run but a couple of them keep failing. So we’re currently investigating that.

Carl started the actual implementation of the uTP protocol in Rust last Friday. Next week, we are hoping to get some early news about how things are progressing in terms of the uTP API.

Routing & Vault

We extended the unit tests, especially for tunnels (nodes that help connect two nodes that fail to establish a direct connection) and section merges, which exposed a few issues. So lots of debugging this week, but we managed to solve several problems and at the same time simplify the merge process.