Wallet capability negotiation
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
From #472
General wallet capability negotiation is a desired feature and should be added.
As part of that, Wallet treatment of credential dataset information as opaque strings should likely be a MUST instead of a SHOULD
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 related issue #472 to understand the intended scope of wallet capability negotiation. No files or tests are named, so identify the relevant specification or implementation entry point before defining the work; done should include an agreed negotiation design and the wallet treatment of credential dataset information as opaque strings.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100