Michael Sproul

Oh yeah, I hadn't considered that + assumed sync _was_ async

The evidence is pretty much anecdotal, Juan noticed it on a bunch of VPS nodes he manages (https://github.com/sigp/lighthouse/issues/3207#issuecomment-1134521896), and another Discord user was having trouble but I just checked the...

We already pre-compute all the sync selection proof signatures. It could be that this burst of signing is what shows up on web3signer's end. Or, alternatively if we do adopt...

Another change we could implement at the same time would be linearising finalized blocks in the freezer database. Currently we key them by block root indefinitely, which leads to lots...

Thanks @tthebst for starting to look into this. Here are a few pointers that might be useful: * The code for the state reconstruction lives in this function: https://github.com/sigp/lighthouse/blob/79db2d4deb6a47947699d8a4a39347c19ee6e5d6/beacon_node/store/src/reconstruct.rs#L18 It...

I think we should be careful about adding any more pseudo-databases due to the trouble we've had in the past with atomicity and crash safety. I think a separate Lighthouse...

Yeah I've been thinking of adding a db sub-command for a while. We could have `lighthouse db info` for stats, `lighthouse db purge`, a command to drop the op pool,...

There's some WIP code here that we could adapt: https://github.com/sigp/lighthouse/pull/2685

This is due to some values only being configurable at compile-time. The specs from the EF define two types of configuration: [presets](https://github.com/ethereum/consensus-specs/tree/dev/presets) and [configs](https://github.com/ethereum/consensus-specs/tree/dev/configs), and Lighthouse only allows the latter...

> So, SLOTS_PER_EPOCH is not rewritable through config.yaml? Yeah that's right > I guess, that was rewritable, but became unrewritable in the latest releases, right? Nah, it's been like this...