Difference between revisions of "Wallet Requests"
(→Problems) |
(→Solutions) |
||
| Line 14: | Line 14: | ||
==Solutions== | ==Solutions== | ||
| + | This page describes two way to handle requests from wallets that need to server multiple purposes in a single request to the wallet. | ||
==References== | ==References== | ||
Revision as of 17:54, 21 February 2024
Full Title or Meme
What should a request to the wallet look like to achieve the purpose of the Verifier and the privacy of the Subject.
Context
Today it is possible to use a driver's license issued in California to enter a bar in Thailand. The question arises about how a request from a Verifier in any jurisdiction can make a request that all digital Wallets could meaningfully handle to allow existing purposes. The use cases listed below include cases were interoperability of wallets with disparate requirements in diverse identity Ecosystems are important to the person that selects which wallet to use.
Problems
Users will not select Wallets that cannot get them access to resources that they depend upon. This page focuses on the way to create a request from a verifier such that it can be handled by the wallets that the user is likely to have in their possession.
Use Cases
- A wallet that holds a California Mobile Driver's License can be used to enter a bar in a different country with different legal requirements.
- A shopper at a grocery store wants to give the store their Loyalty ID in order to take advantage of selective discounts available to loyal customers.
- A sovereign state needs State Mandated Identification in order to have a consistent Identifier for any of the several hundred licenses and other uses.
Solutions
This page describes two way to handle requests from wallets that need to server multiple purposes in a single request to the wallet.
