Требования

Minimum Hardware Requirements

Farming can be Network Intensive.

Make sure you have a stable network connection. During the plotting phase of farming, it can be network intensive.

This may impact your network usage so please check your network connection if you have a hard data limit.

Hardware	Характеристики
CPU	4 Core+
RAM	8GB+
SWAP	4GB
Storage (node)	100GB (SSD)
Storage (farm)	*See Note (SSD)

note

The Autonomys Network is based on Proof of Archival Storage, as such your storage contribution will directly correlate to your block and vote rewards. In other words, the more space you contribute, the faster and more frequently you will earn rewards. While you can farm with as little as 100 GB, it is strongly recommended that you allocate as much space as possible to maximize reward potential. For insights on how this choice impacts our network's consensus mechanism and your potential rewards, see this guide.

Nodes meeting these minimum requirements should be able to farm and sync with the network under typical conditions. However, performance may degrade if the network experiences heavy load, such as blocks filled with a high number of transactions.

Recommended Requirements

To handle increased network demands and maintain optimal performance, we recommend the following hardware specifications:

Hardware	Характеристики
CPU	Intel Core i7-6700 or equivalent
CPU	4 Core+
RAM	16GB+
Storage (node)	256GB (SSD)
Network	Reliable broadband internet connection with low latency

Reference Hardware Details

Our benchmarking tests were conducted using the Intel Core i7-6700 CPU. We have calibrated the transaction weights so that a full block cannot contain more transactions than this CPU can execute within the 2-second block execution time limit. This ensures that nodes running on hardware equivalent to or better than the Intel Core i7-6700 can process blocks at full capacity without performance issues.

While farmers with hardware below the referenced hardware may operate successfully under most conditions, they might experience difficulties during peak network activity. If blocks become consistently full of transactions, nodes with lower specifications may struggle to keep up, potentially affecting farming performance and rewards.

For detailed CPU information and benchmarking results, please refer to our GitHub repository.

Security Considerations

For a secure farming setup, ensure your system is updated, use a secure wallet, configure firewalls properly, and follow network safety protocols. Detailed security practices are available on our Security Best Practices page.

Crypto Wallet

Before running anything you need to have a wallet where you'll receive testnet coins. There are currently two wallets we suggest using, SubWallet being the preferred route.

• SubWallet
• PolkadotJS

Install one of the two wallets above into your browser and create a new account there. The address of your account will be necessary at the last step.

For help refer to our wallets section for Subwallet & Polkadot.js Wallet

Networking Information

For comprehensive details on network configurations, port management, firewall settings, and related networking requirements, please consult our dedicated Networking Guide. This resource provides in-depth information to ensure seamless integration and optimal security of your network connections.

Storage

HDDs are not supported and will never be. We don't recommended trying to use smart caching, tiered storage or other ways to accelerate it, you'll be 100% disappointed and just waste your time.

The node will require 100 GiB of good quality SSD. Doesn't have to be anything amazing, but something mid-range from a reputable manufacturer with decent endurance is recommended.

The farmer side can work with pretty much any SSD whatsoever that is not fake and not outright broken, dedicating high quality high endurance SSD is pointless unless you already have it for reasons unrelated to Autonomys. Software writes to disk in near-perfect for SSD way, effectively doing write leveling if SSD is solely dedicated to farming.

RAID of any kind is pointless and can only harm performance and/or rewards. RAID0 will most likely make things slower rather than faster (application benefits from knowing underlying hardware topology). RAID1 or any other redundancy level is 100% pointless too since farms are stateless and can be removed if a disk breaks without losing data on other disks, it'll just make thing slower and reduce the effective capacity that can be used for farming, reducing farming rewards for literally no benefit in exchange.

Linux File System Recommendations

• ext4: The recommended formatting command for drives dedicated solely to subspace is sudo mkfs.ext4 -m 0 -T largefile4 /path/to/dev, as it maximizes usable space and the plot resizing functionality operates flawlessly. Previously recommended striping and chunk size parameters have not demonstrated any appreciable benefit or harm.

• XFS: No longer recommended as attempting to resize the plot (larger or smaller) with the drive nearly full (98%+) will render the plot unfarmable unless sufficient extra space can be freed up by means other than trying to shrink the plot (try deleting piece_cache.bin if this happens to you). Full XFS disk utilization can only be achieved during the plot's initial creation, and will still yield less usable space than the ext4 recommendation above.

• CoW Filesystems: Avoid using Copy-on-Write (CoW) file systems (like ReFS, BTRFS, ZFS, bcachefs, HAMMER) with Subspace. If using BTRFS, disable CoW using sudo chattr +C path/to/data/dir before starting Subspace. This applies only to newly created files. Alternatively, use a non-CoW filesystem like ext4 as recommended above.

• RAID: Avoid redundancy setups (RAID1/5/6, RAIDZ) for filesystems with plots. The subspace farmer uses checksums for data integrity and can often recover corrupted blocks. Use scrub for maintenance. RAID0 accomplishes little more than to put more of your plots at risk in case of a drive failure.

• SWAP: A swap file is necessary only if your system has a low amount of RAM.

System Adjustments

• File Descriptor Limit: Linux has a hard limit of 100k file descriptors. Exceeding this may cause errors. Substrate has a default limit of 10k. Check and adjust the limit at /proc/sys/fs/file-max. Refer to this tutorial for changing the limit.

• Dependencies: If you encounter an error related to libgomp.so.1, install the libgomp1 library with sudo apt-get install libgomp1. :::

Dependencies

If you face an error where the node outputs nothing and no error code is given it is likely you just need to install the latest Visual C++ Redistributable package here :::

Linux libcomp.so.1 error.

If you encounter an error related to libgomp.so.1, install the libgomp1 library with sudo apt-get install libgomp1.

Linux File Descriptor Limit

Linux has a hard limit of 100k file descriptors. Exceeding this may cause errors. Refer to our guide here