For our use-case in Ahau, we want presentations to be part of our Tribe Registration process.
We have secure end-points (public keys you can encrypt messages to) where it is safe to send messages to Kaitiaki (custodians/ guardians/ admins of a Tribe).
Here:
our applicant is a VC holder, and
our kaitiaki is a VC Verifier (they want to know more about the applicant)
At the moment we have an slightly annoying workflow which goes:
applicant sends registration
kaitiaki (later) sees registration (status: "awaiting VCs"), and sends an oob-connection to initiate presentation of a VC
applicant (later) sees oob-connection invite, accepts it
kaitiaki (later) sees connection is ready, and requests presentation
applicant (later) completes the presentation
kaitiaki (later) sees the registration (status: "VCs confirmed) and can approve the registration
Each of those steps could have significant delays. The applicant may be applying from their phone/ laptop, and the kaitiaki is maybe reviewing applications from their laptop. They are not assumed to be both online at the same time, so each asynchronous step could make significant hold-up for a process
Feature description
The steps we would prefer:
applicant sends in their registration, including an oob connection invite (signalling desire to present VCs)
kaitiaki (later) sees registration, completes connection, AND requests presentation
application (later) completes the presentation
kaitiaki (later) sees the registration (status: "VCs confirmed) and can approve the registration
Anything else?
NOTE: we use scuttlebutt messages to communicate state-progression (which initiates actions) between the applicant (a Holder using the SDK) and the kaitiaki (Verifier, using a hosted Agent via https APIs)
Proposed feature
For our use-case in Ahau, we want presentations to be part of our Tribe Registration process. We have secure end-points (public keys you can encrypt messages to) where it is safe to send messages to Kaitiaki (custodians/ guardians/ admins of a Tribe).
Here:
At the moment we have an slightly annoying workflow which goes:
Each of those steps could have significant delays. The applicant may be applying from their phone/ laptop, and the kaitiaki is maybe reviewing applications from their laptop. They are not assumed to be both online at the same time, so each asynchronous step could make significant hold-up for a process
Feature description
The steps we would prefer:
Anything else?
NOTE: we use scuttlebutt messages to communicate state-progression (which initiates actions) between the applicant (a Holder using the SDK) and the kaitiaki (Verifier, using a hosted Agent via https APIs)