EIP-6963 Support

[gomesalexandre]

Overview

Ticket to be groomed, waiting for product input, but eng. work can be done in parallel as UX/UI for this is decoupled from the technical bits required to support the EIP. See https://github.com/shapeshift/web/pull/7869 PoC.

References and additional details

https://github.com/shapeshift/web/pull/7869 PoC.

Acceptance Criteria

• Installed wallets announcing themselves as EIP-6963 providers are detected
• Coinbase and XDEFI are bye bye as first-class implementation in code but are still shown and work the same as before if you have these installed and are shown regardless of installation:
• Dupes which support more than just EVM chains and are supported as first-class impls (Phantom, Keplr) use the proper full implementation instead
• Stretch: Keplr supports EVM chains as a low lift thanks to EIP magic
• @shapeshift/product to add mocks/flows/add bits to ACC

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

[gomesalexandre]

Partially groomed on the eng. side of things but still needs product input/final mocks.

Copypasta qs:

• How do we handle the case of wallets we do support fully with more than EVM chains, but are only automagically detected as EVM providers? -> this one isn't really a product one, it's pretty obvious from an eng/product standpoint, if there is an implementation we support fully, then use our first-class implementation instead. Don't mind Keplr, it's a weird one, and we don't support EVMs for Keplr (until yesterday we weren't even aware Keplr supported EVM chains). For that specific one, we can eventually support EVM chains for it super easily with magic provider
• How do we handle the case of all other wallets that we will now automagically, but may support more than EVM chains? e.g Trust, XDEFI, etc etc. They support UTXOs and other chains, but we want to make it clear to users they can only interact with EVM chains for these. Maybe a smolish "EVM only" badge or info somewhere ?
• How do we separate detected providers/others?
• How can we clean the wallet selection to the most we can, so things finally don't feel cluttered there?
• Suggestion from @woodenfurniture, we could display one/many recent native wallets as "Recent ShapeShift Wallets" there as easy access too to be unlocked with just one click (click native wallet name) vs. two previously (click ShapeShift then "Native Wallet")

[0xean]

@twblack88 - please get ready for us to groom if possible

[reallybeard]

@0xean We've been working on @gomesalexandre on the first pass of this integration.

The simple version of this:

1. Detect installed wallets, and put those at the top of the list
2. Leave our other wallets as is.

Not sure when/if we will re-design the wallet connect modal.