g11tech

> @g11tech take a look at [ethereum/consensus-specs#2954](https://github.com/ethereum/consensus-specs/pull/2954) yes, the PR is the result of the discussions we already had on discord interop channel. And this PR already incorporates this (if...

> Should you use the LodestarError pattern instead? To render error nicely you can also use the pattern to be used in this PR https://github.com/ChainSafe/lodestar/pull/3595/files#diff-5b8cfb1ff2e4749b7113246ddbe1feaa9810ae7bfbc1a7f460d671e74900045fR158 makes sense! :heart: will update...

> So this covers the case where I know what's the correct state in the future but I don't want to download it. Some issue I see: > Exactly! :slightly_smiling_face:...

> > Hmmm, what you are saying makes sense though I think if we clarify in the help that if weakSubjectivityServerUrl is not provided, it will forward sync and verify,...

> Turning draft, since it has been sitting for a while. Can this PR only include the future check, if wsCp > current DB; but not if wsCp is in...

> @g11tech Likewise with #4060, should we compile remaining tasks here into #4455 ? sounds good to me! :+1:

@dapplion :+1:

assign please

@dapplion these looks like good metrics to pick up next ?

> @g11tech It needs the genesisValidatorsRoot for the export > > https://github.com/ChainSafe/lodestar/blob/266f9e2f4418676c9b070bd0f64d1a755cb8e38e/packages/validator/src/slashingProtection/interchange/formats/v5.ts#L13-L18 i think for the known networks we know this value https://github.com/ChainSafe/lodestar/blob/unstable/packages/light-client/src/networks.ts, so guess we can skip :thinking: (may...