bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 75쪽 중 1쪽
# ENS Documentation
import { Button } from '../components/ui/Button'
## 🪲 Bug Bounty Program
The ENS bug bounty program rewards anyone who finds a bug in covered ENS smart contracts and ENS Labs assets. This page provides a brief overview of the program which is operated by Immunefi and ENS Labs.
[See the full program](https://immunefi.com/bug-bounty/ens)
### Bounties 💸
Reward sizes are guided by the rules below, but are in the end, determined at the sole discretion of the ENS Labs team.
#### Smart Contracts
* **Critical**: up to $250,000 USD
* **High**: up to $150,000 USD
* **Medium**: up to $100,000 USD
#### Websites and Applications
* **Critical**: up to $50,000 USD
* **High**: up to $20,000 USD
* **Medium**: up to $5,000 USD
* **Low**: up to $1,000 USD
The ENS Labs team reserves the right to adjust bounty amounts at any time in the future.
## Building with AI
ENS provides tools and resources for developers building with large language models (LLMs) and AI assistants. Whether you're using AI to help write code, building agentic applications, or integrating ENS into AI-powered products, these resources will help.
### Plain Text Documentation
LLMs work best with plain text content that has fewer formatting tokens. ENS hosts machine-readable versions of this documentation following the emerging [llms.txt standard](https://llmstxt.org/).
| File | Description |
| -------------------------------------------------------- | ------------------------------------------------ |
| [/llms.txt](https://docs.ens.domains/llms.txt) | Concise overview of ENS documentation with links |
| [/llms-full.txt](https://docs.ens.domains/llms-full.txt) | Complete documentation in plain text format |
You can provide these URLs to AI assistants or include them in your RAG (Retrieval-Augmented Generation) pipelines to give your AI tools up-to-date knowledge about ENS.
#### Example Usage
When working with an AI assistant, you can reference these files directly:
```
Please read https://docs.ens.domains/llms.txt to learn about ENS,
then help me integrate ENS name resolution into my application.
```
### Context7 MCP
[Context7](https://context7.com) provides a Model Context Protocol (MCP) server that gives your AI coding assistant access to up-to-date ENS documentation. Once installed, you can simply ask your AI to use Context7 when working on ENS integrations.
#### Installation
Install the Context7 MCP in your preferred AI coding tool:
:::code-group
```bash [Claude Code]
claude mcp add context7 -- npx -y @upstash/context7-mcp
```
```json [Cursor (~/.cursor/mcp.json)]
{
"mcpServers": {
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp"]
}
}
}
```
```json [Windsurf]
{
"mcpServers": {
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp"]
}
}
}
```
:::
#### Example Prompts
Once Context7 is connected, you can use prompts like:
```
Add ENS name resolution to this address input field. Use context7.
```
```
Show me how to fetch a user's avatar from their ENS name. Use context7 for ensdomains/docs.
```
```
Help me implement reverse resolution to show ENS names instead of addresses. Use context7.
```
The key is adding "use context7" to your prompt, which tells your AI assistant to fetch the latest ENS documentation before responding.
### AI Chat Assistant
Every page in this documentation includes an AI-powered chat assistant in the bottom right corner. Powered by [Cookbook](https://ai.cookbook.dev/), this assistant can:
* Answer questions about ENS concepts and implementation
* Help you navigate the documentation
* Provide code examples and explanations
* Assist with debugging ENS integrations
Click the chat icon in the bottom right corner of any page to get started.
### Community MCP Servers
The community has built additional MCP servers that may be useful for ENS and greater Ethereum ecosystem development:
* **[ETHID MCP](https://ethidentitykit.com/docs/ai-tools/ethid-mcp)** - Tools for working with ENS and EFP
* **[Ethereum MCP](https://github.com/gskril/ethereum-mcp)** - General-purpose EVM tools including ENS resolution, ABI parsing, and more
* **[ENS MCP by Namespace](https://github.com/thenamespace/ens-mcp)** - Lets AI agents query ENS names, subnames, ownership, profiles, pricing, availability, and history.
These are independently maintained by community members. Check their documentation for installation instructions and available features.
### Tips for AI-Assisted Development
When building ENS integrations with AI assistance:
1. **Use the full docs** - For comprehensive context, use `/llms-full.txt` in your prompts
2. **Specify your stack** - Mention which library you're using ([viem](https://viem.sh), [ethers.js](https://docs.ethers.org/), [ENSjs](https://github.com/ensdomains/ensjs)) for more relevant code examples
3. **Ensure ENSv2 readiness** - Point your AI to the [ENSv2 readiness guide](/web/ensv2-readiness) to make sure your integration is compatible
### Get Help
For human support, join the [ENS Developers Telegram group](https://t.me/+aLmF83si62ZhOGNh).
### See Also
* [Getting Started with ENS](/web) - Introduction to integrating ENS
* [Preparing for ENSv2](/web/ensv2-readiness) - Ensure your app works with ENSv2
* [Tools & Libraries](/web/libraries) - SDKs and libraries for ENS development
## 📝 Changelog
This page contains a list of changes and events that happened to the ENS protocol & ecosystem.
### Dentity Announcement
On August 21st, 2024 the ENS Labs team announced a new integration with Dentity, an independent identity provider that allows users to verify information and share it on their ENS profile.0
This integration leverages a draft ENSIP that allows for W3C Verifiable Credentials to be stored inside ENS profiles.
### ENSv2 Announcement
On March 28th, 2024 the ENS Labs team announced our plans and roadmap for scaling ENS to the entire internet and beyond.
This involves migrating .eth registrations to a brand new system, in addition to improving support for existing L2 solutions.
You can read more [on our blog](https://blog.ens.domains/post/ensv2), [on X](https://twitter.com/ensdomains/status/1795440186513576318), and [the forums](https://discuss.ens.domains/t/technical-feedback-thread-for-ensv2/19233).
## FAQ
### Which wallets and dApps support ENS?
ENS is supported by a wide range of wallets and dApps, some notable ones can be found on the [integrations page](https://ens.domains/).
This page is currently under construction however a link to add yourself will be put here soon.
### Can I hold my name with one address, and point it at the other?
Yes, you can hold your name with one address and point it at another.
Simply visit the [ENS Manager App](https://ens.app/) and update the appropriate address record (by chain) for your name to point to the address you wish.
### Once I own a name, can I create my own subdomains?
Yes. You can create whatever subdomains you wish and assign ownership of them to other people if you desire. You can even set up your own registrar for your domain.
Some resolvers might provide even more advanced features, read more [about Resolvers](/resolvers/quickstart).
### Can I change the address my name points to after I've bought it?
Yes, you can update the addresses and other resources pointed to by your name at any time.
To update your name checkout the [ENS Manager App](https://ens.app/).
### ETH Registration
#### Why are names registered as hashes?
Hashes provide a fixed length identifier that can easily be passed around between contracts with fixed overhead and no issues passing around variable-length strings.
Read more about [labelhash, namehash, and encodings](/resolution/names).
#### What characters are supported?
ENS names are generally encoded using UTS-46.
This means there is partial support for Unicode characters, including emoji.
However technically possible to register any name, names that are not valid UTS-46 will not be resolvable by most resolvers.
Therefore it is generally recommended for apps that implement registration to limit the characters that can be registered to ensure a smooth experience.
To read more about supported characters [name normalization](/resolution/names).
#### What does it cost to register a .eth domain?
Currently, registration costs are set at the following prices:
* 5+ character .eth names: $5 in ETH per year.
* 4 character .eth names: $160 in ETH per year.
* 3 character .eth names: $640 in ETH per year.
3 and 4 character names have higher pricing to reflect the small number of these names available.
To read more about the pricing structure of .eth names [read more about pricing](/registry/eth)
#### How long can I register a name for?
You can register a name for as long as you would like.
There is no maximum registration duration.
#### What happens if I forget to renew my name?
If you forget to renew your name, it will be released back to the public pool of available names.
Luckily the expiration process has a 90 day grace period.
This means that once the name expires the original owner has 90 days to renew the name before it is released.
After the grace period, the name is released for registration by anyone with a temporary premium which decreases over a 21 days period.
The released name continues to resolve your ETH address until the new owner overwrites it.
#### In what way could I lose access to my name?
The .eth registrar is built to ensure once issued, a name cannot be revoked or taken away from its owner.
Potential loss can occur if the owner loses access to their private key, or if the owner forgets to renew their name.
### Root Registry
#### Who owns the ENS rootnode? What powers does it grant them?
The ENS rootnode is currently owned by the ENS DAO. It used to be owned by the ENS Multi-sig, a group of keyholders from different parts of the ecosystem, however as of [EP4.10](/dao/proposals/4.10) the ownership has been transferred to the ENS DAO.
Ownership of the rootnode grants the ability to do the following:
* Control allocation and replacement of TLDs other than .eth - this is required to implement DNSSEC integration.
* Enable and disable controllers for the .eth registrar, which affect registration and renewal policies for .eth names.
* Update the pricing for .eth names.
* Receive and manage registration revenue.
#### Can I register a TLD of my own within ENS?
Yes and No, We consider ENS to be part of the 'global namespace' in co-existence with DNS, and it is our priority to not pollute the namespace.
ENS-specific TLDs are restricted to only '.eth' on Ethereum Mainnet, or .eth and .test on testnets.
By default ENS allows users to [import their DNS name](/learn/dns) through the use of the [DNS Registrar](/registry/dns).
Existing DNS TLDs can [reach out to us](mailto\:info@ens.domains) to take control of their TLD.
### What are the differences between ENS and other naming services such as Namecoin or Handshake?
ENS complements and extends the usefulness of DNS with decentralised, trustworthy name resolution for web3 resources such as blockchain addresses and distributed content, while Namecoin and Handshake are efforts to replace all or part of DNS with a blockchain-based alternative.
### Governance Token
#### Can I recover tokens accidentally sent to the wrong address?
The answer depends on the address the token was sent to. If you accidentally sent the token to the token.ensdao.eth address (0xC18360217D8F7Ab5e7c516566761Ea12Ce7F9D72) or the wallet.ensdao.eth address (0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7) then the tokens might be recoverable. Contact the [Meta-governance working group](/dao/stewards/) at the [ENS Forum](https://discuss.ens.domains) and explain the situation. Tokens can only be sent back to the address they were sent from, so if it was sent from an exchange, contact your exchange support to make sure the address can receive tokens.
If the tokens were sent to the null address (0x000..) or an address with a typo, then the tokens are unrecoverable and there's nothing that anyone can do. If the tokens were sent to an exchange or a third party, then contact that third party for help.
import { EmbedLink } from '../components/EmbedLink'
## Terminology
This page contains a glossary of terms used in the ENS documentation.
### Name
An ENS identifier such as 'alice.eth'. Names may consist of multiple parts, called labels, separated by dots. This also includes DNS names like `name.xyz`, or subnames like `sub.name.eth`.
### 2LD
Second-level domain.
This refers to a subname/subdomain of a top-level domain.
For example, `name.eth` and `name.com` are both second-level names.
A subname of a 2LD is a third-level domain or 3LD.
### Subname / Subdomain
A child name like `sub.name.eth`, whose parent is `name.eth`. Also referred to as a "subdomain". Every name (except for the root node) has a parent. For example, `name.eth` is a subname of `eth`.
```
sub.name.eth
```
### TLD
Top-level domain. This refers to names like `eth`, `com`, `xyz` which lie at the "top" of the naming hierarchy.
```
.eth .com .xyz
```
### Manager
The account that may edit the records of a name. The Manager may be changed by the Owner.
### Label
An individual component of a name, such as 'alice'.
### Labelhash
The keccak256 hash of an individual label.
### Namehash
The algorithm used to process an ENS name and return a cryptographic hash uniquely identifying that name. Namehash takes a name as input and produces a *node*.
### Node
A cryptographic hash uniquely identifying a name.
### Owner
The owner of a name is the entity referenced in the ENS registry's owner field. An owner may transfer ownership, set a resolver, and create or reassign subdomains.
### Record
A piece of information that an ENS name "resolves" to (points to). The most common record is the ETH Address record, which determines what ETH 0x address an ENS name points to.
### Registration
A registration is a registrar's record of a user's ownership of a name. This is distinct from the owner field in the Registry; registrations are maintained in the registrar contract and additionally store information on expiry date, fees paid, etc.
#### Registrar
A registrar is a contract responsible for allocating subdomains. Registrars can be configured at any level of ENS, and are pointed to by the owner field of the registry.
#### Registry
The core contract of ENS, the registry maintains a mapping from domain name (at any level - x, y.x, z.y.x etc) to owner, resolver, and time-to-live. All lookups start with the Registry.
#### Expiry
The date and time at which an ENS name expires.
The implications of expiration depend on the type of name it is.
When a .eth 2LD expires (and its grace period elapses), then you lose ownership of the name.
When a wrapped subname expires, you may or may not lose ownership, depending on whether the name was emancipated.
#### Grace Period
This is a short window of time after an ENS .eth name expires, in which the owner can still renew and retain the name. Currently this window is 90 days.
#### TTL
Stands for "Time To Live". This is a field in the core registry that can be set alongside the resolver. It can be used as a hint for clients to decide how long to cache resolved data.
### DNS
This is the Domain Name Service used by the internet to resolve addresses and other records from human-readable names. ENS aims to be fully complementary and compatible with DNS, and supports easy importing of DNS names via a special [DNSSEC](#dnssec) registrar.
#### DNSSEC
Stands for Domain Name System Security Extensions. When a particular DNS TLD supports DNSSEC, then the owners of names can cryptographically sign records. This allows ENS to support easy importing of DNS names into the ENS registry, as the owner of the DNS name can prove ownership with those signed records.
### Resolver
A resolver is a contract that maps from name to the resource (e.g., cryptocurrency addresses, content hash, etc). Resolvers are pointed to by the resolver field of the registry.
#### Wildcard Resolver
This refers to a resolver that supports [ENSIP-10](/ensip/10). This scheme allows clients to resolve data for subnames that either don't have a resolver of their own, or subnames that may not even exist onchain at all. For offchain names, this is typically used in conjunction with [CCIP Read](#ccip-read).
### Public Resolver
This is a standard resolver contract implementation written by ENS Labs. It supports all record types and anyone can use it. This is the default resolver used when registering a new name via the official manager app.
### Offchain
This term is typically used with respect to the Ethereum Mainnet blockchain. If data is not posted to the chain via an actual Ethereum Mainnet transaction, then it is "offchain". ENS names can also be offchain. For example names can use a special resolver to resolve records for subnames that don't exist onchain in the Registry. This is also typically done with [CCIP Read](#ccip-read).
#### CCIP Read
The "Cross Chain Interoperability Protocol Read" specification, also known as [EIP-3668](https://eips.ethereum.org/EIPS/eip-3668), authored by Nick Johnson, is a specification that allows for secure and trustless offchain data retrieval.
It allows for an Ethereum call to defer to an [offchain gateway](/resolvers/ccip-read#writing-a-gateway) and then securely verify the resulting data onchain.
With respect to ENS, this is typically used for offchain subnames that don't exist in the core Registry.
<EmbedLink title="Offchain Resolution" href="/learn/ccip-read#offchain-resolution" description="Read more about offchain resolution and CCIP Read here" />
### Primary Name
The ENS name that you want a particular ETH account to be associated with. When set, it will be displayed instead of your 0x address on integrating websites/apps. This is also often referred to as the "reverse record".
#### Reverse Node
A node in the Registry that can be claimed for any Ethereum account. The name this node represents is `[addr].addr.reverse`, where `[addr]` is the Ethereum public address (lowercase, without the "0x"). These reverse nodes are typically used to set a [Primary Name](#primary-name) for an account.
#### Reverse Record
Usually, this is referring to the [Primary Name](#primary-name). Technically speaking, a [Reverse Node](#reverse-node) can have multiple records set on it, the same as any node.
### NameWrapper
#### Wrapped Name
The [ENS Name Wrapper](/wrapper/overview) is a contract for ENS that allows you to "wrap" any ENS name into a ERC-1155 NFT. This includes not only .eth 2LDs like `name.eth`, but also DNS names like `name.xyz`, or subnames like `sub.name.eth`.
#### Fuse
The technical term for a specific "permission" bit for a wrapped name. As the name implies, once that bit is flipped on, the fuse is burnt and cannot be unburnt (unless the name expires).
#### Emancipated
A name is considered emancipated if it's parent is unable to replace/delete it. This is typically used to describe trustless subnames.
### Subgraph
An indexed collection of data using TheGraph protocol.
In this documentation portal, "the subgraph" usually refers to the official ENS subgraph maintained by ENS Labs.
This is a useful offchain service that allows clients to query for information about names or accounts.
## Name Wrapper Contract Details
The Name Wrapper contract is deployed on these chains:
* Mainnet: [wrapper.ens.eth](https://etherscan.io/address/0xD4416b13d2b3a9aBae7AcD5D6C2BbDBE25686401#code)
* Sepolia: [wrapper.ens.eth](https://sepolia.etherscan.io/address/0x0635513f179D50A207757E05759CbD106d7dFcE8#code)
### Wrapping and Unwrapping
When wrapping a .eth 2LD, you're effectively transferring the ERC-721 NFT ownership to the Name Wrapper contract, which will take over the [Manager](/terminology#manager) role f프로젝트로 돌아가기