-
Notifications
You must be signed in to change notification settings - Fork 14
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
Failure to decode EIP-2718 (type2) = 'malformed transaction' #548
Comments
go-ethereumThe
We could make oasis-web3-gateway return the same as web3.pyHas two methods, The
The problem from #501 was that It doesn't do any smart detection of whether or not the chain is EIP-155 or EIP-1559, so defaults to EIP-1559 transactions which will fail because ethersCollects fee data:
Network is considered pre EIP-1559 if No workaround possible, Ethers works fine with the current behavior as the Sapphire is correctly detected as a pre-EIP-1559 network. Can't modify returned blocks in web3 gateway to add a wagmiInvestigating metamaskInvestigating |
AFAIK we use our block hashes, so this isn't the case anyway as we don't actually have Ethereum blocks, just Ethereum transactions. |
If we were to specify That seems like a hacky workaround that would cause clients to think Sapphire is EIP-1559 compatible and start sending type2 transactions - which we want to avoid without full support for EIP-1559. |
RPC Request:
RPC Response:
The responsible code in web3 gateway is:
oasis-web3-gateway/rpc/eth/api.go
Lines 417 to 426 in 9fb1511
The error shown in debug web3 gateway debug logs is:
This error (
errShortTypedTx
) looks like it's thrown from either:We should be using
UnmarshalBinary
instead ofrlp.DecodeBytes
, asUnmarshalBinary
will handle EIP-7218 typed transactions correctly.Decoding test in
modules/evm/src/raw_tx.rs
successfully decodesThe text was updated successfully, but these errors were encountered: