Introduction

How to get started with ID-Vault!

ID-Vault is a Self Sovereign Identity (SSI) framework, that means that it aims to make users (self) the ultimate masters (sovereign) of thier data (identity). It does so by providing them a safe and reliable wallet to store their online data.

The ID-Vault framework


Why ID-Vault?

Historically seen there have been a lot of digital identity wallet solutions, SSI is in fact a popular theme or track on many hackathons and ID-Vault it’s is actually a child of the Dutch / EU odyssey program. So why would we need a new solution?

Well actually there are two main reasons

  • Simplicity
  • Compliance

Let talk a little bit about simplicity first, most wallet and SSI solution operate on a blockchain premise where users make claims about there identity and external organizations back those claims up by proof. A user can then provide there claim + proof to a third party which is based on there trust in the signing organisation accepts the claim. This concept is called chain of trust. Actually ID-Vault is based on the same principle, but with one major difference. We handle all of this blockchain magic on our side. And instead of requiring blockchain knowledge from developers we provide a simple to implement OAuth2 interface. That means that if you as a developer have ever build a Facebook, Google of Github sign-on form you have all the knowledge that you need.

The second major difference is compliance, most if not all SSI solutions give full control to users. In fact in most cases the data is stored in a wallet on a mobile device (like a phone) and a user can delete this data at will. That is a nice and idyllic thought but in practice most organizations that you give access to your data are required by law to “hold on to” that data for a given period of time (in europe for example an employer needs to keep employee data in a register for seven years). That dosn’t fly when a user can delete there data at will of simply lose or destroy a device. So in practice organizations copy data from a user that logs in with SSI to their own databases. Unfortunately that means that data moves out of the users control and that a user leads a breadcrumb trail of data with different organizations. In this way a device based wallet leads to less control on your data. How dos ID-Vault solve this? Quite simple actually, first instead of storing the data on a device we store it in a secure cloud. Secondly we allow users to set up contracts with organizations that guarantee them access to the users data for a given time. That way the organization is ensured of legal compliance and no langer needs to store the data locally. Keeping al the users data where it belongs, in your data wallet.

So I just give you all my data? right….

Well actually no, with ID-Vault a user NEVER transfers the ownership or right of their data to ID-Vault, the data stays yours. You simply use the wallet to store it, and share it. See us as service provider, an online storage box of sorts that helps you keep in control.

But if i’m not paying for it then i am the product right?

Well that part is actually true, but not in a traditional sense of the word. We actually went to great legal lengths to prevent us from owning your data or having any right to it. That means that we can’t sell ot give it to other parties (even if we wanted to, which obviously we don’t).

So who pays for all of this?

The organizations that use your data, in the world of modern e-commerce data equals money. That means that you as a user are sitting on a gold mine without the ability to mine it. With ID-Vault you mine it a little bit, organizations pay for accessing your data and that money is then used to keep your data. In a weird way instead of multinationals datamining you, you mine them. Like a modern day data Robin Hood.


The claim and proof infrastructure