can we remove verification when reading from caches

[samlaf]

Noticed that GET requests on my local devnet are taking ~500ms to complete when using a redis cache

Have not profiled but my guess is that verification is taking most of this time.

@bxue-l2 suggested that we might be able to remove the verification done everytime we read from the cache. When verification is enabled, we verify responses from the disperser before populating the redis cache, so it seems redundant to verify blobs queried from redis?

@epociask wdyt?

[epociask]

seems like a legitimate optimization - assuming that blobs are verified before insertion to cache

[epociask]

feel free to assign to me if no one else is interested

[epociask]

@samlaf @bxue-l2 think we shoudl still keep this given the recent issue that celo had where blob contents being read from cache were incorrectly transformed. If the verification was disabled then the chain's derivation would've halted

[samlaf]

@epociask why were they improperly transformed? Bug in our client?

[epociask]

@samlaf @bxue-l2 if we provide a knob for this we can add a dangerous env type to enable this. There are pretty severe security degradations when using this mode