-
Notifications
You must be signed in to change notification settings - Fork 360
fix: getCode via readonly web3 object
#3477
Conversation
|
CLA Assistant Lite All Contributors have signed the CLA. |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
Pull Request Test Coverage Report for Build 1824281873
💛 - Coveralls |
|
E2E Tests Failed Failed tests:
|
mmv08
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
THE MVP
katspaugh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hallelujah!
Can you provide some more details? If you're using WalletConnect then this is a known problem (solved here #3479). |
|
No, just by being there I get those calls. I don't even need to be connected That being said, I don't see the issue in the 3479, so is fixed there I guess |




What it solves
Resolves #3435
How this PR fixes it
isSmartContractWalletnow checks via the readonlyweb3object instead of that from the provider. Using the standardgetWeb3()object, returned from the provider, was causingweb3interaction in the case of,eth.getCode()to hang when using thehttps://rpc.xdaichain.com/oe-only/RPC.This fix facilitates switching back to the OE RPC for Gnosis Chain instead. This fixes the gas estimation issue. The
isSmartContractWallet()tweak fixes the WalletConnect issue which made us migrate RPC in the first place.How to test it
smartContractWalletflag correctly in theprovidersstoreBefore release
https://rpc.xdaichain.com/oe-only/