We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem: Using WalletConnect with most proxy contracts fails with no matching function error
no matching function
Suggested fix: Add the 'implementation' method to this Set and handle it (it doesn't taking any args unlike getFunctionImplementation).
'implementation'
Set
getFunctionImplementation
web/src/plugins/walletConnectToDapps/hooks/useGetAbi.tsx
Line 42 in 2e2aae1
Why it matters: ERC-1967 with the implementation() method is the most commonly used way to get the ABI of the logic contract from a proxy contract.
implementation()
The text was updated successfully, but these errors were encountered:
This this another idea for a fix: https://ethereum.stackexchange.com/questions/151344/how-do-i-identify-an-erc-1967-contract
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Problem:
Using WalletConnect with most proxy contracts fails with
no matching function
errorSuggested fix:
Add the
'implementation'
method to thisSet
and handle it (it doesn't taking any args unlikegetFunctionImplementation
).web/src/plugins/walletConnectToDapps/hooks/useGetAbi.tsx
Line 42 in 2e2aae1
Why it matters:
ERC-1967 with the
implementation()
method is the most commonly used way to get the ABI of the logic contract from a proxy contract.The text was updated successfully, but these errors were encountered: