Skip to content

Commit

Permalink
docs: update operator guide to v0.5.2 (#908)
Browse files Browse the repository at this point in the history
  • Loading branch information
JuArce authored Aug 30, 2024
1 parent 535f10e commit 6dec1ec
Showing 1 changed file with 13 additions and 2 deletions.
15 changes: 13 additions & 2 deletions docs/operator_guides/0_running_an_operator.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Register as an Aligned operator in testnet

> **CURRENT VERSION:**
> Aligned Operator [v0.4.0](https://github.com/yetanotherco/aligned_layer/releases/tag/v0.4.0)
> Aligned Operator [v0.5.2](https://github.com/yetanotherco/aligned_layer/releases/tag/v0.5.2)
> **IMPORTANT:**
> You must be [whitelisted](https://docs.google.com/forms/d/e/1FAIpQLSdH9sgfTz4v33lAvwj6BvYJGAeIshQia3FXz36PFfF-WQAWEQ/viewform) to become an Aligned operator.
Expand Down Expand Up @@ -41,7 +41,7 @@ Minimum hardware requirements:
To start with, clone the Aligned repository and move inside it

```bash
git clone https://github.com/yetanotherco/aligned_layer.git --branch v0.4.0
git clone https://github.com/yetanotherco/aligned_layer.git --branch v0.5.2
cd aligned_layer
```

Expand Down Expand Up @@ -107,6 +107,17 @@ Update the following placeholders in `./config-files/config-operator.yaml`:
`"<ecdsa_key_store_location_path>"` and `"<bls_key_store_location_path>"` are the paths to your keys generated with the EigenLayer CLI, `"<operator_address>"` and `"<earnings_receiver_address>"` can be found in the `operator.yaml` file created in the EigenLayer registration process.
The keys are stored by default in the `~/.eigenlayer/operator_keys/` directory, so for example `<ecdsa_key_store_location_path>` could be `/path/to/home/.eigenlayer/operator_keys/some_key.ecdsa.key.json` and for `<bls_key_store_location_path>` it could be `/path/to/home/.eigenlayer/operator_keys/some_key.bls.key.json`.

The default configuration uses the public nodes RPC, but we suggest you use your own nodes for better performance and reliability.
Also, from v0.5.2 there is a fallback mechanism to have two RPCs, so you can add a second RPC for redundancy.

```yaml
eth_rpc_url: "https://ethereum-holesky-rpc.publicnode.com"
eth_rpc_url_fallback: "https://ethereum-holesky-rpc.publicnode.com"
eth_ws_url: "wss://ethereum-holesky-rpc.publicnode.com"
eth_ws_url_fallback: "wss://ethereum-holesky-rpc.publicnode.com"
```
## Step 4 - Deposit Strategy Tokens
We are using [WETH](https://holesky.eigenlayer.xyz/restake/WETH) as the strategy token.
Expand Down

0 comments on commit 6dec1ec

Please sign in to comment.