Receiving, storing and disclosing IRMA attributes in Me.

[maxvisser]

Is your feature request related to a problem? Please describe. At common grounds 2018 in march we spoke with the privacy by design foundation. They developed IRMA: I Reveal My Attributes; a react native app for ios and android where you can store zk-proofs (IDEMIX zero knowledge protocol).

We want to try and support this protocol for p2p validation, instead of using a centralized database.

Describe the solution you'd like I want to set up our own irma_api_server (https://github.com/privacybydesign/irma_api_server). written documentation for the api protocol is here: http://credentials.github.io/protocols/irma-protocol/

aswell as a keyshare server to authenticate users. https://github.com/privacybydesign/irma_keyshare_server that uses this protocol: https://credentials.github.io/protocols/keyshare-protocol/

for this to work we have to investigate what needs to be done to implement the irmago client library in the me app: https://github.com/privacybydesign/irmago

We will also try to find a student intern to do a research in exploring the option to receive, store and disclose IRMA attributes in the Me app.

Describe alternatives you've considered Alternatives are also currently being worked on by @jastam and @martijndoornik but these are still in the experimental phase and are therefore not production ready. The IRMA app is already used in multiple application and is therefore more trustworthy.

Additional context https://github.com/privacybydesign/irma_api_server https://credentials.github.io/protocols/keyshare-protocol/ https://github.com/privacybydesign/irmago

[maxvisser]

Update: I spoke with Devon, a student from Texas USA. He is very interested in investigating this issue with a student group.

[maxvisser]

https://www.nijmegen.nl/gns/no_index/irma/info/

[maxvisser]

We could also decide that Me needs to become a product that does research into self sovereign identity and the pragmatic approach I am taking is just called Forus profile/account. Its therefor just a decision if we want to implement irma into Me or just fork irma_mobile and add a tab for forus wallet.

I see pro's / con's for both.

Pro's for implementing irma in Me:

• two native apps, better user experience
• current apps will be enriched with new features and wont be phased out.

Cons:

• high difficulty of implementing irma go library into me (should not be underestimated you basically port all functionality to native or keep some legacy code in the form of react native/go.)
• Me's brand identity will be merged with that of IRMA. Both parties need to decide if this is desirable.

Forking irma_mobile pros:

• only our api needs to be implemented, we currenty dont have any rocket science within Me codebase.
• we could use forus as brand identity leaving Me brand identity open for being its own identity app.
• as irma_mobile is written in go/react native the bugfixes in IRMA can be ported to our fork and maybe only need one dev on our side.

As discussed in #105, added my comment here.

[maxvisser]

As this is currently not actively being worked on I will close this issue. We can reopen it when it becomes relevant again.