.locker's Interoperable Domain Solution
The internet today is split across two parallel systems:
Web2, which relies on DNS, centralized registrars, and traditional web infrastructure.
Web3, which relies on blockchains, smart contracts, and decentralized identity.
Most domain systems live entirely in one world or the other. .locker is designed differently. It is an interoperable domain name system that connects Web2 and Web3 at the protocol level, allowing a single domain name to function across both ecosystems without fragmentation.
.locker as a Web2 Domain Name (ICANN + DNS)
At its foundation, .locker is a Web2 domain name. It is ICANN-accredited, meaning it follows the same global governance, standards, and policies as traditional domain extensions. From a Web2 standpoint, a .locker domain behaves exactly like any other top-level domain. It can be used for a website or email, transferred, and renewed.
.locker as a Web3 Digital Identity
In addition to DNS functionality, the same .locker domain can act as a Web3 digital identity. Instead of long hexadecimal wallet addresses, the .locker serves as a human-readable identifier on Bitcoin and Ethereum. This dual functionality allows one identifier to exist across Web2 and Web3 without duplication or conflict.
Minting on Bitcoin via Stacks
.locker is secured and minted on Bitcoin via a smart contract on Stacks Layer 2. Stacks allows .locker digital identities to be anchored to Bitcoin, immutable once minted, and verifiable onchain. By using Bitcoin as the settlement layer, .locker digital identities gain long-term durability and resistance to modification or censorship.
Resolution on Ethereum via ENS
.locker resolves on Ethereum, meaning it can be used as a digital identity to send and receive digital assets, as login credentials, and more. Resolution is handled through the Ethereum Name Service (ENS) resolver. Any decentralized app on Ethereum that uses the Ethereum resolver can be used with a .locker digital identity.
.locker Sync Application: Seamlessly Bridging Web2 and Web3
The technical bridge between these two systems is .locker’s sync application. Synchronization is what allows .locker to operate as a single, unified digital identity across two fundamentally different systems. And because .locker uses the sync application, DNS records aren’t changed or altered. It’s the domain registrant’s email address and the sync application that keeps everything aligned, not DNS.
Reserved Digital Identity at Registration
When a user registers a .locker domain name on Web2, the corresponding digital identity is automatically reserved on Bitcoin and Ethereum via BNS and ENS, respectively. No other party can mint or claim that digital identity, preventing namespace collisions. In effect, ownership on Web2 guarantees ownership on Web3, protecting digital identity from duplication or impersonation.
Registrar Portability Without Identity Breakage
.locker was designed to be user-friendly. If a .locker domain name is transferred to a different registrar, all DNS ownership changes will be completed as expected and digital identity connections remain intact. No reconfiguration is required- everything stays in place. Because .locker’s bridge to Web3 is at the TLD-level and not the registrar-level, continuity is preserved.
A Unified Domain and Digital Identity Model
.locker demonstrates a model where:
- DNS and blockchain naming systems are not competing
- Web2 and Web3 identities are not fragmented
- Ownership, transfer, and deletion are synchronized across both layers
Rather than forcing users to choose between Web2 and Web3, .locker shows how a single domain name can operate natively in both systems, using existing internet standards alongside blockchain infrastructure.
