What is trust?

It’s the basic foundation upon which all relationships are built. It’s an expectation of behavior, learned incrementally, and deals with respect, reliability and consistency. Trust can take years to build, seconds to break, and forever to repair. Before you trust a person, you have to have faith that they are who and what they say they are. In business, we’ve created very time-consuming processes to transition from faith to a base level of trustworthiness. A mistake during any one of these processes can be expensive, in more ways than one.

What if you could circumvent faith and move directly to trust?

Development and Design

  • Last week, our Development Team worked on our Software Development Kit (SDK) to clean it up and convert it to TypeScript to make it more effective for public consumption. It will also help a number of other internal services which can also take advantage of the tool. The SDK for the platform has been written recently and we are currently integrating it with the workers.
  • On the back-end, we have been working on adding smart contract definition into the Software Development Kit (SDK) which will allow people to interface with our smart contracts. Getting our SDK up and running is critical, not only for us but also for the end users that will want to interface with our platform. It is beneficial for us because it allows our developers to use the same code instead of writing things over and over again.

Activity Update

  • There was an issue raised to address a design/usability issue in the My Data section. Our team discussed about the feasibility of making the necessary changes and when it can be implemented. Visual refinements in My Data section are now ready for implementation.
  • Certain elements associated with the verification methods had to be re-worked. There were a number of changes to a number of views to support the icons as well as highlighting what can be verified and cannot be verified.
  • There was some work done associated with the verification elements & smart contract interfacing and how to handle that, specifically the workflows supporting multiple profiles.

Planning, Implementation and Marketing

  • We have trimmed down the scope of the referral mechanism to be more straightforward and simple to implement.
  • Last week, our team started working on our new blog which is currently up and running. In the next week, design styles for our blog will be customized and we will start migrating all of our previous posts there. We have also configured a Developer and Integrator Documentation portal on the same system, which is designed for developers specifically. This will give us a way to have much better, clean documentation instead of marked down files. Both of these blogs are currently private as they are still being worked on.
  • There were some changes that were made to the header to bring in tabs to allow for link management. Detailed design for profile layout related to profile management has been provided for front-end implementation.
  • There were some small tweaks to Email verification, Stack Overflow & Github verification user flows.
  • The “Alias” attribute type has been replaced with “Social Links” to improve clarity to its intent.
  • We have launched 3 smart contracts that will work together to provide a sovereign identity solution on the Neo platform. The first one is the Claims Contract which maintains verified claims and attestations. The second one is the Identity Contract which manages access control to that data and ownership of accounts. The third one is a DNS (Domain Name Service) contract designed to enhance third party usability by removing the need to retarget script hashes every time we release a contract update. More information regarding these SCs will be available at a later date.

Over the coming weeks, we will continue to work on the Verification & Identity Infrastructure, Smart Contract Infrastructure and our permissioning system.

Thanks for your continued support,

Your Moonlight Team