In the screenshots of the up and coming launcher improvements it shows that there will be a limit on the number of puts. What determines this limit? And does this mean safecoin will be implimented so that users may gain more PUTs? 100 PUTs doesn’t sound like a lot to work with.
2 Likes
i hope you can recover a little bit! you did absolutely impressing - didn’t expect the result to be this amazing - i absolutely love this project and the team =)
11 Likes
It’s curious that despite the damage done by the disruptive event, the network hasn’t recovered in a way that allows new registrations even. I would have hoped that simple catastrophic loss of data from a large chunk of the network being lost, would not stop the remaining nodes resettling. Perhaps the fraction of loss here was too high and when consensus is so disrupted the remainder cannot work?.. but then would they not look back to the seed nodes if they lost all local nodes they could trust??
Vault up and running I think. I got a number of these errors:
ERROR 21:11:58.429295012 [routing::core core.rs:648] Node(2c4dca…) Failed to prepare connection info: Nat(Io(Error { repr: Os { code: 24, message: “No file descriptors available” } }))
And some warnings:
WARN 21:11:59.538260427 [routing::core core.rs:1903] Node(2c4dca…) Prepared connection info for PeerId(54e7…) as 2d4771…, but already tried as 2d4771…
But the rest of the stdout log activity looks healthy (from my untrained eyes!):
INFO 21:24:51.545335297 [routing::stats stats.rs:172] Stats - User (Request/Success/Failure) - Get: 7/7/0, Put: 0/0/0, Post: 0/0/0, Delete: 0/0/0, GetAccountInfo: 0/0/0, Refresh: 13
Just home and getting started right away with testing
Thanks Maidsafe Devs for your hardwork and rigorous analysing/testing of the Network 
4 Likes
For most testnets, your files are stored on droplet cloud server accounts last time I saw. It’s similar to Amazon Web Services. This is only for testing though.
When the BETA Safe Network is ready and live, user account files will be stored in a few duplicate copies on other farming computer drives around the world, through many layers of encryption.
1 Like
Very cool!
I tried to set up a vault, but I am in a loop of
Same here (Mac OSX vault):
INFO 22:42:32.324050000 [routing::core core.rs:1032] Client(2120ae..) Running listener.
INFO 22:42:35.405354000 [routing::core core.rs:1555] Client(2120ae..) Sending GetNodeName request with: PublicId(name: 2120ae..). This can take a while.
INFO 22:43:35.408944000 [routing::core core.rs:1807] Client(2120ae..) Failed to get GetNodeName response.
WARN 22:43:35.409171000 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 22:43:36.708818000 [routing::core core.rs:1032] Client(d77de2..) Running listener.
INFO 22:43:39.714738000 [routing::core core.rs:1555] Client(d77de2..) Sending GetNodeName request with: PublicId(name: d77de2..). This can take a while.
INFO 22:44:39.720577000 [routing::core core.rs:1807] Client(d77de2..) Failed to get GetNodeName response.
WARN 22:44:39.720746000 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 22:44:41.039850000 [routing::core core.rs:1032] Client(f619a6..) Running listener.
INFO 22:44:44.237259000 [routing::core core.rs:1555] Client(f619a6..) Sending GetNodeName request with: PublicId(name: f619a6..). This can take a while.
INFO 22:45:44.240831000 [routing::core core.rs:1807] Client(f619a6..) Failed to get GetNodeName response.
WARN 22:45:44.240956000 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 22:45:45.551241000 [routing::core core.rs:1032] Client(9ccd11..) Running listener.
INFO 22:45:48.754678000 [routing::core core.rs:1555] Client(9ccd11..) Sending GetNodeName request with: PublicId(name: 9ccd11..). This can take a while.
INFO 22:46:48.758055000 [routing::core core.rs:1807] Client(9ccd11..) Failed to get GetNodeName response.
WARN 22:46:48.758173000 [safe_vault::vault vault.rs:145] Restarting Vault
INFO 22:46:50.075371000 [routing::core core.rs:1032] Client(2ac37a..) Running listener.
INFO 22:46:53.264406000 [routing::core core.rs:1555] Client(2ac37a..) Sending GetNodeName request with: PublicId(name: 2ac37a..). This can take a while.
And my launcher doesn’t connect/let me register either.
Installed just minutes ago
Looks like I am connected now 
1 Like
Launcher connected here, too. Restarting vault – no information yet. Edit: appears it connected. Not sure why this would work after the restart and not on its own retry though …
I got that “this could take awhile” error, too. But I restarted vault and it’s fixed now. What a time for me to enter TEST 4 lol. Anyway can’t wait to continue testing…!
1 Like
safecoin …
3 Likes
Thanks for your answer.
We are actually able to rub vaults. And I am rinning one which is eating my disk space 
at least I think it is…
Around 500mb have gone since the vault is running. But a very quick glimse at last changed files didn’t shiw where this space has gone to.
So will we HAVE safecoin? Does this imply it will be implemented? I think I asked this in my original post. So far the test nets have had uploads running off the droplets. And we haven’t had to worry about safecoin. It’s a bit fuzzy as to when the implimentation of safecoin or test safecoin, or however the team wants to do it, will begin.
We will but not just now, this simulates you have paid X safecoin. For now it allow us to model behaviour of safecoin
9 Likes
Awesome. Can we have that as an API for Apps, too? It’d be very helpful if the App could tell the user they need to get more “credit” before performing an action/when an action fails because of that. (Thinking of Ghost in the Safe, which could know the “puts” needed and tell the user, it can’t deploy). Maybe even through some extra headers like for rate-limits?
Did the update actually work?
I am getting:
{"errorCode":-18,"description":"CoreError::GetFailure::GetError::NoSuchData"}
First connected, other three still lurk around. There isn’t a commandline parameter to tell them to connect to the other one I have running first and take it from there, is there? I fear that the ones that are set in the default config might be out of allowed connections counts or something? Restart didn’t change anything.
@ MaidSafe, my stats are a little odd. Seeing a lot of this:
INFO 23:09:20.356934000 [routing::stats stats.rs:172] Stats - User (Request/Success/Failure) - Get: 10/8/1, Put: 2/2/0, Post: 0/0/0, Delete: 0/0/0, GetAccountInfo: 0/0/0, Refresh: 210
Shouldn’t the counts be: Success + Failure = Requests? Why is that not the case for my Get? That sounds like some form of bug…
2 Likes
Here’s @Blindsite2k dragging @dirvine away from his weekly 8-minute nap, to ask about whether Safecoin will come into existence , and when, because no-one ever asked that before.
6 Likes
I can’t register Launcher. I only just recently downloaded all the binaries. Am I missing the update?
3 Likes
No… it’s the same here. Some disruption appears to have caused network to seize up in some way. See above a large chunk of the network went down at the same moment. Too many vaults run by one person in a small network. I was hoping that bringing new vaults online after that would have helped but not seen any improvement… can’t register and appear to have lost access to other accounts.
2 Likes