@T4rQu1N honnestly, I don’t know

Hello Pete,
‘Not verified’ means, that the elextrum client has not yet received information about the transaction from the elextrum server.
I assume, you are doing a full syc. Please do the follwing

check the current status of the icon at the bottom right of the application
* green means syncronized
* red means not syncronized and no server connection
* two arrows mean synchronizing

click on that icon and you will get details of the network status. You should see 3 or 4 servers, depending if your system supports ipv6 or not. The serverlist also shows he acrual block height easch server has seen. In the upper part of the information window you can see the block height of your client. It should be the same height as seen in the server list , or it should be increasing.

If there is a difference and your client’s count is not increasing, please close the client, wait a couple of minutes (3-5) and start the client again. The clients count should be increasing now.
You may have to repeat that several times.

Please provide your acrual cloent count, as the problem occurs in the ‘old’ part of the blockchain mainly.

@j_scheibel there was a tweet relayed on feathercoin account about that. Then i looked for kind of proof through google.

Hello, I’ll ask them to add it

@Bushstar

Updated list of outdated and unsupported PPA in the first post.

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.

Sounds easy :smile:

Great !!!

@cryptofan said in Prove him wrong !!!!!:

As I understood from the comments to this link, it is not worth watching it.

You are so right!!

Just visited the website, it works correctly. Sometimes there can be technical issues, and temporarily the site can be closed.

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.