CloserNet went very nicely, but we want to debug some of the zero payment nodes and data distribution questions it brought up.
As such we’ve got some extra logs on the go, as well as set up the client to choose nodes at random (from close nodes), rather than the cheapest. This should help confirm if we have in a client-side storage choice issue (or indeed price setting issue as our testing has shown) or something else is going on here.
We’ve ask node users to try and keep a good amount of logs too in case we need to try and debug a certain store effort, eg.
It will also be useful if RecordRejected (any other rejection reason except record rejected due to payment not to self) error were collected and reported if node users spot such activity 
.
A note for testers:
Just to highlight for folk (as the question has cropped up in other threads), encryption of files is a client side endeavor, and right now there it s lower limit on what can be encrypted. So small file are not yet encrypted as things stand.
This also means that the DataMaps which are used to know where all the self-encrypted chunks of a file live are may not be encrypted. And these are currently stored on the network by default. (We’ll probably be moving these to be disk-only by default so the only things put to the network would be self-encrypted.)
And finally, registers are currently not encrypted at all. We’re looking at ways to improve UX and allow for encryption there too.
A wee ubuntu iso for verification:
safe --peer /ip4/178.62.3.215/tcp/45315/p2p/12D3KooWHRWEb5XQZU1cksTGxsvzJi22zUTjfhemRNiMHLL88868 files download ubuntu-18.04.6-desktop-amd64.iso f2fe721b1f3f7538de3d6003107a6db799e2f07ac0a0981aa8eae8ae3922cd8e
Network Details
Node version: 0.100.22
Client version: 0.86.76
Faucet url: 138.68.138.2:8000
We have 101 droplets running a total of 2001 nodes. One droplet has 2vcpu and 4GB of memory.
If you are a regular user, see the ‘quickstart’ section for getting up and running.
If you are a first-time user, or would like more information, see the ‘further information’ section.
Quickstart
If you already have safeup, you can obtain the client and node binaries:
safeup client --version 0.86.76
safeup node --version 0.100.22
Run a Node
Linux/macOS:
safenode
Windows:
safenode
Check local node’s reward balance
Your local node’s peer id will be printed to the terminal on startup with an example command). (You can also retrieve this from the node directory.)
safe wallet balance --peer-id="<local-node-peer-id>"
Connect to the Network as a Client
Linux/macOS:
safe wallet get-faucet 138.68.138.2:8000
safe files upload <directory-path>
Windows:
safe wallet get-faucet 138.68.138.2:8000
safe files upload <directory-path>
To do this with non-default batch-sizes (along with SAFE_PEERS set as above):
safe files upload --batch-size 40 <directory-path>
40 being the integer value you want to set
Further Information
You can participate in the testnet either by connecting as a client or running your own node.
Connecting as a client requires the safe client binary; running a node requires the safenode binary.
Obtaining Binaries
We have a tool named safeup which is intended to make it easy to obtain the client, node, and other utility binaries.
Installing Safeup
On Linux/macOS, run the following command in your terminal:
curl -sSL https://raw.githubusercontent.com/maidsafe/safeup/main/install.sh | bash
On Windows, run the following command in a Powershell session (be careful to use Powershell, not cmd.exe):
iex (Invoke-RestMethod -Uri "https://raw.githubusercontent.com/maidsafe/safeup/main/install.ps1")
On either platform, you may need to restart your shell session for safeup to become available.
Installing Binaries
After obtaining safeup, you can install binaries like so:
safeup client # get the latest version of the client
safeup client --version 0.86.76 # get a specific version
safeup node # get the latest version of the node
safeup node --version 0.100.22 # get a specific version
safeup update # update all installed components to latest versions
When participating in our testnets, it is recommended to use a specific version. In our project we release a new version of the binaries every time we merge new code. This happens frequently, so over the lifetime of a testnet, many new releases will probably occur. So for participating in this particular testnet, you may not want the latest version.
The binaries are installed to ~/.local/bin on Linux and macOS, and on Windows they go to C:\Users\<username>\safe. Windows doesn’t really have a standard location for binaries that doesn’t require elevated privileges.
The safeup tool will modify the PATH variable on Linux/macOS, or the user Path variable on Windows. The effect of this is that the installed binaries will then become available in your shell without having to refer to them with their full paths. However, if you’re installing for the first time, you may need to start a new shell session for this change to be picked up.
Running a Node
You can participate in the testnet by running your own node. At the moment, you may not be successful if you’re running the node from your home machine. This is a situation we are working on. If you run from a cloud provider like Digital Ocean or AWS, you should be able to participate.
You can run the node process like so:
# Linux/macOS
safenode
# Windows
safenode
This will output all the logs to the filesystem, with the location of logs being platform specific:
# Linux
~/.local/share/safe/node/<peer id>/logs
# macOS
/Users/<username>/Library/Application Support/safe/node/<peer id>/logs
# Windows
C:\Users\<username>\AppData\Roaming\safe\node\<peer-id>\logs
If you wish, you can also provide your own path:
# Linux/macOS
SN_LOG=all safenode --log-output-dest <path>
# Windows
$env:SN_LOG = "all"; safenode --log-output-dest <path>
The advantage of using the predefined data-dir location is you can run multiple nodes on one machine without having to specify your own unique path for each node and manage that overhead yourself.
Connecting as a Client
You can use the safe client binary to connect as a client and upload or download files to/from the network.
Using the Client
You’ll first need to get some Safe Network Tokens:
safe wallet get-faucet 138.68.138.2:8000
You can now proceed to use the client, by, e.g., uploading files:
safe files upload <directory-path>
To download that same content:
safe files download
This will download the files to the default location, which is platform specific:
# Linux
~/.local/share/safe/client/downloaded_files
# macOS
/Users/<username>/Library/Application Support/safe/client/downloaded_files
# Windows
C:\Users\<username>\AppData\Roaming\safe\client\downloaded_files
To download to a particular file or directory:
safe file download [directory/filename] [NetworkAddress]
Troubleshooting
Cleanup
If you’ve used previous versions of the network before and you find problems when running commands, you may want to consider clearing out previous data (worthless DBCs from previous runs, old logs, old keys, etc.).
# Linux
rm -rf ~/.local/share/safe
# macOS
rm -rf ~/Library/Application\ Support/safe
# Windows
rmdir /s C:\Users\<username>\AppData\Roaming\safe
If you encounter a problem running any of our binaries on Windows, it’s possible you need the Visual C++ Redistributable installed.
, basically christmas eve and new tests popping!