I have 15 k32 plots with expected time to win: 1 year (why does it keep going up?!) so maybe this shouldn’t come as a surprise but I thought that each plot was supposed to find proofs and then the best proof was supposed to create the new block. Is something wrong with my farming setup if it’s always ‘Found 0 proofs’? Does my wallet need to finish syncing before I can farm successfully (it seems like syncing the wallet is going to take forever… currently only at height 10480)? I thought a local wallet instance wasn’t needed for farming.
0 proofs. Time: 0.47498 s. Total 15 plots
2021-05-07T04:04:22.161 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming de9acddd9f... Found 0 proofs. Time: 0.22937 s. Total 15 plots
2021-05-07T04:08:59.670 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming de9acddd9f... Found 0 proofs. Time: 3.09855 s. Total 15 plots
2021-05-07T04:12:25.460 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 2f1dd57f14... Found 0 proofs. Time: 0.32372 s. Total 15 plots
2021-05-07T04:47:03.589 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 7f7f0f32d2... Found 0 proofs. Time: 1.34546 s. Total 15 plots
2021-05-07T04:49:23.797 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 7f7f0f32d2... Found 0 proofs. Time: 1.41917 s. Total 15 plots
2021-05-07T04:49:32.712 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 1.76537 s. Total 15 plots
2021-05-07T04:50:08.995 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 2.52196 s. Total 15 plots
2021-05-07T04:50:48.457 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 0.73629 s. Total 15 plots
2021-05-07T04:51:13.906 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 0.29567 s. Total 15 plots
2021-05-07T04:52:45.337 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 1.49542 s. Total 15 plots
2021-05-07T04:58:00.017 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming db09dea5e1... Found 0 proofs. Time: 1.87423 s. Total 15 plots
2021-05-07T05:02:41.172 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 0809ab8629... Found 0 proofs. Time: 1.76905 s. Total 15 plots
2021-05-07T05:32:19.456 harvester chia.harvester.harvester: INFO 2 plots were eligible for farming 41258fb54b... Found 0 proofs. Time: 4.44604 s. Total 15 plots
2021-05-07T05:36:22.208 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 41258fb54b... Found 0 proofs. Time: 1.73768 s. Total 15 plots
2021-05-07T05:48:49.457 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming d4bf7278d4... Found 0 proofs. Time: 2.23398 s. Total 15 plots
2021-05-07T05:50:10.460 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 23e674d83d... Found 0 proofs. Time: 7.70011 s. Total 15 plots
2021-05-07T05:52:08.960 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 23e674d83d... Found 0 proofs. Time: 2.96046 s. Total 15 plots
2021-05-07T06:00:42.458 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 71b19597e0... Found 0 proofs. Time: 4.19589 s. Total 15 plots
2021-05-07T06:07:06.707 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 71b19597e0... Found 0 proofs. Time: 2.20445 s. Total 15 plots
2021-05-07T06:09:29.983 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming fbd92a643e... Found 0 proofs. Time: 3.00030 s. Total 15 plots
2021-05-07T06:13:11.957 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming fbd92a643e... Found 0 proofs. Time: 2.21831 s. Total 15 plots
2021-05-07T06:20:54.209 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming af8bf0beb4... Found 0 proofs. Time: 2.50202 s. Total 15 plots
2021-05-07T06:21:55.461 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming af8bf0beb4... Found 0 proofs. Time: 1.21447 s. Total 15 plots
2021-05-07T06:40:10.707 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4fdc9735b5... Found 0 proofs. Time: 3.71568 s. Total 15 plots
2021-05-07T06:40:16.737 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming 4fdc9735b5... Found 0 proofs. Time: 2.25604 s. Total 15 plots
Your log looks fine, assuming you are only showing challenges where one plot passed the filter. Your Time: parameter is a bit slow, but as long as it’s under 10 seconds it’ll work. Just make sure it doesn’t go higher.
If you find a proof, you’ll most likely win a 2XCH reward. “Found 0 proofs.” is normal, even for people with over 10,000 plots. It will only show “Found 1 proof” if you find a proof that is smaller than a threshold based on the difficulty level, which is growing every day as the netspace grows.
The wallet doesn’t need to be synced, but the node does.
Expected time to win keeps going up because other people are plotting too and the estimate doesn’t (and can’t) take that into account. It’s also not a progress indicator - you could win in 5 minutes or 5 years from now or never - it’s just a statistical average.
If there aren’t any, you probably aren’t actually farming. The most likely reason is that the full node is not finished syncing. If you are using the CLI, try running chia farm summary, which should confirm whether your farmer is active. I assume that this information is easy to find in the GUI but I don’t know where.
The peer disconnect messages are not normal. Is this a plain default setup using the default config file? If so, my first diagnostic step would be to try increasing the log level. I’m not sure what the next level after info is but debug or trace would be my first guesses. Maybe someone else will know. If you are not running the default config (maybe you have a distributed system) I’d double check the configuration first.