Skip to content

Commit 5c6ca4f

Browse files
committed
docs: fix image indentation
1 parent c43ca45 commit 5c6ca4f

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

docs/multisig.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,6 @@ You can propose the upgrade transaction with the multisig using this calldata
3737
You should save this `calldata` for later use.
3838

3939
2) Start a transaction request on your multisig, clicking on `New transaction` -> `Interact with contracts`
40-
4140
![alt text](./images/multisig-1.png)
4241
![alt text](./images/multisig-2.png)
4342

@@ -50,28 +49,23 @@ jq -r ".addresses.alignedLayerProxyAdmin" contracts/script/output/sepolia/aligne
5049
```bash
5150
jq ".abi" contracts/out/ProxyAdmin.sol/ProxyAdmin.json | pbcopy
5251
```
53-
5452
![alt text](./images/multisig-3.png)
5553
![alt text](./images/multisig-4.png)
5654

5755

5856
5) Scroll down and Fill the `ETH Value` as 0
59-
6057
![alt text](./images/multisig-5.png)
6158

6259
6) Paste the calldata saved on step `1` and paste it on the `Data` box
63-
6460
![alt text](./images/multisig-6.png)
6561

6662
7) Finish creating the transaction
67-
6863
![alt text](./images/multisig-7.png)
6964
You can previously simulate the tx to make sure everything is OK.
7065
![alt text](./images/multisig-8.png)
7166
![alt text](./images/multisig-9.png)
7267

7368
8) Now in your transactions, you should be able to see the newly created Tx
74-
7569
![alt text](./images/multisig-10.png)
7670

7771
9) If the transaction is correctly created, you have to wait until required Multisig member sign the transaction to send it.

0 commit comments

Comments
 (0)