MaidSafe Dev Update - March 1, 2018

Here are some of the main things to highlight this week:

  • Another great episode of the SAFE Crossroads podcast this week from @Fergish who interviewed @Shane, creator of SAFE-CMS and SAFE Search amongst other projects, along with co-author @AndyAlban.
  • We are delighted to announce that we have now filled the role of Customer Support Manager. David Geddes (@dwg74) will be joining us in Ayr at the start of April and will focus on supporting the use of the SAFE Network software released by MaidSafe as well as the APIs and tools used by developers.
  • The front-end team is releasing a WebRTC signalling example application. It lets you send invites to other public names to have a video call. You can try it by going to safe://webrtc.safeexamples using the latest version of Peruse.
  • The Routing team is continuing with the implementation work of the JIRA tasks for Milestone 1. The tasks completed now reach the components related to the upcoming new data chain features.
  • As noticed by the community in the Safe Gossip Protocol topic, the Routing team started to update the current Swarm mechanism with a secure and randomised, push and pull gossip mechanism.
  • The Crust team is happy to announce that netsim was published on https://crates.io. netsim is a testing library that allows one to simulate various network conditions and setups.

Marketing

February Summary and Marketing Stats

Let’s start by taking a look at the end of month marketing statistics:

We’ll be publishing a top-level picture of all of the activity that’s taking place in our monthly round up blog post in the next day or so also.

App of the Month

We’ve now kicked off the new App Of The Month project. Every month, we’ll take the opportunity to shine a light on one community project so that we can share the fantastic work that’s being carried out by the community in order to reach a wider audience. If you think someone’s been working on a valuable project that would benefit from increased exposure, just contact @SarahPentland. We’ll then get to work providing content (written, social media, etc.) to highlight the project and (if they want) the team behind it.

New SAFE Crossroads Podcast

