Receipt after successful transaction
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
One feature that I've been asked about several times is receipts for a given presentation or transaction. This would mean that optionally, the verifier would return a (signed) object that confirms the transaction to the user/wallet.
I believe this would be an important building block for some use-cases and should be added to the protocol --> Add an optional step after Credential Response to convey the receipt.
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
No files, tests, or implementation entry points are identified. Start by reviewing the protocol flow around Credential Response and determine the requirements for an optional signed receipt, including its contents and verification behavior; done means the protocol change is specified clearly enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100