twoeths

prysm also return 0 block ``` Error: peerId=16Uiu2HAm4bkvXdyzkh1wjRPXSXJmYkze2Xr9ZcXnCjm5PsBExJi3 peerClient=Prysm-cgc:128 returns no blocks dataColumnSidecars=3584 for BeaconBlocksByRangeRequest {"startSlot":22304,"count":32,"step":1} ```

we already check earliestAvailableSlot in #8150

> Its possible for a ByRange request to have 0 blocks in it during a period where chain liveness is an issue an there is an epoch with 0 blocks....

one way to make sure it works is to have `config` as a private property of `EpochCache` class

in lighthouse it also has a `ValidatorPubkeyCache` ```rust pub struct ValidatorPubkeyCache { pubkeys: Vec, indices: HashMap, pubkey_bytes: Vec, _phantom: PhantomData, } ``` we can think about it later if we...

need to think about how to populate pubkey2index, index2pubkey for the 1st time when we boost a beacon-node https://github.com/ChainSafe/lodestar/blob/889b1c44754fdfe6acd826fc10b5b0013d9a6faa/packages/beacon-node/src/chain/chain.ts#L325 we don't have a full BeaconState anymore, maybe IBeaconStateView should provide...

we always compute shuffling synchronously and don't use the async build in `beforeEpochTransition` postfulu this shuffling calculation time by source confirm that prefulu, we have an assumption that next epoch...

attaching the profile persisted in the above image [holesky_fulu_oct_02.cpuprofile.zip](https://github.com/user-attachments/files/22656331/holesky_fulu_oct_02.cpuprofile.zip)

root cause could be due to the performance of `asyncAggregateWithRandomness()`, see #8524

this is not fulu specific, it happens pre-fulu as well since this happens randomly, it's very likely it's the result of building a new tree (with `slice()` api) then it...