Today some clients on the Feathercoin blockchain stopped synchronizing.
The team has worked on the problem and released version 0.18.2 of feathercoin-core and gui, which contains a fast fix for the problem.
If you compile the code yourself, get the latest code from “https://github.com/FeatherCoin/Feathercoin/releases” as soon as possible.
If you use a precompiled binary/package for windows download the latest version from “https://github.com/FeatherCoin/Feathercoin/releases”
If you use Linux installation packages, run the OS specific update process for the feathercoin package and if that fails get the latest package from “https://software.opensuse.org/package/feathercoin”. Select ‘community packages’ for your distribution and check that he version displayed is 0.18.2
A detailed description how to install /update the software can be found here at the Feathercoin forum
It has turned out, that the Feathercoin P2Pool nodes are misbehaving due to a flaw in the Feathercoin core software.
An immediate update to Feathercoin v0.16.3 for all P2Pool nodes is required.
All other nodes should use v0.18.x versions of Feathercoin core!
Details of the upgrade process are here
Spam (unsolicited advertising): Spam will be deleted and the account posting it will likely be banned. You are allowed to have links to personal sites in your signature and in your profile, and may post them in threads on occasion (just not often, please) as long as the content of the site linked does not include material that violates this code of conduct and if you are not posting any other form of advertising.
Even when implemenrting a POW/POS solution as described, we still need a POW algorithm. There are two problems that together cause long gaps between blocks.
the difficulty is high, but the hash rate is low, due to a large pool (e.g. nicehash) withdraws it’s hash power.
currently there is no way to announce a new and lower difficulty before the next block is found, what takes a long time due to 1)
POW/POS mixture as described mitigates 2) while a good pow algorithm hopefully mitigates 1)
The short or very short time to block caused by the increase of hash rate has no problem like 2) and a much smaller probelm like 1).
as the blocks are found very fast the pow algorithm can adjust and announce new difficulties very fast.
What also needs to be remembered, is, that a time frame with long or very long time 2 block is required leverage the overall time 2 block. Without time 2 block rates > 1 minute the long average of all blocks generated would get smaller and smaller for every peak in hash rate causing an overproduction of coins.
mhh, I’m using the 0.17.0/0.17.1 version of the client and my original wallet is from 2014.
I didn’t have the problems you faced and all upgrades worked well.
As far as I know you need a clean wallet to enable hd key generatation, but you can dump your private keys to the console, copy/paste the keys to a safe place, delete the wallet.dat file and start the client. It then have hd keys enabled and generate an hd key for you. As soon as that is done you can add your private keys from the console and rescan the blockchain to get your coins.
Another possible solution:
when no new blocks are seen for a given time frame, the daemons themself generate one special block at the configured lowest difficulty.
Characteristics of the block:
no coins generated
no transactions are contained
That way a new difficulty can be calculated /announced after the hash rate drops dramatically and the time to block can be limited without breaking the protocol.
For sure there are complications in this solution, that need to be addressed.
This is a high level idea only