Another great episode of the SAFE Crossroads podcast this week from @Fergish who interviewed @Shane, creator of SAFE-CMS and SAFE Search amongst other projects, along with co-author @AndyAlban. We’re delighted to provide a modest amount of sponsorship these days to help @fergish with his podcasting. Please do all you can to support the show - I’m sure he’d appreciate as many people as possible subscribing to the podcast via your usual podcast provider and sharing the episodes via social media (#SAFENetwork hashtag please!)

Safecoin video and website designs

We’ve been through second storyboard revisions for the new Safecoin video and we’re expecting to see the close-to-final animations early next week. The designs for the new MaidSafe website should be with us by the end of this week also.

Bittrex

We were naturally disappointed to hear that MAID is being delisted from the Bittrex Exchange. We wrote about this here and we’d urge you to read this if you haven’t already done so. As we mentioned in this post, we’re working with other exchanges to ensure ongoing liquidity of MaidSafeCoin which is also good for hodlers, and for the general awareness of the project.

There are a large and increasing number of exchanges available and as part of our selection criteria we are taking into account the number of coins they currently offer, location (an important aspect in regulation), size, length of time trading and professionalism. While we are very keen to move forward with this, we will not do so haphazardly and put our community at unnecessary risk with substandard exchanges.

We appreciate this is an area that is getting a lot of focus at the moment and we’ll update you as and when we see progress.

Recruitment

We are delighted to announce that we have now filled the role of Customer Support Manager. David Geddes (@dwg74) will be joining us in Ayr at the start of April and will focus on supporting the use of the SAFE Network software released by MaidSafe as well as the APIs and tools used by developers. This has been a tricky role to fill requiring a combination of a technical mind, really good communication skills as well as experience building processes and teams within a software support environment, and David certainly fits the bill. As the title suggests this is very much a community facing role so David is someone you will be hearing a lot more from when he starts!

SAFE Authenticator & API

This week, we are ready to release the WebRTC signalling example application we mentioned in last week’s dev update. We have hosted the WebRTC application at safe://webrtc.safeexamples. Please try this WebRTC example using the latest version of Peruse.

You can send invites to other public names to have a video call. Right now, the app does not support groups to join the video call. This is a demonstration of performing secure signalling of WebRTC on the SAFE Network. In this example, the signalling server is replaced with the SAFE Network for enabling exchange of connection information between peers. After successful exchange of connection information, the peers connect through a STUN or TURN server. Please do note that we rely on external servers for STUN and TURN protocols. We will be able to get the support for these in the Crust layer eventually and at that point we can remove the external dependencies.

Several PRs for the safe_app_nodejs package were being finalised with intensive code review cycles, including one of them which incorporates some internal refactoring to the mechanisms to handle errors reported from the native safe_app lib. Along with this refactor, a range for error codes was defined (1000 - 1100) for the safe_app_nodejs layer itself, mostly for some input parameters validations made by the Node-FFI library which returns non-friendly errors that are now being intercepted and converted to our own set of error codes and messages.

The C# API bindings were integrated with the Xamarin mobile apps and tested. The apps are working as expected with the new safe_app C# bindings. However, testing on iOS is still pending. A few upstream pull requests (e.g. https://github.com/maidsafe/safe_client_libs/pull/615) need to be updated with some pending patches before the mobile and C# API branches can get merged upstream. We will now be resuming the work with the Java safe_app library to get it to a similar usability stage too with examples and published packages.

We’ve been making steady progress with Peruse refactors, integrating both the Peruse app (to save/read the browsing state to the network) and the authenticator back-end in a background process. This has involved setting up some tighter integration in the app’s Redux store. We’ve also been making some good progress with our research into removing the handle management from the DOM API, which should eventually help streamline the JavaScript SAFE APIs.

SAFE Client Libs

As mentioned in the previous update, we’ve been working on updating all of our crates to the latest Rust compiler version:

This process has now been finished and several PRs are being reviewed now, waiting to be merged soon.

We’ve also merged the fix for a bug in the test_create_app_with_access function.

Routing & Crust

We are continuing with the implementation work of the JIRA tasks for Milestone 1. The tasks completed now reach the components related to the upcoming new data chain features. For example, the VoteAccumulator has been implemented which will be used to collect votes to accumulate a group consensus block. Another example is the refactored DirectMessage which includes new RPCs that will be used later on data chain related communications.

As noticed by the community in the Safe Gossip Protocol topic, we started to update our current Swarm protocol with a secure and randomised, push and pull gossip mechanism that provides n log round and log log n messages. Regulars on this forum will know that we have been assessing and discussing gossip protocols for quite some time and we believe this will be the most effective way to retransmit messages while reducing the number of messages sent across nodes with a view to improving network performance.

In parallel, we are also reworking the consensus mechanism to better facilitate asynchronous consensus that integrates node ageing.

In Crust this week, we invested most of our time to fight regression. We wrote a lot of integration tests to check if traffic is encrypted and what happens otherwise in various scenarios. For example, if somebody sends random, unencrypted data, Crust terminates the connection immediately thus preventing from further DDoS’ing and other exploitations, etc. Also, we’re happy to announce that netsim was published on https://crates.io. netsim is a testing library that allows one to simulate various network conditions and setups. You can build a network with multiple nodes under different types of NAT devices, introduce packet latencies, etc. and run Rust code on a simulated network. We’re using netsim to test Crust, but it’s a separate library. So if you’re interested, go ahead and try it. We’d be really interested in your feedback :slight_smile:

91 Likes

First?:sweat_smile: Great update once again!

6 Likes

Holy moly - every week a new addition to the team is being announced lately - awesome the plans to grow the team are going well! :hugs: now reading the rest =D

Welcome on board @dwg74 !

The gossip protocol really was some unexpected news and I am curious on the performance of the network with data chains and everything implemented in the end :hugs::sunglasses:

12 Likes

Awesome! Full steam ahead!

8 Likes

Welcome @dwg74! :slight_smile:

I’m personally looking forward to this! :sunglasses:

Good to see everything progressing well. WebRTC looks cool and it will be awesome to push the whole thing through Crust!

10 Likes

Q1 Will the storyboard explain how MAID relates to Safecoin on a 1:1 or is a rename of the ‘asset’ to Safecoin being considered?

Q2 Will the storyboard explain the total supply and how currently what is seen on the exchanges is only a fraction of the asset already issued. Extremely important to discuss the economic side of safecoin alongside the technical.

Q3 Have you popped into the poloniex ‘trollbox’ to gain an understanding of how traders view the asset and the fun they have with the MAID moniker,

The transition from ‘Maidsafe’ to ‘Safenetwork’ would seem impended by the constant need to dance around the MAID asset…at least it’s not still ‘Spacecoin’ I guess.

1 Like

Is there a list of names to connect to with WebRTC? I’ve tried the usual suspects but get “Failed to connect to remote peer”

4 Likes

Thanks so much to the whole team for all of the hard work you put in! Keep it going! :slight_smile:

2 Likes

I thought polo took the trollbox down quite a while ago, didn’t they?

3 Likes

Can someone post in non SAFE crypto reddit please

2 Likes

Great news! Good work team!

Welcome @dwg74

Well done Maidsafe devs, nice to have webrtc to play with

Keep up the good work.

:stuck_out_tongue:

3 Likes

hmhmmm - maybe worth mentioning too:

Telegram: Contact @safenetwork the safe network telegram channel: 1380 members +1075 on Riot+others
Telegram: Contact @maidsafecoin the MAID trading telegram channel: 1055 members +323 on Riot+others

in the trading channel there are a lot of passive members (and many spammer-accounts that were only used once and will vanish again) but start of this year we were at 1000 members in the main channel and somewhere around 900 in the trading channel on telegram (don’t know the others)

the live chats are growing and the atmosphere is awesome there =)

