transaction_data_types_supported to the wallet metadata?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
Similarly to RAR metadata, would it make sense for the wallet to advertise the "types" of the transaction_data that it supports?
For instance, something like
{
"transaction_data_types_supported" : [
"type1", "type2"
]
}
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
Read the issue proposal alongside the RFC 9396 metadata model and the existing wallet metadata definition in OpenID4VP. Determine whether advertising supported transaction_data types is needed, how the values should be defined, and where the specification would document the field; done means an agreed metadata design and corresponding specification changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100