I’ll keep this update as brief as possible, since most of you are fully aware of where things currently stand. The planning phase for RUST-5 is complete and the tasks have been added to Jira, the sprint duration is scheduled to last three weeks. We anticipate the following two deliverables at sprint end.
- Stable vault network, accommodating churn, using TCP/UDP with UDP Hole Punching.
- Core Launcher implementation.
The first will be made available via cross-platform installers in the form of a safe_vault package. The network should provide a stable base for client account handling/NFS storage API. The implementation of this part resulting from RFC-0008 and RFC-0011. The second will be command line only, exposing a CLI example showcasing the features of the Launcher, which in future sprints will be wrapped with a UI. The implementation of this part resulting from RFC-0010. Further detail on both can be found in last week’s update, while sprint progress can be followed on the Dashboard.
As a reminder, the Jira tasks for RUST-5 are available for bounty where some specific GitHub issues have also been included. Anyone wishing to take on a task should write a comment below the task description to that effect, i.e., requesting the task be assigned to themselves, once assigned, hit the start progress button and begin. When the task is complete, issue a pull-request, PR, to the master branch of whichever library is being worked on and someone will be assigned by Highfive as reviewer. For convenience it would be appreciated if the PR comment includes the bitcoin address of the committer. Further, in the Jira task itself click the start review button and assign it to whoever Highfive assigns on Github.
Testing will be ongoing during the sprint, however, it can be expected that some lingering issues may inevitably be present after the deliverables are released. Community support will be of great importance in determining network stability here by providing the first full scale test of the SAFE Network. We would expect to enter an iterative update and release cycle at this point, until stability is realised, based on patches provided/received for any issues discovered.
The weekly transcript is also available for viewing.