Skip to content

Commit bbcd175

Browse files
committed
docs: beter start of document
1 parent 4a6b98a commit bbcd175

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

docs/multisig.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,26 @@
1-
This file temporarily holds the previous multisig docs:
2-
3-
## Multisig Usage
4-
51
> [!WARNING]
62
> Safe Multisig Wallet is not currently supported in Holesky Testnet.
3+
> This guide is ran in Sepolia
4+
5+
# Multisig
76

8-
You can create a Multisig wallet using [Safe](https://safe.global/). For this guide, I have created a 2/3 Multisig.
7+
In this guide we make an upgrade of Aligned Layer Service Manager contract using a multisig wallet. This is important to ensure not one party can do an upgrade, and helps ensure the team is not locked out of upgrading the network due to a loss of keys.
8+
9+
## Requirements
10+
- Multisig Wallet
11+
- You can create a Multisig wallet using [Safe](https://safe.global/). For this guide, I have created a 2/3 Multisig.
12+
- [jq](https://jqlang.github.io/jq/download/)
13+
14+
## Initial setup
915

1016
Once you have a Multisig, you can deploy the contracts using the Multisig wallet address as the upgrader, pauser, etc.
1117

1218
For this, you must set your Safe Multisig's address in the `contracts/script/deploy/config/sepolia/aligned.sepolia.config.json` config file. In case of the `deployer` permission, it is not recommended to set the multisig, as he will deploy many contracts and delegate ownership, it is best to set the address of a wallet with funds, which will be the one that deploys the contracts.
1319

1420
Then, in order to do some action that requires the Multisig Owner, for example upgrading the contract, you must do the following:
1521

22+
## Upgrading the contract
23+
1624
1) Deploy the new implementation by running:
1725

1826
```bash

0 commit comments

Comments
 (0)