Michael Sproul

(thanks @warrengsmith that was just what I needed)

I'll be running this on my local Lighthouse-Nethermind node through the Goerli merge.

This also seems to be running well on one of our Lighthouse-Geth Ropsten nodes. Will keep an eye on it if there's a re-org.

@mkalinin I agree, I'm parking this in the backlog until we can test all of these edge cases super thoroughly.

This is on our long-term TODO list, so I'll leave this issue open, however if you'd like an immediate workaround you _can_ provision the API token if you generate a...

Hey @jmcruz1983, I don't think there's any conflict even when using web3signer, the VC just needs an arbitrary secp256k1 key on disk to sign the HTTP responses. If you don't...

TODO - [x] Re-open https://github.com/sigp/lighthouse/issues/2342, which still isn't fixed in an LMDB release. - [x] Run slasher tests with LMDB on CI

I've marked this ready for review. I haven't updated the LMDB version because I don't have time to test on Windows right now. I figure we can come back for...

I've been running both backends on mainnet for 5 days (since Aug 10 00:00 UTC) and the current stats are as follows: - MDBX + Database size: 22 GiB +...

The reason we currently log this as such a loud error is because this is also the sort of thing you'd expect to see while running multiple validator clients with...