[Executable] Transfer .locker TLD to Orange Domains LLC

## Abstract

Orange Domains LLC is requesting the transfer of ownership of the “locker” Top Level Domain (TLD) in the ENS ecosystem. As the ICANN-accredited registry operator of the .locker TLD and controller of the .locker namespace on the Bitcoin Naming System (BNS), Orange Domains operates a comprehensive Web2-to-Web3 bridge that launched in general availability on October 23rd, 2024.

Our .locker solution enables seamless connection between traditional DNS domain names and Web3 digital identities, with Web2 domains registered through over 50 ICANN-accredited registrars (including GoDaddy and NameCheap) and corresponding Web3 identities minted on Bitcoin’s Stacks L2. Currently supporting Bitcoin, Stacks, Ethereum, and Solana address resolution, we seek ENS integration to provide .locker users with full utility across Ethereum’s vast ecosystem through native ENS resolution and reverse resolution capabilities.

This proposal aligns with ENS’s mission to integrate with existing internet infrastructure while bringing millions of Web2 users into Web3 through trusted, familiar registration channels.

## Proof of Ownership

To demonstrate our legitimate ownership of the .locker TLD and authorization for this transfer request, Orange Domains has set a TXT record on the official .locker DNS infrastructure:

DNS Record: _ens.nic.locker
Value: dotlocker.eth
Verification Command: dig TXT _ens.nic.locker

This record confirms our control over the .locker DNS namespace and our intention to delegate ENS management to our designated Ethereum address, following the same verification pattern established in previous TLD transfer proposals.

## Specification

### Primary Transfer Action

This proposal transfers ownership of the “locker” TLD to Orange Domains LLC by calling setSubnodeOwner on the ENS Root contract at root.ens.eth, passing keccak256(“locker”) as the label parameter and dotlocker.eth as the owner parameter.

### Technical Implementation Architecture

Multi-Chain Resolution System: Orange Domains will implement a hybrid resolver architecture that coordinates resolution across our existing multi-chain infrastructure (Bitcoin, Stacks, Solana) with new ENS capabilities on Ethereum.

Offchain Resolver with CCIP Read: We will deploy an ENS resolver utilizing EIP-3668 (CCIP Read) to enable gasless resolution while maintaining synchronization with our existing Web2 DNS infrastructure and multi-chain Web3 systems. This approach ensures consistency across all supported blockchain networks.

Gateway Implementation: Our existing resolution infrastructure will be extended with an ENS-compatible gateway that can serve Ethereum addresses, text records, and other ENS-standard data types while coordinating with our Bitcoin/Stacks resolution services.

### Community and Ecosystem Benefits

Web2 User Onboarding: This integration enables millions of users registering .locker domains through familiar Web2 channels (GoDaddy, NameCheap, etc.) to automatically gain ENS functionality, significantly expanding ENS adoption beyond crypto-native users.

Cross-Chain Utility: .locker domains will serve as universal identifiers resolving consistently across Bitcoin, Stacks, Ethereum, and Solana, providing users with unified identity across major blockchain ecosystems.

Infrastructure Alignment: Following ENS’s stated goal that “for ENS to succeed, it must integrate with existing infrastructure,” this proposal bridges traditional DNS registration with ENS functionality through established ICANN processes.

Registrar Network Expansion: Leveraging our relationships with 50+ ICANN-accredited registrars creates new distribution channels for ENS-compatible domains through traditional domain registration workflows.

### Migration and User Experience

Seamless Integration: Existing .locker domain holders will automatically gain ENS resolution capabilities without requiring additional registration or migration steps.

Backward Compatibility: All existing .locker functionality (Bitcoin, Stacks, Solana resolution) will be preserved and enhanced with new Ethereum capabilities.

Subdomain Management: Orange Domains will implement subdomain registration and management that maintains consistency across all supported blockchain networks while providing gasless updates through our offchain infrastructure.

## Governance Alignment

This proposal directly supports ENS’s constitutional principles by:

  • Expanding Access: Bringing Web2 users into Web3 through trusted, familiar registration channels
  • Infrastructure Integration: Building bridges between traditional internet infrastructure and decentralized naming
  • Utility Enhancement: Providing cross-chain resolution that increases the practical value of decentralized naming
  • Responsible Stewardship: Leveraging established ICANN accreditation and regulatory compliance to ensure professional namespace management

## Transaction Details

This proposal transfers the ownership of the “locker” TLD to Orange Domains by calling setSubnodeOwner on root.ens.eth (0xaB528d626EC275E3faD363fF1393A41F581c5897) with keccak256("locker") as the label, and dotlocker.eth as the owner.

## Conclusion

Orange Domains’ management of the .locker TLD in ENS represents a significant opportunity to bridge Web2 and Web3 naming infrastructure while maintaining the highest standards of professional registry operation. Our ICANN accreditation, existing multi-chain infrastructure, and extensive registrar partnerships position us to bring unprecedented scale to ENS adoption through traditional domain registration channels.

We respectfully request the ENS community’s support for this proposal, which will enhance utility for millions of potential users while advancing ENS’s mission of universal, decentralized naming.

6 Likes

Nice.

2 Likes

ENS has a standing policy that any DNS TLD owner can have the TLD in ENS transferred to an address of their choosing if they can prove ownership, so this seems uncontroversial. I’m excited to see what you build with it.

8 Likes

It’s exciting to see .locker build out their ENS integration.

I have created a draft proposal via Tally.

I’d appreciate a review of the call data by @blockful.

The plan is to post this on Monday afternoon, August 4, ahead of the all-delegates call on Tuesday.

I intentionally left out the EP number, as the docs automatically assign one when the proposal is submitted onchain. This follows the precedent set by Nick in his last couple of proposals.

6 Likes

Hey @dotlocker, thanks for the proposal, looking forward to see this integration live.

@slobo.eth Thanks for creating the draft proposal.

Draft calldata analysis

The calldata gives complete ownership of .locker TLD to dotlocker.eth (a 1/2 multisig), so it can configure whatever resolver it wants to make an offchain resolver as mentioned in the proposal.

The test can be found here, and verified by cloning the repo and running forge test --match-path "src/ens/proposals/ep-locker-tld/calldataCheck.t.sol".

Other considerations

  • Also important to mention that the ownership can still be claimed back by the DAO in the future.
  • That might be a silly question, but is there a guarantee that a TXT record on _ens.nic.locker means ownership of the DNS TLD? .locker domains are available to buy.
2 Likes

Thanks @blockful.

That might be a silly question, but is there a guarantee that a TXT record on _ens.nic.locker means ownership of the DNS TLD? .locker domains are available to buy.

Under ICANN’s TLD compliance policies the Network Information Center (NIC) domain name, nic.TLD, must and can only be activated by the Registry Operator (i.e. Orange Domains LLC for .locker - .locker Registry Agreement). These nic.TLD domains are locked, cannot be transferred, and are fully controlled by each registry operator including the management of DNS records.

Another example is https://nic.box/. Intercap owns and controls this domain name under ICANN policy.

5 Likes

The proposal is live. Onchain voting possible at the following frontends:

Tally
Agora
Community version by @gregskril

3 Likes

Thanks for the explanation @dotlocker.

Here is the verification for the onchain proposal, same calldata from the draft. @slobo.eth

1 Like

Hi Slobo,

Onchain voting is also now live on DeGov.AI

Just today, WE announced our support for ENS here

Constructive criticism welcome, open to demo the unique features of our product(AI Agent Voting and Sentiment Analysis), and discuss in whatever shape or form.

WE shipped this in under a month, and we are committed to do even more.

Let’s Grow.
PD.