[Offline] Playground sn v0.53.0, sn_cli v0.44.0

Development Updates
1

We’re dropping a wee playground here to keep folk off the streets over the weekend (all being well).

The largest change therein is that registers are now stored at adults, along with chunks. Which makes elders pure relay nodes as things stand. (They will of course eventually have other more, DBCy duties).

There’s also the new logging setup in place too :tada: . (edit, that didn’t get into this release it seems :expressionless: , one for the next one!)

This network is 33 nodes, each with 20gb. We’d ask anyone wanting to join use a smilar sized node (this will be hardcoded in the not too distant future). There has been one split thus far.

You should be able to connect to with the 0.53.0 release thus:

  • remove ~/.safe
  • run curl https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash to install the CLI
  • run safe --version to make sure you’re on the correct version.
  • run safe networks add playground https://safe-testnet-tool.s3.eu-west-2.amazonaws.com/public-node_connection_info.config
  • safe networks switch playground

And you should be good to go :tada: :beers:

If you’re wanting to try joining with a node (which may take a while):

safe node install
safe node join OR
safe node join --skip-auto-port-forwarding OR
safe node join --local-addr <ip of device running node>:<port> \
  --public-addr <your internet public ip>:<port opened on router> \
  --skip-auto-port-forwarding
44 Likes
2

It’s showtime baby!

9 Likes
3

Here’s the spiral to test:

safe cat safe://hygoynyybh5bc3afb8i811wj8dnrpqkfx4mog9m3s1owokcz4763x5rhj9fko > spiral.gif

11 Likes
4

From logs:

➤ Network is set to not taking any new joining node, try join later.

hmm shouldnt this be retrying every 3 mins no? is it set not to accept nodes?

3 Likes
5

Update - it is retrying every 3 mins

Just with odd wording I think “Network is set to not taking any new joining node, try join later.”

All good though, I’m in the queue I think :smiley:

6 Likes
6

Can you confirm in the OP that it should report v0.44.0?

$ curl https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6981  100  6981    0     0  33562      0 --:--:-- --:--:-- --:--:-- 33562
=> Downloading Safe CLI package from 'https://github.com/maidsafe/safe_network/releases/download/0.53.0-0.51.0-0.44.0/sn_cli-0.44.0-x86_64-unknown-linux-musl.tar.gz'...
=> Saving to '/tmp/tmp.gIrPYqpH6Q/sn_cli-0.44.0-x86_64-unknown-linux-musl.tar.gz'...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   685  100   685    0     0   2644      0 --:--:-- --:--:-- --:--:--  2644
100 10.2M  100 10.2M    0     0  10.2M      0  0:00:01  0:00:01 --:--:-- 18.9M
=> Unpacking Safe CLI to '/home/safe/.safe/cli'...
=> Adding statement to '/home/safe/.bashrc' profile to have Safe CLI binary path in the $PATH
=> Profile '/home/safe/.bashrc' already contains a statement to set Safe CLI in the $PATH

$ safe --version
sn_cli 0.44.0
7 Likes
7

Yeah, that’s the correct CLI version.

10 Likes
8

Suggest you put that in the OP.

This doesn’t appear to have the new log functionality - there shouldn’t be a time stamp in the filename:

$ ls -lht ~/.safe/node/local-node/
total 12K
-rw-rw-r-- 1 safe safe 1.8K Jan 21 16:59 sn_node.log.2022-01-21-15
5 Likes
9

Aah, that’s unfortunate. It seems your PR was merged right after the release…

image
image1127×272 48.6 KB

7 Likes
10

added to the title :+1:

8 Likes
11

ahhh damn. Sorry for the misleading excitement! I thought it had gone in :expressionless:

It’ll be in the next one @happybeing, sorry about that!

7 Likes
12

This text should be removed on switching to the playground network:

If you need write access to the 'playground' network, you'll need to restart authd (safe auth restart), unlock a Safe and re-authorise the CLI again

It’s obsolete now

6 Likes
13

For future reference, the compatible versions are always in the title of the release. In this case:

Safe Network v0.53.0/Safe API v0.51.0/Safe CLI v0.44.0
6 Likes
14

I’ll note that to get removed.

7 Likes
15

I tried:

I got (changed some numbers there, to hide myself a bit):

0: Error launching node
   1: Failed to start '/home/topi/.safe/node/sn_node' with args '["-vv", "--skip-auto-port-forwarding", "--local-addr", "132.154.1.104:12000", "--public-addr", "81.144.15.166:58002"]'
   2: No such file or directory (os error 2)

What might be wrong?

16

Did you install sn_node? with safe node install

4 Likes
17

Still in queue.

So a lot more data will be needed to be added to network before I am needed right?

4 Likes
18

I’m also in the queue. May the best node win :horse_racing:

Edit: Plus I’m on an uploading frenzy. We’ll split the bugger yet.

6 Likes
19

Too excited to bother with such details :wink:

Thanks!

6 Likes
20

I’m in!

[just kidding]

3 Likes