[EP 6.8] [Executable] Revoke root controller role from legacy ENS multisig

DAO-Wide Active Proposal
1

[6.8] [Executable] Revoke root controller role from legacy ENS multisig

Status Active
Votes Tally

Abstract

We have identified that the legacy ENS multisig, which originally controlled ENS before the DAO was created, still has the ‘controller’ role on the ENS root. This means that a majority of multisig keyholders could create or replace any ENS TLD other than .eth. .eth is locked and cannot be modified by the DAO or anyone else.

In order to correct this oversight, this proposal revokes the legacy multisig’s controller role from the root contract.

Specification

Call setController on the ENS Root contract at 0xaB528d626EC275E3faD363fF1393A41F581c5897, passing in the address of the legacy multisig, 0xCF60916b6CB4753f58533808fA610FcbD4098Ec0.

Transactions

Address Value Function Argument Value
0xaB528d626EC275E3faD363fF1393A41F581c5897 0 setController address 0xCF60916b6CB4753f58533808fA610FcbD4098Ec0
controller false
3 Likes
2

Apologies for skipping the temp-check phase on this; with this being a security issue (however remote) and the very low risk and contentiousness, I thought it best to post this right away.

1 Like
3

Looks okay I guess. Weird this was not noticed earlier. The function matches and should work. Would appreciate a similation from blockful too.

1 Like
4

Seems reasonable.

FYI, You have reused 6.7 in the actual proposal you have submitted: Tally | ENS | [EP6.7] [Executable] Revoke root controller role from legacy ENS multisig

5

'Yes, apologies - I typoed it onchain.