I am trying to join the comnet through powershell and I am getting a wierd error

safe node join
Joining network with contacts (PublicKey(0065..d226), {,,,,,,,,,,}) ...
Storing nodes' generated data at C:\Users\tseko\.safe\node\local-node
Starting a node to join a Safe network...
   0: ←[91mError launching node←[0m
   1: ←[91merror: Found argument '-v' which wasn't expected, or isn't valid in this context

          sn_launch_tool-join [FLAGS] [OPTIONS] --genesis-key <genesis-key>

      For more information try --help
   1: ←[0m


Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Hmm, is that definitely a native windows binary of safe? And a recent version?

followed the instructions in the safe cli and installed safe through GIT BASH

With a simple well-named script handling the installation such questions would disappear? Am I wrong?

We don’t have a native Windows installation script yet.


What’s the output of safe --version?

I realize that. But I think we should have one. And if it’s easier to write one just for Linux, then why not just do that first? The whole point of my script idea was to avoid such confusion.

safe --version
sn_cli 0.38.0

there was already today a talk about having a powershell script for installing

1 Like

Sorry, I don’t really know what you’re referring to here when you say “my script idea”.

We have an install script for safe just now, but it’s just a Bash script. We need the equivalent one for Powershell.

1 Like

That’s an old version of safe. Try just downloading a recent version of the Windows binary.

1 Like

I’m installing Kali on my old Thinkpad. It doesn’t need the whole disk so I will put Win10 on a dual boot and get familiar with SAFE on Windows, reacquaint myself with Powershell and then look at replicating the existing simplified script.


Just to clarify something here, as I think there might be a bit of confusion. Earlier in the day, when I said we needed a Powershell script, what I was talking about is a Powershell install script just for safe. The equivalent of the install.sh we have for Linux. Not a thing for connecting to the community testnet.

1 Like

Ah… Well I’ll start with an easy repeat of the simple wee script cos its a long while since I did anything serious with Powershell. Then I’ll look at porting the install.sh

Not that I ever did that much serious with Powershell anyway, it was mostly just some backup scripts for a customer.

Oh, it was just something I said in another thread about simplifying joining community test nets. Forget about it.

using the script I get 0.38.0 so the script downloads the wrong sn_cli?

curl -so- https://raw.githubusercontent.com/maidsafe/sn_cli/master/resources/install.sh | bash
=> Downloading Safe CLI package from 'https://sn-api.s3.eu-west-2.amazonaws.com/sn_cli-0.38.0-x86_64-pc-windows-msvc.tar.gz'...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 6445k  100 6445k    0     0  4912k      0  0:00:01  0:00:01 --:--:-- 4912k
=> Unpacking Safe CLI to '/c/Users/tseko/.safe/cli'...
=> Safe CLI binary path was already set in the PATH

That’s a link to an old script (note the sn_cli in the link).

I see, can you point me to a uptodate link?

I cant seem to find it so I downloaded latest safe.exe and replaced the previous one in .safe/cli and it works

run-baby-fleming works and I was able to put but on cat it downloads the file with double the size and cannot open it (its the spiral.gif) though safe files get works ok!

also safe node killall works in powershell but not in wsl2

curl -so- https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash

This should work.

1 Like

there is definetly something wrong either with the windows safe binary or with node binary with the run-baby-fleming network.

i put and the I cat and the file is twice bigger than the original and not playing