### L2 Activation Process
Activating subnames on an L2 network follows **four key steps**:
1. **Create Activation Configuration** – The List Manager backend generates the activation configuration that defines how subnames minting process functions.
2. **Deploy ERC-721 Registry** – An ERC-721 registry contract is deployed on the chosen L2 chain to manage ownership of subnames.
3. **Configure Resolver** – A resolver supporting **ENSIP-10 wildcard resolution** is set and configured to enable flexible, scalable name resolution.
4. **Verify Activation** – The backend performs validation to ensure all on-chain steps (registry deployment and resolver setup) have been completed correctly.
## Minting Process
When a name is activated, the minting process runs **off-chain**. To mint an ENS subname, the minter requests parameters and a signature from the Mint Manager server, then uses those to call the smart contract.\
This off-chain design unlocks key advantages:
* **Richer Activation Features** – Complex logic that would be impractical or impossible to run entirely on-chain can be handled seamlessly off-chain.
* **Dynamic Updates Without Transactions** – Activated name configurations can be changed instantly without requiring new blockchain transactions.
* **Lower Costs** – Both activation and minting fees are significantly reduced, making the entire flow cheaper for users.
## Resolution process
#### L1 Subnames resolution
Since L1 subnames are part of the existing ENS contracts on Ethereum mainnet, they resolve just like any other ENS name:
1. **Fetch Resolver** – Call `getResolver` on the ENS Registry to retrieve the resolver contract for `namehash(name.eth)`.
2. **Resolve Records** – Call the required resolver function (`addr`, `text`, `contenthash`, etc.) on the resolver contract.
#### L2 Subnames resolution
Resolution on L2 relies on **CCIP-Read** in combination with **ENSIP-10 wildcard resolution**.\
ENSIP-10 defines a workflow that allows resolving subnames of a parent name, even if those subnames don’t technically exist on L1.
The process works as follows:
1. **Query ENS Registry** – The client queries the ENS Registry contract for the resolver address of the subname.
2. **Fallback to Parent** – If the resolver address is the zero address, the client strips the leftmost label and queries the Registry again for the parent name’s resolver.
3. **Call Resolve** – Once a resolver is found, the client calls `resolve(name, data)`, where:
* `name` is the DNS-encoded subname.
* `data` is the encoded resolver function call.
4. **Offchain Lookup Trigger** – The resolver reverts with an `OffchainLookup` error (per \[EIP-3668, CCIP-Read]), providing:
* One or more URLs to query off-chain.
* The call data required for resolution.
* The address of the resolver contract to callback.
5. **Offchain Data Fetch** – The client performs an HTTP(s) request to the specified resolution gateway server.
6. **Response Returned** – The server processes the request off-chain and returns signed resolution data with a callback function.
7. **Callback On-Chain** – The client submits the signed response back to the resolver contract via the designated callback function.
8. **Final Resolution** – The resolver verifies the signature and returns the final resolved record (e.g., `addr`, `text`, or `contenthash`).
# How-to Guides and Demos
Source: https://docs.namespace.ninja/developer-guide/guide
Step-by-step guides and video demos for using Namespace products and services.
## Dev Guides
owner field when creating a subname. This allows you to later fetch all subnames owned by a specific address using the SDK or API.
ChainName enum maps blockchain networks to their [SLIP-0044](https://github.com/satoshilabs/slips/blob/master/slip-0044.md) coin types for address records. See the [ChainName](/developer-guide/sdks/offchain-manager/chainname) page for more details.
alice.example.eth).alice).null if the subname doesn't exist.
alice.example.eth).alice).
ENS names have '*address records*' which store addresses from different chains. If you look at the example above (thecap.eth), it has Solana and BTC addresses next to EVM addresses (Eth, Base, Zksync, etc.). So you can send \$BTC to 'thecap.eth' name if the wallet you're using correctly reads/resolves address records from thecap.eth (which most of them do).
Just **One Universal Username**, storing all blockchain addresses the user needs, used as a central point of Web3 Identity for username-to-username payments.
## Vision
Replace all hexadecimal blockchain addresses with human-readable (ENS-powered) names or subnames and streamline ENS implementation across the entire Web3 space.
## Who do we work with?
* **Wallets** → Branded wallet names (human-readable names instead of addresses).
* **L2 chain** → consistent ecosystem naming and discovery with one namespace.
* **Payment apps** → Simple names for sending/receiving payments.
* **AI agents & launchpads** → Auto-assign a subname to every new AI agent created.
* **RaaS providers** → Chain-wide naming service for every rollup.
* **Wallet-as-a-Service** → One wallet name that works across all chains.
* **Blockchain infra/tools** → Adds a universal identity layer for developers.
* **Website builders** → deploy websites to custom immutable subnames.
* **Referral protocols** → custom subdomains as referral tracking links.
* **Games** → Custom player usernames with cross-chain utility.
* **Identity apps/services** → Use ENS as the foundation for digital identity.
* **Communities** → Subnames for members, strengthening shared identity.
* **Individuals** → Creators give subnames to followers for onboarding.
* **All others** → Any user-facing app needs names as identity primitives.
## Traction
* 110,000 subnames minted
* 3M+ resolution requests served
* 200+ names activated (registries deployed)
* 120+ ENS Widgets created
* 30+ partnerships and integrations done
5. Select the ENS name to activate (e.g., `ninjademo.eth`).
## Choose Activation Option
* **Ethereum:** Issue subnames on Ethereum.
* **L2s (Base, Optimism, etc.):** Issue subnames on supported L2s (example: Base).
We are going to use Base for this example.
## L2 Activation & Minting Steps
1. Select "Issue L2 Subnames".
* Name your collection and symbol.
* Decide on burnability and rental options.
2. Define minting price for subnames.
* Set base price, length-based pricing, and special rules (numbers, letters, emoji).
3. Reserve or blacklist subnames as needed.
4. Optionally set a minting deadline.
5. Choose whitelisting options. - Restrict
minting to specific wallets or allow free mints for whitelisted addresses.
6. Optionally
enable token-gated minting (require ERC20/721 ownership).
***
Once setup is complete, click "List Name". Your ENS Name is now ready for subname minting via:
* [Namespace App](https://app.namespace.ninja/)
* [Widget](./widget)
* [Subpage](https://github.com/thenamespace/subpages) for a custom-branded portal
# Search & Register ENS Subname
Source: https://docs.namespace.ninja/user-guide/app/search-register
Search and registration page allows anyone to buy both ENS names and subnames with expanded search functionality.
The search extends beyond the simple word search. If the searched word (e.g. `alice.eth`) is unavailable, users are presented with additional options.
Imagine you want to register `alice.eth`. Since it's a fairly common name, it's likely already taken. The ENS app doesn't offer additional options to find a similar name or a subname.
With Namespace, however, if the searched word (e.g. `alice.eth`) is unavailable, users are presented with additional options!
If you entered "alice" in the Namespace app, it would give you this:
These options are available Subnames of the search word (`alice.eth`) from the parent Names that had been activated on the Namespace platform to issue Subnames, and have that word - `alice` - available.
This expands the registrar's functionality and opens up a lot of potential integrations. Specifically, projects and dapps that need to expand search and registration functionality, such as Website Builders. This allows their users to immediately find and register a domain name/subname for their newly created website.
On top of that, each subname comes with certain perks and benefits that the ENS Name owner of the parent Name has decided to provide to incentivize minting.
This provides an additional reason for ENS name owners to come up with creative and appropriate incentives for their Names, and start issuing subnames!
## Registration
Currently, Namespace is the only Dapp that offers **search and registration** of available Subnames from the activated ENS names! This means that it acts as an aggregate of all ENS names and displays the ones that have available subnames that the user wants to register.
The registration process is familiar and easy to use.
## Feature Overview
* **Subname management**: Simple, clean interface to create and manage ENS subnames, records, and all usernames issued.
* **Resolver Set**: Update your ENS name to use the Namespace Hybrid resolver to make all issued subnames fully resolvable across the Web3 ecosystem.
* **API key generation**: Generate an API key and programmatically manage ENS subname creation, issuance, edits, and updates, and easily plug in Subname registrations in your app.
# API Keys
Source: https://docs.namespace.ninja/user-guide/dev-portal/api-keys
Generate and manage API keys for offchain subnames with address-based and domain-based options.
Easily generate an API key to programmatically manage Offchain subnames in your app, and enable Subname registrations in your project on the [Namespace Dev Portal](https://dev.namespace.ninja).
## API Key Expiry
You can set an expiry date for your API keys when generating them. This helps you control access and rotate keys for better security. Expired keys will no longer be valid for API requests.
{" "}
# Create Offchain Subnames
Source: https://docs.namespace.ninja/user-guide/dev-portal/subnames
Create and manage offchain subnames including text, address, and content hash records through the UI.
Use the "Subnames" tab to create and manage your offchain subnames for the selected ENS name above. You can add, edit, and update records, including text, address, and content hash records.
### Edit records
You can edit any record for subnames — **Text Records**, **Address Records**, and **Contenthash Records**.
### **Getting started**