Skip to content

Commit 80cfc58

Browse files
MadelineAuMadelineAu
committed
Added registering with Fireblocks
1 parent 5a77545 commit 80cfc58

File tree

7 files changed

+118
-6
lines changed

7 files changed

+118
-6
lines changed

‎docs/products/eigenlayer/concepts/eigenlayer-overview.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The core components of the EigenLayer protocol include:
4545

4646
Get started with EigenLayer:
4747
- [Restake on EigenLayer](../restakers/concepts/overview)
48-
- [Register as an Operator](../operators/howto/operator-installation)
48+
- [Register as an Operator](../operators/howto/registeroperators/operator-installation.md)
4949
- [Build an AVS](../developers/concepts/avs-developer-guide)
5050
- Join our Ecosystem: [Discord](https://discord.com/invite/eigenlayer), [Twitter](https://twitter.com/eigenlayer)
5151

‎docs/products/eigenlayer/operators/howto/registeroperators/_category_.json‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
{
2+
"position": 1,
3+
"label": "Install and Register Operators"
4+
}

docs/products/eigenlayer/operators/howto/operator-installation.md renamed to docs/products/eigenlayer/operators/howto/registeroperators/operator-installation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
sidebar_position: 1
3-
title: Install and register Operators
3+
title: Install and Register Operators
44
---
55

66
# Installation and Registration

‎docs/products/eigenlayer/operators/howto/registeroperators/register-operator-with-fireblocks.md‎

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
---
2+
sidebar_position: 2
3+
title: Install and Register Operators using Fireblocks
4+
---
5+
6+
The steps below specify how to onboard to EigenLayer and connect to an AVS when using [Fireblocks](https://www.fireblocks.com/).
7+
8+
## 1. Install the EigenLayer CLI
9+
10+
Follow the steps in [Node Operator Checklist](operator-installation.md#node-operator-checklist) and [CLI Installation](operator-installation.md#cli-installation).
11+
12+
## 2. Create Firebocks Key
13+
14+
In your Fireblocks console, create a ETH-type key to be your Operator address.
15+
16+
## 3. Fund the Operator Account
17+
18+
In Fireblocks, retrieve the deposit address of your Operator key. The deposit address is the ECDSA public key of your Operator.
19+
20+
Fund the Operator account:
21+
22+
• On the Sepolia testnet: [Use a faucet](../../../restakers/restaking-guides/testnet/obtaining-testnet-eth-and-liquid-staking-tokens-lsts.md#obtain-sepolia-eth-sepeth-via-a-faucet).
23+
24+
• On Mainnet: Maintain at least 1 ETH in your Operator account.
25+
26+
## 4. Create Operator Configuration
27+
28+
Run:
29+
30+
```
31+
eigenlayer operator config create
32+
```
33+
34+
A prompt is displayed.
35+
36+
```
37+
Would you like to populate the operator config file?
38+
```
39+
40+
Select No.
41+
42+
## 5. Populate metadata.json
43+
44+
Open the generated `metadata.json` file. Populate as specified in [Operator Configuration and Registration](operator-installation.md#operator-configuration-and-registration).
45+
46+
Host the `metadata.json` file at a publicly accessible URL (for example, GitHub pages, S3, or IPFS).
47+
48+
## 6. Populate operator.yaml
49+
50+
Open the generated `operator.yaml` file.
51+
52+
### Operator Section
53+
54+
In the `Operator` section, specify:
55+
56+
```
57+
Operator:
58+
address: "<your-operator-address>"
59+
delegation_approver_address: "<your-delegation-approver>"
60+
metadata_url: "<link-to-your-metadata.json>"
61+
allocation_delay: <integer-blocks>
62+
el_delegation_manager_address: "<DelegationManager-proxy>"
63+
eth_rpc_url: "<Ethereum-RPC-URL>"
64+
chain_id: <chain-id>
65+
signer_type: "fireblocks"
66+
```
67+
68+
:::important
69+
The allocation delay specifies how many blocks must pass before any allocations become live in an Operator Set.
70+
For example, if the allocation dalay is set to 1200, and a Staker allocates funds to your Operator, the funds do no not
71+
become live before the 1200 block delay. The allocation delay applies globally across all Operator Sets and Strategies
72+
and can be any unsigned integer. Any change to the allocation delay has a 17.5 day delay before taking effect. See the [Safety Delays reference](../../../reference/safety-delays-reference.md) for
73+
more information.
74+
:::
75+
76+
#### EL Delegation Manager Address
77+
78+
You must configure the correct `DelegationManager` contract address for your environment. The Proxy addresses for
79+
`DelegationManager` for your environment (Mainnet, Sepolia, Hoodi, Holesky) are listed in the [GitHub repository](https://github.com/Layr-Labs/eigenlayer-contracts?tab=readme-ov-file#deployments).
80+
81+
Set the value for `el_delegation_manager_address` in your `operator.yaml` file to the appropriate address.
82+
83+
### Fireblocks Section
84+
85+
In the `fireblocks` section, specify:
86+
87+
```
88+
fireblocks:
89+
api_key: "<your-fireblocks-api-key>"
90+
secret_key: "<your-fireblocks-secret>" # Fireblocks secret key. If you are using AWS Secret Manager, this should be the secret name.
91+
base_url: "<your-fireblocks-api-base-url>"
92+
vault_account_name: "<your-vault-account-name>"
93+
secret_storage_type: "plaintext" # or "aws_secret_manager" if you are using AWS Secrets Manager
94+
aws_region: "<your-aws-secret-manager-region>" # if using AWS Secret Manager, leave blank if plaintext
95+
timeout: <integer-seconds>
96+
```
97+
98+
## 7. Register your Operator for EigenLayer
99+
100+
Run:
101+
102+
```
103+
eigenlayer operator register operator.yaml
104+
```

‎docs/products/eigenlayer/operators/howto/troubleshooting.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,11 @@ If you are getting this issue then either you are using a wrong rpc in your [ope
1313

1414
* Please make sure you have correct rpc node chosen for your network and that it is also reachable via your machine.
1515

16-
* Please find the correct smart contract addresses listed in the [Operator Installation](operator-installation.md) section.
16+
* Please find the correct smart contract addresses listed in the [Operator Installation](registeroperators/operator-installation.md) section.
1717

1818
#### How to resolve the error "No contract code at given address" imply?
1919

2020
Ensure that your operator is pointing to the correct RPC service and that it is accessible from your operator ([example](https://chainlist.org/)).
2121

2222
#### My operator's metadata (name, description, logo) is not showing up in the webapp
23-
Please make sure to comply with our metadata [guidelines](operator-installation.md#operator-configuration-and-registration)
23+
Please make sure to comply with our metadata [guidelines](registeroperators/operator-installation.md#operator-configuration-and-registration)

‎docs/products/eigenlayer/operators/reference/operator-faq.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,11 @@ Yes. We only support `.png` format and we strictly check the content of image. I
1919

2020
#### What if I lose access to my keys?
2121

22-
When you [create/import](../howto/operator-installation.md#create-and-list-keys) keys for the first time, it will ask a password to encrypt keys and once created, it will also show plaintext private key. Please make sure to backup the private key and the password. If you lose both you won't be able to get your keys back. If you lose the plaintext private key and still have your password you can run the export command to get your plaintext private key.
22+
When you [create/import](../howto/registeroperators/operator-installation.md#create-and-list-keys) keys for the first time, it will ask a password to encrypt keys and once created, it will also show plaintext private key. Please make sure to backup the private key and the password. If you lose both you won't be able to get your keys back. If you lose the plaintext private key and still have your password you can run the export command to get your plaintext private key.
2323

2424
#### What is my operator address?
2525

26-
After you [create/import](../howto/operator-installation.md#create-and-list-keys) ecdsa key you will be shown below log message
26+
After you [create/import](../howto/registeroperators/operator-installation.md#create-and-list-keys) ecdsa key you will be shown below log message
2727

2828
```
2929
? Enter password to encrypt the ecdsa private key:

‎docusaurus.config.js‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -357,6 +357,10 @@ const redirects = [
357357
from: '/operators/howto/claimrewards/claim-rewards-smart-contract',
358358
to: '/products/eigenlayer/operators/howto/claimrewards/claim-rewards-smart-contract',
359359
},
360+
{
361+
from: '/operators/howto/operator-installation',
362+
to: '/products/eigenlayer/registeroperators/operator-installation',
363+
},
360364

361365
// Fix typo: confirgurerewards -> configurerewards (handles both old typo and corrected version)
362366
{

0 commit comments

Comments
 (0)