Namespace: SPP3 Quarterly Reports

Service Provider Program Reports
2

SPP3 / Q3 2026

Q3 was largely focused on preparing Namespace for ENSv2, expanding our developer infrastructure, improving the core Namespace app, growing business development, starting with marketing, and continuing to experiment with new ENS use cases through new products such as ENS Diamonds, Awakened, ENS Forge, and Namera.

:hammer_and_wrench: Engineering

1. ENSv2 Readiness & Migration

A major focus throughout Q3 was preparing for ENSv2. We made significant progress toward one of our key milestones: enabling L1 subname issuance on ENSv2 from Day 1 of the ENSv2 launch.

More info on the forum post here.

As part of this, we’ve developed:

  1. A complete set of contracts for subname minting on mainnet, using new ENSv2 registries.
    • Built a more modular, plugin-based contract architecture intended to make Namespace easier to extend as ENSv2 evolves.
  2. The minting and pricing logic has moved completely onchain.
  3. Built a proof of concept webapp where users can start issuing subnames on ENSv2.
  4. We’ve added extra features that have been requested by the community:
    • Split payments – ability to select multiple wallets as payment receivers
    • Token gating with multiple NFTs with AND/OR logic
    • Permission and Resolver control

ENSv2 demo is live on Sepolia at demo.namespace.ninja, showcasing all of this.

Note* Existing V1 activations will continue to work. New name activations will move to ENSv2 completely, while existing customers will have an optional migration page to migrate their names and subnames to ENSv2 whenever they want.

2. Avatar and Header Service

Our open-source ENS Avatar Service also received several upgrades including:

  • Support for Sign-In with Ethereum v2.
  • A new API for resolving NFT and IPFS-based avatars.
  • Moved signature verification to SIWE v4
    • Including smart contract wallets (EIP-1271 & EIP-6492).
  • Released Avatar SDK v2 (@thenamespace/avatar).
    • Used by ENS Components and our partner demos.
  • Created Avatar SDK Skill for AI Agents to integrate Avatar Service.
  • Open-sourced the metadata service and added monitoring and metrics.

More detailed overview of Avatar & Header service was published on the forum here.

3. ENSIP-X: Record Verification

We developed a proposal for verifiable ENS records, allowing records to include cryptographic or external proof that the entity controlling a record also controls the referenced account or resource.

Work during the quarter included:

  • Building a working proof of concept / demo here.
  • Collaborating with other ENS ecosystem contributors working on similar problems.
  • Publishing the proposal on the forum for community feedback.

Twitter thread explainer.
Community sentiment is good – Link1, Link2.

4. Unified record discovery (idea stage)

We are also exploring a separate proposal around unified record discovery across L1, L2, and Offchain ENS records, although this remains at an earlier research stage.

:building_construction: Existing Products updates

1. Namespace App – app.namespace.ninja

The main Namespace app was improved and redesigned during the quarter.

We built a new shared UI component library that is now being used across Namespace products to improve consistency and speed up development. The new design brings Namespace closer to the ENSv2 design language while improving navigation and making the app easier to understand.

Updates include:

2. ENS Components - enscomponents.com

ENS Components were updated alongside Namespace app redesign to maintain visual consistency.

We released ENS Components 2.0.0, which is now live in the Namespace app and includes:

  • Avatar and header uploads
  • ENS name normalization
  • Support for imported DNS names
  • Migration to our new UI component library

Additional ENSv2 compatibility work is also underway as the underlying protocol contracts stabilize.

3. Resolvio - resolvio.xyz

Work continued on Resolvio, our unified ENS resolution API service.

Q3 improvements included:

  • New ENS avatar/profile resolution endpoints.
  • Better caching and performance improvements.
  • Scaling improvements.
  • Continued work toward enterprise-grade reliability.

The architecture was tested around significantly higher request volumes using caching and Kubernetes autoscaling.

4. Namera – namera.ai

Namera is a permission layer for autonomous agents. It gives autonomous agents scoped, programmable access to smart wallets without giving them unrestricted access to private keys.

The product uses smart accounts, session keys and policies to define what an agent can do.

During Q3:

  • The product moved into early beta – waitlist is open :rocket:
  • 40+ builders signed up.
  • Integrated Alchemy Modular Accounts.
  • Built dashboard-based wallet/account management.
  • Added transaction simulation and execution, and session-key lifecycle management.
  • Chose a fully self-custodial architecture for the initial release.
  • Started designing GCP-backed key storage for users who prefer a simpler UX.

