twoeths
twoeths
[main_thread_1k_sas_nov_20.cpuprofile.zip](https://github.com/user-attachments/files/23660537/main_thread_1k_sas_nov_20.cpuprofile.zip) we should verify proposer signature once per slot, PR in progress: #8620
there is performance issue deserializing DataColumnSidecar, tracked in https://github.com/ChainSafe/lodestar/issues/8623
there is performance issue in `writeBlockInputToDb`, tracked in https://github.com/ChainSafe/lodestar/issues/8624
also below panels should have short label
all errors are the same: `SYNC_COMMITTEE_ERROR_VALIDATOR_NOT_IN_SYNC_COMMITTEE` ``` Feb-16 00:14:20.583 [NETWORK] ^[[34mdebug^[[39m: The invalid gossip contribution and proof was written to .../contributionAndProof_0x6bb15ca4bbe8160f97304dfe42521a0f3df6cd518ccefe091f3a6f9f929d784a_1644966860583.ssz ```
all of the errors are correct as the validator is really not in the sync committee at the specified slot. This works as designed since some nodes could catch invalid...
> > if a node keeps receiving invalid messages from another node, right now it only decreases gossip score of peer, should we also decrease score at lodestar side, and...
yes it is, will work on this
with `v1.8.0-rc.0` the time to verify execution payload is bigger so it may not be a priority atm - block slot 6314643 ``` 581396:Apr-27 12:49:00.129[network] verbose: Received gossip block slot=6314643,...
seems we fixed this after different improvements/fixes