Chia on Akash

Why use Akash?

Welcome Chia community! We are excited to announce support for Chia on the Akash network! You can now run nodes, plotting, and farming on our marketplace of compute. Below you will find details on how to configure your deployment for different use cases. Akash is a part of the Cosmos ecosystem of blockchains.

Summer Sale

Providers

For the following providers who are participating in the sale, expect to see these prices in Akashlytics! Each provider has been benchmarked and tested to create a $0.10/plot.
On-Sale Providers
BladeBit Price / Month
MadMax Price / Month
bigtractorplotting.com
$556 | 8 Minute Plots
$59 | 71 Minute Plots
xch.computer
$363 | 12 Minute Plots
$44 | 95 Minute Plots
akash.world
$174 | 24 Minute Plots
$42 | 99 Minute Plots

Required SDL

To make sure you get the sale price from the providers, please Copy and Paste the SDL into Akashlytics :
Please wait up to 60 seconds to see bids from all the providers.

Windows/Linux/Mac Users

  1. 1.
    Install Keplr wallet as a browser plugin
  2. 2.
    Install Akashlytics and import your AKT wallet address from Keplr.
For additional help we recommend you follow our full deployment guide in parallel with this guide.

How does this work?

Akash uses its blockchain to manage your container deployment and accounting. To deploy on Akash you will need to fund your wallet with at least 10 AKT. Each time you create a deployment, 5 AKT will be used for escrow and to fund the deployment. If the deployment is canceled, the balance of the escrow is returned to you. You can spin up deployments without worrying about any long term contracts and you can cancel anytime.

Plotting Demo

@DigitalSpaceport
Jonmichael Hands - VP of Storage Business Development at Chia
Andrew Mello - Head of Mining at Akash

Default wallet

Akash uses Keplr as the desktop wallet. Advanced users can follow the CLI instructions.
Once you have set up your Keplr wallet and imported the address to Akashlytics you are ready to create your first deployment. Follow the instructions in Akashlytics to create a certificate, then click on Create Deployment.

Quickest way to get more AKT

To fund your deployment you will need AKT in your account. The fastest way to do that is in one of the following two ways.

Buy on an Exchange

  1. 1.
    Install Keplr
  2. 2.
    Buy AKT on an exchange
  3. 3.
    Withdraw your AKT to your Keplr wallet

Swap from ATOM to AKT

  1. 1.
    Install Keplr
  2. 2.
    Send 10 ATOM to your new Cosmos wallet address inside Keplr (this address will start with cosmos)
  3. 3.
    Go to Osmosis Assets > next to Cosmos Hub - ATOM click on Deposit. This step will deposit ATOM from your Keplr wallet onto the Osmosis platform. Press Connect Wallet to connect your Keplr wallet to Osmosis.
  4. 4.
    Now go back to Osmosis Homepage and ensure ATOM > AKT is selected to complete the swap. This step swaps your ATOM you deposited onto the Osmosis platform into any other supported coin.
  5. 5.
    Return to the Osmosis Assets page to withdraw your AKT to your Keplr wallet. This step withdraws AKT from the Osmosis platform back into your Keplr wallet. You can now send AKT to Akashlytics.
Have more questions? Find our team in Discord and Telegram.

MadMax Disk Plotting

