-
Notifications
You must be signed in to change notification settings - Fork 23
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
docs: connectionless proof #1448
base: main
Are you sure you want to change the base?
docs: connectionless proof #1448
Conversation
Signed-off-by: mixmix <[email protected]>
Signed-off-by: mixmix <[email protected]>
Signed-off-by: mixmix <[email protected]>
|
||
```mermaid | ||
--- | ||
title: Verifier Flow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about the internal states with connectionless flows.
The protocol consists of the following main parts: | ||
|
||
1. The Verifier creates a new proof presentation request invite using the [`/present-proof/presentations/invitation`](/agent-api/#tag/Present-Proof/operation/createOOBRequestPresentationInvitation) endpoint. This returns a unique out-of-band (OOB) invite code which can be used to intiated a presentation request. | ||
2. The Holder/Prover receives the OOB invite code (via some communication channel), and accepts the invitation, triggering a presentation request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to describe what "accepting an invite" means. If you're working with an SDK that's more clear as they have methods, but I think these docs are a bit more generic, and open-agent-centric right? So do we need to describe how to unpack it, build the message to send? (seems verbose)
…roof Signed-off-by: mixmix <[email protected]>
Base branch: #1447 first)
See diff : b5efc5f
Adds