Namespace - Quarterly Reports

Q4 (2025) Namespace Service Provider Report

Summary

This quarter was defined by:

  • Shipping Celonames end-to-end (contracts, UI, verification flows, post-launch promo).
  • Subname growth by >500% (total of ~740,000 subnames)
  • V2 platform (web app, UI Kit + Storybook, SDK/API updates, monitoring, avatar service).
  • Scaling BD + partnerships with a more structured CRM approach and ENS Alliance.
  • Continuous research, conversations, and negotiations with new projects.
  • Working on a feature-rich universal resolution service.
  • TLD application finalized and submitted.

BD & Growth

Scaling BD + partnerships with a more structured CRM approach.

Outreach & Pipeline

  • 335 companies reached
  • 971 leads contacted
  • 29 active opportunities
  • 17 integration proposals sent

Active conversations include a major DeFi app exploring usernames, collaboration with a naming service, a large blockchain evaluating ENS subdomains for permissionless websites, a zk-based government-supported chain and a KYC provider, as well as additional blockchains and wallets.

As usual, sales cycles remain long.

ENS Alliance

Launched a pilot initiative called ENS Alliance V1. Continuation of our intention to create a unified, dedicated BD coordination layer for the ENS ecosystem. Based on feedback from interested Service Providers and Delegates, we decided to start with a minimal, practical implementation and evolve it iteratively. A key proposed component is the Dojo: shared CRM pipeline for transparent tracking of leads, intros, updates, ownership, and outcomes. Designed to prevent overlap in outreach, improve handoffs, and increase the conversion of ENS-related opportunities.

Currently in the private test phase between 2 ENS ecosystem BD teams.

Product/platform work

Namespace v2 app

  • Search & Register flow
  • Onchain and offchain management with all features
    • Features left to build: revenue splitting from subname mints, ability to add sponsored wallet to cover gas fees, and minting subnames with different tokens.
    • On hold until ENSv2/Namechain.
  • Profile + records edits and mobile UX fixes
  • Follow/unfollow with EFP
  • ENS Widget with ENSRewards
  • Announcing private alpha soon

*Note: given other higher-priority client work, the launch of the v2 app has been delayed.

ENS components

Built a React-based component library that enables teams to embed ENS functionality directly into their apps with minimal effort.

Includes:

  • ENS Registration Form – drop-in component for registering ENS names in any React app.
  • ENS Record Management – add record editing and profile management to existing apps.
  • Subname Mint Form – enable minting subnames for activated ENS parent names.
  • Offchain Mint Form – create offchain subnames in your app via Namespace’s Dev portal.

Designed for reuse across apps, wallets, and partner integrations.

Avatar Service

Avatar service for ENS names/subnames on Mainnet & Sepolia – upload avatars and headers with SIWE auth (EOA + smart contract wallets), pre-registration support, and short canonical URLs (avtr.cc/{subname}) under 31 bytes for onchain storage compatibility with gasless, deterministic updates.

What it does?
  • Upload/update/delete avatars (2MB max) and headers (5MB max)
  • Supports JPEG, PNG, GIF, WEBP formats
  • Two upload flows:
    • Immediate — for existing ENS records (instant confirmation)
    • Pending — for pre-registration (5-minute verification window before ENS record exists)
  • Short canonical URLs: https://avtr.cc/{subname} — typically under 31 bytes, suitable for onchain storage in 32-byte constraints
  • Gasless & deterministic updates — change your avatar without any onchain transaction
How it works?
  • Authentication: SIWE (Sign-In With Ethereum) — no JWTs, cryptographic proof of ownership
  • Wallet Support: EOA signatures, Smart Contract wallets (ERC-4337/EIP-1271), pre-deployed accounts (ERC-6492)
  • Storage: Google Cloud Storage with 1-hour cache control
  • Verification: Cron job runs every 5 minutes to validate pending uploads against ENS ownership
  • Rate Limiting: 5 req/min uploads, 10 req/min auth/delete, 100 req/min reads
Key endpoints
Method Path Purpose
POST /profile/:network/:subname/avatar Upload avatar
POST /profile/:network/:subname/header Upload header
DELETE /profile/:network/:subname/avatar Delete avatar
DELETE /profile/:network/:subname/header Delete header
Links

SDK updates

1. New Avatar SDK

TypeScript SDK. Allows devs to add avatar and header management to apps with minimal code.

  • Handles wallet authentication (SIWE) automatically
  • Manages image uploads with progress tracking and file validation
  • Works on Mainnet and Sepolia

Integrating ENS avatar management previously required building custom auth flows, upload handling, and wallet adapters. This SDK handles all of it – developers just pass their wallet and call upload.

2. DevX (SDK + Docs)

SDK:

  • Built-in Adapters: Pass Viem WalletClient or Ethers Wallet directly
    • SDK auto-detects, no wrapper code needed
  • Wagmi Compatible: Works seamlessly with useWalletClient hook
  • Raw Implementation: Manual flow available for custom wallets or server-side signing
  • TypeScript First: Full type safety and IntelliSense support
  • Framework Agnostic: Use with React, Vue, Node.js, or vanilla JS
  • npm link: https://npmjs.com/package/@thenamespace/avatar

Docs:

  • A new page about how WaaS providers can integrate ENS.
  • Updated all starter kits in Docs with the avatar service.
  • Added OpenFort starter kit.
3. Offchain Subnames Package
  1. One-Click Multi-Chain Address Setup
  2. Ability to set a wallet address across 17 EVM-compatible chains with a single API call
  3. Previously required 17 separate calls — now just one
  4. Reduces integration time and code complexity significantly
  5. Expanded Blockchain Support
  6. Monad — Popular new L1 blockchain (upgraded to mainnet in November)
  7. Push Chain — Decentralized communication network
  8. Default EVM Chain — New ENS standard (ENSIP-19) for universal EVM addresses
4. Onchain Subnames Package
  • Simplified Setup
    • New zero-configuration option — start minting subnames with just one line of code
    • Clear separation between mainnet and testnet environments
  • Official Rebranding
    • Package officially moved under the @thenamespace organization on npm
    • Improved discoverability and trust
  • Bug Fixes
    • Fixed Scroll network integration
    • Resolved testnet configuration issues
5. Changelogs
6. Key Pull Requests (Q4 2025

Rebrand:

Stats

  • 740,000 total subnames (>500% growth from the past quarter)
  • 10,000,000 resolution requests (100% growth from the past quarter)
  • 18 new namespaces
  • 15 new L2 registries deployed
  • An additional 200k Base subnames resolution requests this quarter (indicating real usage)
  • Note: we’re still working on an improved stats page. Haven’t had the time to finish it yet.

Ecosystem, community, partnerships

Celonames launch :tada:

We built and continue to maintain a chain-wide identity and naming service for the Celo ecosystem. The implementation is conceptually similar to the Base ↔ Basenames service, but uses celo.eth and includes additional features such as ZK-based human verification via the Self protocol.

Overview:

  • Celoname registration flow (including minting, profile setup, transfer, and record editing).
  • Pricing based on Subname length.
  • Revenue share with ENS DAO (10% of total minting fees).
  • Whitelist + reservation strategy and implementation.
  • Blacklist strategy for brand safety.
  • Self verification added, free-claim flow, and edge-case testing across geographies.
  • Launch planning, “private → public” rollout, stress testing.

Noteworthy links:

Next Steps:

  • Add L2PrimaryName (once L2ReverseRegistrar has been deployed)
  • Integrate Celonames Docs inside official Celo Dev Docs.
  • Work with the Celo team to propagate the use of Celonames in the ecosystem.
  • Continue to build, maintain, and improve Celonames.

PCC / BuidlGuidl / EF

We continue to work with the Pakistan Crypto Council (PCC) and the Pakistan Virtual Assets Regulatory Authority (PVARA) to identify the most suitable solution. Discussions are focused on exploring nationwide initiatives around digital identity and Ethereum education. Following discussions with Consensys and Consensys Academy around developing an Ethereum-centric educational program for Pakistan, which ultimately proved not to be the right fit, we connected with BuidlGuidl, the most well-aligned partner for the initiative. The proposals are currently in a conceptual phase and under review by relevant government stakeholders. Given the public-sector context, progress is expected to be milestone-driven and long-term in nature.

TLD

We have officially applied for a TLD through the Applicant Support Program (ASP) with ICANN, which could reduce the financial burden for us. In parallel, we are working on a contingency plan in case the application is not approved. This includes exploring funding options that would allow us to apply for a TLD without locking ourselves into contracts or obligations that could interfere with our work with ENS/Namespace.

DevConnect

We attended DevConnect, representing ENS, talked Subnames and their usecases, ENS x AI identity and had Namespace Office hours with ENS Labs.

Other

  • New ENS article published, talks about ENS, trading, tokenization, etc.
  • ENS x AI group - still hosting weekly calls, 50+ members, recently spoke to 8004 team.
  • Immutable websites demo by Simon using Celonames and Filecoin.
  • We’re always thinking of ENS even when planting trees :deciduous_tree: (end-of-the-year tradition).
  • Working on ENS AI CEO – building an AI agent designed as a symbolic representation of ENS. The core purpose is to act as a memetic interface to ENS and become an AI personality tied to ENS culture. It can help with answering questions, education, light commentary, and amplification of the ENS ecosystem activity (releasing soon)
  • Working on Resovio – feature-rich, universal ENS resolution service that simplifies reverse resolution, bulk resolution, fetching records in a single API call, etc., built for internal use and will soon be open-sourced.
2 Likes