[FEATURE] Include WalletConnect metadata in `WC/RPC` services
Closed this issue · 2 comments
Issue to be solved
Currently, WC/RPC services are somewhat naiive - they do not store an context/identifiers relating them to their associated wallets registed with WalletConnect. This becomes a hurdle when trying to perform more specialize authentication flows with WalletConnect.
e.g. Currently, all WalletConnect services authenticate the same - they open the generalized "Connect Wallet" modal, but do not associate with a particular wallet, even if the FCL service which the user is connecting to is associated with a particular wallet.
Suggest A Solution
Some level of WalletConnect metadata must exist in these services. Likely an id alone is sufficient, and probably desirable, as the minimal sufficient amount of metadata helps protect the FCL protocol/discovery against any future changes to WalletConnect's data structures/APIs.
What are you currently working on that this is blocking?
No response
Uncertain if this is still needed with Discovery changes, may be needed to support Discovery API still, however.
No longer needed.