Unixhash is the earliest company engaged in the research and development of Arweave mining rigs. At present, we have two clusters of Arweave Miner U5000 55k & Arweave Miner U5100 80K. All keep the latest technology.
Arweave is based on Blockweave, a derivative of blockchain, and provides permanent storage as a solution to the cloud storage challenge.
Buy Arweave Miner
Arweave Mining Equipment-The Ultimate FAQ Guide
Cryptocurrencies are experiencing a booming growth and that can be credited, at least partly, to the introduction of decentralized networks that have provided a solution to the storage problem. The challenge provided by the cloud storage market further entices the market and results in a huge growth of the industry. Cryptocurrencies like Filcoin and Sia saw the challenge of space and storage created by the cloud storage market and solved it by providing contract-based storage solutions.
Explaining Everything Related to Arweave
Arweave is the first blockweave coin in the world, that allows the permanent storage of data such as transactions, contracts, web pages, videos, pictures, and so on. The word blockweave is going to be used quite frequently with arweave as this altcoin uses this derivative of blockchain. In the blockchain, a block refers to different data about a transaction or so that has been grouped together. A block appears every 2 minutes, approximately.
Blockchain and Blockweave: What is the Difference?
The difference between blockchain and blockweave is that with blockchain, each block is a group of data and a new block cannot be introduced till all previous blocks have been validated and verified to be accurate. Blockweave however, allows the introduction of a new block when arweave miner randomly validates one of the old blocks. The entire history or all the prior blocks do not need to be validated and verified by the arweave miner.
Another difference between blockchain and blockweave is that in blockchain, a new block is linked to the next and the previous block in a chain whereas, in blockweave, a new block is connected to the next or coming block and two previous blocks. Amongst the two blocks, one block is the one before the newly mined block, and the second one is one of the previous blocks from the blockweave history, known as recall block. The recall block is of especial importance in discussions of the consensus model of Arweave.
Costs and Payments of Arweave
The Arweave peer-to-peer protocol matches users with available space to those looking for storage. The data on the network or ARdrive is permanent meaning that users can permanently store their data on this decentralized network. Arweave only requires one small payment upfront, which acts as an incentive for the AR miners to continuously replicate the stored data.
The fee is payable in AR, the altcoin of the Arweave network and along with this fee, there is a network fee that needs to be paid as well. However, network fees are in the form of endowments, which are basically a future security fee. This endowment or network fee is taken from the initial fee paid, as it ensures payment for future replications of the stored data. Overall, the payment is made as a one-time payment although a part of it is sent as an endowment for a future security fee.
Arweave: A decentralized storage network
The main aim of Arweave was to offer a decentralized solution to the specific problem of data impermanence on the internet. Internet is known to have all the information there was to ever exist but that is far from the truth of the internet. All information on the internet such as web pages, videos, and pictures, along with everything else can be targeted with malicious intent for manipulation, or it can be censored or it can just simply be lost. This data can also be taken down as there is no permanence with the internet, and Arweave has created a decentralized storage network for the preservation of all data, on the permaweb.
Arweave Consensus Protocol: PoA
Arweave consensus protocol is as unique as everything else about this altcoin. The consensus protocol or model performs the function of maintaining consistency across the blockchain by ensuring the security of the blockchain, or blockweave, for Arweave. The consensus protocol for Bitcoin is proof of proof of work or PoW, which means that miners trying to mine Bitcoin have to break down complex, cryptographic mathematical hashes to mine bitcoin. For filecoin, the consensus protocol is also PoW, however, based entirely on storage. For Arweave, the consensus protocol is known as Proof-of-Access or PoA.
The main job of an Arweave miner is to provide storage space to those who require it and then replicate stored data to ensure permanence on the decentralized network. For this, miners are rewarded AR tokens. For miners to be able to introduce a new block to the blockweave, they should be able to verify that they can access the recall block, which is explained above. This verification is referred to as the consensus protocol, point of access and the point of it is to increase or promote data permanence on the network.
Furthermore, miners have a content policy that strictly prohibits certain data from being stored by the miner, as they cannot store the entire data on the network. During data distribution, data will not be added to the miner’s transaction pool if it happens to be on the particular miner’s prohibited list.
Is Arweave Mining and Investment Worth it?
Before making the decision to mine Arweave, and invest in this decentralized storage network, you need to perform a cost to benefit analysis, as there is quite a bit of capital required for the Arweave mining equipment. The Arweave mining rig can be costly and you need to determine if you have the time and the resources required to make it happen, to the point of earning rewards and a decent profit. If the profit and the cost are equal or if the latter is higher than the former, then maybe Arweave mining may not be the best choice for you. You can still be a part of Arweave as it takes over the industry by purchasing or trading AR tokens.
Arweave Mining Equipment
- A strong CPU such as Ryzen or i7
- 6+ TB NVME, (e.g. RAID 0 of 3x2TB or RAID 0 of 2x4TB, etc). The more NVME you have, the more Weave you can store. As earnings on Arweave are directly related to the amount of the Weave you store, it is best to get more NVME.
- A system with 8 GB is sufficient for Arweave mining as the network doesn’t require much memory.
- Similar to memory, once you have downloaded the Weave, network bandwidth can be reduced too as it no longer requires a lot of it.
It is also highly recommended that you join a mining pool, which is a pool of resources that are shared by multiple miners over a network. There is quite a bit of information with regard to mining pools and Arweave on the Discord and Reddit social media apps. Although some of these mining pools are invite-only, they are definitely worth checking out, as they provide clarification and ease to the mining process, especially for first timers. Some of the popular pools are Kronenberg, Vird, and Hpool.
Want to start mining on Arweave? You’ve come to the right place! Get set up with this quick and easy guide, and join our awesome network of ever-growing miners.
Install the Miner
It is also possible to set-up an Arweave mining environment on Windows using the ‘Windows Subsystem for Linux’ or a virtual machine environment.
Preparation: File Descriptors Limit
The number of available file descriptors affects the rate at which your node can process data. As the default limit assigned to user processes on most operating systems is usually low, we recommend increasing it.
You can check the current limit by executing ulimit -n.
On Linux, to set a bigger global limit, open /etc/sysctl.conf and add the following line:
sysctl -pto make the changes take effect.
/etc/security/limits.confand add the following line:
<your OS user> soft nofile 10000000
Open a new terminal session. To make sure the changes took effect, and the limit was increased, type ulimit -n. You can also change the limit for the current session via ulimit -n 10000000
If the above does not work, set
Running the Miner
Now you’re ready to start the mining process by using the following command from the Arweave directory:
./bin/start mine mining_addr YOUR-MINING-ADDRESS peer 22.214.171.124 peer 126.96.36.199 peer 188.8.131.52 peer 184.108.40.206 peer 220.127.116.11
Please replace YOUR-MINING-ADDRESS with the address of the wallet you would like to credit when you find a block!
If you would like to see a log of your miner’s activity, you can run ./bin/logs -f in the Arweave directory in a different terminal.
The mining console should eventually look like this:
[Stage 1/3] Starting to hash
Miner spora rate: 1545 h/s, recall bytes computed/s: 3129, MiB/s read: 386, the round lasted 145 seconds.
[Stage 1/3] Starting to hash
Skipping hashrate report, the round lasted less than 10 seconds.
[Stage 1/3] Starting to hash
Miner spora rate: 1545 h/s, recall bytes computed/s: 3182, MiB/s read: 386, the round lasted 135 seconds.
[Stage 1/3] Starting to hash
Miner spora rate: 1637 h/s, recall bytes computed/s: 3292, MiB/s read: 409, the round lasted 245 seconds.
[Stage 1/3] Starting to hash
When you mine a block, the console shows:
[Stage 2/3] Produced candidate block … and dispatched to network.
Approximately 20 minutes later, you should see
[Stage 3/3] Your block … was accepted by the network
./bin/stopor kill the OS process (
kill -sigterm <pid>or
pkill <name>). Sending a SIGKILL (
kill -9) is not recommended.
Tuning the Miner
Optimizing Miners SPoRA Rate
Miner spora rate: 1546 h/sand logs –
miner_sporas_per_second. Note that it is 0 when you start the miner without data and slowly increases as more data is synchronized. After the number stabilizes, you can input it into the mining calculator generously created by the community member @tiamat here to see the expected return.
randomx-benchmarkscript./bin/randomx-benchmark –mine –init 32 –threads 32 –jit –largePages. Replace 32 with the number of CPU threads. Note that reducing the number of threads might improve the outcome. Do not specify –largePages if you have not configured them yet. For the reference, a 32-threads AMD Ryzen 3950x can do about 10000 h/s, a 32-threads AMD EPYC 7502P – 24000 h/s, a 12-threads Intel Xeon E-2276G CPU – 2500 h/s, a 2-threads Intel Xeon CPU E5-2650 machine in the cloud – 600 h/s.
hdparm -t /dev/sda. Replace
/dev/sdawith the disk name from
df -h. To be competitive, consider a fast NVMe SSD capable of several GiB per second and more.
./bin/hashrate-upper-limit 2500 1 3where 2500 is a RandomX hashrate, 1 is the number of GiB a disk reads per second, 3 is 1/replicated share of the weave. For example, a 12-core Intel Xeon with a 1 GiB/s SSD with a third of the weave is capped at 540 h/s. In practice, the performance is usually about 0.7 – 0.9 of the upper limit.
Changing the mining configuration
We made our best effort to choose reasonable defaults; however, changing some of the following parameters may improve the efficiency of your miner:
stage_one_hashing_threads (between 1 and the number of CPU threads),
randomx_bulk_hashing_iterations. For example,
./bin/start stage_one_hashing_threads 32 stage_two_hashing_threads 32 io_threads 50 randomx_bulk_hashing_iterations 64 data_dir /your/dir mine sync_jobs 80 mining_addr YOUR-MINING-ADDRESS peer 18.104.22.168 peer 22.214.171.124 peer 126.96.36.199 peer 188.8.131.52 peer 184.108.40.206
recall bytes computed/s should be roughly equal to
Miner spora rate divided by your share of the weave. If it is not, consider increasing
io_threads and decreasing
stage_one_hashing_threads. You can learn the share of the weave the node has synced to date by dividing the size of the
chunk_storage folder (
du -sh /path/to/data/dir/chunk_storage) by the total weave size. Increasing
randomx_bulk_hashing_iterations to 128 or bigger might make a big difference on the powerful machine.
Syncing the weave
rocksdbfolders, the node will fill it up, and your miner may nevertheless be competitive, assuming the disk and the processor are sufficiently performant.
sync_jobsconfiguration parameter like this:
./bin/start mine sync_jobs 80 mining_addr YOUR-MINING-ADDRESS peer 220.127.116.11 peer 18.104.22.168 peer 22.214.171.124 peer 126.96.36.199 peer 188.8.131.52
You can set the sync_jobs back to 2 after historical data is synced. Turn the miner off (do not set the
mine flag) to further speed up syncing.
Configuring large memory pages
cat /proc/meminfo | grep HugePages. To set a value, run
sudo sysctl -w vm.nr_hugepages=1000. To make the configuration survive reboots, create
enable randomx_large_pageson startup:
./bin/start mine enable randomx_large_pages mining_addr YOUR-MINING-ADDRESS peer 184.108.40.206 peer 220.127.116.11 peer 18.104.22.168 peer 22.214.171.124 peer 126.96.36.199
Using Multiple Disks
sudo mount /dev/nvme1n2 /your/dir/rocksdb
sudo mount /dev/hdd1 /your/dir
The output of df -h should look like:
/dev/hdd1 5720650792 344328088 5087947920 7% /your/dir /dev/nvme1n1
104857600 2097152 102760448 2% /your/dir/chunk_storage /dev/nvme1n2
104857600 2097152 102760448 2% /your/dir/rocksdb
Replace /dev/nvme1n1, /dev/nvme1n2, /dev/hdd1 with the filesystems you have, replace /your/dir with the directory you specify on startup:
./bin/start data_dir /your/dir mine sync_jobs 80 mining_addr YOUR-MINING-ADDRESS peer 188.8.131.52 peer 184.108.40.206 peer 220.127.116.11 peer 18.104.22.168 peer 22.214.171.124
Make sure your node is accessible on the Internet
http://[Your Internet IP]:1984. You can obtain your public IP here, or by running
curl ifconfig.me/ip. If you specified a different port when starting the miner, replace “1984” anywhere in these instructions with your port. If you can not access the node, you need to set up TCP port forwarding for incoming HTTP requests to your Internet IP address on port 1984 to the selected port on your mining machine. For more details on how to set up port forwarding, consult your ISP or cloud provider.
Copying data to another machine
1.Stop the first Arweave miner, and ensure the second miner is also not running.
2.Copy the entire
data_dirfolder to the new machine. Note that the
chunk_storagefolder contains sparse files, so copying them the usual way will take a lot of time and the size of the destination folder will be too large. To copy this folder, use rsync with the
-aSflags or archive it via
tar -Scfbefore copying.
3.Start both miners.