tersec
tersec
Is "reduce code duplication between fluffy and nimbus verified proxy" still salient? I'm not sure what the current situation for Fluffy is in that regard, in particular.
Do you have the actual FCs the CL is sending?
To add, in general, the CLs will send fCUs corresponding to whatever they think the current (head, safe, finalized) EL blocks are. They don't, per, se, have a notion of...
Yeah, I understand. But in general, in a well-functioning network, the (head, safe, finalized) epochs in fCU are usually (not always) (`n`, `n -1 `, `n-2`). Is that being seen...
If you look at the CL logs (e.g., look at the `nimbus-eth2` `Slot start` logs to compare the `head` and `finalized` epochs), is F lagging H there too?
It's because of the LC -- the LC gets head but (correctly) doesn't update finalized. This isn't a bug, it's by design. The EL sync should handle it properly.
> The algorithm will works. If there is no finality, the "B-Syncer" will do nothing, it will keep waiting for a valid F from CL. Well, it works within a...
Also, it's not only non-finalizing networks, though that is part of it, but also it would recreate the equivalent of - https://github.com/NethermindEth/nethermind/issues/6338
> > 129 is invalid exit code number because it falls into the signals range. For Linux SIGHUP signal sent to process could also return exit code 129. > >...
One data point about the memory usage growth is from https://github.com/status-im/nimbus-eth2/pull/4513 which as of January 2023 notes: ```make # Windows GitHub Actions CI runners, as of this writing, have around...