[S2S] Support for a 3rd party Wallet Server
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Should support be added for a "3rd party Wallet Server" rather than binding the Wallet client and Wallet server to the same organization. This has implications on overall trust model and liability assignment. As an aside of this higher level concept...
- can wallet clients pass attestations through the protocol to the Issuer so that the issuer has higher assurance of wallet client than just trusting the wallet client by proxy of the wallet server
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 implementation files, tests, or entry points are named. Start by clarifying the proposed third-party Wallet Server trust model and liability implications, then assess whether wallet-client attestations should pass to the Issuer. Done requires an agreed protocol direction and requirements before implementation can be scoped.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100