.kred TLD to Verified Multisig ControllerThis Executable Proposal requests that the ENS DAO assign ownership of the .kred top-level domain (TLD) to the multisig wallet:
0xb9ef2c160D908A4F7a9DFcdba46662C4a7EC4FD9
The proposing entity already owns and operates the ICANN .kred TLD and has demonstrated authoritative control of the DNS registry by publishing the ENS verification TXT record:
_ens.nic.kred TXT "a=0xb9ef2c160D908A4F7a9DFcdba46662C4a7EC4FD9"
This satisfies the ENS DNS-based proof-of-ownership mechanism and confirms legitimate authority over .kred.
The .kred top-level domain is an active ICANN TLD. Establishing .kred within ENS via DNS-verified ownership expands ENS’s integration with traditional DNS namespaces and supports unified Web2 + Web3 identity infrastructure.
Benefits include:
The target controller is a multisig wallet, ensuring secure and decentralized stewardship.
The authoritative DNS TXT record published is:
_ens.nic.kred TXT "a=0xb9ef2c160D908A4F7a9DFcdba46662C4a7EC4FD9"
This demonstrates:
.kred zone.kred to the supplied walletThis proposal instructs the ENS Root contract to assign ownership of .kred to the verified multisig.
setSubnodeOwner( bytes32(0), // The root node keccak256("kred"), // Label hash for .kred 0xb9ef2c160D908A4F7a9DFcdba46662C4a7EC4FD9 // Verified controller multisig );
Effects:
.kred ENS ownershipAssigning .kred to a multisig ensures secure long‑term stewardship and aligns with ENS precedent such as the .ceo TLD assignment.
The proposer has demonstrated verified ICANN authority via DNS TXT record publication, meeting ENS governance expectations for TLD integration.
ACTIVE