Fleming Testnet v1 Release - *NOW OFFLINE IN PREPARATION FOR TESTNET V2*

Development Releases
583

Tried again with a different Linux device (same router). It looks like I can connect OK but the join process times out. I’d be interested to find out if anyone else is having the same problems creating a new safe.

[user@user ~]$ safe auth create --test-coins
Passphrase:
Password:
Sending request to authd to create a Safe…
Error: AuthdClientError: [Error] ClientError - Response not received: read error: connection closed: timed out

Log:

Summary

[user@user ~] cat ~/.safe/authd/logs/sn_authd.log INFO 2021-04-10T17:12:32.009838479+01:00 [sn_authd/operations.rs:144] Running authd instance from executable at "/home/user/.safe/authd/sn_authd" INFO 2021-04-10T17:12:32.009944551+01:00 [sn_authd/operations.rs:150] authd instance starting (PID: 11465)... INFO 2021-04-10T17:12:32.010006396+01:00 [sn_authd/operations.rs:178] Initialising SAFE Authenticator services... INFO 2021-04-10T17:12:32.010044904+01:00 [sn_authd/authd.rs:34] Bootstrapping with contacts: {138.68.146.110:58306, 138.68.152.156:51182, 138.68.131.228:40591, 178.62.58.241:42766, 138.68.138.75:59177, 138.68.154.35:49429, 46.101.48.69:55130, 138.68.131.218:57691, 138.68.137.76:34625, 138.68.137.198:43750, 138.68.154.164:44520, 138.68.142.144:55064, 188.166.169.192:47334, 138.68.141.132:36390, 138.68.139.58:38972, 46.101.17.63:38981, 138.68.146.15:34651, 138.68.142.76:38701, 46.101.1.135:58214, 46.101.93.86:56133, 138.68.133.17:37599, 46.101.72.229:52737, 138.68.131.119:50694, 188.166.146.65:36220, 138.68.139.187:33546, 46.101.78.184:41244, 188.166.146.115:41339, 178.62.101.46:59428, 178.62.80.163:57378, 46.101.55.62:53141, 139.59.181.74:12000, 138.68.138.179:51519, 138.68.139.28:40613} INFO 2021-04-10T17:12:32.010209133+01:00 [qjsonrpc/src/server_endpoint.rs:51] Generating self-signed certificate... INFO 2021-04-10T17:12:32.010570646+01:00 [sn_authd/authd.rs:130] Listening on [::1]:33000 INFO 2021-04-10T17:12:39.804967553+01:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (3292528409): 'status' INFO 2021-04-10T17:12:39.804999416+01:00 [sn_authd/requests/status.rs:29] Preparing authd status report... INFO 2021-04-10T17:12:39.805010545+01:00 [sn_authd/requests/status.rs:55] Status report sent: AuthdStatus { safe_unlocked: false, num_auth_reqs: 0, num_notif_subs: 0, authd_version: "0.5.0" } INFO 2021-04-10T17:12:39.805248770+01:00 [sn_authd/authd.rs:207] Response sent, request 3292528409 complete INFO 2021-04-10T17:13:16.577766702+01:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (2294570910): 'create' INFO 2021-04-10T17:13:16.577828633+01:00 [sn_authd/requests/create.rs:25] Creating a Safe... INFO 2021-04-10T17:13:16.595417063+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/client/mod.rs:109] Client started for specific pk: PublicKey::Ed25519(c235b32efb60f0aec5ad879c094e4e23fa1b261f55e0b7eaa3d94960d23f0b4d) WARN 2021-04-10T17:13:16.595481982+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/config_handler.rs:73] Failed to open config file from '/home/user/.safe/client/sn_client.config': No such file or directory (os error 2) WARN 2021-04-10T17:13:16.595752563+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.7/src/endpoint.rs:235] Ignoring 'forward_port' flag from config since IGD has been disabled (feature 'no-igd' has been set) WARN 2021-04-10T17:13:16.752940585+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.146.110:58306 INFO 2021-04-10T17:13:16.788367427+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.1.135:58214 WARN 2021-04-10T17:13:16.788438008+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders. INFO 2021-04-10T17:13:16.789995598+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.48.69:55130 WARN 2021-04-10T17:13:16.790050203+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders. INFO 2021-04-10T17:13:16.790759317+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.55.62:53141 WARN 2021-04-10T17:13:16.790799158+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders. INFO 2021-04-10T17:13:16.796761287+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.138.179:51519 WARN 2021-04-10T17:13:16.796838869+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders. INFO 2021-04-10T17:13:16.797826839+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.228:40591 WARN 2021-04-10T17:13:16.797879066+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders. INFO 2021-04-10T17:13:16.798046008+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.218:57691 WARN 2021-04-10T17:13:16.798083059+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders. WARN 2021-04-10T17:15:16.579293018+01:00 [qjsonrpc/src/server_endpoint.rs:160] Failed to read incoming request: timed out WARN 2021-04-10T17:15:16.604536162+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:523] Failed to connect to Elder @ : ElderConnection WARN 2021-04-10T17:15:16.604579105+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders. ERROR 2021-04-10T17:15:46.743569866+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:927] Error handling network info message: QuicP2p(Connection(TimedOut)) WARN 2021-04-10T17:15:46.751458543+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 46.101.1.135:58214 INFO 2021-04-10T17:15:46.779047233+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.1.135:58214 WARN 2021-04-10T17:15:46.779088090+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders. INFO 2021-04-10T17:15:46.779764778+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.55.62:53141 WARN 2021-04-10T17:15:46.779807948+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders. INFO 2021-04-10T17:15:46.784496911+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.142.76:38701 WARN 2021-04-10T17:15:46.784539617+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders. INFO 2021-04-10T17:15:46.785382149+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.93.86:56133 WARN 2021-04-10T17:15:46.785428593+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders. INFO 2021-04-10T17:15:46.787676882+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.228:40591 WARN 2021-04-10T17:15:46.787720584+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders. INFO 2021-04-10T17:15:46.789413465+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.218:57691 WARN 2021-04-10T17:15:46.789464326+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders. INFO 2021-04-10T17:15:47.159770158+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.1.135:58214 WARN 2021-04-10T17:15:47.159847444+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders. INFO 2021-04-10T17:15:47.159880636+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.142.76:38701 WARN 2021-04-10T17:15:47.159903536+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders. INFO 2021-04-10T17:15:47.159927478+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.55.62:53141 WARN 2021-04-10T17:15:47.159947616+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders. INFO 2021-04-10T17:15:47.159973515+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.228:40591 WARN 2021-04-10T17:15:47.159994344+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders. INFO 2021-04-10T17:15:47.160010399+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.93.86:56133 WARN 2021-04-10T17:15:47.160023269+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders. INFO 2021-04-10T17:15:47.170415555+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.218:57691 WARN 2021-04-10T17:15:47.170478740+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders. [user@user ~]

