ARCHIEVED

THIS REPO IS ARCHIEVED, it was done for demo purpose only. If you are interested in components which are in used here take a look in DKMS Colossi Network.

Introduction

This is a demonstration of DKMS infrastructure that presents its usage in practice. The demo consists of 2 controllers, where controller1 is an issuer and controller2 is a holder of digitally signed cryptograhpic material that attestates claims about the subject. Controllers communicate indirectly by doing the OOBI's discovery through the infrastructure. For a comprehensive overview of what is going on under the hood, see https://hackmd.io/@bYQK_qO_RLa70okz8n7TQg/rkbCezoBc#Demo-step-by-step-from-the-DKMS-perspective .

License

EUPL 1.2

We have distilled the most crucial license specifics to make your adoption seamless: see here for details.

Structure of this repo

• controller1_terminal_app – A NodeJS based app that demonstrates NodeJS bindings and serves as data issuer
• controller2_mobile_app – A Flutter (currently Android only) based app that demonstrates usage of Dart bindings and serves as data holder;
• infrastructure – A simple network of 3 Witnesses and 1 Watcher;
• watcher_oobi_qr_code – A simple app generating OOBI (given via QR code) for Watcher host

Usage

To run it:

1. Run the infrastructure;
2. Get and install controller2 mobile app;
3. Go to watcher_oobi_qr_code and run it;
4. Using controller2 mobile app scan the QR code printed to the STDOUT by watcher_oobi_qr_code;
5. Go to controller1_terminal_app, run the app, from the main menu select Perform introduction (OOBI via QR code) and scan it from the controller2 mobile app;
6. having running controller1 app, now select from the menu "Issue ACDC" and follow the process. At the end ACDC QR code will be generated. Scan it from the controller2 mobile app.