Hi all, thanks all for working on this proposal
I got a question from an app developer point of view.
the proposal does not seem to specify any api to consume the data
It says
This EIP introduces a transaction type that has a distinct mempool version and execution-payload version, with only one-way convertibility between the two. The blobs are in the network representation and not in the consensus representation; instead, they are coupled with the beacon block. This means that there is now a part of a transaction that will not be accessible from the web3 API.
If i understand correctly it means the actual blob data is not directly available to execution client and as such these cannot provide it, but the consensus client can. Am I right here?
Furthermore it means that the execution client still have access to some data, is that the commitment and so a reference to the blob ?
it would be great if the eip would specify the api for what is available both for the execution client and consensus client. It seems to me that the EIP would not be complete without these. Or maybe there is another EIP that deals with that ?
Also i am wondering if is possible for the execution client to still provide the blob data api by simply forwarding the request to consensus client.
Note that my perspective is that of a app developer that is potentially interested to make use of EIP-4844 to retrieve data from the blobs by calling the user’s wallet rpc endpoint (EIP-1193) and so I am interested to know what this proposal will allow the user to fetch.,
Please correct me if any of my assumption are wrong
Thanks