[Executable] Enable Root and Registrar Security Controllers

What permissions can the Council revoke? I thought it was just the ability to cancel a malicious proposal.

I also disagree a bit with the quoted statement - when the council was voted in under EP 5.13, it was under the assumption that its limited power could be revoked at any time by anyone after 2 years. Unlike the original Security Council design, where anyone could permissionlessly revoke the council’s authority after 2 years, this proposed power would require a full governance proposal to remove - a much higher bar. We should be sure to clarify that.

To be clear, I support this proposal’s initiative and I encourage everyone to support it. But, I think it should be amended to clearly state its purpose and effects, which are to expand the Security Council’s role beyond its initial mandate and without the same built-in sunset. We’ve set a high bar for proposal clarity lately - let’s hold this one to the same standard.


@netto.eth’s comment here brings up another interesting point: After the council was first voted in, there was a request for compensation. In response, we delivered 2-year vesting contracts with 1,000 ENS to all 8 members.

We should ensure the existing Security Council members would be willing to undertake this additional responsibility for the previous compensation amount. If not, we need to establish what the Council members do want and make that a part of this proposal, before the proposal goes live.

Ideally, the council members would make any additional compensation requests known before the proposal goes live, rather than after.

2 Likes