-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] WalletConnect Issue #9673
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
5 similar comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
Is there an existing issue for this?
Product
Trade
Current Behavior
We are in the process of integrating our wallet application with your PancakeSwap platform via WalletConnect. During this integration, we have encountered an additional method, wallet_addEthereumChain.
Currently, we are passing the chainId as a parameter in the request (request?.params?.[0]?.chainId). However, we have observed that this approach yields inconsistent results - it works intermittently.
Expected Behavior
I think wallet_addEthereumChain is only for metamask connection. This method doesn't require for connection type walletconnect. So, I think method should be remove when connection type is wallet connect.
Steps To Reproduce
Try to do walletconnect from wallet app locally and observed the
SESSION_REQUEST
eventEnvironment
Anything else?
No response
The text was updated successfully, but these errors were encountered: