##Updated: 7th May 12:15 BST - Test 2 now complete.
Test 2 is now complete and the network is being brought down - big thank you to everyone who took part .
Firstly, we would like to thank all those who took part in our previous test, your feedback was very useful and allowed us to take many measurements. This has led to several improvements as you can see below. These are very exciting days as we now can run networks, connect people from across the world and from their own homes. So a very important step, but one which must not be misunderstood or extended too much. This milestone is still a test and in the last 14 days we have made significant changes and improvements at quite an incredible pace. This test will help us ascertain that certain invariants are being held.
Again we must emphasise this is a test, we have not fully secured group consensus in this release as well as some network encryption. Data is encrypted, of course, but this test will not maintain anonymity.
###Do you want to run a Vault from your own computer?
Today we are releasing the next iteration of community test binaries: SAFE Vault, SAFE Launcher and the SAFE Demonstration Application; this is the next phase of the rolling test releases. Today, users of the SAFE Network will able to run a Vault locally on their own machine and join this iteration of the test network. So you will be contributing to the SAFE Network which the SAFE Launcher and the SAFE demonstration application will connect to.
So yet again it is time to set up your anonymous ID’s and test what we believe is the world’s first autonomous network that allows you to log in and store / retrieve private data without the involvement of any intermediaries.
###What is new since the last test phase?
As well as squashing bugs, an enormous amount of work has been completed in the last couple of weeks:
- Increased ability for TCP NAT traversal.
- Increased Vault stability.
- Reduced network messages (ongoing work).
- The addition of user facing log messages and statistics.
- Significant simplification of persona strategy regarding ImmutableData (removal of three personas).
- The removal of uTP support (to be assessed during a later release).
- Implement heartbeat messages to detect lost connections more quickly.
- The addition of version numbers to the protocol to avoid connecting to incompatible peers.
- The Implementation of a process to automatically build release binaries.
- The Implementation of a process that automatically creates docker containers.
- The provision of a docker deployment process and documentation.
- An increase in the timeout for polling bucket groups.
- Enhance the network statistics gathering.
- The addition of the routing table to NodeAdded and NodeLost events.
- The addition of NetworkStartupFailed and StartListeningFailed events.
- An improvement in the join limit to prevent damage to the network in case of many simultaneously joining nodes.
- The ability for the network to drop unneeded connections from the routing table.
- Several tweaks to churn handling in data_manager.
- The re-organisation of tests to use mock Crust instead of mock Routing.
- The reimplement the refresh algorithm for structured and immutable data to make it less wasteful and more reliable.
- The re-implementation of TCP send / receive using payload size + data.
- A refinement of deserialisation error reporting.
Please be aware this release will not allow older nodes or clients to connect to the network. You must use the new binaries to connect to the network.
This is a test network and comes with the normal risks of using pre-release software. Please also be aware that this is a test network and will be reset, wiping all data that is stored on it.
We currently provide 64bit test binaries for Linux / OS X / Windows and for Vaults also an experimental ARM release (Requires kernel version > 3.9)
###Where should I report issues?
During this testing phase Github is the best place to report issues and bugs. Using Github will help us (MaidSafe) manage issues and prioritise work within the Dev team faster. We are going to use Github for issues during testing as the uptake of JIRA was pretty low, existing logged issues in JIRA will still be worked on and support and issue management will continue to evolve as we move toward launch.
If you are not sure if it is a real bug and have question, the forums #support category is a great place to post this. As we know this is a friendly and responsive community and someone will help you out.
Thanks again for taking part and we hope you enjoy this test, it’s great to have you guys on this journey with us.