How To Use The D3 Platform
Together with our partners, D3 is developing futureproof, interoperable digital identities. In order for Web3 to be truly ‘web,’ it needs to offer backward compatibility and integration with existing Internet infrastructure, starting with the Domain Name System (DNS). To enable this, D3 provides the D3 Platform and works directly with partners to apply for and obtain their own Top-Level Domains (TLDs) on the DNS and bridging this with Web3 infrastructure.
The D3 Platform is made up of technologies and expert support for partners, including:
D3 Name System: an easy-to-use yet secure name system infrastructure
D3 Marketplace: an online marketplace for communities to buy and sell names
D3 Connect: a developer SDK that simplifies name resolution (DNS, ENS, other) for consumer wallets and decentralized applications (DApps) using the D3 Platform
If your organization is not already working with D3, you can apply to become a partner here.
D3 Name System Quickstart
The guide below illustrates how to get started with the D3 Platform and use D3’s Name System infrastructure to deliver a simple, compliant identity solution for your ecosystem - whether you are starting with a brand new top-level domain name or migrating from an existing name system.
Step 1 - Pick a Name Extension
There are various guidelines and rules to follow when identifying a name extension or top-level domain (TLD). Our team of experts have decades of combined experience to help you pick the right extension and get started on your journey to TLD approval.
Step 2 - Start the Reservation Process
Once you have identified your intended extension/s, the D3 team will assist you in validating it against a list of existing, reserved or restricted top-level domains.
Step 3 - Blockchain to Deploy Smart Contract
D3’s default Name Token smart contract can be deployed on any EVM-Compatible blockchain, including Polygon, Optimism, Arbitrum. If another blockchain is required, this will necessitate a custom smart contract. Contact your D3 Integration Representative for other custom blockchain integration options.
Step 4 - Ensure Compliance
D3 Name Tokens include a `*` separator as opposed to a `.` Name Tokens are limited to Web3 functionality. In order for a name to be considered a valid domain, it needs to be approved by ICANN and be compatible with the DNS.
D3 collects some basic contact information from the registrant when they register a name. This can include individual contact information for a Registrant, Administrator, a Technical Contact, and a Billing contact.
D3 requires Users who purchase Name Tokens pay annual subscription fees, just like domain names, to reserve and utilize their digital identities. Users may manage their subscription and name tokens through the D3 Registrar portal.
Name Collision occurs when the same name is used in different contexts or by different entities, leading to potential conflicts. This can happen when a domain name that is already in use within a private network or for non-public purposes is later registered for public use on DNS. Name collisions can result in confusion, unintended access to private resources, or security risks. D3 ensures that Name Collision does not occur, all names that are issued are uniquely owned by that entity.
Step 5 - Marketplace Distribution
D3 offers partners a host of specialized tools and a dedicated dashboard to monitor and manage your names on the D3 Marketplace.
Migrating Existing Name Systems To D3’s Platform
The guide below illustrates the process to migrate existing name systems to D3’s name infrastructure and ensure your identity solution maintains the necessary industry compliance.
Step 1 - Freeze Token issue
The existing name service issuing new Name Token NFTs should be frozen to prevent future minting and transfer of tokens.
Step 2 - Airdrop New D3 Tokens to Owners of Existing Names
A snapshot of all existing name tokens will be taken including the registered name, and owner’s wallet address.
The list of existing names will be uploaded to D3, effectively reserving those names for their rightful owners.
All existing token owners will be airdropped new name tokens minted from the D3 Smart Contract.
For ICANN compliance, some owners will not be airdropped a new name token either due to:
1) The registered name is not a valid domain name
2) The registered name is on a blacklisted/trademark list
Step 3 - Migrate to new contract
Existing name token metadata should be updated to point to the newly minted token and indicate the token is no longer valid.
Support utility of existing name resolution to wallet providers or DApps, if applicable.
Direct routing from the old name services to D3 for previously issued and newly issued Name Tokens.
Step 5 - Marketplace Distribution
Partners can now offer compliant names through the D3 Marketplace, which includes a host of specialized partner tools and a dedicated dashboard to monitor and manage names.
Last updated