Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AVS: added whitelist information in the manual #82

Merged
merged 1 commit into from
Dec 13, 2024
Merged

AVS: added whitelist information in the manual #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 9 additions & 3 deletions docs/avs/running-avs-operator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Not only will you be helping to maintain the integrity of this innovative system
The following instructions apply to setting up an operator in the testnet environment running on Ethereum [Holesky](https://holesky.etherscan.io/) (L1), where the EigenLayer contracts and Othenic contracts responsible for operator rewards are deployed. Additionally, the L2 Polygon [Amoy](https://amoy.polygonscan.com/) network hosts contracts that validate attester signatures and store the current price and its timestamp.
:::

To become an operator in the RedStone AVS network, you’ll need to follow the three steps outlined below.
To become an operator in the RedStone AVS network, you’ll need to follow the four steps outlined below.

## Step 1: Registering as an Operator

Expand All @@ -31,7 +31,13 @@ After executing the command, the following information will be required:
- **Operator's Private Key**: the private key must be provided to authenticate and secure the operator account. The private key should be provided twice: as a private key and as a signing key.
- **AVS Governance Contract Address**: the following contract address should be entered: [0xBA7A7CaEE3b1ed84a98dBc20Ea20fe21FE7D557e](https://holesky.etherscan.io/address/0xBA7A7CaEE3b1ed84a98dBc20Ea20fe21FE7D557e).

## Step 2: Preparing the Configuration File
## Step 2: Getting Whitelisted as an Operator

To finalize your eligibility as an operator, you must be added to the operator whitelist.

Join the designated Telegram channel for AVS operators: https://t.me/+DlrNvuknRXM3MDgx, and contact the administrators through the channel to submit your request.

## Step 3: Preparing the Configuration File

The next step involves creating a configuration file that will define the essential parameters needed for the operator to function correctly within the RedStone AVS network.
This configuration file, named `.env`, should contain the following content:
Expand Down Expand Up @@ -65,7 +71,7 @@ Below is an explanation of each field and information on which fields need to be
The fields marked with comments (#) need to be filled in with the appropriate values specific to the operator’s setup.
:::

## Step 3: Running the Operator
## Step 4: Running the Operator

To operate within the RedStone AVS network, two Docker images are required: [Attester](/docs/avs/service-components#attester) and [Validation API](/docs/avs/service-components#validation-api).
These images can be launched using the following Docker Compose configuration:
Expand Down
Loading