MetaMask - RPC Error: Invalid transaction params: params specify an EIP-1559 transaction but the current network does not support EIP-1559
Steps to reproduce
- Use MetaMask + Trezor hardware wallet
- Attempt to perform any transaction on the frontend
- The confirmation screen never goes away, and no transaction is prompted from MM
- The console logs the following error:
MetaMask - RPC Error: Invalid transaction params: params specify an EIP-1559 transaction but the current network does not support EIP-1559
Object { code: -32602, message: "Invalid transaction params: params specify an EIP-1559 transaction but the current network does not support EIP-1559" }
Note: The "claim COMP" function works, but not any of the deposit/withdraw/repay/borrow functions
I'm using Trezor-Metamask and am having the same problem with the same error messages. Can't use the Send/Deposit function at Changenow.io. Not sure if the same with other websites
I have metamask 10.1.0 in Firefox 92.0 for macOS Catalina 10.15.7 and the Trezor 1 and I cannot do a darn thing on app.compound.finance. I'm trying to avoid liquidation due to problems originating in China. This is a big problem, are there any answers or just a bunch of people who can't do anything either?
@multineural use https://app.defisaver.com/!
This issue seemed to have been more pronounced as app.compound.finance was set to redirect to the ipfs deloyed address. We have since removed the redirect so app.compound.finance should be back to the original enable flow.
Other users have reported downgrading the MM version will get things working again but seems like a Trezor firmware fix to support EIP-1559 needs to fix this overall.
They actually just released a firmware update which enables EIP-1559. Not sure if that has anything to do with MetaMask acting up.
I'd also point out, there are other interfaces you can use to access the Compound Protocol. If you go to https://compound.finance/ and look for "Community-built interfaces," the "Manage" section has a variety of interfaces that should be cross-compatible to interact with the protocol.
+1 and :eyes:
Well its mid December and the problem is still here. FYI defisaver throws the exact same error. I was able to fix the issue by switching to FireFox and installed an older version of MetaMask from https://addons.mozilla.org/en-US/firefox/addon/ether-metamask/versions/
Version 9.8.2 from Jul 23, 2021 worked for me. Both defisaver and the app.compound worked after that. I hope this helps anyone who comes across this.
Well its mid December and the problem is still here. FYI defisaver throws the exact same error. I was able to fix the issue by switching to FireFox and installed an older version of MetaMask from https://addons.mozilla.org/en-US/firefox/addon/ether-metamask/versions/
Version 9.8.2 from Jul 23, 2021 worked for me. Both defisaver and the app.compound worked after that. I hope this helps anyone who comes across this.
Okay