You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/0_internal/2_deploy_contracts.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ These contracts are not deployed by Aligned. Current EigenLayer contracts:
9
9
10
10
## Aligned Contracts
11
11
12
-
### Deploy Service Manager
12
+
### Set .env variables
13
13
14
14
To deploy the AlignedLayer contracts, you will need to set environment variables in a `.env` file in the same
15
15
directory as the deployment script (`contracts/scripts/`).
@@ -30,6 +30,8 @@ You can find an example `.env` file in [.env.example.holesky](../../contracts/sc
30
30
> [!Warning]
31
31
> All file paths must be inside the `script/` directory, as shown in `.env.example.holesky` because of `foundry`'s permissions to read and write files.
32
32
33
+
### Set DEPLOY_CONFIG_PATH file
34
+
33
35
You need to complete the `DEPLOY_CONFIG_PATH` file with the following information:
34
36
35
37
```json
@@ -61,12 +63,16 @@ You can find an example config file in [aligned.holesky.config.json](../../contr
61
63
>
62
64
> You can find the list of Holesky strategies for the `strategyWeights` field [here](https://github.com/Layr-Labs/eigenlayer-contracts?tab=readme-ov-file#current-testnet-deployment)
63
65
66
+
#### Multisig configuration
67
+
64
68
If you are using a Multisig for the contracts management (like upgrades or pauses), you need to set the Multisig address in the `permissions` sections.
65
69
66
70
For example, if you are using a Multisig for the `upgrader` permission, you need to set the Multisig address in the `upgrader` field.
67
71
68
72
Then run the following command:
69
73
74
+
### Deploy the contracts
75
+
70
76
```bash
71
77
make deploy_aligned_contracts
72
78
```
@@ -107,7 +113,9 @@ Once the contracts are deployed, you will see the following output at `OUTPUT_PA
107
113
}
108
114
```
109
115
110
-
### Deploy Batcher Payment Service
116
+
## Batcher Payments Service Contracts
117
+
118
+
### Set .env variables
111
119
112
120
To deploy the Batcher Payment Service contract, you will need to set environment variables in a `.env` file in the same
113
121
directory as the deployment script (`contracts/scripts/`).
@@ -126,6 +134,8 @@ The necessary environment variables are:
126
134
127
135
You can find an example `.env` file in [.env.example.holesky](../../contracts/scripts/.env.example.holesky)
128
136
137
+
### Set BATCHER_PAYMENT_SERVICE_CONFIG_PATH file
138
+
129
139
You need to complete the `BATCHER_PAYMENT_SERVICE_CONFIG_PATH` file with the following information:
130
140
131
141
```json
@@ -143,10 +153,13 @@ You need to complete the `BATCHER_PAYMENT_SERVICE_CONFIG_PATH` file with the fol
143
153
}
144
154
```
145
155
156
+
#### Multisig configuration
157
+
146
158
If you are using a Multisig for the contracts management (like upgrades or pauses), you need to set the Multisig address in the `permissions` sections.
147
159
148
160
For the batcher payment service, you can set the Multisig address in the `owner` field. This will allow the Multisig to upgrade and pause the contract with the Multisig.
0 commit comments