owner field when creating a subname. This allows you to
Modify text records, address records, content hash, or metadata for an existing subname.
```typescript
-client.updateSubname("superman.namespace.eth", {
- texts: [{ key: "avatar", value: "updated-avatar" }],
+await client.updateSubname('alice.example.eth', {
+ texts: [{ key: 'description', value: 'Updated profile' }],
});
```
diff --git a/developer-guide/sdks/offchain-manager/data-records.mdx b/developer-guide/sdks/offchain-manager/data-records.mdx
index 1950f05..267fb93 100644
--- a/developer-guide/sdks/offchain-manager/data-records.mdx
+++ b/developer-guide/sdks/offchain-manager/data-records.mdx
@@ -1,7 +1,7 @@
---
-title: "Metadata Records"
-description: "Manage custom metadata records for ENS subnames. Useful for discovery and filtering."
-sidebarTitle: "Metadata Records"
+title: "Metadata records"
+description: "Metadata for discovery and filtering."
+sidebarTitle: "Metadata records"
icon: "id-card-clip"
---
@@ -11,16 +11,16 @@ Custom key-value metadata records for offchain ENS subnames. Not used for onchai
Do not store sensitive information. Values are retrievable by anyone with read access.
-### 1. addDataRecord
+## Add or update a metadata record
Add or update a metadata record.
```typescript
-await client.addDataRecord({
- subname: "ns.myensname.eth",
- key: "token-holder",
- data: "1200",
-});
+await client.addDataRecord(
+ 'alice.example.eth',
+ 'membership-tier',
+ 'pro',
+);
```
**Parameters:**
@@ -32,24 +32,21 @@ await client.addDataRecord({
If the key exists, its value will be overwritten.
-### 2. deleteDataRecord
+## Delete a metadata record
Delete a metadata record.
```typescript
-await client.deleteDataRecord({
- subname: "ns.myensname.eth",
- key: "token-holder",
-});
+await client.deleteDataRecord('alice.example.eth', 'membership-tier');
```
-### 3. getDataRecords
+## Get all metadata records
Get all metadata records for a subname.
```typescript
-const allMetadata = await client.getDataRecords("ns.myensname.eth");
-// Returns: Recordnull if the subname doesn't exist.
- Returns `null` when the subname cannot be found.
- For bulk queries or filtering by `owner`, `label`, or `metadata`, see `getFilteredSubnames`.
-
diff --git a/developer-guide/sdks/offchain-manager/installation.mdx b/developer-guide/sdks/offchain-manager/installation.mdx
index 61922d3..50a5fed 100644
--- a/developer-guide/sdks/offchain-manager/installation.mdx
+++ b/developer-guide/sdks/offchain-manager/installation.mdx
@@ -1,6 +1,6 @@
---
title: "Offchain SDK Installation"
-description: "Learn how to install and initialize the Namespace Offchain SDK for managing ENS subnames and records."
+description: "Install and initialize the Offchain Manager SDK."
sidebarTitle: "Installation"
icon: "download"
---
@@ -8,7 +8,7 @@ icon: "download"
Install the Offchain SDK using your preferred package manager:
-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).
+## What Namespace provides
-Just **One Universal Username**, storing all blockchain addresses the user needs, used as a central point of Web3 Identity for username-to-username payments.
+Namespace helps product teams and ENS name owners issue and manage subnames through:
-## Vision
+- The [Namespace App](/user-guide/app) for activating names and managing L1 and L2 subnames without code.
+- [Offchain tools](/user-guide/dev-portal) for resolver configuration, API keys, and gasless subname records.
+- [TypeScript SDKs](/developer-guide/sdks/introduction) for offchain management, mint preparation, and indexed data.
+- [REST APIs](/api-reference/introduction) for hosted subname and ENS-resolution workflows.
+- [ENS Components](/user-guide/ens-components) and [ENS Widget](/user-guide/ens-widget) for ready-made user interfaces.
-Replace all hexadecimal blockchain addresses with human-readable (ENS-powered) names or subnames and streamline ENS implementation across the entire Web3 space.
+Namespace has also been selected as an [ENS Service Provider](https://www.tally.xyz/gov/ens/proposal/20404686300257550242704646761273386459664655640264490428281621095220078268383). This link records the underlying ENS governance proposal.
-## Who do we work with?
+## Partners and integrations
-- **Wallets** → Branded wallet names (human-readable names instead of addresses).
-- **L2 chain** → consistent ecosystem naming and identity 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.
+Namespace works with wallets, payment apps, AI agents, RaaS providers, blockchain infrastructure, games, identity services, and communities to integrate ENS subnames.
-## Traction
+Common integrations include branded wallet names, readable payment identities, and names for AI agents. See [Use cases](/overview/use-cases) for more examples.
-- 160,000 subnames/subdomains minted
-- 4M+ resolution requests served
-- 200+ names activated (registries deployed)
-- 120+ ENS Widgets created
-- 30+ partnerships and integrations done
+If you are interested in partnering, [contact the Namespace team](mailto:hello@namespace.ninja).
-
-
-### 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`).
\ No newline at end of file
diff --git a/overview/offchain-subnames.mdx b/overview/offchain-subnames.mdx
deleted file mode 100644
index e3e9f05..0000000
--- a/overview/offchain-subnames.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: "Offchain Subnames"
-description: "Learn about Offchain Subnames."
----
-
-Namespace platform enables you to create and manage **offchain ENS subnames**. Unlike onchain subnames, they’re **gasless**, easy to integrate through our API or SDK, and free and seamless for end users to get. They also provide **greater flexibility in ownership control** and are built for **scalability**.
-
-## Use Cases
-
-- **Wallets**: Give every user a branded identity (e.g. _user_.**wallet**.eth).
-- **Communities**: DAOs or NFT projects issue subnames or assign to NFTs (_alice_.**bayc**.eth).
-- **L2s / RaaS providers**: Provide an identity layer for the entire ecosystem (_bob_.**base**.eth).
-- **Apps**: Payment, DeFi, or Social apps assign subnames automatically to users (_carol_.**app**.eth).
-- **AI Agents**: Assign persistent, verifiable identities to AI agents (_xbtc_.**agent**.eth).
-
-## How to create an offchain subname
-
-1. Go to the [Namespace App](https://app.namespace.ninja/offchain)
-2. Connect your wallet
-3. Click on the "Create Subname" button
-4. Select the ENS name you want to create a subname for
-5. Click on the "Create Subname" button
\ No newline at end of file
diff --git a/overview/subnames.mdx b/overview/subnames.mdx
index 1be6814..28aea1e 100644
--- a/overview/subnames.mdx
+++ b/overview/subnames.mdx
@@ -1,44 +1,72 @@
---
-title: "Subnames"
-description: "Learn more about Subnames."
-sidebarTitle: "What are Subnames"
+title: "Learn about Subnames"
+description: "Compare offchain, L1, and L2 subname models."
+sidebarTitle: "Learn about Subnames"
icon: "question"
---
-[ENS](https://ens.domains/) maps 20-byte addresses to human‑readable .eth names. Subnames extend a parent name (e.g., `brand.eth`) to create subnames for people, apps, and agents — like `alice.brand.eth`.
+[ENS](https://ens.domains/) maps readable names to addresses and other public records. A subname extends a parent name: the operator of `brand.eth` can create `alice.brand.eth`, `pay.brand.eth`, or deeper names.
-For a concise overview of how to leverage subnames, how to choose the type of Subnames (Offchain, L2, or L1 subnames), and who uses them, see the Getting started page.
+## What subnames enable
-## Different Types of Subnames
+- **Readable payments:** Replace copied addresses with names, which can help reduce address-entry errors.
+- **Branded identity:** Give users a recognizable name under a product or community namespace.
+- **Portable profiles:** Store public addresses and text records that compatible ENS clients can resolve.
+- **Flexible issuance:** Choose application-managed offchain records or owner-held onchain subnames.
-ENS subnames can live on L1 or L2 chains, or offchain. L2 and offchain are similar in UX; the key differences are decentralization, cost, and ownership model.
+See [Use cases](/overview/use-cases) for examples across wallets, payments, AI agents, chains, games, and communities.
-### L1 Subnames
+## L1 subnames
-L1 subnames are minted as NFTs directly on Ethereum, offering a fully trustless, decentralized, and permissionless implementation.
+L1 subnames are created through ENS contracts on Ethereum. Their guarantees depend on the parent name's fuse configuration and the minting contract used.
-When a subname is created through the [ENS Manager app](https://app.ens.domains/), it is registered on Ethereum without burning protective fuses—meaning the parent name still retains certain controls. By contrast, creating a subname via the [Namespace App](https://app.namespace.ninja/) burns a specific set of fuses during the **“**[Name Activation](https://app.namespace.ninja/)**”,** making every subname minted **100% unruggable** and fully controlled by the minter’s address instead of the parent name.
+When a name is activated through the [Namespace App](/user-guide/app#activate-your-ens-name), the activation flow configures the parent and its minting rules before users register subnames. Review the confirmation transaction carefully because fuse changes may be irreversible.
-The main drawback of L1 subnames is cost: Ethereum’s high gas fees create friction for high-volume minting, making them less practical for large-scale distribution.
+L1 issuance usually has the highest transaction cost, so it best fits lower-volume flows where Ethereum-native ownership is a requirement.
-### L2 Subnames
+
+ 
+ 
+ 
+ 
+
-
-
- 
-
- 
- 
- 
- 
- 
-
- 
+
+ 
-Click **Mint** to sign the transaction.
+L1 subname ownership and expiry depend on the parent name's ENS fuse and listing configuration. L2 subnames can also use a registration period when the parent-name owner enables renting.
-
+## Register an ENS name
-L1 (Ethereum) subnames are unruggable by default and inherit the registration length from the parent name. L2 subnames may have a registration period if the parent-name owner chose to rent rather than sell outright.
+For an available `.eth` name, choose the registration period and review the registration fee, estimated network fee, and total. Continue through the wallet prompts shown by the app.
-### Registering an ENS Name
+
-Search for a name that isn't taken (e.g. `youreallywantaname.eth`) and start registration. The **ENS Name Registration** modal asks for:
+## Next steps
-- **Period** — registration duration (default 1 year; adjustable, or pick by date)
-- **Registration Fee** — based on name length
-- **Est. network fees** — gas estimate
-- **Total** — fee + gas, with USD conversion
-- Optional **Complete your profile** flow
-
-Click **Next** to continue, then confirm in your wallet.
-
-
+
-## Creating a new Widget
-
-Once you create a new Widget and give it a name you'll see the following form. This form allows you to further customize what specifically you want to do with your Widget.
-
-
-
-## Choosing Widget Type
-
-
-
-Choosing a widget type comes down to the fact of what specifically you want to sell. Currently, there are 4 different types you can choose from:
-
-1. **All Names** — all available Subnames, from all listed ENS Names on the Namespace platform from every ENS Name owner, will appear in the search and people will be able to mint them from the Widget.
-2. **Owned Names** — all available Subnames, from your listed ENS Names only, will appear in the search and people will be able to mint them from the Widget.
-3. **Selected Names** — all available Subnames, from the ENS Names you listed and selected, will appear in the search and people will be able to mint them from the Widget.
-4. **Single Selected Name** — all available Subnames, from only one ENS Name that you listed and selected, will appear in the search and people will be able to mint them from the Widget.
-
-## Selecting Names
-
-If you opt for either option 3 or 4 outlined above, you'll be prompted to select the ENS Names you wish to add to the Widget. Only this selected Name(s) will be used for issuing Subnames.
-
-
-
-## Optional ENS Registration
-
-You can optionally allow people to register 2nd level ENS Names from your Widget as well by turning on or off the "Allow ENS Name Registrations" toggle button.
-
-## Launch
-
-Once you're happy with your setup, you can click update. You'll be prompted to sign the update, and the widget will then be updated with the latest changes and with your wallet completely gaslessly.
-
-## Integrate into your Website
-
-
-
-Once you're done customizing and setting up your Widget, you can add it to your website and issue Subnames directly from there.
diff --git a/user-guide/app/wizard.mdx b/user-guide/app/wizard.mdx
deleted file mode 100644
index 14c8e38..0000000
--- a/user-guide/app/wizard.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "Wizard"
-description: "Wizard handles activating ENS names and subname management, customization, and issuance with no technical knowledge required."
-sidebarTitle: "Wizard"
-icon: "hat-wizard"
----
-
-Widget lets you activate any ENS name you own and start issuing subnames—whether you want to sell them, gift them, rent them out, or use them to build community.
-
-Designed with simplicity and UX in mind, the Wizard makes subname issuance easy for anyone with no technical knowledge required.
-
-We built it to serve a wide range of users:
-
-- **Wallets** issuing usernames to their users
-- **Games** assigning in-game identities
-- **Payment apps** enabling Venmo-like experience
-- **AI agents** needing sovereign, persistent identities
-- **L2s** offering onchain naming to their users
-- **Tools and infra projects** embedding ENS identity into their stack
-- **Communities** looking to reward members
-- **DAOs** offering identity to contributors
-- **Creators and Bloggers** distributing supporter badges
-
-If you already have an ENS name and an audience, the Wizard helps you turn your name into a utility, giving your people a unique, web3-native identity they can truly own.
diff --git a/user-guide/custom-solutions.mdx b/user-guide/custom-solutions.mdx
index a50e050..db3b0b4 100644
--- a/user-guide/custom-solutions.mdx
+++ b/user-guide/custom-solutions.mdx
@@ -1,12 +1,12 @@
---
-title: "Custom Solution"
-description: "We help teams build custom ENS solutions and implementations"
+title: "Custom Solutions"
+description: "Custom ENS infrastructure for products with unique requirements."
icon: "compass-drafting"
---
Namespace partners with individuals, teams, and companies to design custom ENS Subname solutions and to help people leverage ENS across any use case.
-### **We work with:**
+## Who we work with
- Wallets and WaaS providers
- L2 chains / Rollups / RaaS provider
@@ -14,12 +14,17 @@ Namespace partners with individuals, teams, and companies to design custom ENS S
- AI agents and launchpads
- Blockchain infra, tools, & service providers
- Identity-related apps and protocols
-- Web3 communities, NFT or memecoin projects
+- web3 communities, NFT or memecoin projects
- Brands and influencers
- Individuals / ENS enthusiasts
### Wanna build?
-
+ 
+ 
+ 
+ {" "}
diff --git a/user-guide/dev-portal/subnames.mdx b/user-guide/dev-portal/subnames.mdx
deleted file mode 100644
index 0c5c5c2..0000000
--- a/user-guide/dev-portal/subnames.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: "Create Offchain Subnames"
-description: "Create and manage offchain subnames including text, address, and content hash records through the UI."
-sidebarTitle: "Create Offchain Subnames"
-icon: "plus"
----
-
-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**.
-
-
-
-