Chia-Network / chia-blockchain

Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
Apache License 2.0
10.82k stars 2.03k forks source link

How to check if Plots are broken? #1963

Closed TschiAR closed 3 years ago

TschiAR commented 3 years ago

Hey there,

i now have about 26 TB Plots ( K33/K32). LAST XCH WIN: Confirmed at height 89558 12 days since then..NOTHING!!!

I ask myself now if my plots are borken?

Is there a posibility to check it somehow on windows system?

i need a step by step tutorial please...

Thanks a lot for your help.

eFishCent commented 3 years ago

You can use Powershell command line interface (CLI) and run chia plots check. Instructions can be found here: https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference

A bit of google learning is required to learn how to use Powershell 😄

Additional useful Chia Windows tips can be found here: https://github.com/Chia-Network/chia-blockchain/wiki/Windows-Tips-and-Tricks

flotti455 commented 3 years ago

Last time I needed to rely on checking for broken plots (~4 weeks ago, so older Chia version), chia plots check completely failed to report on plots that were broken - it happily reported "x of y proofs" found, despite the plots being indeed broken:

The broken plots were plots whose transfer to the farmer were interrupted due to a crashing plotter computer. Nevertheless, file size indicated a healthy k32 file size (Windows file copy shenanigans, I guess).

Only by checksumming the files to the original files, I could spot broken plots. A further check on byte-by-byte comparison showed nulled bytes filling up the k32 file size.

TschiAR commented 3 years ago

REALLY

I understand nothing... all the plotting and chia support for month for this? i need a step by step tutorial?

there has to be a more easy way to check that? i guess there are thousands of broken plots wasting space....

eFishCent commented 3 years ago

tldr; There is no 100% way to verify a plot, this is just the way math, probabilities and crypto work. chia plots check help, but can't guarantee.

The way plots are created and checked there is no way to 100% verify a plot without going through every possible permutation of blockchain challenge in the universe. If you suspect there is a possible problem with your plots due to bad hardware or copying errors, you should run chia plots check -n 1000 -g [filename] The higher number -n of random challenges will cover more parts of the file, but again, this is not 100%.

As long as there are some valid proofs in the plot, it will still work. It just won't work as well as a plot that has no errors in it.

@TschiAR - Chia is still an early technology. There isn't step by step tutorial for every situation. You're going to need to learn a bit on your own if you want to be an early adopter. The information link I provided is the best you can find at the moment.

FYI - I am a community contributor and not affiliated with Chia Networks.

flotti455 commented 3 years ago

There is no 100% way to verify a plot, this is just the way math, probabilities and crypto work.

Well, that's where engineering comes to the rescue: make plausibility checks such as "does the file follow the Chia plot file format definition" (magic values, expected metadata thoughout the whole plot, etc.).

With files so big, this is a low-hanging fruit for improvement - a plot with tens-of-gigabytes of garbage shall not happily pass the filter.

eFishCent commented 3 years ago

Well, that's where engineering comes to the rescue: make plausibility checks such as "does the file follow the Chia plot file format definition" (magic values, expected metadata thoughout the whole plot, etc.).

Would love you to solve it. Pull requests welcome :smile:

github-actions[bot] commented 3 years ago

This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.

github-actions[bot] commented 3 years ago

This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.