Recommended MadMax CPU Settings for 1Gbps Connections: ~75 minute plots = 8 cpu / 815Gi Storage
1
---
2
version: "2.0"
3
4
services:
5
chia:
6
image: cryptoandcoffee/akash-chia:200
7
expose:
8
- port: 8080
9
as: 80
10
proto: tcp
11
to:
12
- global: true
13
env:
14
#############################REQUIRED##############################
15
- VERSION=1.3.5
16
#Always check https://github.com/Chia-Network/chia-blockchain/releases
17
- CONTRACT=xch16txqvdlh67m9stvwmx848xzpgesd60swqxll3rrnnafunuluflds03jkt4
18
- FARMERKEY=847b826e653279b9e54ce66a1c55cbfdb1ddc4118e70038cdfbaa7e5cb0a785087bc3a6f055f01bbbf84a2c6a3be4a97
19
- PLOTTER=madmax
20
#Choose your plotter software - madmax, bladebit, bladebit-disk
21
- FINAL_LOCATION=upload
22
#Set to "local" to access finished plots through web interface.
23
#Set to "upload" and finished plots will be uploaded to a SSH destination like [email protected]:/home/user/plots
24
- CPU_UNITS=8
25
- MEMORY_UNITS=6Gi
26
- STORAGE_UNITS=815Gi
27
#Must match CPU/Memory/Storage units defined in resources.
28
#############################OPTIONAL##############################
29
#Uncomment the variables below when set FINAL_LOCATION=upload to enable remote uploading
30
#- REMOTE_HOST=changeme.com #SSH upload host
31
#- REMOTE_LOCATION=changeme #SSH upload location like /root/plots
32
#- REMOTE_PORT=22 #SSH upload port
33
#- REMOTE_USER=changeme #SSH upload user
34
#- REMOTE_PASS=changme #SSH upload password
35
#- UPLOAD_BACKGROUND=true
36
#Change to true to enable multiple background uploading of plots, this is the best option to use use 100% of your bandwidth.
37
#- RAMCACHE=32G
38
#Used only for PLOTTER=bladebit-disk, you must increase the memory resources requested below with this additional cache size.
39
#- RCLONE=true
40
#When true must also update JSON_RCLONE and add any destination in same format.
41
#- TOTAL_UPLOADS=1000
42
#Set the total number of parallel uploads allowed to an rclone destination
43
#- ENDPOINT_LOCATION=google
44
#Only used for RCLONE=true
45
#- ENDPOINT_DIR=plots
46
#Only used for RCLONE=true
47
#- JSON_RCLONE=
48
# [google]\n
49
# type = x\n
50
# scope = x\n
51
# token = x\n
52
# root_folder_id = x
53
#Example of STORJ config for RCLONE=true. If you want to use your own endpoint please escape each line with a backslash n, like in the example.
54
profiles:
55
compute:
56
chia:
57
resources:
58
cpu:
59
units: 8.0
60
memory:
61
size: 6Gi
62
storage:
63
size: 815Gi
64
placement:
65
akash:
66
signedBy:
67
anyOf:
68
- "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
69
attributes:
70
chia-plotting: "true"
71
pricing:
72
chia:
73
denom: uakt
74
amount: 100000
75
deployment:
76
chia:
77
akash:
78
profile: chia
79
count: 1
Copied!

Bladebit RAM Plotting

Plotting with Bladebit has never been easier! There are a few things to note before you start using Bladebit instead of Madmax. Bladebit is so fast it can create plots faster than most home/consumer internet connections (1Gbps) can download them. To compensate for this we can adjust the Bladebit plotting speed by changing the CPU count of the deployment. Recommended Bladebit CPU Settings for 1Gbps Connections: ~20 minute plots = 8 cpu / 915Gi Storage ~15 minute plots = 16 cpu / 915Gi Storage ~10 minute plots = 32 cpu / 2Ti Storage Recommended Bladebit CPU Settings for Multi-Gigabit Connections: ~7 minutes plots = 64 CPU / 2Ti Storage ~4 minutes plots = 100 cpu / 4Ti Storage ~3 minutes plots = 186 cpu / 6Ti Storage
For a standard 1Gbps connection use the settings below, otherwise adjust the CPU units to match the plot time you want to achieve.
1
---
2
version: "2.0"
3
4
services:
5
chia:
6
image: cryptoandcoffee/akash-chia:200
7
expose:
8
- port: 8080
9
as: 80
10
proto: tcp
11
to:
12
- global: true
13
env:
14
#############################REQUIRED##############################
15
- VERSION=1.3.5
16
#Always check https://github.com/Chia-Network/chia-blockchain/releases
17
- CONTRACT=
18
- FARMERKEY=
19
- PLOTTER=bladebit
20
#Choose your plotter software - madmax, bladebit, bladebit-disk
21
- FINAL_LOCATION=upload
22
#Set to "local" to access finished plots through web interface.
23
#Set to "upload" and finished plots will be uploaded to a SSH destination like [email protected]:/home/user/plots
24
- CPU_UNITS=32
25
- MEMORY_UNITS=430Gi
26
- STORAGE_UNITS=1200Gi
27
#Must match CPU/Memory/Storage units defined in resources.
28
#############################OPTIONAL##############################
29
#Uncomment the variables below when set FINAL_LOCATION=upload to enable remote uploading
30
#- REMOTE_HOST=changeme.com #SSH upload host
31
#- REMOTE_LOCATION=changeme #SSH upload location like /root/plots
32
#- REMOTE_PORT=22 #SSH upload port
33
#- REMOTE_USER=changeme #SSH upload user
34
#- REMOTE_PASS=changme #SSH upload password
35
#- UPLOAD_BACKGROUND=true
36
#Change to true to enable multiple background uploading of plots, this is the best option to use use 100% of your bandwidth.
37
#- RAMCACHE=32G
38
#Used only for PLOTTER=bladebit-disk, you must increase the memory resources requested below with this additional cache size.
39
#- RCLONE=true
40
#When true must also update JSON_RCLONE and add any destination in same format.
41
#- TOTAL_UPLOADS=1000
42
#Set the total number of parallel uploads allowed to an rclone destination
43
#- ENDPOINT_LOCATION=google
44
#Only used for RCLONE=true
45
#- ENDPOINT_DIR=plots
46
#Only used for RCLONE=true
47
#- JSON_RCLONE=
48
# [google]\n
49
# type = x\n
50
# scope = x\n
51
# token = x\n
52
# root_folder_id = x
53
#Example of STORJ config for RCLONE=true. If you want to use your own endpoint please escape each line with a backslash n, like in the example.
54
profiles:
55
compute:
56
chia:
57
resources:
58
cpu:
59
units: 32
60
memory:
61
size: 430Gi
62
storage:
63
size: 1200Gi
64
placement:
65
akash:
66
signedBy:
67
anyOf:
68
- "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
69
attributes:
70
chia-plotting: "true"
71
pricing:
72
chia:
73
denom: uakt
74
amount: 100000
75
deployment:
76
chia:
77
akash:
78
profile: chia
79
count: 1
Copied!

