Integrate with EIP-6963 providers

[kdenhartog]

I saw your talk at lightclient summit and wanted to open this issue to track support of 6963 integration. I assisted with authoring this EIP so happy to help with figuring out how to help with this integration if needed.

[arikg]

Can you add more information on the way you see this integrating?
I think it would be useful to have a basic feature spec in mind and the use-case it serves.
Thanks

[kdenhartog]

Sure, the specifics here are that because the wallets are moving away from default injecting on top of the window.ethereum object and moving to each wallet having it's own seperate 1193 provider object it will lead to issues in detecting which provider object needs to be wrapped.

The DApp's could handle this through selecting the provider and then overwriting the window.ethereum themselve, but I don't believe this is what more libraries are doing. Which means you might need to use something like an Event interception pattern where you also listen for the eip6963:announceProvider event and warp them all before firing the event. I'm not certain if this would work or if there's a different approach here that might work.

In any case, my goal is essentially to make sure that 6963 won't break the provider wrapping pattern that you're using is all not to propose a new feature for it.

cc @boidushya in case you might have some ideas of how this could work.

[boidushya]

Yea i think @kdenhartog summed it up pretty well