Will lighthouse return an empty list when fetching an expired blob?

[zhiqiangxu]

We're talking about how should op stack deal with expired blobs here. Currently op stack was expecting an error to be returned for expired blobs. Prysm will return empty list/status=200 for expired blobs. What about lighthouse?

I've read the code for beacon/blob_sidecars/{block_id}, it seems lighthouse will also return an empty list when fetching an expired blob.

Just wanna confirm with the official team:)

[michaelsproul]

Yeah at the moment Lighthouse will also return an empty list.

I don't really like this behaviour though, because it combines the cases for (1) no blobs ever existed at this slot and (2) there were blobs at this slot but we've deleted them.

[dapplion]

Worth it to raise the issue in the beacon APIs specs. There has been similar discussions for the case of missed slots. Would having different HTTP status code serve your use case?

[zhiqiangxu]

I think so, here is how op stack is handling the response.

[michaelsproul]

I think we should just return a 404 here. I'll raise a PR.

[michaelsproul]

PR here:

• https://github.com/sigp/lighthouse/pull/6331

[michaelsproul]

The fix will be in the next release - v6.0.0