Kambria Development Update — February 2019

Today, this is how our key feature sets have been updated.

General Site Usage

With respect to the overall site usage features and transferability of tokens, the team has:

• Implemented the authentication system for app.kambria.io utilizing AWS Cognito services

• Published the User Profile portal

• Implemented Kambria Wallet to allow users to interact with the Kambria platform using their own wallet method

Codebase

As the platform’s module management and build system, the KDNA Codebase is the heart of our open innovation platform. We strive to make the codebase easy to use in order to allow developers to efficiently innovate on the work of others, thereby saving time and cost of reinvention. Delivering a developer-friendly system supports our Master Plan goal of building a strong developer community.

Since our last update, our team has:

• Designed the KDNA schema using RDF (resource description framework)
• Completed the technical paper on Kambria KDNA system utilizing IPFS (interplanetary file system) and RDF

Bounties and Competition

Another integral piece of our platform is our bounty mechanism by which Kambria will provide Open Innovation-as-a-Service (OIAAS) as discussed in our Master Plan. Through OIAAS, corporations will be able to propose bounties for advanced technology and teams will be able to compete for rewards in multiple rounds. At each round, Kambria community and judges will pick the teams to go to the next round and reward them accordingly. Kambria will earn an administrative fee for organizing and running the challenge, thereby generating real-world revenue.

With respect to capabilities for Bounties and Competitions, our team has:

• Revamped the user interface and user experience of the Kambria Innovation Marketplace
• Completed the Kambria judge technical paper
• Designed the Bounty Judge Smart Contract
• Refactored the Kambria Bounty system to utilize the new authentication system. As a team owner, the user needs to login to create a new team and as a team member, the user can send a request to join any team.
• Implemented the Bounty Judge smart-contract on-chain
• Continued implementing the smart contract for the Bounty Judge protocol and continue to revise the smart-contract based on an internal audit of the protocol. The 3 main contracts for judge protocol are BountyModerator, Bounty, and JudgeCommittee. 1) BountyModerator is the contract to create new bounties and to define requirements for a bounty. 2) Bounty is the place for teams to participate in and claim their reward. Moreover, it is where backers sponsor tokens to the bounty and withdraw tokens if JudgeCommitee decides that the bounty has no winners. 3) JudgeCommittee is the contract for teams and backers to choose judges. It is where judges stake/withdraw token, submit results, and decide whether the bounty has winners or not. In order to decide the winners, we use JudgementProtocol contract to calculate the final score from scores submitted by the judges.
• Reviewed and enhanced the user experience of the Bounty system
• Designed the portal for K-Prize Challenges
• Refactored the Create & Join Team workflow of the Bounty system to utilize the new Membership system