Hi everyone, today we are releasing TEST 6
The main focus of this test is the new Launcher UI.
Other changes include reduced network size (we are running 35 nodes compared to 100 nodes in TEST 5), data storage capacity increased to 5 times what a client could do before (500 PUTs instead of 100 PUTs), vaults storing more data per vault (2 GB instead of 1 GB) and max upload file size increased to roughly 50 MB in Demo App (instead of 5 MB).
Because of all these changes, we expect TEST 6 to be a much more stressed network than TEST 5.
Things to try: storing and retrieving data, seeing if you can login after some time progresses and running a vault.
- New Launcher UI with dashboard and log history
- NFS Create File API updated
- User credentials merged to a single input
- Proxy bug fixes
- FFI process restart issue fix
- Log list ordering is not consistent
- While registering an account, tab key doesn’t move to next field (have to hit tab twice)
- File size limit increased to 50 MB
- Compatibility with Launcher v0.6.0
Previously the user was required to enter 3 different credentials (PIN, Keyword and Password), which were used to locate the login packet in the network and decrypt it. Instead of requiring all 3, users now have to type only one secure account-password and the library internally derives three parts by hashing the account password and splitting the resultant digest into 3 parts.
Functionality for getting the account info is also added to
safe_core. With the help of this, Launcher will be able to inform the user about how many PUTs has been performed and how many remain (account balance) before they run out of ability to create more data on the network.
CreateFileAPI in FFI is at a lower level now and allows more direct interaction with the Self-Encryption code via Launcher. This should, among others, prevent the user from seeing 0 byte uploaded files when the account balance is nil but an attempt to create a file has been made.
The Put limit per account has been changed to 500, and the default storage size is now 2 GB. The routing code has seen some major reorganisation and some minor performance improvements.
Please be aware that this release will not allow older nodes or clients to connect to the network. You must use the new binaries below to connect to the TEST 6 network.
You can run only 1 Vault node per LAN – running more than 1 will result in this message “More than 1 routing node found on LAN. Currently this is not supported” – for the objectives of this test please respect this restriction.
This is a test network and comes with the normal risks of using pre-release software. Please also be aware that this test network will be reset, wiping all data that is stored on it.
- How to install SAFE Launcher
- Using SAFE Launcher
- Proxy Setup
- How to install the SAFE Demo App
- Using the SAFE Demo App
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.
If you are not sure if it is a real bug and have a 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 and of course as always thank you for participating in TEST 6.