As the speed and stability of Baby Fleming has improved over the two iterations released since we first announced our Baby, we feel that now is the right time to set up a public shared section that you can all connect to.
This shared section is hosted on DigitalOcean and consists of eight vaults on eight separate droplets, all connected together in one section.
How do I connect to the new shared section?
There is no new version of SAFE CLI, Authenticator daemon, or SAFE Vault being released today, so if you have the latest versions of each of these then you can proceed to the steps listed below.
If you do not have the latest versions of each of these, last updated on Thursday 26th March 2020 as part of Baby Fleming iteration 3, then we recommend you follow the steps listed in the Dev Update
How do I update to Baby Fleming Iteration 3 section from that date. If you have never installed these applications on your machine then we recommend you follow the step by step instructions in our SAFE CLI User Guide for an install script and full instructions on how to use the shared section.
Once you have up-to-date versions of all the applications above and you are ready to connect to the shared section you should follow these steps, taken from the “Switch networks” section of the SAFE CLI User Guide:
Using the CLI, add the shared network to your list of networks with
safe networks add. The config file is stored on S3 for you to access so your command should look like below:
$ safe networks add shared-section https://safe-vault-config.s3.eu-west-2.amazonaws.com/shared-section/vault_connection_info.config Network 'shared-section' was added to the list
Once added, you can now switch the CLI to use this
safe networks switchas follows:
$ safe networks switch shared-section Switching to 'shared-section' network... Fetching 'shared-section' network connection information from 'https://safe-vault-config.s3.eu-west-2.amazonaws.com/shared-section/vault_connection_info.config' ... Successfully switched to 'shared-section' network in your system! If you need write access to the 'shared-section' network, you'll need to restart authd, login and re-authorise the CLI again
Ensure you have started the safe authenticator with
$ safe auth start
Since this will be the first time you connect to the shared section, you should now create an account:
$ safe auth create-acc --test-coins
Once you have created an account, you can now log in and authorise the CLI:
$ safe auth login --self-auth Passphrase: Password: Sending login action request to authd... Logged in successfully Authorising CLI application... SAFE CLI app was successfully authorised Credentials were stored in <home directory>/.local/share/safe-cli/credentials
You should now be connected to the shared section! You can now experiment with the operations detailed in the CLI User Guide such as test-safecoin, wallets, files, NRS names, SAFE sites, etc.
We look forward to seeing the interaction and discussions amongst the community this generates.
Please note that the usual disclaimers apply as with any test network - we may be forced to wipe the data on the shared section at short notice due to bugs or incompatible upgrades we need to make, so keep this in mind!
Also note that the shared single vault that had been in use up until Baby Fleming was released is now redundant and so will be destroyed on Monday 6th April - please ensure that you have copied any data you require from the shared vault before that point.
UPDATE today (1st April) we have released a new Alpha version of the SAFE Browser (Desktop) which works with the new shared section, or indeed your local sections that you may be running. You can download the new Browser here, or if you are on Linux or macOS and you have a previous version of the Alpha Browser you should be able to open that and it will prompt you to download and update to the latest Alpha (this download and update from the previous Alpha is currently broken in Windows, currently investigating why).
UPDATE 2 known issue: please keep in mind that with the current iteration of the network having the client consensus removed, some requests may fail from time to time if the section elders are not all in sync.