twoeths

it could be up to 70 peers after v1.13.0 on unstable mainnet node but seems like it does not happen a lot like before, would like to keep this to...

As of Jul 2023, sometimes it takes more than 3s to process epoch, this consistently happens on all mainnet nodes: The average epoch transition time is way higher than what...

a lot of time could be for `gc`, v1.10.0 has way less gc and the epoch transition time was improved (this is from a mainnet node)

@nazarhussain take a look at https://github.com/sigp/verified-consensus/blob/main/docs/description_and_informal_proof.md

an idea to improve `processRewardsAndPenalties()`: #6229

need to make sure we implement this https://ethresear.ch/t/formally-verified-optimised-epoch-processing/17359/2 looks like we implemented it https://github.com/sigp/lighthouse/blob/d36ebba1eaf4e337fb0038691f2f74ff953b12c7/consensus/state_processing/src/per_epoch_processing/single_pass.rs#L174

@naviechan is looking into this

closing as this PR was merged https://github.com/ChainSafe/js-libp2p-gossipsub/pull/433

not sure why using `proton-runtime` 5.1.0 the performance is 2x slower ``` protobuf ✔ decode Attestation message using protons 5.1.0 1645793 ops/s 607.6100 ns/op - 983127 runs 60.1 s ✔...

this is not ready, got memory leak issue as noted in https://github.com/ChainSafe/js-libp2p-gossipsub/issues/318#issuecomment-1666407160