Thank you to everyone who got involved with TEST 3 last week, the data from these real world tests is invaluable to the Dev team, so your participation is useful and important. We do plan on rolling out another phase of community testing, however, we would like to include the newer async networking component that is currently being implemented in Crust as part of the up and coming TEST 4. We anticipate this will greatly improve data persistence. As you can see from the update below the team are burning the midnight oil and completion of the next batch of pre-release code is imminent, so it should be the beginning of next week when the next iteration of the software is ready for another round of public testing. In the meantime remember that the community have their own test network up and running I personally have a Vault running adding resource to this test network - nice work from @bluebird and to all the community contributors running a Vault, while poking and prodding that network.
##Crust, Core: Andrew, Spandan (tl) & Vinicius.
The team are currently focused on implementing the async work in Crust and that work is nearing completion. Nat traversal is already functional, the only missing piece is IGD. IGD is a 3rd party crate and porting it to async is taking a little time because internally it uses http pull parser, etc which are themselves blocking. IGD or Internet Gateway Device is a client that communicates with a UPNP enabled gateway device (a router).
Service Discovery (beaconing to find peers on LAN) is complete and now tested. The bootstrapping process sans Service Discovery has also been tested. The only remaining parts to conclude are the Direct Connection listener, parallel bootstrapping and hole punching connect which we aim to have completed this week. Although that might sound overly optimistic, the amount of effort being put in by the guys and progress thus far allows us to this prediction relatively confidently.
All of this means that Crust becomes fully async for the first time and on all platforms that we currently support. This will of course result in much less resource usage, context switches and makes for faster and easier to maintain code. We plan on integrating with Routing and thoroughly testing it very soon.
##Routing, Vaults: Adam, Andreas (tl), Fraser & Qi.
We are currently doing some spring cleaning: After months of frantic experimentation some parts of our code have become quite unwieldy, which is slowing us down a little. So we have rewritten much of
kademlia_routing_table and are going to extract some functionality out of the Routing core module, amongst other ongoing simplifications and refactorings. This should not take more than a few days to complete and will greatly help us move forward quickly afterwards.
We also finished the implementation of the “Ack” feature, which will greatly reduce the amount of redundant messages that we send.
##Client : Krishna (tl), Ross, Scott & Shankar.
A test suite is being integrated for the launcher to test the APIs as part of CI. We are in the process of integrating Travis and Appveyor to run the CI scripts with the
ffi dependency of the safe_core.
An RFC for the launcher API standards will be raised this week (tomorrow likely ). The RFC is going to detail how the streaming APIs can be added to the launcher, along with a few clean ups.
We are also planning to drop the encryption between the applications and the launcher. Since the launcher and the applications all run on the same local machine, it wouldn’t be a necessity to have the encryption between the applications and launcher. A few community members were in favour of this approach, however, please feel free to let us know your thoughts.
The launcher tests that were integrated have exposed few bugs with the APIs, the plan is to work on these and get them fixed before we start on the next set of launcher enhancements.
We shall announce and release the next round of community testing here on the SAFE Network forum, so keep your eyes peeled for the TEST 4 post.
Thanks as always for your all of your support, here is a link to the weekly transcript.