Participants

Luc Jarry-Lacombe (BC Diploma), Matt Sonatti (Inokufu), @Perrin, @Laurine B, @Mathieu S 

Course

Presentation of the prototype: https://gr2lxo.axshare.com/#id=yxkx39&p=home and exchanges

Luc presented us what BCD has started to design, namely a webwallet.

We did not have the opportunity to explore the identity creation phase on the BCD side.

Conclusions

• Each user of the portal would have 1 mywallet account per Enterprise, for example: 


• As Matt Sonatti, I would need to use (and therefore own): 


• An "Inokufu" mywallet account when I publish Inokufu-tagged services on the portal


• An "X" mywallet account when I decide to publish services marked X on the portal 


• login/logout of wallets when I switch from one company to another


• The user logs in to his company account on the wallet, at which point he is automatically logged in to his company (no double login)


• We have to consider a V0 without an identity accreditation body for individuals and companies, otherwise "we can wait until 2025". 


• We did not have the opportunity to explore the identity creation phase, including, in a V0, the provision of 2 essential proofs for a person to participate in the portal: 


• The user is who they claim to be. In V0, it is suggested to use an Individual API


• The company is who it claims to be. In V0 it is suggested to use an Enterprise API 


• Prometheus should be used as a real proof of concept to motivate organizations to provide these VC emission infras. In the meantime, we need to use enterprise/individual API workarounds.

Issues/Blockers

What is the production status of mywallet.cloud? 

In this V0, what is included in the Enterprise and Citizen VCs?

Is BCD implementing the Individual and Enterprise APIs to create the VCs? Or does Prometheus do it?

This choice has several impacts: 

If Prometheus is in charge of the link between the DID from mywallet and the proofs of connection via the Personal and Enterprise APIs:

• The user makes the link by logging in via these APIs on Prometheus, in which case Prometheus is in charge of the API implementation 


• Prometheus becomes the controller because it is Prometheus that stores the proof of link between these two entities in a DB 

If BCD is in charge of the link between the mywallet DID and the proof of connection via the individual and enterprise APIs: 

• The user makes the link by logging in via these APIs on Mywallet.cloud in which case BCD is in charge of implementing the APIs 


• BCD becomes the controller because it is BCD that stores the proof of connection between these two entities in a DB

Actions

 Review the prototype @Mathieu S

 Make a note on the risks and responsibilities involved in V0 (Trusted third party) @Laurine B

 Program a new workshop @Mathieu S

 Realize the functional and technical specifications of the V0 @Perrin