Every Namera agent can get namera.id subname, tying agent permissions & identity together.

Namera received coverage from 3 publications this quarter:

:rocket: New Products and Tools

1. Subname.dev (not live yet)

Development started on subname.dev, a developer-focused infrastructure and deployment platform for launching ENS-compatible subname systems across L2 chains.

Rather than requiring developers to manually assemble contracts, resolvers, gateways, and indexing infra, subname.dev is designed as a deployment kit that packages these components together.

Initial design work was started, with very early stage proof of concept available at https://subname-dev-portal.namespace.ninja/

The product specification and architecture were defined during Q3, with the first deployment and testing of our first proof of concept now underway.

2. ENS Forge (live) – ensforge.com

We shipped ENS Forge, a developer toolkit for interacting with both ENSv1 and ENSv2.

The initial TypeScript SDK includes:

  • One API for ENSv1 and ENSv2 with auto-detection.
  • Read, write, and batch operations.
  • Promise or typed Effect APIs behind every action.
  • HCA permissions & sponsored actions for apps and agents.
  • Ability to plan and manage multi-step actions like registration and migration, including simulation, batching, fallbacks, and resuming interrupted flows.

We started experimenting with sponsored and gasless ENS interactions, including integrations with account-abstraction infra such as Pimlico and Rhinestone.

X thread / announcement link.
GitHub repo.

:game_die: New Sidequests / Experiments

1. ENS Diamonds (live) – ens.diamonds

We launched ENS Diamonds, an experimental way for multiple people to collectively acquire and manage valuable ENS names.

During Q3 we:

  • Built and launched the app.
  • Added privacy and front-running protections, and referrals.
  • Started conversations with ENS marketplaces around potential integrations.
  • Performed multiple security reviews.
    • 5 AI audits and 1 human audit with the Nethermind team.

Launch announcement.
Audits overview.
GitHub repo.

2. Awakened – Agent NFTs

An experiment combining NFTs, ENS identities, and AI agents.

The initial product allows a single NFT to be “awakened” into an autonomous AI agent with its own ENS name, ERC-8004 identity, ERC-6551 token-bound account, and AI-powered personality and capabilities. Each awakened NFT can have its own identity, wallet, memory, and behavior, turning a static collectible into an interactive onchain agent that can act, communicate, and evolve over time.

During Q3 we:

  • Completed the initial registration flow for Ethereum and Base.
  • Built a simple four-step flow: create → preview → publish → register.
  • Added ERC-8004 agent identity support and ERC-6551 token-bound wallets.
  • Implemented bindings using Adapter8004.xyz by Unruggable team.
  • Integrated ENS/subname registration + profiles setup.
  • Developed a launchpad flow for creating entire agent-NFT collections.
  • Began testing larger NFT collections and scaling requirements.

Demo.

3. Cross-chain naming bridges (for SuiNS and SNS)

We built CCIP-Read gateways that let names from other chains resolve through ENS, so any ENS-aware wallet or app can read them without new integrations.

SuiNS × ENS

Any .sui name resolves as name.onsui.eth (happysingh.onsui.eth returns happysingh.sui). SuiNS stays the source of truth, and name holders can add other chain addresses and text records on top.

Demo link.
GitHub link.

Note* We were working with SuiNS team but the integration paused since the leadership changed.

SNS × ENS

The same model for Solana .sol names under onsol.eth. The gateway, contracts and demo app are built; mainnet deployment is next.

Both SuiNS and SNS combined with ENS integration closely resemble recent Hyperliquid implementation done by .hl names team.

Given this is becoming a trend, we were considering building a dedicated how-to guide that would show step-by-step instructions how to make any Naming Service compatible with ENS.

:handshake: Business Development & Partnerships

Business development in Q3 increasingly focused on wallets, exchanges, fintechs and neobanks, where ENS can provide a practical improvement to the end-user experience.

We are currently in active conversations with 15 high value companies building wallets, exchanges, trading apps, payments, and fintech apps about integrating ENS.

Several of these conversations have progressed beyond initial outreach, with tailored ENS integration demos, technical materials, functional prototypes, and walkthroughs delivered to prospective partners. Some are now under internal or technical review, while others remain in earlier-stage discussions around ENS resolution and subnames.

Polybaskets

Polybaskets is prediction-market basket app. They integrated Namespace offchain subnames. Users and trading agents get .polybaskets.eth subnames, and those subnames now show on the Polybaskets leaderboard storing Polkadot and Vara address. They also shipped an agent skill that lets AI agents claim their own {name}.polybaskets.eth. Will be live after this PR gets merged.

Bonuz

We partnered with Bonuz wallet to integrate ENS and started issuing bonuz.id subnames mapped to its existing username system. This allows Bonuz to retain its existing username system while using ENS to make those usernames resolvable across the broader Ethereum ecosystem.

Pakistan Crypto Council (PCC) / Pakistan Virtual Asset Regulation Authority (PVARA)

We continued expanding our relationships with PCC and PVARA, including conversations around potential large-scale .eth usernames deployment ahead of CBDC rollout. We remain engaged with Bilal bin Saqib (CEO & Chairman) and Talal Ahmad (Chief of Staff). As part of our broader relationship-building efforts, we are also engaged with Waqar Zaka, a prominent KOL and crypto advocate, whom we gifted the zaka.eth name. Announcements are pending.

Note* Demos & Proposals

We moved from static proposals to working demos. With AI speeding up our build process, we produced custom demos for wallets, exchanges, bridges, chains, neobanks, and NFT communities in hours instead of days/weeks. We also started building reusable wallet demos that can be adapted to new prospects quickly, and can be used by anyone inside or outside Namespace.

:globe_showing_europe_africa: Events & Ecosystem

Events

We attended several events during Q3:

  • Malaysia Blockchain Week
  • CoinFest Asia
  • ETH Belgrade
  • ETHGlobal Tokyo

We used these events primarily for business development, identifying projects for ENS support (resolution and subnames), developer outreach, and ENS ecosystem building.

Malaysia Blockchain Week and CoinFest Asia in particular generated a significant number of wallet, exchange, and fintech opportunities.

At ETHBelgrade, we helped support the ENS hackathon and selected 3 winning projects.

ENS x AI

We continued hosting and participating in the weekly ENS x AI ecosystem calls, where builders working on ENS, agents, identity, ERC-8004, ERC-6551, wallet infrastructure, and related standards regularly present their work and receive feedback and further guidance.

Join us here!

:ocean: Marketing & Growth

Q3 also marked a bigger investment in Namespace growth and communications.

We hired Maxi.eth as Head of Growth in late July and increased the amount of marketing around product updates, integrations, event activity and partner launches, and will start working more closely with partners on joint announcements rather than treating integrations as purely technical releases.

The new comms strategy is already showing good results. We earned 115k impressions from July ‘25 to July ‘26 (~10k/mo average). This number grew to 27k impressions in Aug and 39k in Sep.

Q4 will be even more interesting with multiple co-marketing activations coming up.

August

image
image1498×358 82.1 KB

September

image
image1498×360 79.9 KB

:bar_chart: Stats

Key metrics:

  • 871,975 total subnames issued through Namespace.
    • 863,137 Offchain subnames
    • 3,564 Base subnames
    • 2,098 Ethereum subnames
    • 353 Optimism subnames
  • 24.5M+ ENS resolutions processed.
  • 248 active namespaces – .eth names issuing subnames.
  • 108 L2 registries deployed.

npm downloads in Q3 (Jul 1 – Sep 30):

  • @thenamespace/offchain-manager: 2,676
  • @thenamespace/ens-components: 2,331
  • @thenamespace/uikit: 1,151
  • @thenamespace/avatar: 833
  • @thenamespace/mint-manager: 581
  • @thenamespace/addresses: 483
  • @thenamespace/ens-components-v2: 371
  • @thenamespace/indexer: 160

ENS Forge npm downloads since launch (Aug 29 – Sep 30):

  • @ensforge/contracts: 1,537
  • @ensforge/core: 1,470
  • @ensforge/sdk: 1,332
  • @ensforge/react: 1,305
  • @ensforge/hca: 485

:broom: Operations & Housekeeping

We also spent meaningful time improving internal infrastructure and reducing technical debt.

Work included:

  • New docs pages – Fintechs & Neobanks, Wallet infra / WaaS, Universal Usernames.
  • Released Mint Manager SDK v2.0.0, with ENS name normalisation, mint parameter checks before a transaction is sent, and a checkName helper.
  • Major Notion cleanup and restructuring.
  • GitHub cleanup / removed deprecated repos and services.
  • Cloud infra optimization - consolidating roughly 20 test databases/services.
  • Better staging/preview deployment workflows.
  • Automated end-to-end application testing.
  • Improved monitoring and logging.
  • Built a Grafana MCP service, allowing developers and coding agents such as Claude to query application logs directly while debugging.
  • Lastly, we celebrated our 3rd birthday :tada:
3 Likes