RLP decoding doesn't work for EIP1559 transaction hex

[crisog]

Ethers Version

5.6.9

Search Terms

eip1559,rlp,decode

Describe the Problem

I cannot decode raw tx bytes from tx using EIP1559.

EIP1559 non-parseable hex

https://etherscan.io/getRawTx?tx=0x00ae7c86db0c7a91c63e1a088305b3f0ad67ca57d722c9b84f623b1d1ce10f4f

Non EIP1559 parseable hex

https://etherscan.io/getRawTx?tx=0xe2e988933dfa2337ecbd72affe0d23bab373a6cbd4795a53df3fe7467a104590

Code Snippet

utils.RLP.decode('0x02f8b401830153b4843b9aca008507f3be98328301d4c094dac17f958d2ee523a2206206994597c13d831ec780b844a9059cbb000000000000000000000000622779096805724b38c42b51989ddca32d671a000000000000000000000000000000000000000000000000000000000022df0080c001a0236084da36000fb2c7373cfa78e8f1bc9d8eb081dc240630c8024aa06fc39f96a030bdc5cd4e1f5f6abbb36c3b004270b68724cc46c56ad5847c99f8ced9c4112d')

Contract ABI

No response

Errors

"invalid rlp data (argument=\"data\", value=\"0x02f8b401830153b4843b9aca008507f3be98328301d4c094dac17f958d2ee523a2206206994597c13d831ec780b844a9059cbb000000000000000000000000622779096805724b38c42b51989ddca32d671a000000000000000000000000000000000000000000000000000000000022df0080c001a0236084da36000fb2c7373cfa78e8f1bc9d8eb081dc240630c8024aa06fc39f96a030bdc5cd4e1f5f6abbb36c3b004270b68724cc46c56ad5847c99f8ced9c4112d\", code=INVALID_ARGUMENT, version=rlp/5.6.9)"

Environment

node.js (v12 or newer)

Environment (Other)

Linux

[ricmoo]

EIP-1559 uses a typed transaction envelope, so the first byte is an out-of-bounds type. You need to remove the first byte (I.E. 02). Pass in the hexSlice from 1 onwards.

[crisog]

Thank you. Is this something that can be added to the docs? I struggled a lot to find this information - for some reason I thought I would be able to pass any hex and it would get decoded.

[ricmoo]

Do the docs indicate somewhere that a transaction is RLP encoded? If so, i definitely need to fix that; let me know if that’s the case.

Transactions are encoded as transactions, which is why there is a parseTransaction function though; which should be used as it uses the transaction envelope type to determine how to decode the the envelope contents, since not all transaction types should have the first byte nipped off. RLP is specific to RLP-encoded data.

[crisog]

Do the docs indicate somewhere that a transaction is RLP encoded? If so, i definitely need to fix that; let me know if that’s the case.

Transactions are encoded as transactions, which is why there is a parseTransaction function though; which should be used as it uses the transaction envelope type to determine how to decode the the envelope contents, since not all transaction types should have the first byte nipped off. RLP is specific to RLP-encoded data.

You are right. I was confused and didn't realize I should be using parseTransaction instead. Thanks!