Topic: Feathercoin broken? (Read 1428 times)
A block is supposed to be generated every 2.5 mins. When the time from the last block is over an hour the client thinks it is unsynced. Wait for the next block to be found and all will be fine.
Dont worry about the out of sink problem, honestly it is not a problem
its happening because the difficullty is high and is taking a while before a block is found. which makes the system thinks its out of sync. once a new block is created and detected by network it will be fine
its happening because the difficullty is high and is taking a while before a block is found. which makes the system thinks its out of sync. once a new block is created and detected by network it will be fine
Definitely make sure you're on 0.6.4 and give it some time. These things usually work themselves out.
There was a hard fork at 33000. If it isn't syncing with the new client try posting in the FTC thread
FFS we are at block 32928 several days away from block 33,000
There was a hard fork at 33000. If it isn't syncing with the new client try posting in the FTC thread
Its not yet to 33000 block and my client says out of sync and is connected to 8 peers. I have tried both the old wallet and the new wallet and neither will sync.
Is anyone else having this problem?
Is anyone else having this problem?
How can there be a problem in a decentralised P2P network?
It must be something specific to your computer or location.
Are you using version 0.6.3 or version 0.6.4?
If you're stuck at 33000, probably 0.6.3.
https://bitcointalksearch.org/topic/critical-update-feathercoin-064-hard-fork-at-block-33000-206010
Replace your files with that if so.
If you're stuck at 33000, probably 0.6.3.
https://bitcointalksearch.org/topic/critical-update-feathercoin-064-hard-fork-at-block-33000-206010
Replace your files with that if so.
Its not yet to 33000 block and my client says out of sync and is connected to 8 peers. I have tried both the old wallet and the new wallet and neither will sync.
Is anyone else having this problem?
Is anyone else having this problem?
Jump to: