- From: Keerthi Thomas <thomas.keerthi@gmail.com>
- Date: Mon, 13 Jul 2020 15:58:54 +0100
- To: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CAEBq9d_-U_siV7gyUW62kEX7MsgNEdegLkCnkjvXokYwxVoAWw@mail.gmail.com>
Hello everyone, I thought this community might be able to provide some direction. I am still on the learning curve, apologies if I missed some earlier work done by yourselves. I am currently working on a problem which I think may have already been solved, I would appreciate it if you can kindly point me in the right direction. I understand and I have previously built POCs using Hyperledger Indy/Aries that allows for verifiable credentials to be issued by a single party (issuer). The question is, how do we issue verifiable credentials issued by multiple-parties? Contracts and other legal documents are sometimes signed between multiple (more than two) parties. In a paper based approach, it is relatively straightforward, signatures are obtained serially. A similar approach is adopted in electronic signing where copies of PDF are signed serially, internally, the system generates a 'certificate of completion' which captures metadata for legal purposes. In the real-estate use-case I am currently working on similar 'certificate of completion' to hold multiple cryptographic signatures of contracting parties over an digital artifact i.e. 'smart legal contract' (for simplicity, consider the artifact as a file containing some text and source code before they are deployed on a DLT or VM). I was thinking the SSI + VC model could be appropriate for this 'certificate of agreement or completion' but I am happy to hear your thoughts and suggestions. Many thanks in advance. Best wishes, Keerthi Thomas
Received on Monday, 13 July 2020 14:59:18 UTC