chia-plotter VS bls-signatures

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.

$ git submodule update --init Submodule 'lib/BLAKE3' (https://github.com/BLAKE3-team/BLAKE3.git) registered for path 'lib/BLAKE3' Submodule 'lib/bls-signatures' (https://github.com/madMAx43v3r/bls-signatures.git) registered for path 'lib/bls-signatures' Submodule 'lib/libbech32' (https://github.com/dcdpr/libbech32.git) registered for path 'lib/libbech32' Cloning into '/home/plotter/chia-plotter/lib/BLAKE3'... Cloning into '/home/plotter/chia-plotter/lib/bls-signatures'... Cloning into '/home/plotter/chia-plotter/lib/libbech32'... Submodule path 'lib/BLAKE3': checked out '037de38bfec4e813ab6189a50cb7c4cbae47268a' Submodule path 'lib/bls-signatures': checked out 'd9e42922e4a21fe8fc50733b93c16f582022621f' Submodule path 'lib/libbech32': checked out '954b14fe81602dde0cf5cb6d45208403160fb76c'

Enter the directory and execute some necessary commands to install requirements and compile the tool: $ git submodule update --init Submodule 'lib/BLAKE3' (https://github.com/BLAKE3-team/BLAKE3.git) registered for path 'lib/BLAKE3' Submodule 'lib/bls-signatures' (https://github.com/madMAx43v3r/bls-signatures.git) registered for path 'lib/bls-signatures' Submodule 'lib/libbech32' (https://github.com/dcdpr/libbech32.git) registered for path 'lib/libbech32' Cloning into '/home/plotter/chia-plotter/lib/BLAKE3'... Cloning into '/home/plotter/chia-plotter/lib/bls-signatures'... Cloning into '/home/plotter/chia-plotter/lib/libbech32'... Submodule path 'lib/BLAKE3': checked out '037de38bfec4e813ab6189a50cb7c4cbae47268a' Submodule path 'lib/bls-signatures': checked out 'd9e42922e4a21fe8fc50733b93c16f582022621f' Submodule path 'lib/libbech32': checked out '954b14fe81602dde0cf5cb6d45208403160fb76c' $ ./make_devel.sh This command will produce a lot of output while compiling. In the end, you should get a message indicating the compile was successful: [...] [ 98%] Built target relic_s [ 98%] Built target gmock_main [ 98%] Built target UnitTests_bech32 [ 99%] Built target bls [100%] Built target chia_plot Try to call the program and get the usage help information: $ ./build/chia_plot --help If you can see the following line in the output, you have successfully built the chia-plotter version compatible with pool plots: -c, --contract arg Pool Contract Address (64 chars) Getting your keys sorted and jumping in the pool With the binary in place, it is time to check for the data required to create plots that fit your chia keys. To get those keys, execute the following commands: $ chia plotnft create -u https://farm.pool.garden -s pool It can take a little while until the transaction is confirmed. Once it is, execute: $ chia plotnft show Find the P2 singletom address (pool contract address) and save it for later - it should look something like this: P2 singleton address (pool contract address for plotting): xch1es7mmxmgxkv67q69m8j9p5akxk4zhv7h45hxvp*****k4q7527tqu6xhhc (64 characters) The other required key is the "Farmer public key". Execute the following statement to get it: $ chia keys show Note the Farmer public key and save it for later. Ignore the "Pool public key"! It is not the droid you're looking for.