Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Holder initiated Presentations #118

Open
mixmix opened this issue Nov 8, 2023 · 3 comments
Open

Holder initiated Presentations #118

mixmix opened this issue Nov 8, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@mixmix
Copy link
Contributor

mixmix commented Nov 8, 2023

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:

  • 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:

  1. applicant sends registration
  2. kaitiaki (later) sees registration (status: "awaiting VCs"), and sends an oob-connection to initiate presentation of a VC
  3. applicant (later) sees oob-connection invite, accepts it
  4. kaitiaki (later) sees connection is ready, and requests presentation
  5. applicant (later) completes the presentation
  6. 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:

  1. applicant sends in their registration, including an oob connection invite (signalling desire to present VCs)
  2. kaitiaki (later) sees registration, completes connection, AND requests presentation
  3. application (later) completes the presentation
  4. 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)

@mixmix
Copy link
Contributor Author

mixmix commented May 6, 2024

update .... we're working on this now with a grant!
First step is "Holder initiated connections"

@mkbreuningIOHK mkbreuningIOHK added the enhancement New feature or request label May 6, 2024
@mkbreuningIOHK
Copy link
Contributor

@mixmix , so should this issue be assigned to you?

@mixmix
Copy link
Contributor Author

mixmix commented Jul 19, 2024

@mkbreuningIOHK what does "assigned" mean in your org context?
In orgs I've been in it means "is going to take this work on". It's unclear what sort of Open Source project this is at the moment - is Identus collaborating with outsiders, welcoming PRs, contributions to direction setting? If yes then those things would need resourcing - people and time on Identus side to weave others work in (I've been on the other side where we have under-resourced this and it's a bad time)

cc @elribonazo here is an example of me asking for more power at the "edge" (shift towards fully p2p agents)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants