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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
I'vent checked lisk source code, but it seems it's working on normal http requests, wouldn't it be better to implement network connectivity additionally over websockets? Additionally limit connected peers to 15-25 per node, so network would be able to propagate data much, much faster and more reliably. Current propagation times are not good (many blocks are propagated in 1-2s, while IMO it should be less than 1s, possibly for most of network participants should be around or less 500ms.
I have also noticed that most nodes are usually "connected" to 100 or more peers, how it's being calculated ? If it's not websocket connection, then technically it can't be understood as connected, but maybe more like was connected in last N seconds?
The text was updated successfully, but these errors were encountered:
I'vent checked lisk source code, but it seems it's working on normal http requests, wouldn't it be better to implement network connectivity additionally over websockets? Additionally limit connected peers to 15-25 per node, so network would be able to propagate data much, much faster and more reliably. Current propagation times are not good (many blocks are propagated in 1-2s, while IMO it should be less than 1s, possibly for most of network participants should be around or less 500ms.
I have also noticed that most nodes are usually "connected" to 100 or more peers, how it's being calculated ? If it's not websocket connection, then technically it can't be understood as connected, but maybe more like was connected in last N seconds?
The text was updated successfully, but these errors were encountered: