We’re delighted to announce we have the next piece of the puzzle toward Vault Phase 1 milestone, ready for you

So far, on this particular milestone journey, we started with a focus on evolving the CLI (bringing you wallet, files, and most recently NRS related commands), all of which worked in tandem with mock SAFE Client Libs + mock Vault.

With the CLI in a great position we took on the next piece of the puzzle, which was to swap out mock SAFE Client Libs with real SAFE Client Libs. And today’s release is the result of this work. So today you’ll have two binaries to play with: SAFE CLI (including the real SCL + mock Vault) and the latest SAFE Authenticator CLI.

Also, a wee reminder this release still stores everything locally on your machine, so don’t go uploading 10GB worth of files, or it’ll slow things right down

Feedback and support

You know we love the community giving us feedback so don’t be shy! As always, you can drop your comments or feedback below this post or, if you prefer, in GitHub in the corresponding repo.

If you need any support, don’t hesitate to pop your question below either and one of the team will happily help you out.

What’s next

We’ve already started work on the next release iteration of this milestone, which is swapping out mock Vault with a real Vault.

Working towards this, we’ve spent the last week identifying and fixing discrepancies discovered when running against a real Vault vs a mock one. So far only minor issues have been found. These include things like reporting back to the Client when uploading duplicate unpublished immutable data; the reason for balance refunds (which can happen for example when trying to transfer coins to a non-existent balance); apps with insufficient permissions should trigger access denied rather than invalid permissions; stricter checks for coin operations and the CreateLoginPacketFor RPC should report a transaction response.

The only slightly more involved fix was having to restructure the connection logic in safe_core to be able to juggle multiple connections to the same vault simultaneously. Again the SCL team delivered the goods!

As you can see, none of these are show-stoppers of any kind so very soon you’ll be able to run a local Vault instance and have your local client connect to it as when connecting to the real network. The next phases would then focus on assembling multiple Vaults into a full-fledged peer-to-peer network, step-by-step.

As a reminder, when this Phase 1 Vault milestone is completed, it will emulate the entire network in its fundamental state. In other words, clients will connect to a running Vault instance as if they are connected to the whole real Network.