Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions mining/mining-quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,19 +61,19 @@ There are numerous options when it comes to SAS controllers. For a straightforwa

Syncing is the process of downloading data from network peers. Your node will continuously check for any gaps in the data you have already packed and then search out peers from which to download the missing data.

Packing is the process of encrypting the synced data with your public Arweave key in order to mine against it. Syncing and packing are typically done at the same time. For more information see the [Syncing and Packing Guide](syncing-packing.md)
Packing is the process of encrypting the synced data with your public Arweave key in order to mine against it. Syncing and packing are typically done at the same time. For more information see the [Syncing and Packing Guide](syncing-packing.md).

### Mining

Once you have fully packed all of your data and configured your storage modules, you can mine against them. This is a relatively straightforward process, but requires monitoring of your systems periodically. For more information see the [Mining Guide](mining-guide.md)
Once you have fully packed all of your data and configured your storage modules, you can mine against them. This is a relatively straightforward process, but requires monitoring of your systems periodically. For more information see the [Mining Guide](mining-guide.md).

### data_dir

The `data_dir` folder is an extremely important folder, as it stores indexing files, block data, transaction data, and is the target location where you mount or link to your `storage_modules` folder. It should be created on an SSD/NVME drive with at least 200GB of space (ideally 500GB for future-proofing).

### VDF Servers

The VDF (Verifiable Delay Function) releases new mining "seeds" roughly every second and controls the speed of mining. Historically, each miner had to operate their own VDF server, however now you are able to utilize the Arweave Team VDF servers. For more information see the [VDF Guide](vdf.md)
The VDF (Verifiable Delay Function) releases new mining "seeds" roughly every second and controls the speed of mining. Historically, each miner had to operate their own VDF server, however now you are able to utilize the Arweave Team VDF servers. For more information see the [VDF Guide](vdf.md).

### Packing / Mining Servers

Expand Down Expand Up @@ -108,7 +108,7 @@ Currently, my full weave consumes approximately 1.3 kW per hour, excluding the p

#### Hardware Summary

For the purposes of this Quickstart guide, we have suggested a simple and high-end system that utilizes easily purchasable used equipment from eBay, Facebook, and other sources. While there are many other variations (including used servers), this setup will provide you with a solid starting point. For more information see the [Hardware Guide](hardware.md)
For the purposes of this Quickstart guide, we have suggested a simple and high-end system that utilizes easily purchasable used equipment from eBay, Facebook, and other sources. While there are many other variations (including used servers), this setup will provide you with a solid starting point. For more information see the [Hardware Guide](hardware.md).

##### Minimum Suggested
|||
Expand Down Expand Up @@ -209,7 +209,7 @@ You must create your first AR wallet in order to prepare your hard drives to be

### Prepping your hard drives to be storage modules

The Arweave data set (sometimes called "the weave") is divided up into 3.6TB partitions. As mentioned earlier miners typically store each partition on its own 4TB disk - the extra 0.4TB of space is needed for extra metadata. Before you can start mining you need to configure "storage modules" that cover the data you plan to mine. Often miners will have 1 storage module for each partition - but this is not required. We'll describe how to configure this basic case below, but for more information please see the [Mining Guide](mining-guide.md#preparation-storage-setup)
The Arweave data set (sometimes called "the weave") is divided up into 3.6TB partitions. As mentioned earlier miners typically store each partition on its own 4TB disk - the extra 0.4TB of space is needed for extra metadata. Before you can start mining you need to configure "storage modules" that cover the data you plan to mine. Often miners will have 1 storage module for each partition - but this is not required. We'll describe how to configure this basic case below, but for more information please see the [Mining Guide](mining-guide.md#preparation-storage-setup).

You will need to mount your drives into subdirectories within `/opt/data_dir/storage_modules.` There are various methods for achieving this, such as direct mounting or using symbolic links (symlinks). For the purposes of this Quickstart guide, we will employ the direct mounting method. Ensure that you create only one instance of each storage module, as there is no advantage to duplicating the same storage module. To maximize efficiency, pack as many drives as possible concurrently to fully utilize your CPU. It is advisable not to mine while packing.

Expand Down Expand Up @@ -428,6 +428,6 @@ Local mining stats:
- <https://docs.arweave.org/developers/mining/syncing-packing/estimated-partition-sizes>


For additional information on topics covered in this quickstart guide, please review the official [Arweave Mining Guide](mining-guide.md). It is a living document and will continually receive additional/updated content
For additional information on topics covered in this quickstart guide, please review the official [Arweave Mining Guide](mining-guide.md). It is a living document and will continually receive additional/updated content.