From a9c11e7e326566fc8ed422963d9df2ef0585f319 Mon Sep 17 00:00:00 2001 From: Kris Kocic Date: Thu, 13 Aug 2026 18:57:40 +0200 Subject: [PATCH] docs: refresh overview content and copy - Rework "About Namespace" (learn-more): tighten intro, add ENS DAO/Service Provider positioning, Onchain/Offchain app links, Resolvio and ENS Diamonds - Move "ENS and subnames" section into "Learn about Subnames"; restructure into "What ENS does" / "What subnames unlock" and add a Benefits list - Refresh "Creators or communities" (for-name-owners) overview and add a "Who this is for" section - Rewrite "Universal usernames" intro (two approaches + a better way with ENS); rename page slug make-usernames-universal -> universal-usernames with redirect - Copy edits across getting-started Co-Authored-By: Claude Opus 4.8 (1M context) --- docs.json | 6 ++- getting-started.mdx | 8 ++-- learn-more.mdx | 38 ++++++------------- overview/for-name-owners.mdx | 11 +++++- overview/subnames.mdx | 37 +++++++++++++++--- ...-universal.mdx => universal-usernames.mdx} | 30 ++++++++++----- 6 files changed, 83 insertions(+), 47 deletions(-) rename overview/{make-usernames-universal.mdx => universal-usernames.mdx} (54%) diff --git a/docs.json b/docs.json index 955f840..691182f 100644 --- a/docs.json +++ b/docs.json @@ -45,7 +45,7 @@ "overview/for-name-owners", "overview/for-product-teams", "overview/for-fintechs-neobanks", - "overview/make-usernames-universal", + "overview/universal-usernames", "developer-guide/integrations/waas" ] }, @@ -351,6 +351,10 @@ ] }, "redirects": [ + { + "source": "/overview/make-usernames-universal", + "destination": "/overview/universal-usernames" + }, { "source": "/apps/onchain-subnames-app", "destination": "/user-guide/app" diff --git a/getting-started.mdx b/getting-started.mdx index cb3fbda..2fb9021 100644 --- a/getting-started.mdx +++ b/getting-started.mdx @@ -4,11 +4,13 @@ description: "Understand subnames and choose how to build with Namespace." icon: "hand-wave" --- -[**ENS**](https://ens.domains/) turns blockchain addresses into readable names such as **alice.eth**. A subname extends a parent name. For example, **alice.brand.eth** sits under **brand.eth**, allowing a product, community, or any name owner to issue subnames (as identities) within a shared namespace. +[**ENS**](https://ens.domains/) maps blockchain addresses to readable names such as **alice.eth** or **alice.id**. Names are hierarchical: whoever owns e.g. **brand.eth** can issue **[username].brand.eth** to a user, a product, or a community member, giving everyone an identity inside a shared namespace. -[Namespace](https://namespace.ninja/) provides no-code apps, APIs, and SDKs for issuing and managing ENS subnames. It lets developers easily implement Subname (identity) registration for their users, agents, or general-purpose identifier. +[Namespace](https://namespace.ninja/) is the infrastructure for issuing ENS subnames. We provide no-code apps, APIs, and SDKs for issuing and managing ENS subnames, so developers can give every user, agent, or resource a name of its own. -**Choose where subnames live:** Subnames can be issued on Ethereum, on an L2 chain, or through an offchain service. All 3 work the same, but they differ in cost, control, and ownership. +### Choose where subnames live + +Subnames can be issued on Ethereum, on an L2 chain, or through an offchain service. All 3 work the same, but they differ in cost, control, and ownership. | Model | Best for | Cost to issue | Ownership model | | --- | --- | --- | --- | diff --git a/learn-more.mdx b/learn-more.mdx index 772f427..d79427d 100644 --- a/learn-more.mdx +++ b/learn-more.mdx @@ -4,36 +4,27 @@ description: "Products, partnerships, and resources for building with ENS." icon: "sparkles" --- -## ENS and subnames - -The [Ethereum Name Service](https://docs.ens.domains/learn/protocol) is an open naming protocol. ENS names can resolve to blockchain addresses, websites, and public profile records. Subnames extend a parent name, so the owner or operator of `brand.eth` can issue names such as `alice.brand.eth`. - -ENS clients can resolve supported address records across multiple chains. The receiving wallet or app must support the relevant record type and, for offchain names, CCIP Read. - -ENS profile showing Ethereum, Base, Bitcoin, and Solana address records for one name +Funded by the ENS DAO to put ENS names in the hands of millions of users. Namespace has been an official [ENS Service Provider](https://www.tally.xyz/gov/ens/proposal/30153206728472299340257495645753485226870528642942223493225654414745632348879) for 3+ years. We focus on ENS growth and distribution, delivered through subname products and integrations. ## What Namespace provides Namespace helps product teams and ENS name owners issue and manage subnames through: -- The [Namespace App](/user-guide/app) for activating names and managing onchain subnames on Ethereum and L2 chains without code. +- The [Namespace App](/user-guide/app) for issuing and managing subnames without coding. + - [Onchain subnames](https://app.namespace.ninja/onchain): mint subnames as NFTs on Ethereum or an L2. + - [Offchain subnames](https://app.namespace.ninja/offchain): issue gasless subnames. - [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. +- [Resolvio](https://www.resolvio.xyz/), a universal ENS resolution API with one endpoint for forward, reverse, and offchain lookups. +- [ENS Diamonds](https://ens.diamonds), an app to pool ETH with others and co-own premium `.eth` names during their expiry auction. -Namespace has also been selected as an [ENS Service Provider](https://www.tally.xyz/gov/ens/proposal/30153206728472299340257495645753485226870528642942223493225654414745632348879). This link records the underlying ENS governance proposal. - -## Partners and integrations +## Partnerships and integrations -Namespace works with wallets, payment apps, AI agents, RaaS providers, blockchain infrastructure, games, identity services, and communities to integrate ENS subnames. +Namespace works with wallets, payment apps, AI agents, WaaS providers, blockchain infrastructure, games, identity services, and communities to integrate ENS subnames. -Common integrations include branded wallet names, readable payment identities, and names for AI agents. See [Use cases](/overview/use-cases) for more examples. +See [Use cases](/overview/use-cases) for more examples. If you are interested in partnering, [contact the Namespace team](https://t.me/+5FAwyiKOTeswNTIy). @@ -50,17 +41,15 @@ If you are interested in partnering, [contact the Namespace team](https://t.me/+ ## Current usage -Namespace publishes changing usage metrics on its live dashboard. Linking to the dashboard keeps figures current instead of duplicating time-sensitive counts in this page. - - + View current subname, registry, widget, and resolution activity. ## Official links - + - Explore Namespace products, services, case studies, and updates. + Explore products, services, case studies, and updates. Register names and manage onchain or offchain subnames. @@ -68,9 +57,6 @@ Namespace publishes changing usage metrics on its live dashboard. Linking to the Read product updates, case studies, and ENS guides. - - Follow Namespace news and ecosystem updates. - ## Start building diff --git a/overview/for-name-owners.mdx b/overview/for-name-owners.mdx index 60bee65..eeb4176 100644 --- a/overview/for-name-owners.mdx +++ b/overview/for-name-owners.mdx @@ -7,7 +7,16 @@ sidebarTitle: "Creators or communities" ## Overview -Turn your ENS name into a namespace users can mint from. +A subname is the clearest way to show someone belongs to your community. + +Buy `yourcommunity.eth` and issue a subname to every member, holder, or follower you have. They carry it into every ENS-compatible wallet, explorer, and app, and it points back to you every time. Every transaction becomes a brand impression, boosting your visibility every time your users transact. + +## Who this is for + +- **NFT projects and communities.** Give holders a name that proves membership and carries your brand wherever they go. +- **Creators.** Turn an audience into a namespace. Every fan with `name.yourname.eth` is a walking link back to you. +- **DAOs and teams.** Names for contributors, working groups, and treasury addresses, all under one root. +- **Anyone sitting on a good .eth name.** A short, memorable name is worth more as a namespace than as a personal wallet label. ## What you can do diff --git a/overview/subnames.mdx b/overview/subnames.mdx index a3ac671..aed6276 100644 --- a/overview/subnames.mdx +++ b/overview/subnames.mdx @@ -1,21 +1,46 @@ --- title: "Learn about Subnames" -description: "Compare offchain, L1, and L2 subname models." +description: "Learn more about Subnames and how to choose between offchain, L1, and L2." sidebarTitle: "Learn about Subnames" icon: "question" --- -[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. +## What ENS does -## What subnames enable +ENS turns blockchain addresses into names. `yourbrand.eth` resolves to your addresses across chains, your website, and your public profile, all from one name you own. -- **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. +## What subnames unlock + +ENS gives one readable name to one owner. Subnames turn that name into a namespace: whoever owns `brand.eth` can issue `alice.brand.eth` to a user, `pay.brand.eth` to a payment endpoint, `agent.brand.eth` to an AI agent, and thousands more. + +ENS profile showing Ethereum, Base, Bitcoin, and Solana address records for one name + +## Subnames become + +- **Readable payments:** Replace copying addresses with typing names. +- **Branded identity:** Users carry your brand name identity everywhere onchain. +- **Portable profiles:** Public addresses and text records all ENS-integrated clients can resolve. +- **Agent identity:** Agents get a name, a wallet, and more records other agents can check. - **Decentralised hosting:** Point a subname to content hosted on IPFS or other decentralised storage to serve websites and other static content. See [Use cases](/overview/use-cases) for examples across wallets, payments, AI agents, chains, games, and communities. +## Benefits + +- **Better UI/UX:** Users send to a readable name instead of a 42-character hex string. +- **Smoother onboarding:** Users claim a name at signup, not a wallet address. +- **Higher retention:** A name is an identity users own. An address is not. +- **Existing network:** No integrations to chase. 1,000+ apps already support ENS. +- **Portable identity:** Profiles and addresses resolve in any ENS-compatible app. +- **Optional revenue:** Charge for renewals or premium names, or keep issuance free. +- **Stronger security:** Showing a name and avatar helps users verify a recipient, which can reduce address-poisoning and lookalike-address scams. +- **Brand distribution:** Users carry your brand into every app they touch, and every transaction becomes a brand impression. + ## L1 subnames L1 subnames are created through ENS contracts on Ethereum. Their guarantees depend on the parent name's fuse configuration and the minting contract used. diff --git a/overview/make-usernames-universal.mdx b/overview/universal-usernames.mdx similarity index 54% rename from overview/make-usernames-universal.mdx rename to overview/universal-usernames.mdx index 0321a49..9159650 100644 --- a/overview/make-usernames-universal.mdx +++ b/overview/universal-usernames.mdx @@ -1,17 +1,23 @@ --- -title: "Make your usernames universal" -description: "Give the usernames you already issue an ENS name." +title: "Universal usernames" +description: "Connect ENS to your existing usernames." sidebarTitle: "Universal usernames" icon: "globe" --- import { FlowExplainer } from '/snippets/flow-explainer.jsx' -Inside your product, `happy.brand` is enough to find someone or send them money. Outside it, the name means nothing. No other wallet has heard of your suffix, so your user goes back to pasting an address. +## Two ways teams do usernames today -The usual fix is to ask every wallet to support your names. That is a long list of integrations you do not control. +Almost every product that ships usernames picks one of two approaches. Both leave the user stuck at the same place. -The shorter path is a second name pointing at the same person and the same records: +**Plain usernames:** usually displayed like `@alice` or `alice`. Fast to build, and inside your app they work exactly as intended. But the name only exists in your database. Send `@alice` to someone in another wallet or app, and it simply won't work. Users are back to copying and pasting an address. + +**A custom TLD:** something like `alice.wallet` or `alice.pay`, whatever reads well next to your brand name. This looks like the better option but it's not. Your TLD isn't in DNS and isn't in ENS, so no wallet outside your product has any way to look it up. Making it work means asking every wallet, explorer, and app to integrate your naming system one at a time. Also, collisions are the other half of the problem: multiple projects have built competing versions of the same TLD, so `alice.wallet` can resolve to two different people depending on which app you ask. + +## A better way with ENS + +Every username you've already issued gets a matching ENS name. One rule, applied across your whole user base: ``` Your username: happy.brand @@ -25,13 +31,17 @@ Your system stays the source of truth and no data moves. The username just gains This does not turn `.brand` into a new ENS top-level domain. Each user gets an ENS name for the identity they already have. -## ENS is not only about .eth +## ENS isn't limited to .eth or Ethereum + +Two (wrong) assumptions people usually make. + +**You don't need a `.eth` name.** -Two assumptions stop teams before they start. +`happy.brand.eth` and `happy.brand.id` resolve identically. The first means registering `brand.eth`. The second means taking a domain you already own, turning on DNSSEC, and [importing it into ENS](https://docs.ens.domains/learn/dns/). Same result, so pick on branding. -**You do not have to use a `.eth` name.** Either register `brand.eth` and issue `happy.brand.eth`, or take a domain you already own like `brand.id`, turn on DNSSEC, and [import it into ENS](https://docs.ens.domains/learn/dns/). Both resolve the same way, so choose on branding, not mechanics. +**ENS isn't only for Ethereum.** -**ENS names are not only for Ethereum.** One name holds an address record per chain, and they need not be EVM chains. Bitcoin, Solana, Base, Arbitrum, and Ethereum can all sit on the same name, alongside profile fields like a display name and avatar. +One name holds a separate address record for every chain, and they don't have to be EVM chains. Bitcoin, Solana, Base, Arbitrum, and Ethereum sit side by side on the same name, along with profile fields like display name and avatar. Your user has one name and it works everywhere they hold funds. ## Follow one lookup @@ -55,7 +65,7 @@ Records can live in the database you run today, on an L2, or on another chain. N ## What this does not do -- Your existing suffix does not become part of ENS. Users gain an ENS name; `.brand` stays yours. +- Your existing TLD does not become part of ENS. Users gain an ENS name; `.brand` stays yours. - Support varies. Most major wallets resolve these names, but not every app does, so test the ones your users actually use. - Anything served this way is public. Addresses, avatars, and profile fields are readable by anyone who asks.