Pangea Jurisdiction Development Update 06 - November 2017

Updates since last month:

• New team members.
• Outlined requirements
• The Lucy Bot
• Ethereum on Mobile
• First transaction with the Panthalassa
• PAT token pre-sale completed
• Pangea Agreement Standard draft
• TODO

Staffing

We've been through some growing pains but with the hire of two additional developers (Solidity and Senior iOS/ Android developer) we will have a fully-staffed and full time dedicated dev team to reflect our current scaling needs, which gives us confidence we'll be able to accelerate velocity so we can make our targeted release for Pangea 0.3.

Requirements

To help streamline on-boarding we've clarified requirements and scope for the 0.3 release and have prepared documentation. While not comprehensive in scope, we believe it's pragmatically effective for our current phase of development, given the highly fluid nature of the underlying technology. That said: we've created a functional UI walk-through of the aspired functionality, which helps align execution, from UI dev to back-end engineering work.

Lucy

The first draft of Lucy that we hope to make available by Q2, 2018 is available for review and community input on GitHub now. The currently posted version on GitHub includes the beginning of a rating system that would help Lucy become autonomous in her assessment of fitness for some "actors" within the Pangea ecosystem (a function of Timeliness, Efficiency, and a level of Efficacy, relative to observed and quantified baseline for peer "actors" within the Pangea ecosystem). Actors includes individuals, arbitrators, nations and contracts.

Ethereum on Mobile

We got a very basic version of our Ethereum daemon working. We are using status-im’s Ethereum daemon (if some status.im dev is reading this, thank you for the work you put into it). We plan to create a react native module for the Ethereum daemon so that anyone can easily pull it into their project. Of course we will consume the React Native module as well. It’s a win win situation, since we will use it, and at the same time we provide the world a user friendly Ethereum daemon for React Native.

First transactions with Panthalassa

As you might know, pangea will use a quantum resistant mesh network as the communication protocol. We call it Panthalassa (after the sea that surrounded the ancient supercontinent Pangea). This backend is responsible for singing transactions managing private keys and much more. We did our first ETH transactions in the last month. This is special and exciting because you as a user have to confirm transactions AND decrypt your private keys (we will leave it up to you if you decide to encrypt your private key). So when ever you create transactions / sign contracts you will have to confirm that the transaction is OK.

Here is the flow:

• You init a transaction
• The transaction data is validated.
• Your private key is fetched (if encrypted we will display you a dialog to decrypt it)
• The transaction will be signed
• Pangea will ask you really want to do the transaction
• Depending on your wish Panthalassa will execute the transaction / send it to the Ethereum chain.

PAT pre-sale completed

The PAT token pre-sale ended on November 21st. Despite issues many had with the KYC process, it went well, and we raised a total of $2,7M in pre-ICO funding. The public sale will start after the Pangea 0.3 release. Thank you to all who participated, we are excited to, with your help and confidence, take Pangea to the next level.

Pangea Agreement Standard Draft

A first Solidity draft for how to create peer-to-peer agreements in chat conversations has been designed. It will be tested in the Pangea 0.4 iteration when agreements are created in chats. Input is very welcome.

TODO the next month ahead:

• Update the wireframes for Pangea
• Finish building the Pangea 0.3 mobile app
• Finalize the DBVN Solidity contract
• Finalize Panthalassa 0.3 (wallet, web3, etc)
• Finish the react native daemon
• Prepare for the public PAT sale