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
times should be strings like "5s" or "3w" or something more human readable than the current secs and nanos fields
peer config should not require peer_id and db_path - we might as well just use the address to identify the peer since we don't authenticate the peer_id (though if we ever adopt a p2p reactor for the light client this would change). Then really all we need in the config is a list of tcp addresses ... but this might be a larger discussion about updating the PeerID in the light-client crate ...
On startup it should log what block it's at before it starts syncing
The text was updated successfully, but these errors were encountered:
Given that we archived the light node last year, I'm closing this for now. If there's anything from here that needs implementation in the light client itself, please let me know and we can reopen or open separate issues.
Breakout from #442:
Some more follow up:
secs
andnanos
fieldspeer_id
anddb_path
- we might as well just use theaddress
to identify the peer since we don't authenticate thepeer_id
(though if we ever adopt a p2p reactor for the light client this would change). Then really all we need in the config is a list of tcp addresses ... but this might be a larger discussion about updating the PeerID in thelight-client
crate ...The text was updated successfully, but these errors were encountered: