espresso-sequencer
espresso-sequencer copied to clipboard
EspressoSystems
We ideally should have a way to fully test upgrades locally. Right now we test going from v2 -> v3, but only on the upgraded v3 binary. We should also...
We suspect the issue we currently see with timestamp validation failing is caused by the replicas doing requests to L1 before checking the timestamp. Any slow operations should happen after...
Closes #2118 ### This PR: - warps timestamps so that we can more accurately test the results of escapeHatch related functions - tests in a more realistic way by updating...
We now have the light client contract and hotshot state prover and should remove the old (mock) implementations.
- [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2119 - [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2071 - [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2072 - [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2073 - [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2074 - [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2075 - [ ] https://github.com/EspressoSystems/espresso-sequencer/issues/2076 - [...
Closes #2119 ### This PR: - changes the comparison in the `updateStateHistory` function to the upcoming block timestamp instead of the most recent one in the array
Affected Code: LightClient.sol (line 322-L340) Summary: updateStateHistory function incorrectly computes updates by comparing the first and last elements instead of the first and newly added element, potentially retaining outdated data....