Downloading plots

To access the Chia Plot Manager, click on the `Uri` link on the deployment detail page. To download plots, click an invididual plot in the Chia Plot Manager and click on Download/Open.
Chia Plot Manager
*Once your download has finished - Delete the plot from the container - to make room for new plots! Plots will continue to be created as long as there is enough free space available in the container (Max 32Tb) and the deployment is fully funded.

Uploading plots

If you want to upload plots created on Akash directly to a remote destination such as your farm or a storage provider, you have 2 main options.

SSH

Upload your plots to any SSH destination by modifying the env:
1
env:
2
#############################REQUIRED##############################
3
- VERSION=1.3.5
4
#Always check https://github.com/Chia-Network/chia-blockchain/releases
5
- CONTRACT=
6
- FARMERKEY=
7
- PLOTTER=bladebit
8
#Choose your plotter software - madmax, bladebit, bladebit-disk
9
- FINAL_LOCATION=upload
10
#Set to "local" to access finished plots through web interface.
11
#Set to "upload" and finished plots will be uploaded to a SSH destination like [email protected]:/home/user/plots
12
- CPU_UNITS=32
13
- MEMORY_UNITS=430Gi
14
- STORAGE_UNITS=1200Gi
15
#Must match CPU/Memory/Storage units defined in resources.
16
#############################OPTIONAL##############################
17
#Uncomment the variables below when set FINAL_LOCATION=upload to enable remote uploading
18
- REMOTE_HOST=changeme.com #SSH upload host
19
- REMOTE_LOCATION=changeme #SSH upload localtion like /root/plots
20
- REMOTE_PORT=22 #SSH upload port
21
- REMOTE_USER=changeme #SSH upload user
22
- REMOTE_PASS=changme #SSH upload password
23
- UPLOAD_BACKGROUND=true
24
#Change to true to enable multiple background uploading of plots, this is the best option to use use 100% of your bandwidth.
25
#- RAMCACHE=32G
26
#Used only for PLOTTER=bladebit-disk, you must increase the memory resources requested below with this additional cache size.
27
#- RCLONE=true
28
#When true must also update JSON_RCLONE and add any destination in same format.
29
#- TOTAL_UPLOADS=1000
30
#Set the total number of parallel uploads allowed to an rclone destination
31
#- ENDPOINT_LOCATION=google
32
#Only used for RCLONE=true
33
#- ENDPOINT_DIR=plots
34
#Only used for RCLONE=true
35
#- JSON_RCLONE=
36
# [google]\n
37
# type = x\n
38
# scope = x\n
39
# token = x\n
40
# root_folder_id = x
41
#Example of STORJ config for RCLONE=true. If you want to use your own endpoint please escape each line with a backslash n, like in the example.
42
Copied!

