Skip to content

Commit

Permalink
Merge pull request #217 from ArbitrumFoundation/fredlacs-patch-1
Browse files Browse the repository at this point in the history
Update security-council-nominee-vetting.md
  • Loading branch information
DZGoldman authored Oct 4, 2023
2 parents b5794ce + ae11774 commit 0f7c75f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/security-council-nominee-vetting.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The address authorised to exclude and include addresses should be a multisig tha
- Is the address already a member of the opposite cohort? The contracts check that this was not the case at the time of creation, but manipulation in the Manager could cause this to be violated at a later time.
- Is the owner of the address able to create a signature of all chains where a Security Council is located that will be accepted by a Gnosis Safe?

If any of the above are false the Foundation should call `excludeAddress` to stop that address from proceeding to the next stage.
If any of the above are false the Foundation should call `excludeNominee` to stop that address from proceeding to the next stage.

### Including addresses

Expand All @@ -28,4 +28,4 @@ During the 14 day vetting period the Foundation should include new addresses if
2. Contenders who did not receive 0.2% threshold of votes should be included, in order of votes descending
3. If there still aren’t 6 nominees the Foundation may include any address they see fit

In the event that the Foundation does not fill these spots the DAO or Security Council will need to take action to remedy the situation.
In the event that the Foundation does not fill these spots the DAO or Security Council will need to take action to remedy the situation.

0 comments on commit 0f7c75f

Please sign in to comment.