keyko-io / filecoin-verifier-service Goto Github PK

This endpoint will create the new multisig account and add it to the already existed verifier multisig account

Test the whole flow:

Create Multisig for Verifier (as Textile) -> Register App (as Slate) -> Request datacap for user

Depending of the role configured, the service should expose the registerApp endpoint if the service runs with the verifier rile, or the requestDatacap endpoint if the service runs with the app role.

The service would check the configuration is properly set for the role

The service needs to sign messages to setup the multisig configuration to allow automated client verification. So the service instance must custody/store/access the private key in a secure way

the current status of the service is Poc, so we need to gather the requirements and needs to implement a robust and scalable service that allows Keyko to act as an automated Notary and provide a reference implementation for the rest of organizations

Prepare a demo of an e2e flow of the automated datacap allocation service, showing both roles, as a verifier and as an app

Only apps with valid address in the filecoin network and a valid token generated by the service can use the endpoints exposed