Currently there is no standard of how a decentralized application interacts with a wallet, resulting in uncertainty from the developers perspective. In order to guarantee broad adoption of applications leveraging Tezos smart contracts the right developer tools need to be provided.
Not having a standard also results in bad end user experience, having a dedicated wallet for each service hat the user needs to setup first is not feasible.
We’ve gathered our initial thoughts and put them in a draft proposal and tentatively made it available in a repository.
The proposal describes the various message types and provides examples of transport layers.
The different message types that exist between the app and wallet.
- Broadcast Transactions
Example of possible transport layers using these message types, we only describe two here that are distinctly different.
- QR Codes
- Push Notification / Relay Network
Feedback - Round 1
We came together for a workshop with parties like Stove Labs, Cryptonomics, CamlCase, ECAD Labs, Keefer Taylor & Cryptium Labs during the TQuorum Global Summit.
The workshop was immensely valuable and productive as were able to gather a lot of feedback and discuss eventual scenarios and why certain changes to the draft are required.
Now we’re also looking to you, please share your thoughts on such a standard and the proposed message types. Keep in mind the great feedback we have already received and will incorporate in the next iteration of the proposal.
The next steps from our side to continue this effort will happen shortly.
- Adapt draft with feedback for the next iteration
- Implementation -> first step: wallet browser extension MVP (signing, broadcasting)