All the latest code. All the hottest fixes. And at least some of the beta reward tracking flow!
THIS IS NOT THE REAL DEAL. Do not get excited about anything beta-rewardsy happening early. We’re hope you can help us with some pre-flight checks of the flow here, that is all.
In this testnet we’re really just looking to asses:
- If folk can use the Node Launchpad to start nodes with a
Discord Username(Windows users see notes below) - Is that
Discord Usernametracked by the network properly - We can see and perhaps generate a leaderboard from this!
With this we have most of the flow for the reward calculations (beyond some discord plumbing).
So please let us know if you have issues, UX woes, or node world problems.
This testnet might well be short lived.
Testing The Flow
So first, we’d like everyone who’s interested to try starting nodes inputting their Discord Username into the launchpad.
Oallows you to allocate resourcesDsets Discord Usernamectrl+gactually starts the nodes (assuming the rest is set)
What is my Discord Username?
This is your username on discord. Note that it can be different from your display name on a particular server.
You can copy it from Discord by clicking your profile (bottom left) and then clicking your name just under the profile image. It’s the Username you see when you right click on your name in discord and copy your id. It’s also the number you see in the URL when you visit your profile on discord.
Note: Discord Usernames aren’t validated in the launchpad, so you’ll have to watch out for typos…
Once you have have entered your Discord Username, please comment it in the thread here.
What happens next?
Nodes will encrypt the discord id as metadata when forwarding rewards to the foundation.
The foundation DAG has the ability to decrypt this, and will allow us to collate stats on rewards being generated by nodes.
To enable this, we’ll periodically update the DAG node with shared discord ids (from this thread), which will allow us to see rewards being forwarded to the foundation key.
(For rewards to be generated, we’ll obviously need some data to be uploaded, so the faucet still exists here, and we’d encourage folk to use that as normal).
And then
We’ll report back here with any modicum of success or no!
Stretch goals (for advanced users):
There’s a potential fix in for some home node issues (we’re seeing a 2%->15% increase in success rates here). We’d be keen to know if anyone is seeing a lot of the follow error (searched for via ripgrep in the node logs dirs)
rg -c 'Dcutr with remote peer: PeerId\(".*"\) is: Ok' ./ --search-zip | awk -F: '{sum += $2} END {print sum}'
rg -c 'Dcutr with remote peer: PeerId\(".*"\) is: (Ok|Err)' ./ --search-zip | awk -F: '{sum += $2} END {print sum}'
Windows
For Windows users, the launchpad and/or node manager requires the availability of WinSW.
To do this:
- Download the
WinSW-x64.exebinary from here - Rename the downloaded binary to
winsw.exe - Copy the binary to
C:\Windows\system32or another location that is on the system or userPath
The C:\Windows\system32 is just somewhere that is guaranteed for every Windows install.
Network Details
Launchpad version: 0.2.0
Node version: 106.5
Client version: 0.92.0
Faucet url: 161.35.173.105:8000
You should download the launchpad from here choosing your platform there.
We have 50 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 binary:
safeup client --version 0.92.0
Connect to the Network as a Client
Linux/macOS:
safe wallet get-faucet 161.35.173.105:8000
safe files upload <directory-path>
Windows:
safe wallet get-faucet 161.35.173.105: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.92.0 # 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.
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 161.35.173.105: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.
