Parse type field in Receipts

[mfornet]

This field was introduced Berlin Hard Fork as part of EIP-2930

[ricmoo]

Is this widely adopted now? At the time, it was hit-or-miss if a backend returned it. I'll look into this. :)

[mfornet]

Is this widely adopted now? At the time, it was hit-or-miss if a backend returned it. I'll look into this. :)

I've only tried geth, and some common RPC providers (like infura) and they are providing this field both for Ropsten and Mainnet.

We need this features in our project, since we are building proofs for inclusion of Receipts in blocks, and they need to be serialized exactly as expected, and this field is necessary to know how to serialize it properly. Read more in this issues: Near-One/rainbow-bridge#557, aurora-is-near/eth-object#1

In case these field doesn't exists, it should be probably safe to initialise it with 0.

[ricmoo]

I’ve added this locally and been chatting with some people on Geth and the author of the EIP.

There seems to be a disconnect; some expected type 0 to be available as a future type and some thought it was reserved to represent legacy transactions.

I’ve started a document in the specifications to formalize the reserved typed transaction version bytes and will give it a few days to settle and get some feedback before sending a PR. Then I should be able to add the necessary changes to start using 0 for legacy transactions. :)

[ricmoo]

This has been published in 5.4.0. I've added type to TransactionResponse and TransactionReceipt as well as effectiveGasPrice to TransactionReceipt. Try it out and let me know if you have any problems. :)

[mfornet]

It is working! Thanks