search

status-im / pm

PM for Core Dev calls, etc
3 stars 5 forks source link

Status Dev Call 25 Agenda #47

Closed StatusSceptre closed 5 years ago

StatusSceptre commented 5 years ago

Please leave your agenda items here.

Note: We no longer open core dev calls with team updates. We only discuss specific points for the agenda.

yenda commented 5 years ago

RFC for reintroduction of send and receive commands https://github.com/status-im/team-core/issues/5

yenda commented 5 years ago

To sum up:

Bob uses request command:
- Bob selects his wallet, the asset and amount, it sends an EIP681 URI for paiment request in a text message to Alice, that's a simple URI in the form "ethereum:pay-XXXXXXX..."
- Alice taps on the request message (it is displayed in a rich form with a pay action) and it opens the transaction drawer with a transaction already filled, she just has to sign the transaction
- (optional: Alice sends a transaction URI following ERC831 in the form of "ethereum:tx-0xTXHASH", but later on we could ditch that in favor of in app transactions?)

Bob uses send command:
- Bob selects the wallet he wants to send from, as well as asset and amount
- if Alice has an ens name,
     - Bob is asked if he wants to sign and send the transaction directly to Alice known address, and wants to request to Alice which address to use
     - if he decides to use Alice known address, a transaction URI message is sent (as in the case above), 
     - otherwise same case as if he didn't know her address
- if Alice doesn't have an ens name,
   -  Bob sends a  URI "ethereum:request-XXXXX" to Alice, modeled on EIP681 
   - After tapping on the message, Alice is invited to choose which wallet to request the funds on, when she chooses, a payment request URI is sent to Bob, the flow is the same as using request command from there
StatusSceptre commented 5 years ago

Notes: https://notes.status.im/cW_ng1skT2SkxpVRQ3nkxA