Swar's Chia Plot Manager
https://www.chia.net/
A plot manager for Chia plotting:Development Version: v0.0.1
This is a cross-platform Chia Plot Manager that will work on the major operating systems. This is not a plotter. The purpose of this library is to manage your plotting and kick off new plots with the settings that you configure. Everyone's system is unique so customization is an important feature that was engraved into this library.
This library is simple, easy-to-use, and reliable to keep the plots generating.
This library has been tested for Windows and Linux.
Features
- Stagger your plots so that your computer resources can avoid high peaks.
- Allow for a list of destination directories.
- Utilize temporary space to its maximum potential by starting a new plot early.
- Run a maximum number of plots concurrently to avoid bottlenecks or limit resource hogging.
- More in-depth active plot screen.
Sponsor / Support this Library
This library took a lot of time and effort in order to get it before you today. Consider sponsoring or supporting the library. This is not necessary but more a kind gestures.
- XCH Address: xch134evwwqkq50nnsmgehnnag4gc856ydc7ached3xxr6jdk7e8l4usdnw39t
- ETH Address: 0xf8F7BD24B94D75E54BFD9557fF6904DBE239322E
- BTC Address: 36gnjnHqkttcBiKjjAekoy68z6C3BJ9ekS
- Paypal: https://www.paypal.com/biz/fund?id=XGVS7J69KYBTY
Installation
The installation of this library is straightforward. I have attached detailed instructions below that should help you get started.
- Download and Install Python 3.7 or higher: https://www.python.org/
git clone
this repo or download it.- Open CommandPrompt / PowerShell / Terminal and
cd
into the main library folder.- Example:
cd C:\Users\Swar\Documents\Swar-Chia-Plot-Manager
- Example:
- OPTIONAL: Create a virtual environment for Python. This is recommended if you use Python for other things.
- Create a new python environment:
python -m venv venv
- The second
venv
can be renamed to whatever you want. I prefervenv
because it's a standard.
- The second
- Activate the virtual environment. This must be done every single time you open a new window.
- Example Windows:
venv\Scripts\activate
- Example Linux:
. ./venv/bin/activate
orsource ./venv/bin/activate
- Example Windows:
- Confirm that it has activated by seeing the
(venv)
prefix. The prefix will change depending on what you named it.
- Create a new python environment:
- Install the required modules:
pip install -r requirements.txt
- Copy
config.yaml.default
and name it asconfig.yaml
in the same directory. - Edit and set up the config.yaml to your own personal settings. There is more help on this below.
- You will need to add the
chia_location
as well! This should point to your chia executable.
- You will need to add the
- Run the Manager:
python manager.py start
- This will start a process in the background that will manage plots based on your inputted settings.
- Run the View:
python manager.py view
- This will loop through a view screen with details about active plots.
Configuration
The configuration of this library is unique to every end-user. The config.yaml
file is where the configuration will live.
This plot manager works based on the idea of jobs. Each job will have its own settings that you can configure and customize. No two drives are unique so this will provide flexibility for your own constraints and requirements.
chia_location
This is a single variable that should contain the location of your chia executable file. This is the blockchain executable.
- Windows Example:
C:\Users\<USERNAME>\AppData\Local\chia-blockchain\app-1.1.2\resources\app.asar.unpacked\daemon\chia.exe
- Linux Example:
/usr/lib/chia-blockchain/resources/app.asar.unpacked/daemon/chia
- Another Linux Example:
/home/swar/chia-blockchain/venv/bin/chia
manager
These are the config settings that will only be used by the plot manager.
check_interval
- The number of seconds to wait before checking to see if a new job should start.log_level
- Keep this on ERROR to only record when there are errors. Change this to INFO in order to see more detailed logging. Warning: INFO will write a lot of information.
log
folder_path
- This is the folder where your log files for plots will be saved.
view
These are the settings that will be used by the view.
check_interval
- The number of seconds to wait before updating the view.datetime_format
- The datetime format that you want displayed in the view. See here for formatting: https://docs.python.org/3/library/datetime.html#strftime-and-strptime-format-codesinclude_seconds_for_phase
- This dictates whether seconds are included in the phase times.include_drive_info
- This dictates whether the drive information will be showed.include_cpu
- This dictates whether the CPU information will be showed.include_ram
- This dictates whether the RAM information will be showed.include_plot_stats
- This dictates whether the plot stats will be showed.
notifications
These are different settings in order to send notifications when the plot manager starts and when a plot has been completed.
progress
phase_line_end
- These are the settings that will be used to dictate when a phase ends in the progress bar. It is supposed to reflect the line at which the phase will end so the progress calculations can use that information with the existing log file to calculate a progress percent.phase_weight
- These are the weight to assign to each phase in the progress calculations. Typically, Phase 1 and 3 are the longest phases so they will hold more weight than the others.
global
max_concurrent
- The maximum number of plots that your system can run. The manager will not kick off more than this number of plots total over time.
job
These are the settings that will be used by each job. Please note you can have multiple jobs and each job should be in YAML format in order for it to be interpreted correctly. Almost all the values here will be passed into the Chia executable file.
Check for more tails on the Chia CLI here: https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference
name
- This is the name that you want to give to the job.max_plots
- This is the maximum number of jobs to make in one run of the manager. Any restarts to manager will reset this variable. It is only here to help with short term plotting.- [OPTIONAL]
farmer_public_key
- Your farmer public key. If none is provided, it will not pass in this variable to the chia executable which results in your default keys being used. This is only needed if you have chia set up on a machine that does not have your credentials. - [OPTIONAL]
pool_public_key
- Your pool public key. Same information as the above. temporary_directory
- Only a single directory should be passed into here. This is where the plotting will take place.- [OPTIONAL]
temporary2_directory
- Can be a single value or a list of values. This is an optional parameter to use in case you want to use the temporary2 directory functionality of Chia plotting. destination_directory
- Can be a single value or a list of values. This is the final directory where the plot will be transferred once it is completed. If you provide a list, it will cycle through each drive one by one.size
- This refers to the k size of the plot. You would type in something like 32, 33, 34, 35... in here.bitfield
- This refers to whether you want to use bitfield or not in your plotting. Typically, you want to keep this as true.threads
- This is the number of threads that will be assigned to the plotter. Only phase 1 uses more than 1 thread.buckets
- The number of buckets to use. The default provided by Chia is 128.memory_buffer
- The amount of memory you want to allocate to the process.max_concurrent
- The maximum number of plots to have for this job at any given time.max_concurrent_with_start_early
- The maximum number of plots to have for this job at any given time including phases that started early.stagger_minutes
- The amount of minutes to wait before the next job can get kicked off. You can even set this to zero if you want your plots to get kicked off immediately when the concurrent limits allow for it.max_for_phase_1
- The maximum number of plots on phase 1 for this job.concurrency_start_early_phase
- The phase in which you want to start a plot early. It is recommended to use 4 for this field.concurrency_start_early_phase_delay
- The maximum number of seconds to wait before a new plot gets kicked off when the start early phase has been detected.temporary2_destination_sync
- This field will always submit the destination directory as the temporary2 directory. These two directories will be in sync so that they will always be submitted as the same value.