twoeths

I found all Sockets have a timeout and they're all destroyed all connection statuses are also "closed" also there are socket events attached during the `MultiaddrConnection.close()` function, especially the "drain"...

@SgtPooki here's the libp2p dashboard in lodestar https://github.com/ChainSafe/lodestar/blob/unstable/dashboards/lodestar_libp2p.json

@achingbrain need to reopen until it's confirmed this is fixed in lodestar, waiting for a new release of `transport-tcp` to test

@achingbrain we tested v9.0.22 and found it does not resolve the memory leak issue. It also introduced some performance impact that caused node to forward less gossip messages to mesh...

I think we need to upgrade all libp2p dependencies to the latest versions and evaluate again cc @wemeetagain need to take a new profile with leaked memory for `libp2p-tcp` >=...

in progress PR by @wemeetagain : https://github.com/ChainSafe/lodestar/pull/6711

this is because `latestExecutionPayloadHeader` in capella has 15 fields, deneb adds 2 fields which makes it 17 fields, which makes the merkle tree to grow to 1 more depth the...

nice, will add this to ssz so lodestar does not need to deal with this

there is an issue with `ecdsa_pubkey_negate` function this did not exist with v1.17.0 [here](https://github.com/ChainSafe/lodestar/pull/6523#issuecomment-1996232103) [v1.19.0-rc.0_mainnet_main.cpuprofile.zip](https://github.com/user-attachments/files/15546575/v1.19.0-rc.0_mainnet_main.cpuprofile.zip)

posting `gc pause time rate` metric here for later reference: vs stable mainnet node (6h rate interval in the last 24h) this affects other metrics, for example epoch transition time