Rclone

Upload your plots to any Rclone endpoint! You need to first create a connection to your endpoint on a standard client so that you have a valid configuration in ~/.config/rclone/rclone.conf You need to modify this block and add \n to the end of each line to make it valid for Akash. Below you can find examples of how the env: should look.

Rclone to Dropbox

Change the replaceme values below to match your client settings
1
env:
2
#############################REQUIRED##############################
3
- VERSION=1.3.5
4
#Always check https://github.com/Chia-Network/chia-blockchain/releases
5
- CONTRACT=
6
- FARMERKEY=
7
- PLOTTER=bladebit
8
#Choose your plotter software - madmax, bladebit, bladebit-disk
9
- FINAL_LOCATION=upload
10
#Set to "local" to access finished plots through web interface.
11
#Set to "upload" and finished plots will be uploaded to a SSH destination like [email protected]:/home/user/plots
12
- CPU_UNITS=42
13
- MEMORY_UNITS=430Gi
14
- STORAGE_UNITS=1200Gi
15
#Must match CPU/Memory/Storage units defined in resources.
16
#############################OPTIONAL##############################
17
#Uncomment the variables below when set FINAL_LOCATION=upload to enable remote uploading
18
#- REMOTE_HOST=changeme.com #SSH upload host
19
#- REMOTE_LOCATION=changeme #SSH upload location like /root/plots
20
#- REMOTE_PORT=22 #SSH upload port
21
#- REMOTE_USER=changeme #SSH upload user
22
#- REMOTE_PASS=changme #SSH upload password
23
#- UPLOAD_BACKGROUND=true
24
#Change to true to enable multiple background uploading of plots, this is the best option to use use 100% of your bandwidth.
25
#- RAMCACHE=32G
26
#Used only for PLOTTER=bladebit-disk, you must increase the memory resources requested below with this additional cache size.
27
- RCLONE=true
28
#When true must also update JSON_RCLONE and add any destination in same format.
29
- TOTAL_UPLOADS=8
30
#Set the total number of parallel uploads allowed to an Rclone destination
31
- ENDPOINT_LOCATION=dropbox
32
#Name of Rclone endpoint
33
- ENDPOINT_DIR=replaceme
34
#Upload directory on Dropbox
35
- JSON_RCLONE=
36
[dropbox]\n
37
type = dropbox\n
38
client_id = replaceme\n
39
client_secret = replaceme\n
40
token = {"access_token":"replaceme","expiry":"replaceme"}
41
#Example of Dropbox config for RCLONE=true. If you want to use your own endpoint please escape each line with a backslash n, like in the example.
Copied!

Rclone to Google Drive

Change the replaceme values below to match your client settings
1
env:
2
#############################REQUIRED##############################
3
- VERSION=1.3.5
4
#Always check https://github.com/Chia-Network/chia-blockchain/releases
5
- CONTRACT=
6
- FARMERKEY=
7
- PLOTTER=bladebit
8
#Choose your plotter software - madmax, bladebit, bladebit-disk
9
- FINAL_LOCATION=upload
10
#Set to "local" to access finished plots through web interface.
11
#Set to "upload" and finished plots will be uploaded to a SSH destination like [email protected]:/home/user/plots
12
- CPU_UNITS=42
13
- MEMORY_UNITS=430Gi
14
- STORAGE_UNITS=1200Gi
15
#Must match CPU/Memory/Storage units defined in resources.
16
#############################OPTIONAL##############################
17
#Uncomment the variables below when set FINAL_LOCATION=upload to enable remote uploading
18
#- REMOTE_HOST=changeme.com #SSH upload host
19
#- REMOTE_LOCATION=changeme #SSH upload location like /root/plots
20
#- REMOTE_PORT=22 #SSH upload port
21
#- REMOTE_USER=changeme #SSH upload user
22
#- REMOTE_PASS=changme #SSH upload password
23
#- UPLOAD_BACKGROUND=true
24
#Change to true to enable multiple background uploading of plots, this is the best option to use use 100% of your bandwidth.
25
#- RAMCACHE=32G
26
#Used only for PLOTTER=bladebit-disk, you must increase the memory resources requested below with this additional cache size.
27
- RCLONE=true
28
#When true must also update JSON_RCLONE and add any destination in same format.
29
- TOTAL_UPLOADS=8
30
#Set the total number of parallel uploads allowed to an Rclone destination
31
- ENDPOINT_LOCATION=google
32
#Name of Rclone endpoint
33
- ENDPOINT_DIR=replaceme
34
#Upload directory on Google
35
- JSON_RCLONE=
36
[google]\n
37
type = drive\n
38
scope = drive\n
39
token = {"access_token":"replaceme","token_type":"Bearer","refresh_token":"replaceme","expiry":"replaceme"}\n
40
root_folder_id = replaceme
41
#Example of Google config for RCLONE=true. If you want to use your own endpoint please escape each line with a backslash n, like in the example.
42
Copied!

