You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With EVM support coming to Flow, this brings the potential for any Cadence account to interact with Flow EVM. However, any dApps interacting exclusively with the EVM wallets via EVM client libraries will be unable to support existing Flow wallets, unless these wallets configure explicit support for Flow EVM.
Suggest A Solution
Potentially, a "FCL Ethereum Provider" could be created, such that it interfaces with a user's Flow wallet via FCL in order to interact with Flow EVM. This provider could handle the connection to the wallet, as well translate the necessary EVM interactions into a native Cadence transaction, which the provider would then request from the Flow wallet.
It is uncertain how feasible (or necessary) this is, but I've created this issue to track this idea.
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered:
Issue to be solved
With EVM support coming to Flow, this brings the potential for any Cadence account to interact with Flow EVM. However, any dApps interacting exclusively with the EVM wallets via EVM client libraries will be unable to support existing Flow wallets, unless these wallets configure explicit support for Flow EVM.
Suggest A Solution
Potentially, a "FCL Ethereum Provider" could be created, such that it interfaces with a user's Flow wallet via FCL in order to interact with Flow EVM. This provider could handle the connection to the wallet, as well translate the necessary EVM interactions into a native Cadence transaction, which the provider would then request from the Flow wallet.
It is uncertain how feasible (or necessary) this is, but I've created this issue to track this idea.
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered: