SPP2: NameHash Labs - Application

0. Introduction

0.1. Proposal Summary

NameHash Labs is an existing ENS Service Provider with a team of 14. We are seeking a $1.1M budget from the ENS DAO to deliver key infrastructure for the ENS ecosystem.

This includes 8 substantial ENS infrastructure engineering projects, to include ENSNode, ENSAdmin, NameGraph, and NameAI to address urgent ENS infrastructure needs:

1. Close critical ENS infrastructure gaps:

Indexed ENS data is vital for the upcoming launch of ENSv2 and Namechain. Existing ENS indexed data providers (the ENS Subgraph) are fundamentally unsuitable for ENSv2 and a replacement is critically required for many of ENS’s most important apps, including the official ENS Manager App among many others.

2. Strengthen the decentralization and “unstoppability” of ENS:

Our infrastructure under development removes a strict dependency on many centralized offchain gateway servers whose downtime would otherwise shut down impacted multichain ENS names that are key to the future of ENSv2 and Namechain, such as subnames of base.eth, linea.eth, or tokenized DNS names such as .box names or 3DNS names.

3. Deliver game-changing ENS protocol innovations:

We are engineering radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains. This can be contrasted with the status quo strategy that requires time-consuming routing through the multi-step CCIP-read handshake process and offchain gateway servers that are potentially centralized or potentially implement request tracking. For most ENS names, enjoy ~20 times faster ENS resolutions of live (not stale) ENS records with more privacy and no centralized dependencies.

4. Support a restabilization of declining ENS DAO revenues:

We are executing a number of infrastructure-level strategies to help boost and restabilize ENS DAO revenues to ensure the indefinite continuation of ENS protocol development.

With your approval of our $1.3M total “Extended Scope” budget (please vote us to be your #1 ranked proposal :pray:), ENS will additionally gain solutions for other urgent needs, including:

5. Guarantee the creation of an ENS Referral Program to promote the launch of ENSv2 and Namechain with a minimum budget of $50k.

The guarantee is simple, if our “Extended Scope” budget is approved and if the ENS DAO still has not launched a different ENS Referral Program prior to the launch of ENSv2, then upon the launch of ENSv2, we will deploy our own permissionless ENSv2 Referral Program contracts. We will fund these contracts ourselves with $50k to provide revenue sharing rewards for registrar apps that refer a minimum number of their users to make .eth registrations and renewals.

We will also invest in the creation and distribution of marketing materials, community outreach, and related “microsites” for the ENS Referral Program.

6. Boost ENS revenue stabilization and the long-term health of the ENS DAO through a new (and much needed!) infrastructure project - ENS TokenScope:

We will deliver infrastructure for ENS registrar apps to easily identify that a name might be taken, but could still be purchased for a fair price and to help facilitate that aftermarket transaction. This action further supports ENS DAO revenues as secondary market transactions ultimately encourages more .eth registrations and renewals.

Relatedly, we will also deliver ENS infrastructure to trace the relationship from an ENS name (including tokenized DNS names) to the specific NFT that tokenizes the ownership of the name.

ENS TokenScope closes a key vector of adoption risks for ENS vs. Namechain’s highly VC funded competitors, and supports the attraction of new DNS TLDs from the upcoming ICANN auctions to tokenize their names on Namechain.

Our team of 14 includes highly accomplished senior engineers and is delivering big for ENS.

Now we need your help.

We are 100% bootstrapped and have never raised any money from investors. The ENS Service Provider Program is crucial for us to continue supporting our team and maintaining our commitment to ENS.

We really appreciate your consideration for funding and thank you so much for your support.

0.2. ENS Key Infrastructure Needs

Our team is building key solutions for ENS’s 3 key areas of need:

  1. Critical infrastructure gaps for ENSv2;

  2. DAO financial stability; and

  3. Developer enablement for more big ENS integrations.

0.2.1. Critical Infrastructure Gaps for ENSv2

First, and most importantly, ENSv2 has a critical unsolved infrastructure gap: indexed data.

The ENS Subgraph has been critical infrastructure for ENSv1, serving as the source of indexed ENS data. However, the Subgraph is fundamentally unsuitable for ENSv2.

How critical is the need for indexed ENS data? There’s over 700 million / requests for it a year, and growing! And this is only for mainnet!

Critical ENS Apps currently rely on this service, including:

The official ENS Manager app.

Core ENS Developer Tooling like ENSjs.

Wallets like Rainbow.

Marketplaces like Vision.

Chain explorers like Blockscout.

Social apps like the Ethereum Follow Protocol.

… and many other key platforms that form the ENS ecosystem, including:

As you can see, indexed data is key to the ENS protocol.

However, even for ENSv1, a strong argument can be made that the Subgraph is already unsuitable. Data for 90% of ENS names is already missing in the Subgraph!

The Subgraph has many big problems. Chief among those: the Subgraph is single-chain only.

Let’s make some practical examples. Because the Subgraph is single-chain only, this means for over 90% of ENS names it’s not currently possible to answer fundamental questions like:

What are all the names owned by this address?

Or, what are all the social records / chain addresses set on this name?

This data is currently available only for mainnet, which is why you may not have noticed the problem yet.

But ENS is multichain, and ENS is offchain, too! 90% of ENS names are already issued off of mainnet, this includes base.eth subnames on Base, linea.eth subnames on Linea, and offchain subnames including uni.eth, cb.id, and many more.

And crucially, what happens with ENSv2? For ENSv1 the Subgraph at least is working for direct subnames of .eth on mainnet.

However, when ENSv2 launches, direct subnames of .eth are transitioning off of mainnet to Namechain.

:fire: The limitations of the Subgraph are critical.

Key limitations include being single-chain only. ENS is already 90% multichain, the key exception has been .eth on mainnet. However with ENSv2, even .eth is becoming multichain!

:star: We need to ensure ENSv2 launches with a strong data indexing solution!

0.2.2. DAO Financial Stability

ENS is blessed to have a meaningful financial runway saved in reserves. However, we should take note:

:fire: ENS Revenues are trending downward.

The ENS DAO daily revenues graph from Steakhouse show a concerning trend that would be unwise to dismiss.

DAO Revenues originate from .eth registrations and renewals.The historical active .eth graph from Makoto shows this critical metric for ENS dropping over time.

Growing subnames in general is good for ENS, but only direct subnames of .eth produce revenue for the ENS DAO.

:star: We need .eth registrations and renewals to be healthy and growing (or at least stable)!

0.2.3. Developer Enablement for ENS Integrations

ENS provides powerful capabilities, but some developers experience challenges with integrations.

:fire: A number of ENS integrations fail to support all ENS names, use cases, or best practices.

A number of operations in the ENS protocol require special care to implement correctly. A lot of documentation may already exist, but that doesn’t mean developers are correctly reading the docs in full. For important use cases it can be a lot of work to correctly understand, implement, and test. This ultimately is resulting in fewer ENS integrations, or flawed ENS integrations that lead to bad ENS user experiences.

:star: We need to enable developers to more easily build optimal ENS integrations.

0.3. Strategy Overview

The following table outlines the relationship between ENS’s 3 key needs, our solutions, and funding of the basic vs extended proposal scope:

0.4. Our ENS Infrastructure Solutions

To service ENS’s 3 key needs, our team is building 8 key ENS infrastructure projects:

These eight ENS infrastructure projects work together to address the critical needs of ENSv2, enhance DAO financial stability through increased registrations and renewals, and support developers to build more big ENS integrations.

0.4.1. ENSNode

  • Product Webpage
  • Infrastructure Summary
    • ENSNode is the new multichain ENS indexer for ENS and ENSv2.
    • ENSNode builds on Ponder. Ponder’s powerful open source framework enables many of the key ENS indexing innovations in ENSNode.
  • Strategic Goals
    • Fill critical ENS infrastructure gaps for ENSv2.
    • ENS developer enablement.
  • Selected Key Benefits
    • Close critical ENS infrastructure gaps:
      • Indexed ENS data is vital for the upcoming launch of ENSv2 and Namechain. Existing ENS indexed data providers (the ENS Subgraph) are fundamentally unsuitable for ENSv2 and a replacement is critically required for many of ENS’s most important apps, including the official ENS Manager App among many others.
    • Strengthen the decentralization and “unstoppability” of ENS:
      • Our infrastructure under development removes a strict dependency on many centralized offchain gateway servers whose downtime would otherwise shut down impacted multichain ENS names that are key to the future of ENSv2 and Namechain, such as subnames of base.eth, linea.eth, or tokenized DNS names such as .box names or 3DNS names.
    • Deliver game-changing ENS protocol innovations:
      • We are engineering radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains. This can be contrasted with the status quo strategy that requires time-consuming routing through the multi-step CCIP-read handshake process and offchain gateway servers that are potentially centralized or potentially implement request tracking. For most ENS names enjoy ~20 times faster ENS resolutions of live (not stale) ENS records with more privacy and no centralized dependencies.

0.4.2. ENSRainbow

  • Product Webpage

  • Infrastructure Summary

    • Heal millions of unknown ENS names with this ENSNode sidecar service.
  • Strategic Goals

    • Fill critical ENS infrastructure gaps for ENSv2.
    • ENS developer enablement.
  • Selected Key Benefits

    • Reduce ENS’s UX / DX complexity:
      • The ENS community has better things to do than learn about technical complexities like unknown names or encoded labelhashes.
  • Key Metrics / User Traction / Successful Deployments and Integrations

0.4.3. ENSAdmin

0.4.4. ENSv2 Referral Programs

  • Product Webpage
  • Infrastructure Summary
    • Smart contracts for implementing an ENS Referral Program on ENSv2.
  • Strategic Goals
    • DAO financial stability.
    • ENS developer enablement.
  • Selected Key Benefits
    • Incentivize platforms with large existing audiences to integrate and promote .eth registrations and renewals.
    • Permissionless. Not only to participate as a referrer, but also to create and fund.
    • Enables any number of ENSv2 Referral Programs to be created. Each can define their own rules for what qualifies for a reward, how rewards are scored, how they are withdrawn, etc…
    • Mitigates previously voiced concerns of theoretical referral program uncertainties through support for optional finite-lifespan referral program strategies that constrain any “blast radius” of unintended side effects. Let’s try, learn, and iterate with improvements!
    • Compatible with the ENSv2 contracts ENS Labs has open sourced.
  • Additional Links

0.4.5. NameGraph

0.4.6. NameAI

  • Product Webpage
  • Infrastructure Summary
    • Building on NameGuard, NameAI enables sophisticated multi-dimensional scoring for ENS names, helping ENS marketplace apps automatically sort the most attractive names to the top. Through advanced tokenization and analysis techniques, NameAI evaluates all possible ENS names across various attributes to effectively approximate their overall attractiveness, making it easier for name collectors to find and collect more names they love.
  • Strategic Goals
    • DAO Financial Stability
    • Developer Enablement
  • Selected Key Benefits
    • Multi-dimensional Name Scoring: Customize name scoring strategies that are optimized for your community.
    • Advanced Tokenization: Probabilistic parsing of name components into recognized words. Filter names by word-count.
    • Fast and easy integration: even small teams can now offer sophisticated name discovery features, fostering innovation throughout the ecosystem.
  • Key Metrics / User Traction / Successful Deployments and Integrations
  • Additional Links

0.4.7. NameGuard

  • Product Webpage
  • Infrastructure Summary
    • NameGuard provides comprehensive security analysis for ENS names, identifying and preventing malicious use through advanced detection systems. It creates a safer environment for ENS users by detecting potential security risks, impersonation attempts, and usability issues in ENS names, addressing the “sharp edges” that could lead to unexpected or harmful consequences. Currently being rearchitected to leverage ENSNode services, NameGuard will deliver improved analysis capabilities while transitioning core logic to TypeScript for broader application integration.
  • Strategic Goals
    • Developer Enablement
  • Selected Key Benefits
    • Multi-level Protection: Comprehensive security checks across various dimensions
    • Impersonation Detection: Identifies names attempting to mimic legitimate ENS names
    • Confusable Character Analysis: Detects visually similar characters that could be used to deceive
    • Internationalization Checks: Assesses accessibility across language barriers
    • Unified Rating System: Clear Pass/Warn/Fail classifications for security issues
    • Key Metrics / User Traction / Successful Deployments and Integrations
    • Foundation for NameAI, which has already received 40,000,000 requests since launch
  • Additional Links

0.4.8. NameKit

  • Product Webpage
  • Infrastructure Summary
    • NameKit is a developer toolkit that aims to make ENS onboarding fun and easy.
    • Major ENSv2 rearchitecture in progress. NameKit will build for ENSv2 using ENSNode.
    • The vision is to provide developers with tools to easily integrate rich ENS user journeys into wallets, apps, and games. Currently focused on core ENS functionality, NameKit offers a suite of packages including React components, TypeScript utilities, and contract templates that simplify ENS integration.
  • Strategic Goals
    • DAO Financial Stability
    • Developer Enablement
  • Additional Links

1. Applicant Information

1.1. Company Name

NameHash Labs

1.2. Websites

Our company

Our 8 key ENS infrastructure products

  1. ENSNode
  2. ENSRainbow
  3. ENSAdmin
  4. ENSv2 Referral Programs
  5. NameGraph
  6. NameAI
  7. NameGuard
  8. NameKit

1.3. Company ENS Name

namehashlabs.eth

1.4. Primary Contacts

lightwalker.eth and caldonia.eth.

1.5. Company Overview

Founded in 2022, NameHash Labs is dedicated to developing open source infrastructure to support the global adoption of ENS.

We are honored to be an existing ENS Service Provider. Thank you for your trust and for the opportunity.

Our team’s expertise has matured a lot this past year. We’re now in discussions with ENS Labs for taking the lead on some of the key ENS infrastructure responsibilities for ENSv2.

As we continue to mature, with the support of the DAO and ENS Labs, we aim towards one day qualifying to “graduate” from the ENS Service Provider program. As the ENS ecosystem matures, our evolution demonstrates the success of the ENS Service Provider Program’s ability to foster organizations capable of maintaining and advancing critical components of the protocol alongside ENS Labs.

1.6. Requested Budget

NameHash Labs is applying for a 2-year funding stream, in addition to the 1-year stream option. Please see section 4 (Scope of Work & Budget) below for details.

1.7. Team

Our team of 14 passionate “ENS wizards” includes:

  • Seasoned founders, with more than 20 years experience building innovative technology organizations.
  • Former OpenZeppelin maintainers, co-authors of ERC-1271, and auditors of ERCs such as ERC-721 and ERC-1155 (yes, those massively influential NFT standards!).
  • Experts in AI and Natural Language Processing (NLP) who have won numerous international awards. Their expertise helps drive forward key ENS infrastructure such as NameGraph, NameAI, and NameGuard that help ENS grow.
  • Software engineers with extensive background in smart contracts, blockchain indexing, and tokenization protocol standards.
  • Developer relations (DevRel) engineers with broad experience growing developer ecosystems.
  • UX/UI designers with over a decade’s experience crafting beautiful products with strong usability.
  • … and many more talented engineers with years of experience and dedication building for ENS!

Additional details on our team can be found near the bottom of our homepage.

2. Eligibility Confirmation

2.1. Company Age

NameHash Labs was established in 2022.

See section 1.5 (Company Overview) above for more information about our company.

2.2. Team Experience

NameHash Labs has exclusively focused on building ENS infrastructure and products for more than 3 years. Our general blockchain and software development experience goes far deeper.

See section 1.7 (Team) above for more details on our experience.

2.3. ENS Token Endorsement

Nick Johnson (nick.eth) has confirmed with us that he will be endorsing our proposal.

2.4. OFAC Sanctions Compliance

We, NameHash Labs, confirm that neither our organization nor any of our employees, contractors, or executive leadership is located in, or a resident of, an OFAC-sanctioned country. We further confirm that none of our business resources are derived from or routed through any country or entity that is subject to sanctions imposed by the United States (OFAC) or equivalent regulatory bodies. We pledge to remain compliant with all applicable sanctions laws and will promptly notify the ENS DAO if our status changes.

2.5. Multi-Year Stream Eligibility

NameHash Labs is a Season 1 ENS Service Provider applying for a multi-year stream in Season 2.

See section 0.4 (Our ENS Infrastructure Solutions) above for more details on our Season 1 work.

3. Open Source Commitment

We commit to our work as an ENS Service Provider being open sourced and MIT licensed in our GitHub.

4. Scope of Work & Budget

Please see the next post in this thread for our detailed scope of work & budget. The forum doesn’t support enough characters to fit into a single post.

5. Additional Information

Please refer to section 0.4 (Our ENS Infrastructure Solutions) above for info on our 8 key ENS infrastructure projects, including key metrics, user traction, successful deployments and integrations, links to GitHub repositories, websites, and more.

5.1. Outreach for ENS Growth

Our team has been active on the broader Ethereum conference circuit. We’ve participated in many global events to help represent ENS and advocate for it within the broader ecosystem, including:

  • DevCon Bogota
  • ETHGlobal NYC
  • ETHGlobal London
  • DevConnect Istanbul
  • DevCon Bangkok (including frENSday)
  • ETHDenver (2024 & 2025)
  • EthCC
  • ETHDubai
  • deBasel Miami
  • SmartCon Barcelona
  • ETHGlobal SF

We look forward to continuing to engage with the community and support the promotion of ENS at more global events over the coming years.

5.2. Testimonials

Our team is honored to have received a number of testimonials within the ENS community, including the following:



6. Video Introduction

Please see the video at the top of this post in section 0.1 (Proposal Summary) above.

7. Conflict of Interest Statement

We have no conflicts of interest.

4 Likes

(continued from first post above, the forum doesn’t support so many characters in a single post)

4. Scope of Work & Budget

The budget for our “basic” scope of work is: $1.1M.

The budget for our “extended” scope of work is an additional $200k, for $1.3M (total).

We take the responsibilities in this proposal with great care. The “basic” scope is the minimum budget required to properly advance our 8 key ENS infrastructure projects over the coming year. The “extended” scope budget is recommended as it provides a high ROI for ENS.

These budgets align with our team taking a significant load of responsibility for ENS infrastructure development. This includes substantial engineering projects that are not only critical to the successful launch of ENSv2 and Namechain, but also deliver fundamental innovations for how future applications integrate with ENS and perform ENS lookups and resolution.

The budget for this scope of work represents the ENS DAO making an important investment into advancing valuable ENS infrastructure. Several of our ENS infrastructure projects are working to restoratively boost ENS DAO revenues and contribute back to the long-term financial sustainability of ENS. We hope that for every $1 the DAO invests in our team, we return multiples of that as direct revenue back to the DAO in the future.

100% of this budget is devoted to supporting our mission to help ENS grow. Outside of relatively minor overhead costs and hosting expenses, all of this budget goes to supporting the salaries of our 14 existing team members and the recruitment of additional super talented full-time engineers who will dedicate themselves to building up the ENS protocol and ENS infrastructure.

This budget will enable us to further expand our engineering capacity, adding more full-time engineers to tackle the substantial infrastructure responsibilities outlined in this proposal.

Our KPIs for each quarter are to deliver a minimum of 90%+ of that quarter’s total Target Deliverables within the quarter.

At the conclusion of each quarter, we will publish a quarterly report summarizing our delivery for the quarter to the ENS DAO.

We want to ensure we’re always doing our best to maximize value creation for ENS. The ENS Ecosystem evolves quickly. A quarter, and especially a year is a long time in the web3 world. If opportunities are identified for higher-value Target Deliverables over the duration of this proposal, we reserve the right to replace a Target Deliverable with an alternate of approximately equal or greater scope.

Additionally, some Target Deliverables may have dependencies on external parties that are not fully under our control. For example, some of our Target Deliverables are dependent on the launch of ENSv2. We cannot fully control when ENSv2 launches. If Target Deliverables become blocked due to external parties, we reserve the right to replace an impacted Target Deliverable with an alternate of approximately equal or greater scope.

We have a discussion open with ENS Labs about the possibility of an ENS Referral Program launching as part of ENSv1, rather than ENSv2. In the event the ENS DAO votes to approve and fund alternate ENS Referral Program strategies from those we have proposed, we reserve the right to replace impacted Target Deliverables with alternates of approximately equal or greater scope. If our Extended Scope is approved and the situation described in this clause is triggered, we will coordinate with Metagov Stewards on a responsible solution, such as us transferring the $50k in guaranteed ENSv2 Referral Programs funding into whatever pool of funds is servicing the alternate ENS Referral Program strategy, such that the broader intentions motivating the approval of our extended budget are followed as best as possible.

The following tables identify a quarterly breakdown of Target Deliverables for each of the ENS Infrastructure Solutions in our “basic” and “extended” scope.

Each quarter listed in these tables is relative to (the commencement date of SPP2 funding streams) + (3 months * quarter) ~ ending day of that calendar month.

Each quarterly report will be delivered within 10 days of the conclusion of the quarter.

4.1. Basic Scope of Work

4.1.1 ENSNode

Quarter Target Deliverables
Q1 1. Transition ens-test-env from the ENS Subgraph to ENSNode in preparation for ENSv2 release.
2. Coordinate with the ENS Labs team to identify and document the key requirements for transitioning the official ENS manager app and ENSjs to ENSNode and for supporting their ENSv2 requirements.
3. Release “v1” of tokenized DNS name indexing.
4. Complete audit of ENSv2 contracts and submit suggestions for optimized ENSv2 indexing.
5. Expand multichain indexing support to 1-2 additional chains.
6. Release L2 Primary Names indexing.
Q2 1. Release “v1” of ENSNode to ensure the ENS ecosystem has an indexed data solution available prior to the ENSv2 release.
2. Preview release of “ENS Resolution Accelerator” technology.
3. Deploy hosted instances of ENSNode with optimized uptime availability free for the ENS community to use.
4. Ship “v1” of ENSNode developer docs.
5. Expand multichain indexing support to 1-2 additional chains.
6. Support the transition of 1-3 apps in the ENS ecosystem from the ENS Subgraph to ENSNode.
Q3 1. Ship “v1” of “ENS Resolution Accelerator” technology.
2. Optimized self-hosting and DevOps to support stronger ENS protocol decentralization.
3. Preview release of Offchain ENS Name indexing.
4. Release “v2” of tokenized DNS name indexing.
5. Expand multichain indexing support to 1-2 additional chains.
6. Support the transition of 1-3 apps in the ENS ecosystem from the ENS Subgraph to ENSNode.
Q4 1. Ship “v1” of Offchain ENS Name indexing.
2. Ship “v2” of “ENS Resolution Accelerator” technology.
3. Optimized scalability and maximised uptime enhancements.
4. Ship “v2” of ENSNode developer docs.
5. Expand multichain indexing support to 1-2 additional chains.
6. Support the transition of 1-3 apps in the ENS ecosystem from the ENS Subgraph to ENSNode.

4.1.2. ENSRainbow

Quarter Target Deliverables
Q1 1. Release “.ensrainbow” file type format for improved portability of ENSRainbow data sets.
Q2 1. Release “Intelligent Data Set Versioning” capability, enabling a single ENSRainbow instance to grow its set of healed labels across time while maintaining stable behaviour for each connected ENSNode instance.
Q3 1. Release “ENSRainbow Searchlight Server”, which will continuously use a variety of strategies to heal otherwise unknown labels.
Q4 1. Release “ENSRainbow Searchlight Protocol”, which will enable anyone in the ENS community to submit healed labels they discovered for broader ENS community use.

4.1.3. ENSAdmin

Quarter Target Deliverables
Q1 1. Ship “ENS Protocol Inspector” support for 2 additional ENS resolution scenarios.
2. Expand the ENS integrator library of important ENS resolution test cases by 2 or more.
3. Ship optimized ENSNode indexing status dashboard.
Q2 1. Ship “ENS Protocol Inspector” support for 2 additional ENS resolution scenarios.
2. Expand the ENS integrator library of important ENS resolution test cases by 2 or more.
3. Ship ENSv2 Protocol Inspector (specialized for ENSv2 contracts).
Q3 1. Ship “ENS Protocol Inspector” support for 2 additional ENS resolution scenarios.
2. Expand the ENS integrator library of important ENS resolution test cases by 2 or more.
3. Ship “ENS Protocol Inspector” for “ENS Resolution Accelerator”.
Q4 1. Ship “ENS Protocol Inspector” support for 2 additional ENS resolution scenarios.
2. Expand the ENS integrator library of important ENS resolution test cases by 2 or more.
3. Ship ENSNode DevOps dashboard for improved ENSNode operations, monitoring, and maintenance.

4.1.4. ENSv2 Referral Programs (Technical Deployment)

Quarter Target Deliverables
Q1 1. Ship contracts and documentation with proposed referral program revenue sharing strategy in preparation for ENSv2 launch.
Q2 1. Ship promotional landing page microsite in preparation for ENSv2 Referral Programs launch.
Q3 1. Ship indexer and live reward tracking dashboards for ENSv2 Referral Programs launch.
Q4 1. Launch ENSv2 Referral Programs in coordination with the launch of ENSv2.

4.1.5. NameGraph

Quarter Target Deliverables
Q1 1. R&D for supporting community curated name collections.
2. R&D for LLM-augmented collection refinements.
3. Ship 1-2 new NameGraph integrations.
Q2 1. R&D for supporting community curated name collections.
2. R&D for LLM-augmented collection refinements.
3. Ship 1-2 new NameGraph integrations.
Q3 1. Preview release for supporting community curated name collections.
2. Preview release for LLM-augmented collection refinements.
3. Ship 1-2 new NameGraph integrations.
Q4 1. Ship “v1” release for supporting community curated name collections.
2. Ship “v1” release for LLM-augmented collection refinements.
3. Ship 1-2 new NameGraph integrations.

4.1.6. NameAI

Quarter Target Deliverables
Q1 1. Ship enhanced AI tokenizer strategies.
2. Ship 1 new NameAI integration.
Q2 1. Ship enhanced internationalized name tokenizer strategies.
2. Ship 1 new NameAI integration.
Q3 1. Ship “v1” release of an enhanced NameAI technology showcase demonstrating valuable strategies for multi-dimensional name scoring.
2. Ship 1 new NameAI integration.
Q4 1. Ship “v2” release of an enhanced NameAI technology showcase demonstrating valuable strategies for multi-dimensional name scoring.
2. Ship 1 new NameAI integration.

4.1.7. NameGuard

Quarter Target Deliverables
Q1 1. R&D for rearchitecture transitioning to use of ENSNode services for improved analysis of ENS names.
Q2 1. Ship “v1” rearchitecture transitioning to use of ENSNode services for improved analysis of ENS names.
Q3 1. Ship “v2” rearchitecture transitioning core NameGuard and LabelInspector logic from Python into TypeScript packages that can be embedded directly into ENSNode or other apps / services.
2. Ship 1 new ENS name configuration health check.
Q4 1. Ship 3 new ENS name configuration health checks.
2. Ship NameGuard integration with the “ENS Protocol Inspector” in ENSAdmin.

4.1.8. NameKit

Quarter Target Deliverables
Q1 1. R&D for rearchitecture transitioning to use of ENSNode services as an accelerated loading strategy for NameKit React hooks and UI component libraries.
Q2 1. Ship preview React Hooks and UI component library for accelerated ENS social profiles.
Q3 1. Ship “v1” React Hooks and UI component library for accelerated ENS social profiles.
2. Ship integration with ENSAdmin.
3. Ship integration with NameGraph.
4. R&D for “Universal” ENS profile editing React hooks and UI components.
Q4 1. Ship “v1” of “Universal” ENS profile editing React hooks and UI components.
2. Ship 3-6 integrations of NameKit.

4.2. Extended Scope of Work

4.2.1. ENSv2 Referral Programs (Guaranteed $50k Funding)

Quarter Target Deliverables
(circa 2 quarters before expected ENSv2 launch) 1. Ship 5-10 targeted outreach campaigns to prospective ENSv2 Referral Program apps and wallets, promoting the recurring revenue model opportunity for promoting the registration and renewal of .eth names.
(circa 1 quarter before expected ENSv2 launch) 1. Deliver ENS integration support to apps and wallets expressing interest to participate in ENSv2 Referral Programs.
2. Ship 5-10 additional targeted outreach campaigns to prospective ENSv2 Referral Program apps and wallets, promoting the recurring revenue model opportunity for promoting the registration and renewal of .eth names.
(quarter of ENSv2 launch) 1. Fund ENSv2 Referral Programs contracts with guaranteed $50k.
2. Deliver ENS integration support to apps and wallets expressing interest to participate in ENSv2 Referral Programs.
3. Ship 5-10 additional targeted outreach campaigns to prospective ENSv2 Referral Program apps and wallets, promoting the recurring revenue model opportunity for promoting the registration and renewal of .eth names.
(quarter after ENSv2 launch) 1. Report on outcomes, lessons learned, and suggestions for the future for ENS Referral Programs.

4.2.2. ENS TokenScope

Quarter Target Deliverables
Q1 1. R&D for protocol implementation strategies to map from ENS names to their ownership controlling tokens.
2. Ship support for name sales history.
Q2 1. Ship support for aggregation of onchain and offchain buy and sell order data for tokenized ENS names.
2. Ship support for querying the top buy and sell orders for tokenized ENS names.
Q3 1. Ship support for updating the status of buy orders based on wallet balance changes.
2. Ship support for creating new buy and sell orders for tokenized ENS names.
Q4 1. Ship support for unified queries of primary and secondary market state for tokenized ENS names.
2. Ship 2-4 integrations with ENS TokenScope.

4.3. Second-Year Stream Scope of Work

The ENS ecosystem changes fast. The details of specifically what may be the most impactful Target Deliverables to create value for ENS more than a year from now are likely to change.

What doesn’t change is our team’s “north star” of identifying key high-value needs in ENS and then working to solve them. We follow an opportunistic and pragmatic approach to optimise for value creation.

The scope for the second-year of our budget would include an equal or greater scope of work as the first-year. On a rolling basis, upon the delivery of our quarterly reports, we will maintain a roadmap of Target Deliverables extending at least 2 quarters into the future for each quarter in the second-year.

Target Deliverables in a second-year can confidently be assumed to include continued high-value enhancements to each of our 8 ENS Infrastructure projects in addition to new valuable ENS infrastructure project opportunities that emerge over time.

12 Likes

Dam! What a proposal - Firstly big ups for the how in-depth this proposal is, specifically 4.1 with deliverables broken down by quarter. Very impressive.

FireEyes supports Namehash’s continuous development of ENS and is excited to see how as a service provider they’re able to deliver the huge list of outcomes :fire:

9 Likes

Hey @lightwalker.eth

Thank you for submitting your application for the ENS Service Provider Program, Season 2. We are pleased to confirm that your application meets the eligibility criteria as outlined in the program design.

Good luck running for SPP2!

-MetaGov

3 Likes

I’m happy to endorse Namehash’s nomination as a streaming provider this term. Their subgraph replacement in particular will be vital infrastructure for ENS going forward.

8 Likes

@lightwalker.eth and his team @namehash are doing incredible work in the ENS space. We @vision already profit from their work they have put into NameAI and Namegraph. I def. support their proposal and look forward to continue to work with them!

:slight_smile:

To add: @ensnode I use the ENS Subgraph for vision.io since inception of ens.vision back March 2022. And my feedback would be that it “sucks”. There are a whole lot of unknowns and things that you have to guess and figure out by your own as nothing is documented. Especially since the introduction of the NW I had to add a whole lot of workarounds and had a whole lot of redeployments because something was not as I did expect. Example: Subgraph Domain.expiryDate checkup - #4 by Zimtente (there are whole lot more of these). Or that Renew Events are for some reason not considered a “Domain Event” which just makes use consume double the credits as we need to track 2 event streams from the graph instead of just one.

So I’m very much looking forward to use ensnode instead as it would make our lives @ vision much easier in terms of indexing ENS related data that we use to power vision back and frontend.

3 Likes

Indexing ENS names is a hard task that I myself was trying to tackle in 2018 (I did a hackathon on it in ETHBerlin 2018 and I used node data that Nick helped to dump out for me on big query) just before the graph was built. The graph was never built for dealing with CCIP-read and it makes sense for a team to take on this task as with ENS going to its own L2 this has to be production ready.

I’m happy to endorse Namehash for SPP2.

7 Likes