EOS London hackathon was a huge push in creativity for us and as we have mentioned in our previous newsletter we have made three different products.

This article is the starting of this series and we are glad to begin with the Ducatur passport!

The project has been born on the hackathon itself and the first name we have came up with was “EOSPassport”. The following development has brought an idea of declining the EOSio blockchain monopoly as a storage.

With the help of the homomorphic encryption user will be able to prove his age, country and other personal data without any ability to fake it. Moreover, thanks to the algorithm, the data won’t be decrypted while sharing, so it is as secure as it could be.

Data model

• Name
• Home address
• Age
• Country
• ID num
• E-mail
• Phone number
• Addresses of the cryptocurrency wallets
• Bank statement to prove solvency
• Government e-keys (e-passport, pki and etc)

Such types of data can be stored and verified through the identification solution we have created. But, why is it better than the classy KYC we all are so used to?

KYC is a very hard and expensive procedure, goal of which is a filtering process which is needed for a client ordering KYC. KYC ordering client doesn’t need any personal data, the only thing needed is a proof that the customer is passing the filter the client has set to use the products provided.

Ducatur passport solves the above-mentioned problems through storing homomorphically encrypted personal data authorized by the third party (government structure or licensed organization) in the blockchain.

Homomorphic encryption allows performing computational operations without any access to the decryption key. This creates an ability to perform procedures which hold the KYC function without decrypting the personal data. It can verify the age or the country of the user without showing this data to any kind of service provider.

Profile is encrypted by the third party — the verifying center (or something else).

Company doing the verification process requests user constraints necessary to launch FHE (Fully Homomorphic Encrypted) contract. Then, service launches FHE contract and gets the response (isUserOlderThanXyearsOld function returns boolean value about the user). On the further steps we want to include the ability to execute FHE contract from the third party, so it can just send the results and proofs of the execution.

System components

Back-end

1. User EOS contract
2. Verification requesting company contract
3. FHE VM engine

Front-end

• iOS app

iOS app is the only front-end we are developing at the moment and we are considering extending the application to different platforms to create the needed usability for an application of such scale. Here is a list of the functions that app supports now:

• Passport creation
• Transfer of the passport to the verifying entity
• Getting the encrypted profile from the verifying entity
• Verification of your identity for the service provide

Flow diagrams

Acquiring the passport

Authorization through your passport

Here is an example of the age verification on a service without revealing your personal data.

What we have created now are two applications: the passport manager itself and the cinema with Passport verification included.
The back-end part now consists out of the contract launch service and the contract storing encrypted profiles. The version of the application is very early and this piece of coding actions will be the basis of the full Ducatur Passport for much larger range of purposes.

As we have said the blockchain storage monopoly should not be present and in the next releases we will move the storage of the data to the user’s device, so the security levels will be at the highest point.

The implementation opportunities for such application are infinite and we are going to continue developing it. Personal verification is a huge part of our lives. In the system we are living in — proving who we really are to other people is our security, but it is perfect time to bring this security to a new level.

The system, where personal data only belongs to the person owning it is the goal of this product.