Update DIP-10

[sunmilee]

Updating DIP-10 to reflect the current PayAddress MVP spec. Changes include:

• Include using CSV file for domain distribution
• Include Reference ID exchange
• Remove UserObject and ProfileURI

[davidiw]

A lot to chew on, I'm not convinced I have the best wording or structure in mind, so consider this a conversation. Also what's up with the conflicts on the tests? weird :(

[davidiw]

Okay, this is coming together really well, I think the next push should probably make this ready for more reviews

[davidiw]

after tweaks, ready to approve

[davidiw]

Looks good to me!

[davidiw]

Let's make an issue for this DIP where folks can continue to give feedback.

[dahliamalkhi]

Thanks for making substantial improvements to this DIP!

I wanted to offer some high level comments:

• I would add a brief introduction to the effect of:

  This DIP has two components.

  The first part is a 2-level namespace for VASP user addresses, consisting of a username and a VASP name. It includes a method for registering VASPs name(s) on the Diem blockchain.

  The second part is a standard framework for initiating a payment transfer to a recipient whose address has already been communicated to an originator (by means left outside the scope of this DIP). The protocol standard arranges for the originator and recipient VASPs to coordinate a transaction referenceID. Other off-chain information exchanges can occur as described in other DIPs (e.g., in DIP-1) and can be embedded within the proposed framework.

• I would refrain from claims about greater privacy, and any other unsubstantiated privacy statements

• I am not supportive of the (two part) name Diem ID, since it it not clear it will be the only identity we will have on Diem. I would prefer something more specific, e.g., VAEP (VASP Endpoint) or the like.

• The user story is cute, but we should emphasize this is only for demonstration purposes, it is NOT part of the proposed standard

• I wonder whether we should permit more characters in VAEP in order to be compatible with addresses on other blockchains?

[davidiw]

@dahliamalkhi, great feedback, routing it to: #156

[longbowlu]

I think we should also talk about what happens when a reference id is used multiples times. Do we expect the receiver to refund?