\[Solved\] Feathercoin Client \* Synching to the network

kuroato

OK, so it’s been maybe two days and my Feathercoin - Wallet is still not fully synced although I have not left it for 24 hours, I’m usually on my PC about 8 Hours a Day and have had Feathercoin - Wallet running but still after i guess 16 Hours I’m only at 45% done. Is this Normal??

Also, it does seem to be moving along alittle faster right now as I write this and I notice I have more active connections than before, so maybe that’s why it’s going faster because I’m connecting to more Clients (Nodes) in the Network to Download the Ledger. While this makes sense… I curious about something…

What happens if there are 0 Active Connections? What if No one has their Feathercoin - Wallet Running? That means the whole Network is pretty much down? Since this is a P2P Network Right?

Also if No one has their Feathercoin - Wallet Running, then how does Feathercoin continue to function? Why would it not just crash the minute that happens?

Finally in order for Feathercoin to continue growing, do we all need to participate and keep our Feathercoin - Wallet Running at all times, even if we are not using Feathercoin at any given moment?

Wellenreiter

The principle is this:

the client has a number of IP adresses from known other clients
it tries in a round robbin mode to connect to these clients
if it gets a connection it requests the list of known clients from the partner and adds these to the list of known clients. These additions will be lost when the client exists and rebuild next time it starts
there is a command in the console window of the client to manually add a host to get started.
after an initial time trying to connect the client also starts to request block chain information as current block, compares it to the locally stored blocks and requests the missing blocks from one of the currently active connections.
If that fails it uses the next connection, drop the connection not providing data and tries to open another one (not sure about the last thing)
it showed out lately, that for the first sync the client sometimes gets stuck.
if that happens (no progress > 10-15 minutes, a restart of the client helps

There are always active clients as each solo miner and every mining pool needs to run an instance of the client in order to mine. This means if there are no clients online at all, the whole blockchain ist stopped and no transaction can be executed.

If you client needs a very long time

kuroato

thank you for the awesome response… really appreciate your time and details.

I totally didn’t think about the miners… so the network will always be operational as long as their are miners. That’s good to know. Thanks again,

wrapper

It has only been a slight problem, gaining the initial seed network connection for a new user. Most people connect straight away

When there has been a problem with a new user not joining the network quickly, I have sent them an “anddnode” of a current IP address. Using - “getpeerinfo” on the debug console.

That helps get them seed a current open node on the network and thus find more nodes.

As the network increases, exponentially at the moment, this will be less and less of an issue. From now on, there will always be multiple wallets on line to connect to.