[s2s] : Ratify Verification flow
Open
Nobody has claimed this yet.
server-to-server
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
This issue is tracking consensus on the Verification endpoints in the current proposed text.
Currently there are Five proposed endpoints:
- Initiate: Issuer Endpoint to start a verification session and establish a WSK. Optionally provides VerificationData
- Supplement: Issuer Endpoint to provide additional VerificationData
- Notify: Wallet Endpoint used by the Issuer to notify it on Verification Status changing
- Status: Issuer Endpoint to fetch the current Verification Status
- Cancel: Issuer Endpoint to terminate a Verification Session
On completion transition to the 'credential/provision' endpoint.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the current proposed text for the Verification flow and compare the five named endpoints: Initiate, Supplement, Notify, Status, and Cancel. Trace how VerificationData, the WSK, and the Verification Status move through the flow. Done means consensus is reached on the endpoints and the completion transition to credential/provision is ratified.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100