Privacy for vulnerable people

We believe in the data economy and empowerment of people protecting their personal data.

What it does

Using a personal data wallet our clients selectively disclose personal data using Ocean marketplace services and workflows in order to issue, load or verify credentials, whilst preserving privacy. No more lengthy forms to submit. Instant checking of verifiable credentials against eligible benefits. Straight-through processing of credentials using Ocean marketplace services in government application procedures. By using these services, we are able to collect anonymized transactions as input datasets in building AI models for predictions of top chosen benefits and services ratings, in order to help government invest in the right kind of services and benefits. This model and its inputs are to be published in the Ocean marketplace as free assets, for anyone to audit the (un)biased inputs and transparency of the model itself and account for the fact that it’s built with public funding.

About this project

How we built it

By publishing qualifying services and workflows in an Ocean Protocol powered Marketplace, we can hook up a Vue.js data wallet by means of a simple QR-code-service as glue for data transfer of DIDs and webtokens in order to preserve privacy and use service endpoints according to Ocean OEP 8 metadata to disclose and verify information and issue verifiable credentials as well. Every piece of data in the wallet or an asset in the marketplace is modeled after a credential, published as a DDO (data asset) in the marketplace. We first publish a base credential DDO like some university degree format description using in the Ocean marketplace, issued by a public organization, as a template from which we instantiate –issue– timestamped credential objects to a client. This event will be published as a DDO of a Verifiable Credential according to the W3C standard, using OEP 8 service endpoints as a means to interact with this asset, like authenticate, read the accompanying data and verify. If service endpoints link to public documents, like in the case of the base credential DDO, we use IPFS to download files, lifting the burden of managing storage facilities. When service endpoints link to private or verifiable data, like in the case of a verifiable credential DDO, we use authentication services and separate DLT to get to the data.


In progress

node.js | oceanprotocol | react | typescript


Wat kunnen we voor je betekenen?

Meer weten over dit project?
We geven je graag een demo.

Meer projecten

Bredewater 16 | 2715CA | Zoetermeer
telefoon +31 79 203 3019