Add EIP-4844 transaction reading

[BlazeWasHere]

Closes #79

supports reading EIP-4844 transactions (BLObs) from a chain.

@alisinabh to add writing support will require a KZG library might just use https://github.com/ethereum/c-kzg-4844 as a NIF and add writing support in another PR, wdyt?

[alisinabh]

Firstly, thank you for taking to time to add this. 🙏

to add writing support will require a KZG library might just use https://github.com/ethereum/c-kzg-4844 as a NIF and add writing support in another PR, wdyt?

TBH I'm not very familiar with the blobs and their encoding. So far I cannot think of a usecase when creating the blob here would be a common usecase. On the other hand, encoding/decoding EIP-4844 transactions can be a common usecase. I suppose we don't need KZG to just encode/decode the transaction right?

[BlazeWasHere]

Firstly, thank you for taking to time to add this. 🙏

to add writing support will require a KZG library might just use https://github.com/ethereum/c-kzg-4844 as a NIF and add writing support in another PR, wdyt?

TBH I'm not very familiar with the blobs and their encoding. So far I cannot think of a usecase when creating the blob here would be a common usecase. On the other hand, encoding/decoding EIP-4844 transactions can be a common usecase. I suppose we don't need KZG to just encode/decode the transaction right?

Yes agreed, but ethers.js does something similar so it does have its use cases ethers-io/ethers.js#4650 (comment)

Though for the majority of users they will not be sending blob transactions

EIP-4844 txs post blobVersionedHashes which are commitments (references) to the actual blob data, to get the hashes one must use a KZG library

[alisinabh]

EIP-4844 txs post blobVersionedHashes which are commitments (references) to the actual blob data, to get the hashes one must use a KZG library

Now I understand what you mean. Yeah I think it would be useful to implement that. I would personally like it as an opt-in library (optional) since it is not going to be useful for everyone. We can create a new issue and discuss it there.