Rclone to Storj

Change the replaceme values below to match your client settings
1
env:
2
#############################REQUIRED##############################
3
- VERSION=1.3.5
4
#Always check https://github.com/Chia-Network/chia-blockchain/releases
5
- CONTRACT=
6
- FARMERKEY=
7
- PLOTTER=bladebit
8
#Choose your plotter software - madmax, bladebit, bladebit-disk
9
- FINAL_LOCATION=upload
10
#Set to "local" to access finished plots through web interface.
11
#Set to "upload" and finished plots will be uploaded to a SSH destination like [email protected]:/home/user/plots
12
- CPU_UNITS=42
13
- MEMORY_UNITS=430Gi
14
- STORAGE_UNITS=1200Gi
15
#Must match CPU/Memory/Storage units defined in resources.
16
#############################OPTIONAL##############################
17
#Uncomment the variables below when set FINAL_LOCATION=upload to enable remote uploading
18
#- REMOTE_HOST=changeme.com #SSH upload host
19
#- REMOTE_LOCATION=changeme #SSH upload location like /root/plots
20
#- REMOTE_PORT=22 #SSH upload port
21
#- REMOTE_USER=changeme #SSH upload user
22
#- REMOTE_PASS=changme #SSH upload password
23
#- UPLOAD_BACKGROUND=true
24
#Change to true to enable multiple background uploading of plots, this is the best option to use use 100% of your bandwidth.
25
#- RAMCACHE=32G
26
#Used only for PLOTTER=bladebit-disk, you must increase the memory resources requested below with this additional cache size.
27
- RCLONE=true
28
#When true must also update JSON_RCLONE and add any destination in same format.
29
- TOTAL_UPLOADS=8
30
#Set the total number of parallel uploads allowed to an Rclone destination
31
- ENDPOINT_LOCATION=storj
32
#Name of Rclone endpoint
33
- ENDPOINT_DIR=replaceme
34
#Upload directory on Storj
35
- JSON_RCLONE=
36
[storj]\n
37
type = storj\n
38
api_key = replaceme\n
39
passphrase = replaceme\n
40
satellite_address = replaceme\n
41
access_grant = replaceme
42
#Example of Storj config for RCLONE=true. If you want to use your own endpoint please escape each line with a backslash n, like in the example.
Copied!

Speed up downloads

Windows/Mac/Linux : Use a download manager like DownThemAll on Chrome/Firefox/Opera Linux/CLI: Use aria2 : apt-get install aria2
1
aria2c -c -s 16 -x 16 -k 64M -j 1 $plot_download_url
Copied!

Waiting for bids...

If Akashlytics hangs on "Waiting for Bids" that could be an indication that all providers are full at the moment. The recommended fix is to reduce the requested storage amount from 1Ti to something more reasonable like 768Gi
1
profiles:
2
compute:
3
chia:
4
resources:
5
cpu:
6
units: 8.0
7
memory:
8
size: 6Gi
9
#Chia blockchain is currently ~40gb as of November 2021 / if you are plotting please use at least 256Gi
10
storage:
11
size: 768Gi
Copied!

How to speed up plotting?

Use only providers with the chia-plotting attribute

To limit the selection of providers to those with fast storage that meets the requirements for plotting, we recommend you keep the chia-plotting attribute to the placement section of deploy.yaml file.
1
placement:
2
akash:
3
attributes:
4
chia-plotting: "true"
5
pricing:
6
chia:
7
denom: uakt
8
amount: 100000
Copied!

Create more deployments

Easily scale your total plotting output by creating a new deployment. Click the three dots next to the Add Funds button on the deployment details page and click Redeploy.