-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
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
SERVER_ERROR and INVALID_ARGUMENT errors for version 5.4.1 #1766
Comments
What is the error you get? |
Same here. Works for 5.3.1 but failed with 5.4.1 Error message I got:
|
I'm running into a similar problem, seems likely the same one, though I am running into this problem even on version 5.3.1 Here is my code snippet:
This is the error that I get
|
Since Kovan hasn't been upgraded to support 1559, it looks like Kovan developers won't be able to use ethersjs versions that support 1559 until Kovan is upgraded. Otherwise endpoints like Alchemy or infura will not recognize the new transaction format. 5.4.1 works with Goerli. But Alchemy Goerli hasn't support 1559 atm from what I can tell, only Infura does. |
Never mind, my problem was unrelated. I got the "invalid ENS name" because I passed in the wrong data type. |
We have this problem too, and find out it is caused by wrong it can be triggered by call
|
@ricmoo breaking support for pre-1559 networks is a backwards incompatible change. v5.4.1 should be v6.0.0 |
hmmm looking at this more, it may be an unintentional breaking change. I think there are a few problems
|
for anyone wondering the workaround we're using is:
|
Related issue #1795 (comment) |
The new block format is optional; if the old block format is received, things keep on trucking. :)
No, the default is EIP-1559 only on networks which support EIP-1559. For non-EIP-1559 networks this is detected and legacy transactions are used. See the
If the tx.type is not specified, it uses the network default. On EIP-1559-enabled networks this will ensure a transaction costs no more than it would in a pre-EIP-1559 world (will probably cost less). On a pre-EIP-1559 network it will continue using the same format.
Which should be fine. If it isn't present, the values for EIP-1559 properties are left null (which is how you can detect EIP-1559 networks) Are you finding Kovan does not work without specifying |
(Note: all changes in 5.4 should be backwards compatible; if you find they are not, provide a concise example and I'll look into it ;)) |
I linked to specific codepaths with explanations of why they break. I am not sure what more concise information you want. 🤔 |
@prestwich An example of a transaction (preferably to a verified contract) on Kovan that doesn't work, and the error it gives. The code paths you linked to, should not be an issue. Otherwise |
it's not whether London is activated, it's whether the rpc method gives a response or a method-not-found error |
e.g. for your point 2, check the code path. There could well be bugs, but that is why I need an example transaction. :) |
I don't use |
here's your concise example lmao:
|
Thanks! Exactly what I needed. :) From the error, it looks like the issue is the explicit |
@prestwich As a side note, I've just confirmed the issue is only with Alchemy and INFURA. If you use the EtherscanProvider, it will work fine; if you need a quick work around. This is also why the default provider works, the sendTransaction hits all them at once, and returns whichever one returns a non-error. So for a quick work around, I recommend: const provider = ethers.getDefaultProvider("koran");
// or
const provider = new ethers.providers.EtherscanProvider("kovan"); I'll get a fix out as soon as possible for the others. |
This has been fixed in 5.4.3. For future reference, anyone who happens across this issue, the cause was an bug in the JsonRpcProvider for For a network that supports Berlin, the The Anyhoo, it should be fixed. But please let me know if you continue to experience any issues. :) |
hey im still seeing this with Alchemy and Infura on Kovan right now
looks like they still dont support a |
The Have you updated to the latest version of ethers? The error you provided looks incomplete, it should contain more data about the request. |
Kovan has upgraded to support EIP-1559 (see this tx for proof), still seeing the issue.
Yep i'm on latest. And yea truncated the full error message. |
Can you please include the full error? |
|
the etherscan kovan provider works btw, seems like its specific to infura/alchemy's nodes? |
I wonder if they haven’t updated yet? Because |
aight an alchemy engineer let me know he thinks its a parity bug 👍 |
Hey there, I'm "the alchemy engineer" :) Just updated our |
@brg8 Thanks for the quick response! @TransmissionsDev is there still a problem with INFURA? They use Geth, I think, but if there is an issue I can reach out to them. |
iirc Kovan is OpenEthereum only? but yea still seeing it with Infura :(
|
Oh, interesting. I didn’t realize the consensus engine wasn’t available in Geth, but that kinda makes sense. Ok, I’ll reach out. Thanks! :) |
@TransmissionsDev Heya! Looks like Infura has fixed the issue from my tests. Can you confirm with yours? |
I've also received word from INFURA that it has been fixed, so I'll close this now. If anyone continues having issues, please feel free to re-open. Thanks! :) |
Currently having this issue on Goerli as well! |
@ratankaliani did you find the issue? |
Are you having a server error or invalid argument error? My issue was an invalid argument to my contract which I resolved by changing the input type. Server error is likely an internet issue of some form. |
but the same code works fine with ethers version 5.3.1
The code
The text was updated successfully, but these errors were encountered: