Closed ronaldoguedess closed 3 weeks ago
??
Hi thanks for reporting! Please help me understand why it's wrong. The protocol doesn't manipulate requests, it passes through what app sends. What can I do to reproduce it?
I initially thought there was an issue because the TrustWallet provider was returning a different function when dApps called the approval function. In WalletConnect, it's defined as eth_sendTransaction. I later realized I needed to check the first 10 characters of the data to identify if it was an approval or not.
After investigating, I understood it wasn't actually an issue, just a difference in implementation.
I have identified an issue where Wallet Connect is incorrectly receiving parameters. Specifically, when approving a token, it is not receiving the correct argument:
Supported namespaces include "eth_signTransaction":
The incorrect method returned is:
eth_sendTransaction
and it should return:eth_signTransaction
Include the screenshot to help clarify the issue to see i'm approving: