[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Why are we doing this?
@TheDivic figured the following:
I figured out last night what’s going on, it’s a small fix I just don’t have the time to push it today.
The error “we can’t execute this request” comes exclusively from Ankr and people are regularly complaining about it (last message from 8 days ago).
And when I looked at the logs it happens only in the GasPrice service when trying to fetch EIP1559 gas values.
We also call the GasPrice service when we check the user op for rejection, and that’s when the client encounters the error.
The reason is that for gas price we are using a raw RPC call (not viem) so it’s not using the fallback provider.
We should just add a public RPC or some other RPC as a fallback and update the EVMNetworkService.getEIP1559FeesPerGas to use viem.estimateFeesPerGas and it should work.
What did we do?
Used viem's estimateFeePerGas method instead of raw RPC call
How Has This Been Tested?
Tested this manually by sending a user op on the Gnosis mainnet
đź“– Context
Type of change
Why are we doing this?
What did we do?
estimateFeePerGasmethod instead of raw RPC callHow Has This Been Tested?