WeTrust Community Update - ROSCA Technical Deep Dive & More

Team WeTrust, reporting in with another Community Update. We’ve spent much of the last two weeks hashing out details of our ROSCA product, so much so that we’re including a Technical Deep Dive (details below) to keep you abreast of these changes. At this point, we have hit a feature freeze on our TLC product, and have started in-depth testing of it. Testing will continue in the coming weeks as we deploy our code on a staging server and start investigating the app flow and additional UI changes, leading up to our product launch.

We’ve continued to work on our website revamp, and appreciate everyone’s patience while we work out some final details before we release it. In addition, we have begun creating a KnowledgeBase and Help Center that will help our customers, both individuals and organizations, understand how to best use our products. At a managerial level, we have decided on an aggressive milestones roadmap that charts our deliverables through the end of the year. Take a look at our updated Product Milestones below. We’ll be striving to hit each of the goals laid out in the roadmap, culminating in delivering a Trusted Lending Circles product this December.

In our last update, we described a new “ROSCA for one” product that would encourage people to save and help them build credit in the meantime. Internally, we have taken to calling this product the “Piggy Bank” (though unlike the piggy banks we used to save our coins as kids, this piggy bank can help improve a person’s credit score). We have created a mock-up of this product and have been performing user testing with students at a local community college.

ROSCA Technical Deep Dive

Our Engineering team has been making great progress on creating a more robust Trusted Lending Circle platform. Those of you who have seen our previous technical deep dives know that the unique architecture of the WeTrust platform means we make two calls when the user interacts with the TLC Smart Contract: one to the backend server for static data, and one to the Smart Contract (via MetaMask) for dynamic data. As we made progress towards completing the happy flow, we encountered an issue with dealing with data from two different sources. We are creating a cleaner layer for doing this that will make our code more robust and make it easier for us to add new features in the future.

We’ve also explored uPort integration, and were able to let users log in using the uPort app installed on the user’s smart phones. As we have our own server, we will need to implement the authentication on the backend to protect our users’ privacy. Given uPort is still in alpha, we won’t be releasing this feature on the mainnet anytime soon, but we may introduce it on testnet when it is more stable.

In addition, we’ve heard from talented techies on our Slack that have great ideas on how to code improvements to our product, particularly on the React.js and server side. We are creating a development environment in Docker to let people test out their new code, and creating guidelines and readmes to make it easier for contributors to get started. This is a first step towards our goal of making WeTrust open source.

One last thing…

We want to remind everyone that WeTrust is looking for Front End Engineers to join our team and build products that reduce financial complexity and increase inclusion. The job description is here, and as a reminder, any successful referrals sent our way will earn a $10,000 bounty (to be paid in TrustCoins) and a huge debt of gratitude (and trust, of course) from all of us.

Yours in Financial Inclusion,

The WeTrust Team