1 Like
584

Same timed out error for me (maybe I do something wrong, who knows - I type commands semi-randomly ))

585

Had a different problem earlier but now I’m getting the same.

586

did anyone successfully connected his node for the first time today ?

3 Likes
587

Figure I should put my experience here as well:

I have also been having periodic timeout issues with this and other commands. In my case, I am fairly certain it is not my router as the same command might time out 2 or 3 times, then complete successfully the fourth time for example. At times, commands return very quickly (in a handful of seconds), and at other times they randomly refuse to complete, giving timeout errors.

In a few cases, I was running safe wallet balance ... and getting “permission denied” on the CLI. When I looked in auth.log, i found the underlying cause was actually also a timeout.

At first I was sure it was my local network, or me misunderstanding commands. But after seeing commands succeed after failing consistently, I’m not sure that’s the case any longer.

(I have observed this both on an Ubuntu VM on my local machine, and an Alpine container running on a VM host.)

Really enjoying getting to play with the testnet! Thank you for all your hard work everyone!

5 Likes
588

Thanks @maidsafe and team. I am so excited to try out the testnet. Your perseverance is amazing.

Using the join script from @wydileie resulted in a successful join. WIN! Thanks wydileie for sharing. It took about 10 hours to join and get one chunk. I don’t think that I am still connected but not sure. My log is full of these messages.
Error in sn_node.log after node join: Unable to send Message to Peer: MissingSecretKeyShare

@happybeing I finally installed vdash. Thank you for putting your time into this. Unfortunately I started after I joined so I did not get to see it capture the connection. Trying again.

Thanks to everyone for the troubleshooting and tips. I love the collaborative attitude here.

13 Likes
589

Thanks for trying vdash, it’s quite useful as is but I’m looking into updating it to show more info with a testnet. If you start it late it doesn’t matter too much as it reads the whole logfile so you will see the history in the timelines across the middle.

Until the join you will get an error for each rejection, and then there will be a delay until you start seeing PUTS. It doesn’t show GETS at the moment but I hope to fix that. It does show how much data you have stored next to “Immutable” near the top.

tip: press ‘i’ to zoom in, and ‘o’ to zoom out.

4 Likes
590

Well done everyone. Congrats on launching this testnet :slight_smile: .

18 Likes
591

Has anybody thought about shutting down their node to give others a chance to run one and to see how the network handles churn? Do things really change that much after hours and days that you must continue indefinitely?

1 Like
592

I have a node connected! I set it on early in the morning, and checked just now. It connected at
2021-04-10 T 15:09:20.

But if I read the log correctly, it has stored four chunkcs only, last one T 15:15:18. I don’t know if it is running anymore. Ubuntu activity monitor doesn’t show anything, that would evidently be my node. How do I check?

EDIT: found it sn_node is running. Using 0% CPU and 14,5MiB RAM.

6 Likes
593

@happybeing

Those with more money/resources have always, and will always, dominate everything in the material world. They’ll operate the majority of the safes unless the selection algorithm prioritizes balanced clearnet address space distribution, and even that isn’t a guarantee. If you believe I’m mistaken, I’d appreciate being corrected and gaming the scenario out.

