Skip to content

Commit ef2d9ef

Browse files
committed
docs: add titles
1 parent 8053639 commit ef2d9ef

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

docs/0_internal/2_deploy_contracts.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ These contracts are not deployed by Aligned. Current EigenLayer contracts:
99

1010
## Aligned Contracts
1111

12-
### Deploy Service Manager
12+
### Set .env variables
1313

1414
To deploy the AlignedLayer contracts, you will need to set environment variables in a `.env` file in the same
1515
directory as the deployment script (`contracts/scripts/`).
@@ -30,6 +30,8 @@ You can find an example `.env` file in [.env.example.holesky](../../contracts/sc
3030
> [!Warning]
3131
> 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.
3232
33+
### Set DEPLOY_CONFIG_PATH file
34+
3335
You need to complete the `DEPLOY_CONFIG_PATH` file with the following information:
3436

3537
```json
@@ -61,12 +63,16 @@ You can find an example config file in [aligned.holesky.config.json](../../contr
6163
>
6264
> 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)
6365
66+
#### Multisig configuration
67+
6468
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.
6569

6670
For example, if you are using a Multisig for the `upgrader` permission, you need to set the Multisig address in the `upgrader` field.
6771

6872
Then run the following command:
6973

74+
### Deploy the contracts
75+
7076
```bash
7177
make deploy_aligned_contracts
7278
```
@@ -107,7 +113,9 @@ Once the contracts are deployed, you will see the following output at `OUTPUT_PA
107113
}
108114
```
109115

110-
### Deploy Batcher Payment Service
116+
## Batcher Payments Service Contracts
117+
118+
### Set .env variables
111119

112120
To deploy the Batcher Payment Service contract, you will need to set environment variables in a `.env` file in the same
113121
directory as the deployment script (`contracts/scripts/`).
@@ -126,6 +134,8 @@ The necessary environment variables are:
126134

127135
You can find an example `.env` file in [.env.example.holesky](../../contracts/scripts/.env.example.holesky)
128136

137+
### Set BATCHER_PAYMENT_SERVICE_CONFIG_PATH file
138+
129139
You need to complete the `BATCHER_PAYMENT_SERVICE_CONFIG_PATH` file with the following information:
130140

131141
```json
@@ -143,10 +153,13 @@ You need to complete the `BATCHER_PAYMENT_SERVICE_CONFIG_PATH` file with the fol
143153
}
144154
```
145155

156+
#### Multisig configuration
157+
146158
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.
147159

148160
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.
149161

162+
### Deploy the contracts
150163

151164
Then run the following command:
152165

0 commit comments

Comments
 (0)