Getting Started
Configuration
Operator configuration guide.
We are providing Operators with pre-made configuration files based on the information provided through the application form.
In order to download these configuration files, we provide a Convenience Script that installs configurations to ~/.fermah/config/testnet
Please replace OPERATOR with your operator name, in lowercase.
BASE_URL=https://fermah-releases.s3.us-east-2.amazonaws.com
SCRIPT=setup.sh
VERSION=0.1.2
NETWORK=testnet
TYPE=operator
OPERATOR=operatorname
curl $BASE_URL/$SCRIPT | bash -s -- $VERSION $NETWORK $OPERATOR $TYPE
Latest version: 0.1.2
SHA256: fc93b1a0ee55cb0cce3c34f80628610a43d90c7609ef9e45d4f0d6da500d592f
GPG verification available, check GPG.
Notes
Running the above command sets up two configuration files corresponding to:
- Registration Information
- Hardware Resource Commitments
The JSON configuration files are expected to exist in ~/.fermah/config/[net]. Configuration filenames have the format [type].[name].json, where [name] is a user-controlled name, usually default, and [type] corresponds to either operator or registration. For Testnet, we are currently manually handling the creation of these configurations for smooth onboarding.
Registration Information
This configuration file contains information necessary for an optional EigenLayer registration, as well as Quorum numbers for the required AVS registration itself.
This file is used when running Registration.
Hardware Resource Commitments
For Matchmaker to properly assign proof generation tasks, resource commitments need to be received when the Operator is joining the P2P network.
This file is used when Starting a Node.
Configuration Examples
operator.[name].json
{
"operator": {
"name": "operatorname",
"resources": {
"cpu_threads": 8,
"memory_mb": 16384,
"storage_gb": 50,
"gpu": {
"count": 0,
"type": "none"
}
}
}
}