Chia plotting service FAQ
Simply open the Keys page in Chia GUI and click the «eye» icon.
On Chia version before 1.2.0
Linux and MacOS
To find your farmer and pool keys on Linux or MacOS you can use the following command:
chia keys show | grep ‘Pool\|Farmer’
If you use the GUI on MacOS try:
cd /Applications/Chia.app/Contents/Resources/app.asar.unpacked/daemon ./chia keys show
Windows
- Open the Command Prompt by going to Start and typing cmd and pressing enter.
- Paste the following command in the line
%APPDATA%/..Local/chia-blockchain/app-1.1.6/resources/app.asar.unpacked/daemon/chia.exe keys show
You will find your keys in the output. If you got an error you might be on another version of chia application. To figure out which version you need type
cd %APPDATA%/. /Local/chia-blockchain/
followed by dir
Hopefully you will see a version number that looks like app-1.1.5 or app-1.1.6 etc. Replace the version number in the command on line 2 and try it again.
If nothing works send us a message at contact@plotting.cloud and we will look over it together.
First you need to join a Chia pool (see the next question).
Using Chia GUI
- Open the Pool page
- Hover over the ? icon next to the plot NFT name
- Click the «Copy to Clipboard» icon
Using the command line
- Run: chia plotnft show
If everything is ok, you should get a pool contract address which starts with xch .
The amount of Chia that a farmer can earn is proportional to the percentage of the network that they own. For example, a farmer that owns 0.25% of the total network space can expect to win 0.25% of the blocks. As the Chia network™ is growing daily, it becomes incrementally more difficult to win Chia (XCH) coins as a solo farmer. When the network space reaches 1 EB a farmer with 10 TB of space would own 0.00001% of the network and can expect to wait over 20 days to win a single block. If they are unlucky they could easily be waiting several months. Somebody with less than 10 TB of space could be waiting a lot longer.
You can reduce the waiting period for a possible reward and increase your chances by joining a pool. We recommend you to join Chiahub pool. Since the entire space of the pool determines the chances of winning, you start earning a small amount of Chia much quicker compared to participating as an individual.
Pools require new, special plots. All previously created plots cannot be used for pooling – only for single farming. These new so-called “portable plots” will enable owners to move the plots from one pool to another. If you are looking to buy portable plots, feel free to place your order on our website and receive portable plots as soon as we generate them.
How To Plot
This page will give a basic overview of how to obtain these values. For a detailed description, see the Beginner's Guide to Farming.
If you already have a wallet with a plot NFT, feel free to skip to the section for CLI Plotting or GUI Plotting.
Public Keys
If you do not have a key/wallet, run the following command:
You will be prompted to add a human-readable name to your wallet. This name is only used locally (it is not stored on the blockchain). If you do not enter a name, a number called a fingerprint will be used instead. It is possible to change this name later.
In order to view your farmer public key, run chia keys show , optionally including the -f <fingerprint> flag to show only the info for the key you just generated:
The result will include the farmer public key and the pool public key. Make note of them for the subsequent steps. For example:
If you do not have a key, you will need to create one:
You will be presented with a list of twenty-four words. This is your wallet's recovery phrase. These words are all that are needed to recover your wallet on a new computer. Write them down and store them in a safe place. The order of the words is important.
You can also choose a custom name for your wallet. Click NEXT when you are finished.
If someone obtains a copy of these words, they can steal your entire wallet, including all of its funds. Be sure to store your recovery phrase in a safe place.
You will be taken to your new wallet. In order to obtain your farmer public key, you will need to log out of the wallet. Click the icon next to the bell icon.
Click the three dots in the lower-right corner of your wallet, then click Details .
Among other information, your farmer public key and pool public key will be shown. If you plan to plot from the CLI, make note of these keys. If you will stick with the GUI for plotting, these keys will be obtained automatically later.
Pool Contract Address
In order to obtain a pool contract address, you will need to create a Plot NFT.
First, you will need to decide whether to join a pool. For this example, we will use -s pool to join a pool. If you want to solo farm, use -s local instead. (Later, you can change pools, using the plot NFT you are about to create.)
If you choose to join a pool, you will need to add the URL by adding the -u flag. For this example, we will join OpenChia, but there are many great pools to choose from. For a list of reputable pools, see Chialinks.com. (Chia Network, Inc. does not run a pool, and is not affiliated with OpenChia or Chialinks).
Finally, you have the option of adding a blockchain fee with the -m flag. We will add a one-mojo fee for this example, which typically is sufficient to complete your transaction within a few minutes.
In order to run this command, you will need to have one mojo in your wallet for the plot NFT, and one mojo for the blockchain fee.
madMAx43v3r быстрый плоттер для майнинга Chia Coin. Настройка. Батник.
Майнинг
С тех пор как майнинг Chia Coin стал популярным, люди ищут всё более оптимизированные и быстрые способы создания плотов. Кто-то засеивает жёсткие диски параллельно кучей плотов, кто-то формирует по одному участку, при этом используя интерфейс официальной программы Chia Blockchain или прописывает конфиги в PowerShell. Существуют также сторонние плоттеры, одни ничем непримечательны, а другие позволяют реально задействовать все ресурсы компьютера правильным образом, благодаря чему, можно наблюдать прирост скорости процесса создания плотов, что экономит время и косвенно сокращает сроки окупаемости вашего железа. В этой статье речь пойдёт об одном таком новом плоттере для Chia Coin от разработчика madMAx43v3r.
Изначально данный софт можно было использовать только на Linux, но другой разработчик перекомпилировал исходный код под Windows.
Распакуйте файлы из архива в любое место на жёстком диске.
Настройка быстрого плоттера от madMAx43v3r.
Итак, приступаем к настройке.
Первое, что необходимо сделать это узнать два своих ключа от Чиа:
- Pool public key
- Farmer public key
Для этого нужно перейти в папку с исполняемыми файлами Chia Blockchain по следующему адресу:
Потом с зажатой клавишей Shift кликните правой кнопкой мыши на пустое место в этой папке, в появившемся контекстном меню выберите пункт “Открыть окно PowerShell здесь”.
Откроется синее окно PowerShell и в нём вам нужно будет ввести команду:
и нажать Enter.
Если не сработает, то введите просто “chia keys show” без “.\” в начале.
Скопируйте все ключи в текстовый файл, чтобы в будущем иметь быстрый доступ к ним.
Теперь нужно открыть в текстовом редакторе файл plot.cmd в папке с плоттером.
Вставляем свои ключи после -p и -f
Должно выглядеть так:
Если разглядите на скриншоте =)
Теперь разберём как работает плоттер. Программа способна засеивать всего лишь один плот, но делает это максимально быстро. Нет возможности засеивать параллельно несколько плотов, да и смысла в этом нет. Вы не заметите разницы с обычным способом.
Для процесса засеивания используется временная папка на быстром накопителе, как правило это NVME SSD, что может похвастаться своими показателями скорости чтения и записи. Выявлено, что в последней фазе формирования участка на крайние 110 Gb приходится 75% операций записи. Данная нагрузка очень вредна для Nand памяти в SSD, и для того чтобы продлить срок службы накопителя, разработчик madMAx43v3r советует использовать вторую временную папку, размещённую либо в RAM-диске (если есть возможность), либо на SAS-жёстком диске и SAS-SSD (серверные решения, аппнутые SATA так сказать).
На первой же временной папке требуется 220 Gb свободного места, и нагрузка при формировании участка будет всего 25% всех операций записи данных.
Параметры для батника Chia.
- -n — Количество плотов для создания (стандартно = 1, -1 = бесконечно)
- -r — Количество потоков процессора (стандартно = 4)
- -u — Количество корзин (меняйте на 128)
- -t — Путь к временной папке 1, нужно
Плоттер со временем сам подберёт максимальное количество потоков процессора, но можете установить сами.
Рассчитайте сколько плотов может поместиться на вашем жёстком диске и введите нужное количество в текст батника. Уточню, если у вас жёсткий диск объёмом 1 Gb, то на нём может поместиться около девяти плотов. Значит вписываем в конфиг “-n 9“. Если вы укажете “-n -1“, то плоттер будет создавать плоты на жёстком диске, пока не закончится свободное место, и только тогда он остановится.
Количество корзин для временных файлов устанавливайте 128 если не используйте RAM-диск, а если у вас очень много оперативной памяти, и вы создали там папку, то меняйте значение на “-u 256” в конфиге.
Пути для папок прописываются примерно так:
Где -t это путь к первой временной папке, а -2 путь ко второй (которая должна быть либо на втором NVMe SSD, либо на SAS HDD или SAS SSD, либо в Оперативной памяти.
Приведу пример батника под свою систему на intel 8700k 16 Gb ОЗУ с двумя SSD и HDD для майнинга на 2 Tb.
Без моих ключей соответственно, вы можете дописать в конфиг свои.
Результаты скорости плоттинга.
madMAx43v3r опубликовал тайминги всего процесса формирования плотов на своей конфигурации dual Xeon (R) E5-2650v2@2.60GHz, R720, 256GB RAM, 3x800GB SATA SSD RAID0, using a 110G tmpfs for <tmpdir2> .
Можете сравнить со своими.
Даже с использованием двух NVMe SSD можно добиться двукратной прибавки к скорости формирования плотов для майнинга криптовалюты Chia Coin, но всё будет упираться в процессор. Идеально, конечно же использовать серверную оперативную память и материнские платы под два многопоточных процессора.
Если статья оказалась полезной для Вас, угостите автора чашечкой кофе, чтоб были силы на новый контент =)
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
CLI Commands Reference
Clone this wiki locally
This page should provide additional high-level documentation and explanation beyond just chia -h .
This is not meant to be comprehensive, because often the -h (help) text is clear enough. We recommend fully investigating with the -h switch before looking elsewhere.
If want to know what a command’s options are, append -h at the end to see options and explanations.
- chia -h
- chia plots -h
- chia plots check -h
- chia plotters madmax -h
- chia start -h
As with the rest of this project, this doc is a work-in-progress. Feel free to browse the source code or the Chia Proof of Space Construction Document for more insight in the meantime.
Locate the chia binary executable
If you installed Chia.app in your /Applications directory, you can find the chia binary at /Applications/Chia.app/Contents/Resources/app.asar.unpacked/daemon/chia .
Do a sanity check in Terminal.app with
You can use that if you augment your PATH with
and then chia -h should work.
Windows
There is more than one chia.exe binary; the GUI is Chia.exe (two of these!) and the CLI is chia.exe . They are found in different places. Note the big C versus the little c.
The CLI one is the one referred to in this document, and for version 1.1.3 it can be found at
This has changed location to
Command: chia init
First, init checks for old versions of chia installed in your
If so, init migrates these old files to the new version:
- config (including old SSL files)
- db
- wallet
- Using config.yaml, updates wallet keys and ensures coinbase rewards go to the right wallet puzzlehash.
If no old version exists, init :
- Creates a default chia configuration
- Initializes a new SSL key and cert (for secure communication with the GUI)
start
Command: chia start
- Service node will start only the full node.
- Service farmer will start the farmer, harvester, a full node, and the wallet.
- positional arguments:
Flags
-r, —restart : Restart of running processes
plotters
In 1.2.11 the option to use different plotters was introduced. The plotters supported include Bladebit, madMAx, and the original reference chiapos plotter. Each plotter has slightly different hardware requirements and may need slightly different options specified. Learn more about the alternative plotters here: Alternative Plotters
madmax
For details on settings and usage of madMAx please refer to the original madMAx Github repository, or run the help command chia plotters madmax -h .
bladebit
chia plotters bladebit -h
plots
create
Command: chia plots create [add flags and parameters]
Flags
-k [size]: Define the size of the plot(s). For a list of k-sizes and creation times on various systems check out: k-Sizes
-n [number of plots]: The number of plots that will be made, in sequence. Once a plot is finished, it will be moved to the final location -d , before starting the next plot in the sequence.
-b [memory buffer size MiB]: Define memory/RAM usage. Default is 4608 (4.6 GiB). More RAM will marginally increase speed of plot creation. Please bear in mind that this is what is allocated to the plotting algorithm alone. Code, container, libraries etc. will require additional RAM from your system.
-f [farmer pk]: This is your «Farmer Public Key». Utilise this when you want to create plots on other machines for which you do not want to give full chia account access. To find your Chia Farmer Public Key use the following command: chia keys show
-p [pool pk]: This is your «Pool Public Key». Utilise this when you want to create plots on other machines for which you do not want to give full chia account access. To find your Chia Pool Public Key use the following command: chia keys show
-c [pool contract address]: This is your «Pool Contract Address». This replaces your Pool Public Key used previously in OG plots. This is used to point a plot to a plotNFT, which allows you to switch plots from local farming to pooling. To find your PlotNFT Contract Addres use the following command: chia plotnft show
-a [fingerprint]: This is the key Fingerprint used to select both the Farmer and Pool Public Keys to use. Utilize this when you want to select one key out of several in your keychain. To find your Chia Key Fingerprint use the following command: chia keys show
-t [tmp dir]: Define the temporary directory for plot creation. This is where Plotting Phase 1 (Forward Propagation) and Phase 2 (Backpropagation) both occur. The -t dir requires the largest working space: normally about 2.5 times the size of the final plot.
-2 [tmp dir 2]: Define a secondary temporary directory for plot creation. This is where Plotting Phase 3 (Compression) and Phase 4 (Checkpoints) occur. Depending on your OS, -2 might default to either -t or -d . Therefore, if either -t or -d are running low on space, it’s recommended to set -2 manually. The -2 dir requires an equal amount of working space as the final size of the plot.
-d [final dir]: Define the final location for plot(s). Of course, -d should have enough free space as the final size of the plot. This directory is automatically added to your
/.chia/VERSION/config/config.yaml file. You can use chia plots remove -d to remove a final directory from the configuration.
-r [number of threads]: 2 is usually optimal. Multithreading is only in phase 1 currently.
-u [number of buckets]: More buckets require less RAM but more random seeks to disk. With spinning disks you want less buckets and with NVMe more buckets. There is no significant benefit from using smaller buckets — just use 128.
-e [bitfield plotting]: Using the -e flag will disable the bitfield plotting algorithm, and revert back to the older b17 plotting style. After 1.0.4 it’s better to use bitfield for most cases (not using -e ). Before 1.0.4 (obsolete) using the -e flag (bitfield disabled) lowers memory requirement, but also writes about 12% more data during creation of the plot. For now, SSD temp space will likely plot faster with -e (bitfield back propagation disabled) and for slower spinning disks, i.e SATA 5400/7200 rpm, not using -e (bitfield enabled) is a better option.
-x [exclude final dir]: Skips adding [final dir] to harvester for farming.
Example Plotting Commands
Example below will create a k32 plot and use 4GB (note — not GiB) of memory.
chia plots create -k 32 -b 4000 -t /path/to/temporary/directory -d /path/to/final/directory
Example 2 below will create a k34 plot and use 8GB of memory, 2 threads and 64 buckets
chia plots create -k 34 -e -b 8000 -r 2 -u 64 -t /path/to/temporary/directory -d /path/to/final/directory
Example 3 below will create five k32 plots ( -n 5 ) one at a time using 4GB -b 4000 (note — not GiB) of memory and uses a secondary temp directory ( -2 /path/to/secondary/temp/directory ).
chia plots create -k 32 -b 4000 -n 5 -t /path/to/temporary/directory -2 /path/to/secondary/temp/directory -d /path/to/final/directory
Additional Plotting Notes
During plotting, Phase 1 (Forward Propagation) and Phase 3 (Compression) tend to take the most time. Therefore, to maximize plotting speed, -t and -2 should be on your fastest drives, and -d can be on a slow drive.
There are 4 major phases to plotting. Phase 1 of plotting can utilize multi-threading. Phases 2-3 do not. You can better optimize your plotting by using the -r flag in your command and setting it to greater than 2, e.g,. -r 2 . Above 4 threads there are diminishing returns. Many Chia users have determined it’s more efficient to plot in parallel, rather than series. You can do this by just having multiple plotting instances open but staggering when they start 30min or more.
It’s objectively faster to plot on SSD’s instead of HDD’s. However, SSD’s have significantly more limited lifespans, and early Chia testing has seemed to indicate that plotting on SSD’s wears them out pretty quickly. Therefore, many Chia users have decided it’s more «green» to plot in parallel on many HDD’s at once.
Plotting is designed to be as efficient as possible. However, to prevent grinding attacks, farmers should not be able to create a plot within the average block interval. That’s why the minimum k-size is k32 on mainnet.
plotnft
Using the CLI, you can perform the same operations as with the GUI. There is a new command, called chia plotnft . Type chia plotnft -h to see all the available sub-commands:
To create a Plot NFT, use chia plotnft create -u https://poolnamehere.com , entering the URL of the pool you want to use. To create a plot NFT in self-farming mode, do chia plotnft create -s local . To switch pools, you can use chia plotnft join , and to leave a pool (switch to self farming), use chia plotnft leave . The show command can be used to check your current points balance. CLI plotting with create_plots is the same as before, but the -p is replaced with -c , and the pool contract address from chia plotnft show should be used here.
check
Command: chia plots check -n [num checks] -l -g [substring]
First, this looks in all plot directories from your config.yaml. You can check those directories with chia plots show . This command will check whether plots are valid given the plot’s associated keys and your machine’s stored Chia keys, as well as test the plot with challenges to identify found plots vs. expected number of plots.
-g check only plots with directory or file name containing case-sensitive [substring]. If -g isn’t specified all plots in every plot directory in your config.yaml will be checked.
Examples for using -g
- Check plots within a long directory name like /mnt/chia/DriveA can use chia plots check -g DriveA
- Check only k33 plots can use chia plots check -g k33
- Check plots created on October 31, 2020 can use chia plots check -g 2020-10-31
-l allows you to find duplicate plots by ID. It checks all plot directories listed in config.yaml and lists out any plot filenames with the same filename ending; *-[64 char plot ID].plot . You should use -l -n 0 if you only want to check for duplicates.
-n represents the number of challenges given. If you don’t include an -n integer, the default is 30. For instance, if -n is 30, then 30 challenges will be given to each plot. The challenges count from 5 (minimum) to -n , and are not random.
Each plot will take each challenge and:
- Get the quality for the challenge (Is there a proof of space? You should expect 1 proof per challenge, but there may be 0 or more than 1.)
- Get the full proof(s) for the challenge if a proof was present
- Validate that the # of full proofs matches the # of expected quality proofs.
Finally, you’ll see a report the final true proofs vs. expected proofs.
Therefore, if -n is 20, you would expect 20 proofs, but your plot may have more or fewer.
Running the command with -n 10 or -n 20 is good for a very minor check, but won’t actually give you much information about if the plots are actually high-quality or not.
Consider using -n 30 to get a statistically better idea.
For more detail, you can read about the DiskProver commands in chiapos
What does the ratio of full proofs vs expected proofs mean?
- If the ratio is >1, your plot was relatively lucky for this run of challenges.
- If the ratio is <1, your plot was relatively unlucky.
- This shouldn’t really concern you unless your ratio is <0.70 # If so, do a more thorough chia plots check by increasing your -n
The plots check challenge is a static challenge. For example if you run a plots check 20 times, with 30 tries against the same file, it will produce the same result every time. So while you may see a plot ratio << 1 for a plot check with x number of tries, it does not mean that the plot itself is worthless. It just means that given these static challenges, the plot is producing however many proofs. As the number of tries ( -n ) increases, we would expect the ratio to not be << 1. Since Mainnet is live, and given that the blockchain has new challenges with every signage point — just because a plot is having a bad time with one specific challenge, does not mean it has the same results versus another challenge. «Number of plots» and «k-size» are much more influential factors at winning blocks than «proofs produced per challenge».
In theory, a plot with a ratio >> 1 would be more likely to win challenges on the blockchain. Likewise, a plot with a ratio << 1 would be less likely to win. However, in practice, this isn’t actually going to be noticeable. Therefore, don’t worry if your plot check ratios are less than 1, unless they’re significantly less than 1 for many -n .
upgrade
Command: chia db upgrade [add flags and parameters]
Flags
—input [PATH] : (optional) Specify a database input file. Must be a v1 database.
—output [PATH] : (optional) Specify a database output file. Can be any name, but must not already exist.
—no-update-config Don’t update the config file to point to your new database. When specifying a custom output file, the config will not be updated regardless.
Database upgrade notes
- This will upgrade your database from version 1 to version 2, which is around 45% smaller and slightly faster.
- The upgrade could take several hours to complete. Use at your own leisure.
- You do not need to stop your Chia node while performing the upgrade.
- The new database file will be written to the same folder as the original. The current size requirement (2nd quarter 2022) is around 55 GB. Note that the database is always growing, so the size requirement for the v2 database will have gone up by the time you are reading this — plan accordingly. After the version 2 file has been created, you can stop Chia and move/delete your version 1 file, which will free up enough space to move your version 2 file to the original folder. Finally, update the references in config.yaml to point to your version 2 file.
- After the upgrade has completed, run chia start farmer -r . This will restart your farmer, and begin using your new database. Note that it will have the same peak as version 1 at the time you initiated the upgrade. Your node will still need to run a short sync to fetch the remaining blocks that had gotten added while the upgrade was being performed.
- For more info, see our FAQ.
derive
Command: chia keys derive [OPTIONS] COMMAND [ARGS]
Flags
-f , —fingerprint [INTEGER] : The fingerprint of the key you want to use.
—mnemonic-seed-filename [TEXT] : The filename containing the mnemonic seed of the master key to derive from.
Notes on deriving keys
- This command will display or search for derived keys or wallet-addresses.
- This command requires either a fingerprint or a mnemonic seed file.
- The valid values for COMMAND are child-key , search , and wallet-address .
- See below for details and example commands.
child-key
Command: chia keys derive child-key [OPTIONS]
Flags
-t , —type [farmer|pool|wallet|local|backup|singleton|pool_auth] : Type of child key to derive.
-p , —derive-from-hd-path [TEXT] : Derive child keys rooted from a specific HD path. Indices ending in an ‘n’ indicate that non-observer derivation should used at that index.
Example HD path: m/12381n/8444n/2/-i , —index [INTEGER] : Index of the first child key to derive. (Index 0 is the first child key.)
-n , —count [INTEGER] : Number of child keys to derive, starting at index.
-d , —non-observer-derivation : Derive keys using non-observer derivation. [default: False]
-s , —show-private-keys : Display derived private keys. [default: False]
—show-hd-path : Show the HD path of the derived wallet addresses. [default: False]
Examples
Show the first singleton pubkey: chia keys derive -f <fingerprint> child-key -t singleton
Show a pair of public and private keys derived from a mixed observer/non-observer HD path using an imported key’s mnemonic seed: chia keys derive —mnemonic-seed-filename <(chia keys generate_and_print | sed -n 2p) child-key —derive-from-hd-path ‘m/12381n/8444n/2/’ —show-private-keys —show-hd-path
Generate a mnemonic seed and show the farmer pubkeys 10-14 derived from that seed: chia keys derive —mnemonic-seed-filename <(chia keys generate_and_print | sed -n 2p) child-key -i 10 -n 5 -t farmer
search
Command: chia keys derive search [OPTIONS] [SEARCH_TERMS].
Flags
-l , —limit [INTEGER] : Limit the number of derivations to search against. [default: 100]
-d , —non-observer-derivation : Search will be performed against keys derived using non-observer derivation. [default: False]
-P , —show-progress : Show search progress. [default: False]
-t , —search-type [public_key|private_key|address|all] : Limit the search to include just the specified types. [default: address, public_key]
-p , —derive-from-hd-path [TEXT] : Search for items derived from a specific HD path. Indices ending in an ‘n’ indicate that non-observer derivation should used at that index. Example HD path: m/12381n/8444n/2/
Examples
- Search for a wallet address: chia keys derive search -t address -l 100 <xch address>
wallet-address
Command: chia keys derive wallet-address [OPTIONS]
Flags
-i , —index [INTEGER] : Index of the first wallet address to derive. Index 0 is the first wallet address.
-n , —count [INTEGER] : Number of wallet addresses to derive, starting at index.
-x , —prefix [TEXT] : Address prefix (xch for mainnet, txch for testnet).
-d , —non-observer-derivation : Derive wallet addresses using non-observer derivation. [default: False]
—show-hd-path : Show the HD path of the derived wallet addresses. If non-observer-derivation is specified, path indices will have an ‘n’ suffix. [default: False]
Examples
Show first 10 wallet addresses:
chia keys derive -f <fingerprint> wallet-address -i 0 -n 10 —show-hd-path