10 Likes

Your right maybe their having a laugh elsewhere these days…it was always in good spirit, but the number of newbies that came in and didnt have a clue about the relationship between MAID, Maidsafe and Safecoin was regular and could have been avoided with all the wisdom of hindsight.

To meet the increasing demands on support staff, the Trollbox has been disabled indefinitely and moderators have been reallocated to assist in support

1 Like

to be honest i liked to visit polo and read the bad MAID-jokes when the price was going up and people went nuts xD

4 Likes

Yeah no problem there, it’s just that MAID is an extra layer of understanding for newbies. You get someone interested to the point of purchase and then the MAID part needs to be explained…comes across dumb when the project is in fact awesome.

3 Likes

This is so cool! Crust is just amazing. Very excited about the resurrection of WebRTC but it’d be crazy cool to be able to do group chats with STUN & TURN implemented in Crust for Alpha 3 :wink::wink:

So much good news sprinkled in this update. Really great to see the team consistently expanding and finally filling the Customer Support position with @dwg74, warm welcome to you and the most recent recruits to @maidsafe! Hoping to see things expand in India in time as well, mostly front end positions there if I remember correctly?

Simply can’t wait for the Safecoin and Consensus video. @nicklambert are those being produced back to back or in tandem? Lastly, friggan Data Chains man. Friggan Data Chains… :hear_no_evil: this is getting real!!!

12 Likes

@JPL Before we start a connection with the remote peer’s public name, the remote peer should have at least once initialised with the webrtc application. The initialisation process will setup a channel for that public name to communicate with other peers.

6 Likes

With regards to Q2: With regards to the total supply and how what is currently seen on the exchanges being a fraction of the issued amount, what fraction is on the exchanges vs the total issued amount? Can the issued coin be dumped on exchanges dramatically changing the traded volume? If so by whom?

We decided just to work on the safecoin video for the moment, the next video will follow when the safecoin video is finished/further through the production process.

6 Likes