What Are Web3 Domains? Names, Records and Wallet Identity

A Web3 name gives people a readable way to identify an address or profile in applications that support its naming system.

Start with the job you need done

For example, someone may want a memorable name for receiving payments, a public identity across apps, or an address for decentralized website content. These are different tasks. Your choice should follow the apps and networks you actually use.

Understand the three layers

1. The name: a readable identifier such as an ENS name.
2. The records: information associated with that name, such as an address.
3. The app: the wallet or website that reads and uses those records.

A name is useful when the receiving app can interpret it correctly. Treat registration, record setup and app compatibility as separate checks.

A practical first decision

Write down your main wallet, network and intended use. Then compare services against those requirements, including their full cost over the time you expect to keep the name.

A small example

Imagine that Maya wants a readable identity for her project. First she lists the wallet and apps her community already uses. Next she checks which naming services those apps recognize. Finally she compares registration terms and the steps for maintaining the name. This produces a more useful shortlist than simply choosing the shortest available word.

Questions worth answering before you choose

• Purpose: Is this primarily a payment alias, a profile identity or a website destination?
• Audience: Where will people encounter and use the name?
• Maintenance: Who will control it and check its registration status?
• Portability: Which parts of your setup remain useful if you change apps?

You can use more than one name for different purposes. Start with a clear reason for each one, and keep a record of its owner, renewal responsibilities and configuration.