(Feature) [GoodID] location certificate

[johnsmith-gooddollar]

Description

• added goodid utils
• added endpoints
• implemented flow core
• check is phone verified
• issue certificate through veramo
• adjusted eslint & babel versions & options according to the veramo sdk packages requirements (some files were updated by the new prettier)
• TODO: fix unit tests failing due to the build failed

About #523

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• [x] PR title matches follow: (Feature|Bug|Chore) Task Name
• [x] My code follows the style guidelines of this project
• [x] I have followed all the instructions described in the initial task (check Definitions of Done)
• [ ] I have performed a self-review of my own code
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] I have added reference to a related issue in the repository
• [x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
• [ ] I have added screenshots related to my pull request (for frontend tasks)
• [ ] I have pasted a gif showing the feature.
• [x] @mentions of the person or team responsible for reviewing proposed changes

[johnsmith-gooddollar]

@sirpy here is a most simple veramo setup I was able to run: https://github.com/GoodDollar/veramo-nodejs-simple-setup/blob/master/src/veramo/setup.ts

1. I used keyDIDprovider so we do not need infer project
2. But Veramo needs to store some data, at least one DID and some private keys attached to it. This is needed to check certificates issues in future. Otherwise it will create new dids with new keys each server call and of course will fail to verify certificate issues previously.

By default they want to use TypeORM over relational database (mongo won't work with this setup). But they have an beta implementation of JSON storage could store all data required as simple JSON object snapshot. I created own implementation of this interface which will store snapshot to a single document of server_properties collection (like we store database version for migrations)

[johnsmith-gooddollar]

example of the data veramo will store in Mongo:

[sirpy]

@johnsmith-gooddollar no need to store credentials.

1. credentials are signed, so if user shows a credential it is easy to check if it is valid.
2. private keys should be used from our wallet. no need to store anything else.

[sirpy]

@johnsmith-gooddollar Also plugins are optional https://veramo.io/docs/api/core-types.iagentoptions

So we just need the minimal plugins, for keystore look at https://veramo.io/docs/api/key-manager.memoryprivatekeystore which has the import to import a private key

[johnsmith-gooddollar]

@sirpy Yep I found all 3 memory stores (for keys, private keys and dids). The only 2 questions left

• how to create did from keys (I think I would need to research source code)
• which keys I should import, how to get them and how to pass. I suppose it should be private key of admin wallet, right ? how could I get it ? regarding how to pass - I will research it

[johnsmith-gooddollar]

@sirpy I finally was able to generate keys & did using admin wallet private keys as seed: https://github.com/GoodDollar/veramo-nodejs-simple-setup/blob/master/src/veramo/setup.ts#L27

now we have the same DID each run, everything kept in-memory. if you're ok with it - I could hook it up to this PR

[johnsmith-gooddollar]

@sirpy wired it up

[johnsmith-gooddollar]

Please undo all line length formatting. it is confusing. make sure you use the prettier settings defined

done