[EP 6.7] [Executable] Transfer .ceo TLD to the DNSSEC registrar

DAO-Wide Active Proposal
1

description: Transfer ownership of the .ceo top-level domain to the DNSSEC registrar

[Executable] Transfer .ceo TLD to the DNSSEC registrar

Status Active
Discussion Thread Discuss
Votes Tally

Abstract

The .ceo TLD, formerly owned by Kred Pty, has since been acquired by XYZ. Prior to the formation of the DAO, the previous owner asked for .ceo to be delegated to a custom address so they can manage a bespoke DNS integration. The new owner has requested that this change be undone, and that ownership of .ceo be reverted to the DNSSEC registrar so owners of .ceo TLDs can use the standard integration to claim their names on ENS.

To prove ownership of .ceo and their intention that we action this request, they have set a TXT record on _ens.nic.ceo to the address of the DNSSEC registrar, 0xB32cB5677a7C971689228EC835800432B339bA2B. This can be verified with the following command:

dig TXT _ens.nic.ceo

Specification

Call setSubnodeOwner on the ENS Root contract at 0xaB528d626EC275E3faD363fF1393A41F581c5897, passing in the keccak256 hash of ceo and the address of the DNSSEC registrar, 0xB32cB5677a7C971689228EC835800432B339bA2B.

Transactions

Address Value Function Argument Value
0xaB528d626EC275E3faD363fF1393A41F581c5897 0 setController address 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7
controller true
0xaB528d626EC275E3faD363fF1393A41F581c5897 0 setSubnodeOwner label 0xa695017707ee0c04095f723270b3c315654d16e337ad54039175a4b000894676
owner 0xB32cB5677a7C971689228EC835800432B339bA2B
18 Likes
2

Awesome to see this @nick.eth, thanks for coordinating and putting it forward.

Because this is a straightforward action based on the request from the provable owner, I’d expect this to be a purely administrative vote with full support.

2 Likes
3

I was interested in reading more about this in the linked Discussion Thread above, but it says the page doesn’t exist or is private. Is there a way to read more about this?

4

Sorry, I forgot to edit that part of the template. This is the discussion thread.

5

Freaking awesome

6

This is now live on Tally!

I had to make a last minute change to set the DAO wallet as a controller on the root contract - since we’ve never manually updated a TLD before.

2 Likes
7

The simulation and tests of EP 6.7 can be found here. Calldata matched the proposal description as expected. The proposal was simulated by passing, executing, and asserting the difference between states after the operations.

This can be checked by cloning the repo and running:
forge test --match-path src/ens/proposals/ep-6-7/* -vvvv

1 Like
8

Thanks for the simulation data!

@nick.eth any more info on how it was acquired by xyz? Am just curious.

9

No idea! I just verified current ownership, but don’t know how the name came to be acquired.