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
Today electrumx-2.feathercoin.com has been moved to production.
The server is designed to serve older electrumx-clients ( < 184.108.40.206) so the current connection provblems for older clients are solved.
It also supports newer clients.
for client version >= 220.127.116.11
for client version < 18.104.22.168
Other server showing up in the clients gui are currently not operated b the Feathercoin team and may or may not work
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