chia-plotter VS chiapos

The original Madmax plotter supports both K33 and K34, https://github.com/madMAx43v3r/chia-plotter

I didn’t use madmax for like 8 months so I don’t remember, but checkout the default number here https://github.com/madMAx43v3r/chia-plotter The thread number is depending on how many thread your cpu got. I think the more thread is better. Try to put thread = 36 and buckets = 256

I would suggest canceling and plotting with the Chia POS plotter. For testing, the Chia POS plotter should be fast enough. The madMAx plotter is generally faster but it has had issues plotting from the Chia Network client in the past. If you want to use the madMAx plotter, I would suggest using the standalone version directly from madMAx's github (which has a link to the github that does windows compiles in the install directions).

git clone https://github.com/madMAx43v3r/chia-plotter.git

No need to reverse engineer anything. It's explained in all the detail you need in the Chia Proof of Space Construction document. It's implemented in chiapos though I find madmax's implementation of the plotter to be easier to read: https://github.com/madMAx43v3r/chia-plotter/tree/master/include/chia

The article you mentioned said that all the questions about the madmax plotter has to updated on its official GitHub repo, https://github.com/madMAx43v3r/chia-plotter, so I made a copy of the same complained and updated it onto the official madmax plotter repo (and the link was given by the official chia repo).

Yes, see https://github.com/madMAx43v3r/chia-plotter for plotting with a ramdisk and https://github.com/ericaltendorf/plotman to automate everything.

The OP can try using the non-packaged version https://github.com/madMAx43v3r/chia-plotter

You can get around this by using the standalone version of madmax or setting your temp directory as your final directory and using a script to monitor and move .plot files to your final directory.

You can install madmax directly (or use the compiled windows binary). Disclaimer: neither are officially endorsed but I've used them with no issues.

No need to reverse engineer anything. It's explained in all the detail you need in the Chia Proof of Space Construction document. It's implemented in chiapos though I find madmax's implementation of the plotter to be easier to read: https://github.com/madMAx43v3r/chia-plotter/tree/master/include/chia

If true, my assumption is they are implementing a Hellman attack on Table 1. Chia already describes the process here: https://github.com/Chia-Network/proofofspace/blob/master/proof_of_space.md#Hellman-Attacks and gives example code here: https://github.com/Chia-Network/chiapos/tree/main/hellman_example

I'm trying to farm plots created with different keys on a different machine. I know that I could add the plotter machine's keys to the farming machine and there is no official way to edit plots and change keys, but I'm interested in hacking things and looking at plotter_disk.hpp of chiapos, this is how the header (first few bytes) of a plot file looks like:

git clone https://github.com/Chia-Network/chiapos.git cd chiapos && mkdir build && cd build && cmake .. && make -j8 ./ProofOfSpace check -f plot-k32-???.plot \[num\_iterations\]

Is this the branch https://github.com/Chia-Network/chiapos/commit/369c9e773d9d43b00696771aad46cc5b4c54e785 ?

on my list above is just hard to do perfectly unless you specifically engineer the system that way. Thsi project probably manages to hit erasure blocks just right by virtue of the fact that it uses fairly large files, but it could probably be tuned to work better. You could maybe get partway there by changing the internal buffer size of the buffered disk in the plotter and recompiling/pip install-ing the plotter. In that case the buffer size would need to be the same size as the erasure block size of the SSD (or a multiple of it), but that is generally ~64-128MB these days. This approach would also cause somewhat higher memory consumption because the internal buffer size is for each bucket in each sort manager that is being actively written to, so more buckets with a larger buffer -> more RAM use (this is outside the memory limit you set on the command line).

By the time you get to NVME you are definitely CPU starved; give it more buckets and leave RAM at 3390. I dont think you can go past 512 without applying https://github.com/Chia-Network/chiapos/pull/202

The changes from https://github.com/Chia-Network/chiapos/commits/main commit cleanly into combined with the exception of the std::cout << "Using optimized chiapos"; bits which can be manually fixed, just FYI.

Sure you're not thinking of the P1 speed up from #208?