SAFE Network - TEST 6

Development Updates
1

Hi everyone, today we are releasing TEST 6 :tada:

The main focus of this test is the new Launcher UI.

1651Ă—648 58.6 KB

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.

What’s new?

Client: Krishna (tl), Scott & Shankar

Launcher

  • 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

Known limitations:

  • Log list ordering is not consistent
  • While registering an account, tab key doesn’t move to next field (have to hit tab twice)

Demo App

  • File size limit increased to 50 MB
  • Compatibility with Launcher v0.6.0

Core: Spandan (tl) & Vinicius

  • 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.

  • The CreateFile API 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.

Routing, Vaults: Adam, Andreas (tl), Fraser & Qi

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.

Get involved in TEST 6!

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.

Download

Documentation

Where should I report issues?

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.

53 Likes
3

wow, how many long does this pw have to be? I’m half way through Pink Floyds wish you were here and I’m still short…

8 Likes
4

yeeeeeey :smiley: let the party begin! :smiley:

routing table size 25 and growing :slight_smile:

6 Likes
5

the launcher looks amazing!!!

try http://www.chunky101.safenet/ in a few mins, its uploading now but Ive got to dash out for a few mins

8 Likes
6

This is great to hear, exactly what we were working with this morning: integrating additional API commands into the SAFE-FS web app.

Very glad these parts received attention.

Making a push to release another version of the SAFE-FS Web App with more API integration before our sale finishes

AND: New Launcher UI is great, very clean and functional :slight_smile:

5 Likes
7

http://polpolrene.safenet

2 Likes
8

Looks like the demo app for Linux is missing

1 Like
9

34 in the routing table.

http://test.bluebird.safenet

3 Likes
10

I have 3 PUTS already and the only thing I did was register my account.

http://www.upstate.safenet - Just the template for now but doing my part to test. :slight_smile:

3 Likes
11

Yeh sorry about that. @AndreasF is just updating the Linux binary for the demo app right now since the original upload had a space in the file name.

Should be up in a few minutes

EDIT: Should be updated now

9 Likes
12

Problem remains with failed service creation then not allowing second attempt.

Upload speed is fast!.. visible in the dashboard… I just did 19.4MB and it zipped upto 99% but then has stuck there. It could do with some indication of what then is occurring at that point… I guess it’s perhaps validation on the upload.

Dashboard total data upload suggests 18.5MB and the diff I guess is compression.
What’s hard for the user is guessing how many PUTs will be used.

So, I’ve used 30 PUTS… had to close the Demo App after ~10mins of nothing apparently happening.

I tried to return to create the same service… hoping that failed service would not be an issue and that I’d be able to redo it but it fails to create the directory in /public/ because something of the fail exists.

So, knot.safenet doesn’t exist… though PUTs have been used and perhaps small files within the directory might have been successful… I expect the larger file will be more likely the issue. [Add Some Web Content] suggests nothing and looks brand new but then can’t create directory because it suggests NFS error /public/www/ exists.

(This was on the back of the Linux Demo App originally - so unclear what the space in filename issue was, as I grabbed it ok.)

2 Likes
13

Same here, I’m stuck at 99% with some personal data.

1 Like
14

Just to note there’s a 50MB file size limit.

1 Like
15

would be running 2 vaults if it wasn’t for the:

root@ncac111:~/safe_vault-v0.10.4-linux-x64# ./safe_vault 
INFO 18:42:59.889482890 [safe_vault safe_vault.rs:99] 

Running safe_vault v0.10.4
==========================
ERROR 18:43:01.983720251 [routing::core core.rs:270] Disconnected(dd72f1..) More than 1 routing node found on LAN. Currently this is not supported

bugger!

so only able to run one… :disappointed:

rup

1 Like
16

have discovered if you start the 2 vaults at as close to the same time they both run without a problem… :slight_smile:

not sure if this is an issue?

but i’ll run both unless i hear there is a problem…

rup

2 Likes
17

That makes perfect sense: they only look for other vaults during a brief time window before they actually start.

18

My file upload (42 MB) is stuck on 99% for over 5 minutes already.

1 Like
19

Looks like everyone is having that problem (me included)

Smaller files works

1 Like
20

It can tell “heaven from hell, blue skies from grey” etc. :wink:

7 Likes