Open friedger opened 2 years ago
Thanks for starting this SIP, @friedger.
What are your thoughts on following a scheme similar to EIP-1102, whereby we use a JSON RPC style API, rather than a set of methods. I'd be in favour of this.
A rpc style api makes sense because it would work also for a https provider
A rpc style api makes sense because it would work also for a https provider
Another benefit is that, with Web Extensions, it'll be easier to forward events when they go through the same method. For each new method, a new handler is needed in the forwarding script contexts.
In page script context → Content script context → Background script context
This SIP specifies how applications and wallet should exchange messages and how applications and wallets agree on the protocol.
While writing "SIP for Authentication Protocol", it became clear that the communication should be handled in a separate SIP.