Topic: Does the standard client cache peers' addresses? (Read 1520 times)
Nope. I'm still using 3.20 though, is this a new feature?
%appdata%/bitcoin
try
addnode=64.27.57.225
in your bitcoin.conf file
There are longer lists of reliable nodes out there...
addnode=64.27.57.225
in your bitcoin.conf file
There are longer lists of reliable nodes out there...
Where would that bitcoin.conf be?
try
addnode=64.27.57.225
in your bitcoin.conf file
There are longer lists of reliable nodes out there...
addnode=64.27.57.225
in your bitcoin.conf file
There are longer lists of reliable nodes out there...
I find that whenever I start the client, it takes a long time to bootstrap (stays at 0 connections for a good amount of time).
Is there currently any caching of peers' addresses?
One idea is having the client keep track of peer statistics and thus find which peers will probably be up.
It can keep a simple table of (peer ip, connections attempts, successful connections), and on restart try to connect to the peers with the best past performance.
An improvement is tracking each connection attempt and decaying the weight of old successful connections (weighted probability).
Is there any work done/planned in this area?
Is there currently any caching of peers' addresses?
One idea is having the client keep track of peer statistics and thus find which peers will probably be up.
It can keep a simple table of (peer ip, connections attempts, successful connections), and on restart try to connect to the peers with the best past performance.
An improvement is tracking each connection attempt and decaying the weight of old successful connections (weighted probability).
Is there any work done/planned in this area?
Jump to: