Orie Steele

I'm struggling to grok this exactly. It feels like there are a couple things, which each might be connected to wallet apis: ## Simple Presentations initiated by the sender pushing...

@troyronda @sudeshrshetty There are arrows with no labels, but I will try to add labels to the stuff that is numbered. 1. VP-Request Spec, Alice Requests Credentials from Bob. 2....

### Case 0 The simplest meditated exchange is one where the mediator only collects encrypted presentations from a front end user agent / wallet.

### Case 1 Is like case 0, but instead of directly submitting the encrypted VP to the mediator, the holder user agent requests a backend service do so.

Both case 0 and case 1, assume a verifier can decrypt.... this requires the verifier to do key management. If we remove this requirement, the mediator can observe the presentation...

Personally, I prefer case 2 as a starting point, not just because its what we support today, but because we have no real need for yet another word for holder......

If case 2, step 6 used an encrypted VP, its essentially the same exact flow as case 0. except for the fact that the VP is originating from a web...

It seems like the main things missing from the universal wallet spec to support these flows are: 1. JSON models for queries, with mediator addresses, and encryption keys (partially described...

yes, in case 2, if the domain and challenge are part of the step 1, we can skip step 4, and go right to step 5.

### Case 2.1 ^ If we assume verifiers can decrypt.