Operating from that assumption, my focus is how to maintain network viability. If it’s trivial to starve the network of additional nodes, that’s worse than if it’s difficult/expensive. If spam/flooding isn’t managed, to say nothing of more sophisticated attacks, who runs the majority of safes will be irrelevant because the network will be unviable.

With that, none but the lowest tier of script kid (connect/disconnect/reconnect) would be excluded or burdened, so I fail to see the practical centralization of proof of work.

Perhaps there’d be value in a topic dedicated to brainstorming resource_proof ideas that could be used in different ways by the network to validate clients and their capabilities? If done well it could lay the foundation to autonomous network upgrades.

4 Likes
594

Damn, I am 2 days late, I thought the Testnet release may have been postponed for next week, because I did not see an announcement on Thursday. Was wondering why the page had suddenly gone quiet with no activity.

This is a wonderful surprise and awesome news, congratulations and massive kudos to the Maidsafe team on reaching this significant milestone. :clap:t6: :clap:t6: :clap:t6: :partying_face: :champagne:

16 Likes
595

Correct me if I’m wrong but I think we’re agreed that PoW is centralising, but you see it as useful because it’s more help than not. I don’t disagree with that, I don’t know either way.

I have taken a step back from where you are I think. So we’re both trying to solve the same problem from different positions, and David from another.

So there isn’t necessarily any disagreement, just different starting points, probably some different perspectives and of course different ideas. I’m not looking at PoW but was looking to see if there are other ways that avoid its pitfalls.

1 Like
596

I disagree that proof of work is centralizing. I think the centralization that you may observe is the nature of a world dominated by those with wealth and an inclination toward domination.

597

That’s what makes it centralising. What you seem to be saying is that there’s no way to avoid that, which may be true but could be called defeatist thinking.

That’s what I said in my post, you seem to accept this while I’m still looking to see if we can do better. Maybe we can’t, I don’t know.

5 Likes
598

Have you read the primer.safenetwork.org?

1 Like
599

Great that a public testnet is up and running! Looking forward to seeing what people do with it.

The performance of the network is not a priority for this release but it’s good to have these figures anyway as a point of interest.

Storing a 30 MB file (containing random data) with safe files put /tmp/data.bin took 11m19.459s which is a rate of 370 Kbps

The filescontainer is
safe://hyryyry7be3kgcr85t759xxspqszgf4gaen9fwej6c7dietksostbnfqroenra
which resolves to
safe://hyfeynypda4r1i8z389ci3pinu3jhj5uz16j8biq7pe6nu9t9i8t1t59wua

I couldn’t fetch the file using safe cat or safe files get with these error:
Error: NetDataError: Failed to GET Public Blob: ErrorMessage(NoSuchData)
and
Error: NetDataError: Failed to GET Public Blob: SelfEncryption(Storage)
I suspect the upload did not actually work despite giving a positive response.

The sha256 of the data is 181754fa0d1a7ab38648a5ccb9e7f0961ba5fdb2ce8af2117af074139af0afd3 if anyone is wanting to verify the download.

Using an old hack to store the same 30 MB in a sequence, it took 2m46.593s which is a rate of 1511 Kbps. The url is
safe://hyryyyy3ouwbr16hi6oozixtnpo58mgyfsuzwatwpkewguyjc6s9u6kiyxhnmy

Downloading the hack version (using safe cat safe://hyryyyy3ouwbr16hi6oozixtnpo58mgyfsuzwatwpkewguyjc6s9u6kiyxhnmy > /tmp/data.bin) took 2m18.349s which is a rate of 1819 Kbps.

This hack will probably not be possible when crdts is upgraded away from using lseq. Mentioned in the OP under “what doesn’t this testnet do” as “Not all data types are CRDT compliant just yet”.

Would be interested if anyone has a node running in the section holding this data whether you see a 30 MB file in there (xorname in hex starts with 0x309d).

I tried joining a node but am still waiting, no worries there.

A small easter egg

safe cat safe://hyryyyy3q1ff1faj9p9qqj5dnrfshj3uasfq1hw7edzetsz76a9riqjp74onmy

21 Likes
600

Are we there yet ?
Are we there yet ?
Are we there yet ?

yes

Are we th… wait, WHAT !?

Congratulation to everyone involved, your level of dedication is unreal.

17 Likes
601

A feature request for the team after using the test net. Can you implement bash completion for the CLI? It would make things much easier to work with without having to use the help command all the time.

I’d be willing to put in a proposal to do it myself under the Bamboo Garden Fund when applications open back up, if the core team doesn’t have time.

6 Likes
602

@wydileie Yes indeed - this is a niggle that stops me running the safe command on its own

willie@mir:~/.safe$ safe

Welcome to Safe CLI interactive shell!
Type 'help' for a list of supported commands
Pass '--help' flag to any top level command for a complete list of supported subcommands and arguments
Type 'quit' to exit this shell. Enjoy it!

> auth start
Failed to start authd
> auth stop
Stopping SAFE Authenticator daemon (sn_authd)...
Success, sn_authd (PID: 4351) stopped!
> ^[[A^[[A

thats what I get for letting instinct take over and hit the up arrow twice to repeat auth start