espresso-sequencer
espresso-sequencer copied to clipboard
EspressoSystems
- [x] https://github.com/EspressoSystems/espresso-sequencer/issues/1928 - [x] https://github.com/EspressoSystems/espresso-sequencer/issues/1938 - [x] #1942 Current light client contracts contains logic related to epoch change and stake table commitment updates, which won't be needed for our...
Currently, contract compilation is too slow and hurts dev experience. We should remove these from default profile to speed things up https://github.com/EspressoSystems/espresso-sequencer/blob/50e0368f3efd7485cbfecf687c066a46a4b3f1fc/foundry.toml#L12-L14 I believe the reason we set `via-ir =...
It is confusing running things in docker and then requiring host setup to check the containerized app.
See [zulip thread](https://espresso.zulipchat.com/#narrow/stream/330967-Sequencer/topic/Sequencer.20STF.20spec) The STF should be described in a new markdown file in the `doc` folder.
Currently restartability is broken if all but one nodes restart. The surviving node enters view sync, and then the restarted nodes all enter view sync at different views, and view...
add a second view parameter when initializing HotShot: we should start in view v, the view we were in when we shut down, which makes view sync and other consensus...
As reported by @alxiong ``` --- using `forge test --gas-report --mt "testCorrectUpdateBench"` with gradually uncommented logic in `newFinalizedState()`---- 39.6k for pre-verifier logic 556.8k for verifier 27k for `states[finalizedState] = newState;`...
This issue was reported by @alxiong: also our gas benchmark code is flaky, mostly because forge snapshot is flaky, (the vm.pause/resumeGasMetering() isn't very accurate) also i find that forge test...