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
1. Install aragonCLI globally (specifying the package version because latest seems to be broken for some machines):
56
69
```sh
@@ -62,10 +75,12 @@ Run it and make sure that it is connected to the correct chain.
62
75
63
76
3. Inspect the DAO with the following
64
77
```sh
65
-
aragon dao apps <DAO kernel address> --use-frame
78
+
aragon dao apps 0x593ea926ee9820a933488b6a288433c387d06dba --use-frame
79
+
```
80
+
Review that the displayed information is correct.
81
+
```sh
82
+
aragon dao apps 0x9B64177757a0BD2A042446C8d910526476B7Bf57 --use-frame
66
83
```
67
-
For example, you can use `0x825cc178f0510de72c8d3af4be69917935b3d269` on Rinkeby (**note that this may not be identical to the final version**).
68
-
Review the displayed information is correct.
69
84
70
85
4. In (3), you should have seen Api3Voting apps with the ID `0x323c4eb511f386e7972d45b948cc546db35e9ccc7161c056fb07e09abd87e554`.
71
86
This is derived as `namehash("api3voting.open.aragonpm.eth")`.
@@ -80,13 +95,18 @@ Then check the source code at this implementation address using Etherscan and ve
80
95
81
96
6. Verify that the ACL (Access Control List) is configured correctly
82
97
```sh
83
-
aragon dao acl <DAO kernel address> --use-frame
98
+
aragon dao acl 0x593ea926ee9820a933488b6a288433c387d06dba --use-frame
99
+
```
100
+
101
+
You can compare with API3DAOv1
102
+
```sh
103
+
aragon dao acl 0x9B64177757a0BD2A042446C8d910526476B7Bf57 --use-frame
84
104
```
85
105
86
106
7. Check that the following values are initialized correctly
87
107
-`api3Pool` and the voting parameters (`supportRequiredPct` and `minAcceptQuorumPct`) at the Api3Voting apps
88
108
-`api3Token`, `timelockManager`, `agentAppPrimary`, `agentAppSecondary`, `votingAppPrimary` and `votingAppSecondary` at the pool contract
89
-
- If any claims manager contracts are set for the pool, they are audited and implemented to pay out claims in a trustless way with fail-safes such as payout limits (note that the pool will be deployed with no claims managers set initially)
109
+
- If any claims manager contracts are set for the pool, they are audited and implemented to pay out claims in a trustless way with fail-safes such as payout limits (note that the pool will be deployed with no claims managers set initially and the DAO does not allow proposals in the first epoch to set a claims manager)
0 commit comments