refactor(protocol): optimize storage reads/writes in proveBlock

[dantaik]

Most proveBlock transactions submit a new state transition for blocks. Previously we would fetch and compare storage values from the state transition ring buffer with the prover's values, updating each slot one by one.

With the new optimization, we bypass fetching these values for new state transitions (because the slots' current values don't matter), instead opting to perform a direct storage save at the end.

This optimisation reduces gas by 20K.

[openzeppelin-code]

refactor(protocol): optimize storage reads/writes in proveBlock

Generated at commit: 46e0ff5a2803df01526703a316e1c6a3a6a722ee

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	2 2 0 8 42 54
Dependencies	Critical High Medium Low Note Total	0 0 0 0 0 0

---

For more details view the full report in OpenZeppelin Code Inspector

[Brechtpd]

Looks okay, but there's a lot of logic related to these state transitions and it's too much for me to keep in my head just reviewing these PRs without going through all the logic again so I don't know for sure.

[dantaik]

Looks okay, but there's a lot of logic related to these state transitions and it's too much for me to keep in my head just reviewing these PRs without going through all the logic again so I don't know for sure.

We do need to review the changes more carefully before pushing them. Please take your time.

[dantaik]

Looks okay, but there's a lot of logic related to these state transitions and it's too much for me to keep in my head just reviewing these PRs without going through all the logic again so I don't know for sure.

Brecht, please take another look. I made some new changes.