Baby Fleming Public Shared Section

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
    Network 'shared-section' was added to the list
  • Once added, you can now switch the CLI to use this shared-section network. Use safe networks switch as follows:

    $ safe networks switch shared-section
    Switching to 'shared-section' network...
    Fetching 'shared-section' network connection information from '' ...
    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
    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.

Have fun!

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.


Timed out when bootstrapping.

Need open some port o similar?

Shouldn’t need to open any ports.
1st thing to check is that your apps are all up to date - is CLI v0.11.0 (run $ safe -V) and is authd v0.0.7 (run $ safe auth install to be sure).

If you still have problems after updating both then let me know what platform you are on and paste your full error message, thanks.

UPDATE - would also be worth you sending me the results of you running $ safe networks check and $ safe auth status. Thanks
Note I edited the OP to add a step for $ safe auth start.




This sounds very interesting. Excellent advancement.


Safe Browser v0.17.0-alpha.0 is compatible with this network? Because couldn’t connect.

At the moment the desktop & mobile SAFE Browsers are not compatible with the shared section. Something we will work to resolve asap. In the meantime all the actions you can run on the shared section are in the CLI user guide


My setup was a bit messed up when I started this as my old ~/.safe had been deleted and I skipped the local single section release. This is what happened and my progress fixing this:

A gotcha that might need a code fix. Having earlier downloaded safe to ~/bin/safe which is on my path I updated as instructed above. Using safe update works fine, but then:

safe auth update
[2020-03-31T10:54:59Z ERROR safe] safe-cli error: [Error] AuthdClientError - Failed to execute authd from '/home/mrh/.safe/authd/safe-authd': No such file or directory (os error 2)

Looking in ~/bin shows that safe was updated but nothing else:

$ ls -l ~/bin/safe*
-rwxr-xr-x 1 mrh mrh  26824936 Mar 26 15:12 /home/mrh/bin/safe
-rwxr-xr-x 1 mrh mrh  17447520 Feb 24 21:10 /home/mrh/bin/safe0.2.2
-rwxr-xr-x 1 mrh mrh  13560224 Feb 24 21:10 /home/mrh/bin/safe_auth
-rwxr-xr-x 1 mrh mrh  19023728 Feb 24 21:10 /home/mrh/bin/safe_auth0.2.0
-rwxr-xr-x 1 mrh mrh 112504460 Feb 24 21:10 /home/mrh/bin/safe-browser.AppImage
-rwxr-xr-x 1 mrh mrh  12239576 Feb 24 21:10 /home/mrh/bin/safe_vault
-rwxr-xr-x 1 mrh mrh  18526096 Feb 24 21:10 /home/mrh/bin/safe_vault0.19.0

So I guess we need to only install safe and its buddies in ~/.safe/. Ideally this should be enforced, and documented in the mean time.

I’ve posted this as issue #496, but also here for visibility.

I’ve run the and it has installed .safe/cli/safe but nothing else, so I’m missing .safe/auth etc. How is that supposed to be installed?

OK, ok, RTFM…

safe vault install
safe auth install

And to finish…

safe networks add shared-section
safe networks switch shared-section

But oops… Not sure if this is a more general issue, but:

safe networks switch shared-section
Switching to 'shared-section' network...
Fetching 'shared-section' network connection information from '' ...
[2020-03-31T11:31:09Z ERROR safe] safe-cli error: Unable to write config in /home/mrh/.config/safe_vault/vault_connection_info.config: No such file or directory (os error 2)

The last error is fixed by mkdir ~/.config/safe_vault so maybe the command should check for its existance?

I’ve done safe auth start but am unable to create an account:

safe auth create-acc --test-coins
Creating a SafeKey with test-coins...
Unexpected error Io(Custom { kind: UnexpectedEof, error: "failed to fill whole buffer" })
Sending account creation request to authd...
[2020-03-31T11:43:08Z ERROR safe] safe-cli error: [Error] AuthdError - [Error] AuthError - Failed to create an account: Account containers creation error: NFS error: NfsError::CoreError -> Data error -> Balance does not exist - CoreError::DataError -> NoSuchBalance. Login to attempt recovery.

Seemed better after safe auth restart, but then fails to bootstratp:

safe auth create-acc --test-coins
Creating a SafeKey with test-coins...
Sending account creation request to authd...
[2020-03-31T12:01:39Z ERROR safe] safe-cli error: [Error] AuthdError - [Error] AuthError - Failed to create an account: Account containers creation error: Core error: Unexpected: Connection timed out when bootstrapping to the network. Login to attempt recovery.

Also, don’t I need SAFE App or something for auth?

FYI, this is Ubuntu 19.10 with:
safe-cli 0.11.0
safe-auth 0.11.0
safe-vault 0.11.0


Please DO NOT run any test scripts from my github repo on this shared section

It would be all too easy to fill this valuable resource up with random data


Are we actually paying for the network usage here or is this just a rounding error? I expect a final balance of 9500, not 9499.999999999


Creating an account has an associated cost because data are created. Probably when you asked for the balance the first time, account creation was not finished, or even started. I doubt that an account creation cost only one unit. I guess if you issue the command again you will get a lower balance.

1 Like

We are back to trying to do decimal with binary maths. I thought we had dealt with that ages ago

USE FIXED POINT INTEGER GUYS, then it will ALWAYS be accurate, absolutely accurate

The value should hold an integer 0 to 2^32 * 10^9 in the 64 bit variable (eg signed 64)

And then use fixed point displaying to show the value

So a value of 1 in the balance is 0.000000001 safecoin

And @Southside if they do not do this then the SCREAMS from the ordinary public will be loud and clear and even generate a lot of anger against the network stealing from them.

Money and coins HAVE TO BE IN FIXED POINT integer format. @maidsafe this was agreed by Fraser a long time ago. 0.99999999 does not equal 1.0 when dealing with money and coins.

0.999999999 will not buy an item worth 1.000000000

This was computer science 1st year stuff. And I will grovel at the feet of the dev team with many apologises if fixed point has been implemented


Absolutely @neo

This needs sorted sharpish.
Unless there are extremely good reasons for sticking with it, I seriously recommend changing to fixed point integer as a top priority. We can have the nicest, most secure and performant autonomous network anyone could ever dream of but if we can’t purchase a 1.0 coin item with 0.9999999 coins then all that good work is utterly wasted. This HAS to work in the real world or it is nothing more than an intellectual curiosity. And that would be a shame.


This has been implemented by maidsafe, so
unless a last minute regression has appeared, the explanation lies somewhere else.


There is no good reason as far as I can see because the network will be getting judged by on lookers from Fleming onwards since its supposed to represent what the basics of the network is and money coins being there means it will examined with a fine tooth comb.

To have such a fundamental flaw like this will not help to sell the network later on. People will be expecting issues even though it could have been fixed.

Its too much a co-incidence since for some reason many in the dev team did not want fixed point, they seemed to think binary was easier and close enough being good enough.

So I do not hold such confidence that the test code was changed from binary to fixed point when implemented

@tfa Plausible but unfortunately not the case…

I think we have a problem…

From my understanding that’s the cost you paid to create the account


@bochaco so the cost to create an account is 0.000000001?


IF that is the case, that’s cool - BUT we MUST have a warning about this cost - even in the CLI.

I have great faith in @JimCollinson to sort this out in the GUI(s) but this is fundamental - we must have a warning - even at this very early stage in the CLI

I think so, I even put some notes in some tests with a similar amount for Wallet (MutableData container) creation cost: