🥷
Namespace
  • [ Introduction ]
    • ENS
    • Namespace
      • Products and Services
      • Use Cases
  • [ Namespace Platform ]
    • Overview
    • Search & Registration
    • Manager
      • Listing an ENS Name
      • Features List
    • ENS Widget
    • Farcaster Frames
      • Default Frame
      • Custom Frame
    • Tutorials and Demos
  • [ Dev Docs ]
    • Overview
    • How-To Guides
      • Mint L1 or L2 subnames using SDK
    • Smart contracts
      • Namespace Minter
    • Backend API
      • POST /api/v1/mint
      • POST /api/v1/mint/verified
      • GET /api/v1/listings/availabe
    • Offchain Subnames API
      • Setting Up Offchain Resolver
      • Minting
        • Create a new ENS subname
      • Subnames
        • Resolve subname address
        • Check subname availability
        • Retrieve Complete Subname Dataset
        • Subname Search
        • Delete Subname
      • Text Records
        • Create or update subname text record
        • Delete a subname text record
        • Retrieve single subname text record
        • Retrieve all of subname's text records
      • Custom Data
        • Create or update custom subname data
        • Delete custom subname data
        • Retrieve single custom data object
        • Retrieve all of subname's custom data
    • Namespace SDK
      • Offchain Manager
        • Installation
        • Methods
        • Generate API key
        • CreateSubname
        • DeleteSubname
        • IsSubnameAvailable
        • GetFilteredSubnames
        • TextRecords
        • DataRecords
      • Indexer Manager
        • Installation
        • Methods
        • GetL2Subname
        • GetL2Subnames
        • GetL1Subnames
        • GetL1Subnames
        • GetL1Subname
      • Namespace Client (deprecated)
        • Installation
        • GetListedName
        • GetMintDetails
        • GetMintTransactionParameters
        • IsSubnameAvailable
        • GenerateAuthToken
    • Namespace L2 Subnames
  • [ ecosystem ]
    • Partnerships
    • Integrations
    • Links
    • ENS ideas and projects
  • [ Legal ]
    • Disclamer
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  • Who do we work with?
  • Wallets
  • Payment apps
  • AI agents and launchpads
  • RaaS (Rollup-as-a-Service) providers
  • Blockchain infra, tools, & service providers
  • Wallet-as-a-Service providers
  • Games
  • Identity (apps or services)
  • Communities
  • Individuals (entrepreneurs, influencers, bloggers)
  • All Others
  1. [ Introduction ]
  2. Namespace

Use Cases

PreviousProducts and ServicesNextOverview

Last updated 11 days ago

If you're interested in any of the use cases below, or to tell us about a new one, we're happy to hear from and work with you.

Feel free to join our Telegram group.

Who do we work with?

Wallets

Custom-branded wallet names (e.g., alice.metamask.eth) replace traditional wallet addresses, allowing users to register and use ENS subnames for their wallets. This improves wallet UX, simplifies onboarding, and enhances transaction safety for users.

Payment apps

Payment apps integrate ENS subnames to simplify transacting for users by replacing complex wallet addresses with human-readable names, enabling faster, more secure, and user-friendly, and even cross-chain payments.

AI agents and launchpads

AI agents and launchpads use ENS subnames to create unique, verifiable identities for all AI agents, improving discoverability, interoperability, and user trust while offering a decentralized naming service for AI agents from the launch.

RaaS (Rollup-as-a-Service) providers

RaaS providers leverage ENS subnames to offer a complementary chain-wide naming service for every rollup. Enabling scalable, branded identities for rollups and enhancing the user experience with human-readable names.

Blockchain infra, tools, & service providers

Companies that focus on providing developers the best suite of tools to build on any blockchain benefit from having ENS as the best naming service in Web3 to make their offering more complete and appealing to developers.

Wallet-as-a-Service providers

Wallet-as-a-Service providers use ENS subnames to offer branded, user-friendly wallet names, enabling one wallet name for all chain addresses. Giving subname registration as a service to wallets.

Games

Games use ENS for custom-branded player usernames (alice.yourGame.eth), offering cross-chain functionality and interoperability, unlike siloed, centralized usernames that lack utility beyond their platforms.

Identity (apps or services)

Identity requires a name and all identity-related apps and services should integrate ENS as a naming service for their clients or users.

Communities

Communities use subnames to strengthen their collective identity, boost brand reputation, and create a more connected, recognizable presence across Web3.

Individuals (entrepreneurs, influencers, bloggers)

ENS advocates issue subnames to their community, followers, readers, or anyone else interested in getting a name for their wallet when onboarded to crypto.

All Others

Identity starts with a name. And all user-centric or AI Agent-centric apps, protocols, or chains need an identity and a naming service.

Namespace Builders