Cache prev_hashes input prover data

[atanmarko]

When proving consecutive blocks, we should reuse already retrieved data.

[Nashtare]

Isn't it what #282 was supposed to do already? Or do you mean if you kick of a job proving blocks 1 to 10. And then a next job proving blocks 11 to 30, the latter should retrieve the previously fetched hashes?

[atanmarko]

@Nashtare #282 just halved the number of calls to retrieve the previous 256 hashes. We still call fetch_other_block_data for every block. We also call provider.get_block on multiple places for the same block. Everything should be cached.

[Nashtare]

Ah ok. I got confused because the linked issue in #282 wasn't about going from 256 to 128 RPC calls but really about caching previously fetched block hashes (effectively what this new issue wants to address). But thanks for clarifying.

[atanmarko]

@Nashtare aha, OK. I opened the #282 to port 0xPolygonZero/zero-bin#62 to alloy and it didn't implement cache.

EDIT: it did in some capacity. Anyway it has to be done with current zero-bin setup ASAP.