Failed to meet target


#1

Hello, I’m seeing in epoch_pow_cuckoo.log a lot of Failed to meet target:

2018-11-28 19:18:21.299 [debug] <0.29118.0>@aec_pow_cuckoo:parse_generation_result:448 42-cycle found
2018-11-28 19:18:21.299 [debug] <0.29118.0>@aec_pow_cuckoo:parse_generation_result:448 334-cycle found
2018-11-28 19:18:21.301 [debug] <0.29118.0>@aec_pow_cuckoo:parse_generation_result:448 findcycles edges 66855 time 158 ms total 1188 ms
2018-11-28 19:18:21.301 [debug] <0.29118.0>@aec_pow_cuckoo:parse_generation_result:444 Failed to meet target (521440014)
2018-11-28 19:18:21.301 [debug] <0.29118.0>@aec_pow_cuckoo:parse_generation_result:448 Verified with cyclehash 52bbe10047831fe…
2018-11-28 19:18:21.301 [debug] <0.29118.0>@aec_pow_cuckoo:parse_generation_result:448 1 total solutions
2018-11-28 19:18:21.362 [debug] <0.29118.0>@aec_pow_cuckoo:generate_int:155 No cuckoo solution found

Is it normal? How to check if mining goes well?


#2

I know not all cuckoo have a solution. But this should not be that often.


#3

It isn’t often. Almost all “0 total solutions”, but those which are “1 total solutions” are with “Failed to meet target” and " No cuckoo solution found" after that


#4

Target is meant to be the difficulty target. if you meet the target you found a block. :slight_smile: There are a lot of peers so it may not be as easy to hit the dynamic target


#5

Yes, that is entirely expected.

Cuckoo PoW is looking for a cycle in a graph. There is about one in 50 chance to find a cycle, so that is most of the runs will have 0, some will have 1. Then, once a solution/cycle is found you have to check if the solution is good enough. Currently the difficulty is at a level where one in 2500 solutions is accepted - thus you expect to see “Failed to meet target” most of the times you find a solution :wink: