-
Notifications
You must be signed in to change notification settings - Fork 3
Home
- Home
- Architecture
- P2P Verifiable credentials model
- Functionality overview
- Security
- Functionalities
- Installation
The creation of this codebase has been funded by and contributed into IHAN – Fair Data Economy. IHAN is a project by Sitra, the Finnish Innovation Fund, and aims to lay the foundation for fair data economy. To create new tools, and enable fair exchange of personal data, IHAN funded two 'Digikunto' projects:
- Finnish Olympic Committee: Top athlete data system
- Finnish Defence Forces: Life-long combat fitness
The projects enabled privacy-preserving, consent-based personal data exchange between a person using a wearable sensor, and an organisation (other than the sensor provider) wishing to retrieve and use the sensor data.
More on project IHAN & the projects: https://www.sitra.fi/en/projects/ihan-pilot-projects/
The MyData Agency solution is a distributed platform that gives the identity holder / individual capabilities to manage their own digital identity, control access to personal device data, manage consent and communicate with an organisation.
The solution is based on a P2P communication model that uses a distributed ledger network to secure the communication channel and verify the integrity of the shared information.
The solution uses Hyperledger Indy agents to enable blockchain-rooted, peer-to-peer interactions. It includes a shared cryptographic wallet, as well as a communications protocol for enabling the P2P interaction between identity holders.
The MyData Agency solution includes two types of agents: a multi-tenant agency enabling multiple individual users to set up their personal agents with wallets, and enterprise agent that an organisation uses to facilitate interactions with the individual agency users.
This wiki describes the MyData Agency solution, their setup protocols and what can be done with them.
The consenting solution demonstrates how an individual can give consented data access to a third party API. The current version gives the individual identity holder the following capabilities:
- Subscribe to data services, like sensor APIs
- Connect with organizations using the DIDComm protocol
- Receive Authentication credentials from an authentication service
- Issue a consent credential for fetching personal data from data services
- Revoke the previously issued credential
The organization's Agent does not have a user interface, instead it employs webhooks and APIs to control the workflows.