in the api doc I see there's the /blocks/id endpoint that returns useful information such as the blob gas price, but for blocks that don't include blob transactions it returns an error (NOT FOUND). That doesn't make it a good endpoint if I need to get the blob gas price for a certain block I provide in input. Furthermore I think an endoint specific to the blob gas price is really useful in order to not having to get the entire block data and then discard everything besides the blob gas price, which would be a waste.
It could also be an estimate for blocks that don't have blob txs based, on the previous one.
I imagine the api something like:
You provide the block id (hash or number) as input and it returns the blob gas price at that block (eventually estimated if there was no blob tx in that block).
in the api doc I see there's the
/blocks/idendpoint that returns useful information such as the blob gas price, but for blocks that don't include blob transactions it returns an error (NOT FOUND). That doesn't make it a good endpoint if I need to get the blob gas price for a certain block I provide in input. Furthermore I think an endoint specific to the blob gas price is really useful in order to not having to get the entire block data and then discard everything besides the blob gas price, which would be a waste.It could also be an estimate for blocks that don't have blob txs based, on the previous one.
I imagine the api something like:
blob-gas-price/blockidYou provide the block id (hash or number) as input and it returns the blob gas price at that block (eventually estimated if there was no blob tx in that block).