Documentation for setup

[pranavkirtani88]

Hi, I am trying to setup Cordentity but I do not see any documentation regarding steps to perform the setup,can anyone assist?

[alkopnin]

Hi,

Yes, indeed. Could you provide details what exactly are you looking for? Which setup do you mean?

[pranavkirtani88]

I am looking for the following:

• An architecture diagram/explanation demonstrating which layer is the Corda layer. Indy uses plenum to maintain DID mapping are we replacing it with Corda ? or is Corda layer just for Flows?
• A quick guide for setting up this cordapp to get atleast one workflow running , I have worked with Indy but new to Corda so this would really help.
• Why use this instead of building your own solution on top of indy? whats the added value?

I can write this documentation as well. But I need a brief description on the above points and I can expand on it

[alkopnin]

Thank you for good questions.

Corda is DLT framework, like Ethereum, Fabric or Sawtooth. An advantage of platform is capability to build flexible decentralized protocols between multiple participants (Party). The Parties jointly elaborate on a common immutable view of data (State) over P2P transport framework on top of Artemis and AMQP.

Indy is Identity solution, it implements W3C standard of Claims, DID, and DKMS. Plenum Ledger needs to maintain DPKI and metadata (Revocations, PublicKey, schema, etc). Actually, Indy is an effective mix of crypto-library and DPKI.

Answering your questions:

An architecture diagram/explanation demonstrating which layer is the Corda layer. Indy uses plenum to maintain DID mapping are we replacing it with Corda ? or is Corda layer just for Flows?

No, we don't re-implement Indy ledger. But, we want to be abstract from implementation of Identity Ledger and if it requires the Identity Ledger might be implemented on top of Corda. In this case we lose global Identity layer, but such isolation might be requirements for some private networks.

Cordentity works in 2 modes: B2C & BCB. In current version (0.5) B2B implies Corda' transport to exchange a credential, in 0.6 we provide B2C mode via Cloud Agents (based on Python Ref Agent).

Why use this instead of building your own solution on top of indy? whats the added value?

Each technology should be used in proper place. On top of Corda your can build very effective decentralized applications. Indy is an Identity technology, it manages digital personal information.

The added value is Identity layer for private DLT Corda network. A "credentials processing" can be run between companies and/or individuals. A proof provided by individual can trigger event within a private network as a guarantee of agreement between participants.

There are 3 types of relationship: company-to-company, company-to-client/client-to-company, company-to-public-registry. Cordentity supports 1 and 2. In our roadmap we are going also to support on-boarding process and payment transactions.