You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we use libp2p connection manager and maxPeers to control the peer count of es-node, but these two are duplicated, we can use one of them to control the peer count (like prysm used max Peers, and op used connection manager)
Implementation
investigate prysm, remove libp2p connection manager and use max peers to control the peer count, as we have our logic to decide whether we need the new peer or not.
The text was updated successfully, but these errors were encountered:
Rationale
Currently, we use libp2p connection manager and maxPeers to control the peer count of es-node, but these two are duplicated, we can use one of them to control the peer count (like prysm used max Peers, and op used connection manager)
Implementation
investigate prysm, remove libp2p connection manager and use max peers to control the peer count, as we have our logic to decide whether we need the new peer or not.
The text was updated successfully, but these errors were encountered: