Service Provider Stream Nomination Thread

[russell]

Name and website of Provider

Name: dappling.eth
Website: dappling.network

Name of main point of contact

bookland.eth

What do you want to build on ENS?

dAppling is a tool that makes it easy for developers to deploy secure decentralized frontends to IPFS & ENS. Developers connect their GitHub account, and with a few clicks get a decentralized site with CI/CD, preview builds, and best practices for a fast decentralized site out of the box.

We believe that it’s instrumental for the front end layer of applications to become decentralized. As ENS continues to grow, new use cases are popping up. We envision a future where ENS is used to provide a decentralized access point for all applications. For this to happen, developers need a way to host their sites in a decentralized way with a great developer experience, good performance for their users, and web3 grade security.

Some problems we are working on solving

Frontends need to be reliable.

Smart contracts have 100% availability, but 100% availability doesn’t mean much if the way users access the smart contract (the frontend) is unavailable. We are working to provide decentralized access points to make sure users are always able to interact with the smart contracts through a user friendly frontend.

This is especially important for DeFi protocols, where their frontend being down may result in significant issues, like users getting liquidated because they can’t add collateral.

Frontends need to be secure.

DeFi frontends are plagued with hacks. These need to stop for mass adoption of DeFi. Here’s a few from just the last month…

• TraderJoe Frontend Hack
• Balancer Frontend Hack
• Velodrom Frontend Hack
  
  

Since we are helping sites with their deployments, we are in a core position to help prevent these types of frontend attacks.

Frontends need to be fast for users.

We scraped all of the DeFi protocols that are on https://defillama.com/ and found that over 50% of them are using centralized frontends with tools like Vercel or Netlify.

We talked with many of these teams and learned the main reasons they aren’t using decentralized frontends with ENS:

1. They want their site to be really fast for users, and currently decentralized sites are plagued with speed issues.
2. The developer experience for deploying to IPFS + ENS sucks (no automatic cicd/ no preview builds, no instant rollbacks, users have to pay gas to update their .eth website).
   
   

Future of Frontends

Some things we want to accomplish in addition to making it really easy to build fast secure decentralized frontends.

• Build a standard way for protocols to prove their canonical contract addresses using ENS. We built an MVP of this with uniswap, where they use v3deployments.uniswap.eth to show their canonical addresses on each chain.
• Build a standard way for users to define their different access points for their frontend, and a way to verify that the access points are not malicious.
• Create a directory of decentralized sites and their access points, to make the discovery of secure frontends easy.

Past experience working on ENS

We have been working on dAppling for the past year and our team has been building in the Ethereum ecosystem since 2021.

Our team previously built arbor.finance, which helped DAOs raise ~3m in debt based financing and had ~15m max TVL

We’ve also built several tools: v3deployments, ggp dashboard, blockchain event explorer

Size of team and commitment

We are currently a team of 3 working on this full time. We may bring on a few more people if we are selected as a service provider.

• Russell (me)
• Kyle
• Grace

Links to documents with further information

• Site: dappling.network
• Docs: docs.dappling.network
• Blog: blog.dappling.network

Conflict of interest statement

None!

10k Endorsement link

Delegate Support for ENS Provider Application

Thanks for starting this thread @she256 Coltron also gave his endorsement of Tally. Endorsements given: I can give an endorsement for @stevegachau.eth : he deserves to be on the ballot. I endorse @russell to be on the ballot

Budget Requested

400k

Other notes

90 sec platform demo
An public project on the dAppling platform

Thanks for considering our application!

[Raphael_StableLab]

Name and website of Provider: StableLab.eth

Name: StableLab
Website: https://stablelab.xyz/
Safe Address: StableLab.eth

Name of main point of contact:

Raphael Spannocchi (spannocchi.eth) - Governance Lead

What do you want to build on ENS?

We’re looking to build a procurement platform for DAOs.

From the ENS Governance Process:

The primary mechanism by which the DAO gets things done is via “Requests for Proposal” (RFPs). An RFP is a request from the DAO for contributors to offer to do work on its behalf, and receive compensation in return.

How can DAOs attract as many offers as possible and find the best candidate?

There’s an acute need for a platform where many DAOs publish RFPs and service providers can easily find work they’re interested in and apply. A platform that makes it easy for DAOs to think through the nooks and crannies of how to write a great RFP. And a place where the best service providers come to bid for work.

This is precisely what we want to build.

For the supply side (DAOs looking for service providers):

An easy-to-use UI/UX that guides DAOs through setting up a great Request For Proposal (RFP) process so they can get a specific scope of work done.

For the demand side (Service Providers looking for work):

An easy-to-use UI/UX where they can easily find open RFPs and apply with open, public profiles built on top of ENS names that develop over time to showcase their work and the success they created.

We will use ENS as the basis for applicants and DAOs, so the domain names become “LinkedIn-style” profiles.

Please see the link to the Slide deck for further information.

Past experience working on ENS:

We have not contributed to ENS prior to this engagement, but are excited to get started.

Size of team and commitment

We will deploy one full-stack engineer and one UX engineer full-time exclusively to this project, plus one project manager with about 2/3rd to full-time commitment.

Links to documents with further information

Please review our pitch deck for the platform here.

Conflict of interest statement

There are no conflicts of interest. StableLab is not a steward or in any other active role at ENS DAO.

10k Endorsement link: Delegate Support for ENS Provider Application

Budget Requested: $300,000 for developing and improving a DAO procurement platform built on top of ENS for one year.

Other notes (optional field)

If successful, we will continue to operate the platform and improve it. The project would be completely open source but could be made to monetize and pay for itself by introducing a small bps fee on top of project volume for successful matchmaking.

This fee-taking could make the project self-sustaining and pay into the ENS DAO Treasury if it is successful enough.

[slobo.eth]

Name and website of Provider:

Name:
resolverworks.eth

Website:
namestone.xyz

Name of main point of contact:

slobo.eth

What do you want to build on ENS?

We want to build the premier subname provider of ENS.

Registering an ENS name for everyone on Earth would take 33 years and every block on mainnet. We want to sustainably expand the ENS ecosystem by making gasless subnames and L2 names a reality. This way, any individual from any country who wants an ENS can easily get one.

What we have done

We launched namestone.xyz and have issued thousands of subnames for more than a dozen ENS enabled domains. These names are used extensively as we receive thousands of forward resolution requests each day. We have provided and managed subnames for:

• Obvious Technology via obv.id, a smart contract wallet
• POAP.xyz, bookmarks for your life platform
• Converse.xyz, a messaging app built on top of XMTP
• PoolTogether, Saving & winning protocol
• Wassies, NFT project
• GreenPill, a regen network
• Mailchain, web3 email

We have made it simple to use ENS across platforms, protocols, NFT projects, and wallets. And we are just getting started!

What we plan to do

With the ENS DAO stream, we will expand and enhance our services, offering subnames to any person or group that wants one. We will develop websites for managing subnames and offer diverse options for registration. Our goal is to enable trust-minimized subname registration on a variety of L2s as well as gasless registration in a centralized database.

Below are the target personas who will most benefit from our efforts. Until now, we have only been able to target personas that had the ability to pay for our services. With the support of the DAO, we can bring ENS to anyone!

Newcomer Nancy
Nancy is brand new to Web3. She’s attended a few web3 events and has heard people refer to their .eth. When she searches ENS and visits the current frontend she is able to find a name she likes, but she is confused by the checkout experience and is put off by the price.

OG Olga
Olga has been in web3 for a few years. She owns her own ENS name and has it on all her socials. She wants a way to organize her public addresses and sees ENS as the pricey solution. She also has out of date social handles on her ENS name because she doesn’t want to pay to update them. She would be happier if there was a free way to manage her socials and subnames.

Company Carl
Carl is responsible for improving his community/company/protocol’s user experience. He knows that adding an ENS enabled namespace via subnames would add value to his users. Resources are tight and he would prefer an easy to use off the shelf solution.

Deliverables

To serve these personas and make ENS subnames easy to issue and use, we will deliver and enhance the following:

• L2 enabled and tradable ENS subnames
• A website where anyone can claim their own ENS subname
• A website where admins can manage subnames through a web portal
• An API that allows developers to issue subnames programmatically
• Marketing and educational materials to support our efforts as needed

We expect our offerings to evolve as we continue to engage with ENS labs, fellow stream recipients, customers, and layer 2s.

All software developed will be open sourced. This includes front ends, smart contracts, and custom resolvers that may need to be developed. We will also release our design system.

Past experience working on ENS:

We have created products in crypto used by tens of thousands. Our expertise lies in delivering products quickly and then effectively iterating based on community feedback.

ENS Ecosystem Contributions:

• Developed namestone.xyz, an easy to use API for gasless subname management, integrated by POAP, PoolTogether, obv.id, and more. Namestone has issued thousands of subdomains and resolved them hundreds of thousands of times
• Created nftychat.xyz, an ENS-based alternative to Discord
• Created teamnick.xyz, which issues tradable ENS subnames of teamnick.eth on base

Further, slobo.eth has co-authored ENS-IP 14, a method to track the source of .eth registrations on-chain, served as a Lead Ecosystem Working group steward for four terms, and has consistently acted as an educator and evangelist for all things ENS.

Size of team and commitment
Our team consists of a full stack engineer, a product/marketing lead, and a designer, all with demonstrable experience building tech in crypto. The current team is committed to working full time. With this new direction, we plan to hire a solidity focused dev and 1-2 full stack engineers to help develop our new offerings. The total team size is expected to be 4-6 people.

Conflict of interest statement

Slobo.eth is a current ENS Ecosystem Steward. Slobo.eth plans to run for steward next term as well. In the event that we are selected as a service provider and slobo.eth is also elected as a steward, slobo.eth will work with metagov to come up with an appropriate solution.

10k Endorsement link:
https://snapshot.org/#/ens-streams.eth/proposal/0x868c2cb397102197d954314c2ae2b3140c4750452b7bacc4eb99e3b039ea6c38

Budget Requested:

700,000 USDC / Year

We expect that the majority of the budget will be spent on salaries, with $50,000 reserved for professional services, such as legal, accounting, etc.

[stevegachau.eth]

Name and website of Provider : Wildcard Labs - wildcardlabs.xyz, wildcardlabs.eth

Wildcard Labs is a developer team based in Nairobi, KE. We specialize on creating tools and platforms that actively contribute to the increased adoption of ENS domains and records, making them an essential component of the decentralized web.

Name of main point of contact :

Steve @stevegachau.eth

What do you want to build on ENS?:

We hope to secure a funding stream that will empower us to work full-time, channeling 100% of our focus and energy into enriching the ENS protocol without distraction, in line with our dual goals:

1. Enhancing ENS Functionality: Our commitment involves developing user-friendly applications that extend the functionality of ENS, ensuring versatility and accessibility for a broader audience. Projects like Optinames and Wildcards Protocol are living examples, providing practical solutions that empower users.
2. Boosting Adoption: Beyond functionality, our focus extends to actively contributing to the increased adoption of ENS domains and records. Tools like Avatarsync & ENS Redirect aim to seamlessly integrate ENS into users’ online presence, fostering a sense of ownership and utility.

While we continue these projects, we’re excited to channel this momentum into creating new, groundbreaking applications over the next 18 months, and hopefully beyond. This funding will not only facilitate continuous improvement but will empower us to explore and develop new and impactful experiments.

In line with our commitment to innovation, we’re thrilled to introduce our upcoming project, the Superchain Resolver. Leveraging the recently released EVM gateway by the ENS Labs team, this initiative will revolutionize ENS usage by providing users with seamless records management across Optimism, Base, Zora, PGN and other OP-chains. We aim to make ENS more cost-effective compared to managing records on the Ethereum mainnet. This approach addresses the rising expenses associated with mainnet transactions, ensuring a more economical solution for ENS users.

The Superchain Resolver is just the tip of the iceberg, as we remain dedicated to a continuous exploration of new tools and experiments, ensuring that Wildcard Labs remains at the forefront of ENS innovation.

Past experience working on ENS :

In line with our commitment to make ENS more user-friendly and widely adopted, we’re excited to share the impact of our work through the following projects:

1. Avatarsync: Enables users to sync their social media profiles with their ENS avatars, ensuring automatic updates whenever their profile pictures change on platforms like Twitter, Lens Protocol and Farcaster.

2. ENSRegistry Twitter Bot: Posts real-time updates on all ENS names registered to Twitter, promoting transparency and awareness within the community. Live since Jan 2022, the bot has posted 535,873 times, that’s over 2 million names.

3. Optinames: Introduces ENS subdomains on the Optimism network, expanding the ENS ecosystem to Layer 2 solutions.

   • A substantial 7,723 Optimism users have successfully acquired free ENS sub-names via Optinames.
   • 25,484 ENS sub-names have been registered on OP Mainnet.

4. ENS Redirect: Allows users to point their ENS domains to traditional Web2 URLs, bridging the gap between decentralized and centralized web experiences.

5. Wildcards Protocol ^BETA : Links ENS to NFT collections on any EVM chain, providing instant sub-domains to NFT holders without the need for individual claims/registrations.

   • 7 NFT communities have been onboarded on OP chain. Check them out.
     (OptiChads, Apetimism, Tickled Picklez, Optimistic Bunnies, Optimism Quests, Deggkies Optimism, HyperChads)
   • 3 NFT collections have been onboarded on Base.
     (Tiny Based Frogs, Base Wars, Summer Kevin)

Size of team and commitment:

Wildcard Labs is currently a team of three individuals, with two members working full-time and one part-time. We are fully committed to dedicating our efforts exclusively to ENS development. Upon securing the service provider stream, we plan to expand our team by adding a dedicated developer (frontend/react) and a marketing/community relations specialist (both full-time).

Current full time team members:

stevegachau.eth
davidwachira.eth

Links to documents with further information:

Website: wildcardlabs.xyz (portfolio of past work)

Conflict of interest statement:

Projects developed by our team have previously received grants from the ecosystem working group, however we have no relationships with entities within the ENS ecosystem or roles within the DAO that could potentially lead to a conflict of interest.

10k Endorsement link :

AvsA | Delegate Support for ENS Provider Application

Budget Requested :

$200,000 / year

[juankbell.eth]

Gravity DAO service provider proposal for ENS

Name and website of Provider:
ENS: Gravitydao.eth
Website: https://gravitydao.org/en/

Name of main point of contact:
Project leader: juankbell.eth
Team members: biscoito.eth, durgadas.eth, zeptimus.eth

What do you want to build on ENS?

We want to facilitate a culture of competence in managing conflict on ENS. Working on learning to overcome obstacles individually and collectively would benefit the growth and adoption of ENS worldwide, as teams would be able to solve frictions effectively and peacefully, improve communication, and develop a stronger relational fabric to foster smooth coordination.

We have seen how easily, internet drama can affect the well-being of a community, and our work supports minimizing snowball effects and having adequate processes to look for solutions to disputes while caring for all parties involved. By minimizing the negative impact of conflict and maximizing the learnings that can come from it, organizations can become resilient to stress and prevent violence or unresolvable conflict.

We have been building good practices to manage conflict in DAOs for over 3 years now, having already 5 cohorts of live Graviton Trainings, which are our certified 8-week online social skill boot camp, where we educate and develop multiple skills, that are key to increasing the competence of the collective in regards to transformation. We also developed our first Free online course, which is open 24/7 for everyone who wants to learn about these concepts as an async alternative to the live cohorts.

With this application, we propose to have two Graviton trainings on the ENS Discord Server during 2024, one each semester of the year. These learnings are better developed when continuously practiced, and we will certify the participants, to create a nucleus of “Gravitons” or conflict management agents in the community.

During 2024, we are also planning to develop our second free online educative course, this one focused on leadership, and once we have it, the ENS community will be the first ones to be impacted by it.

Our goal is to support DAOs to be sustainable over time and to foster nonviolent ways to solve disagreements. We are proposing solutions to specific coordination issues, and the work we are doing is key for the ecosystem, even when usually underseen.

Why should YOU be picked?

Gravity DAO is uniquely suited to support tightening the relational fabric of ENS because of its expertise in creating trust in teams, developing conflict transformational platforms, and deep understanding of blockchain systems. We’ve proven our ability to design and create solution spaces that respect and uphold the values of communities. Our approach is conceptually robust, minimal in governance, and efficient in progressive decentralization.

Our team has consistently displayed dedication towards Open Source Work by creating free content that is forkable and adaptable to any organization that decides to get inspired by it. A big part of our educational offer is available 24/7 in the online course, but we also like to host live spaces on trust creation practices, nonrelated to work conversations, co-creation, Study Groups, and facilitation of simulations and roleplays about conflicting scenarios.

The biggest milestone we’ve had has been to position our message in the web3 space by carrying the flag of social development in communities. At this point, we have worked with big organizations, like Aragon, Commons Stack, Giveth, Token Engineering Commons, and Optimism, where we’ve provided educational and consultation services, developing a high impact towards community building and maintaining positive relations. We want ENS to be the next community to intentionally make space for conflict management in its DNA.

We are a public good project in development for over 3 years (first as a Working Group of the TEC), and managing our funds as a DAO for 1.5 years, with transparency and accountability over treasury using Dework, having more than 200 tasks reviewed to over 30 contributors.

At this point, we have mediated over 30 conflicts in DAOs and trained more than 50 “Gravitons” (1st & 2nd gen , 3rd gen , Aragon gen & Optimism gen) to be active ambassadors within public goods communities.

Some of the Frameworks we use are:

• Alternative Dispute Resolution
• Non-Violent Communication
• Process-Oriented Psychology - Deep Democracy
• Serious Play - Liberating Structures
• BATNA and negotiation strategies
• Ho’Oponopono Healing practices
• Cynefin Contextualization for decision making
• Mental Health and Individual wellbeing
• Polarity Mapping
• Elinor Ostrom’s Principles for the Commons, and more.

We have uniquely curated content bridging social sciences to Web3 and we want to continue being a beacon of nonviolence and human-centered coordination in Web3

Size of team and commitment

5 core members: (10 to 20 Hours/week)

Juan Carlos Bell. Twitter: @ Bellcho, Political Scientist, MSc in Alternative Dispute Resolution, Project Lead.
Bianca. Twitter: @ biancagadelha, Psychologist, researcher, Coordination manager
Zeptimus. Twitter @ zeptimusQ, Economist, Transparency and accountability advocate
Durgadas. Twitter @ durgada29002529, Yogi, Polymath, Contextualizer, and Operations Manager
Nikola Creatrix. Twitter @ NikolaCreatrix, Mediator, Framework developer, Active Graviton

15 external contributors (5 to 10 Hours/month)

These contributors are SMEs that contribute to our project by facilitating calls or creating content according to their fields.

Links to documents with further information

• Gravity DAO Twitter
• Gravity presentation: Conflict management and Trust Creation in Web3
• Graviton training on Optimism
• Graviton training on Optimism recordings
• Past Graviton Training slides
• Collection of POAPs on Juankbell.eth
• Treasury and rewards management on Dework

Conflict of interest statement

Our team does not have any conflict of interest with this application on ENS.

10k Endorsement link:

We haven’t been able to make the snapshot, will update this post once we can propose.

Budget Requested: $100.000 USD/y

We expect the majority of the budget to be spent on salaries. We don’t plan to stop our work on a time base, and we want to continue developing conflict management in online communities for the long term.

[garypalmerjr]

Name & Website of Provider:

• ENS: Web3Domains.com
• Name: Web3Domains.com
• Website: Web3Domains.com

Name of Main Point-of-Contact:

• GaryPalmerJr.eth

What do you want to build on ENS?

We plan to build for, 1. the Web3-Developer Ecosystem; and, for 2. the “End Users” of ENS-and-Web3 identity:

// For Web3-Developers:

• Web3Domains/.com is dedicated to the growth of ENS by meticulously reviewing, updating, and enhancing existing ENS code and documentation.
• Our active participation includes open sourcing software and systems, optimizing smart contracts, and ensuring ENS remains developer-friendly.
• We aim to facilitate ENS integration into various decentralized applications, protocols, and services within the broader Web3 landscape, ensuring its relevance and resilience; and to ensure that ENS remains a robust and developer-friendly platform.

// For End-Users:

• Web3Domains/.com is on a mission to empower end-users by providing a user-friendly platform for minting, buying, selling, and managing their ENS names, in safe and familiar environment.
• We are focused on creating an intuitive experience, offering bulk management tools, domain trend analytics, and a secure interface to mint, manage, and more.
• Our goal is to make ENS domains accessible to everyone, regardless of crypto knowledge, making it as effortless as managing traditional domains; We envision a future where anyone, regardless of their crypto knowledge, can seamlessly navigate and benefit from ENS domains.

Past Experience Working on ENS:

• As the team behind Web3Domains/.com, we have extensive experience in the Web2 and Web3 domain services industry, with a strong focus on the intersection of blockchain technology and domain management.
• Our previous projects include advancing ‘unruggable ENS renewals’ and ‘sovereign ownership’ theory for ENS protocols; and contributing to the broader understanding and adoption of digital assets, domain analytics, marketing-technology systems, and market trend predictions; plus solving for security issues via system procedures and code, in the Web3 domain industry.
• Helped create many community favorite features on current solutions and secondary markets, (ie: BulkRegistration, SyncExpirations, etc).
• Reported multiple vulnerabilities to ENS securing the protocol and community.
• Helping community members rescue hacked and exploited ENS names.

Size of Team & Commitment:

We plan to have five (5) full-time people on our team:

// Management Team:

1. GaryPalmerJr.eth, Operations Manager – Full-Time Commitment
2. Ada.eth/UnfoldedLife, Project Manager – Full-Time Commitment

// Developer Team:

3. LCFR.eth, Senior/Lead Solidity Developer – Full-Time Commitment
4. Zantron.eth, Web3/JavaScript Developer – Full-Time Commitment

// Support Team:

5. To-Be-Announced, Support Specialist – Full-Time Commitment
6. Limited Contract, UX/UI Designer(s) – As-Needed Commitment
7. Limited Contract, Web3 Developer – As-Needed Commitment

Links to documents with further information:

ENS Discuss Posts & Blog:

• blog.ens.domains/post/null-byte-vulnerability

• discuss.ens.domains/t/ens-subdomains-renewal-rugability-pricing-methods-rental-pricing-options/12372

• discuss.ens.domains/t/namewrapper-updates-including-testnet-deployment-addresses/14505/9

• discuss.ens.domains/t/ens-affiliate-marketing-affiliate-program/11819

External Links & Social Posts:

• twitter.com/lcfr_eth/status/1664809442645356544

• twitter.com/realZadok7/status/1587101085876953088

• lcfr.io/ens-namewrapper-bounty

• lcfr.io/duplicate-ens-names

• Web3Domains.com

Conflict-of-Interest Statement:

• While Web3Domains/.com has received a few small grants via the ENS DAO; Web3Domains/.com operates independently and has no current financial relationships with entities within the ENS ecosystem that could lead to a conflict of interest.
• Our commitment is solely to the advancement-and-usability of ENS protocol.

10k Endorsement Link:

• 10k Endorsement link, for Web3Domains.com, via Snapshot

Budget Requested:

• $480,000/year ($40,000/Month);
• This will enable five (5) full-time salaries, and
• +includes necessary budget for resources + contract work.

Other Notes:

• Our team is committed to the sovereign development of Web3—We have been participating with ENS/Discord, (since the release of the ENS protocol, May 4th, 2017)…And we have been working as an active ENS DAO Delegate, (since the ENS DAO announcement, November 2021).
• Our team supports the ENS DAO, and the foundation outlined via the ENS DAO Constitution.
• Our team is well-versed and committed to Web3 security, gas efficiencies, and best practices.
• Our team is committed to the development of open source software, and public-viewable systems.
• Our team is committed to the enhancement-and-inclusion of developer notes, and updating developer documentation, for open source software and any released code.

[sem]

Name and website
wayback-machine.eth

Name of main point of contact
sem-the-bee.eth

What do you want to build on ENS?

We are poised to develop an ENS Archive, a comprehensive historical repository of ENS-linked content, marking a significant stride in preserving the decentralized web’s legacy.

Our objectives include:

1. Enhancing the ENS Wayback Machine: This will involve expanding support to include various decentralized storage providers such as IPNS, Swarm, and Arweave. These enhancements aim to deepen our understanding of an ENS domain’s history, offering richer insights and broader data accessibility.
2. Maintaining a Robust IPFS Node: This endeavor will ensure the preservation of pivotal content from the decentralized web, safeguarding the most influential and notable digital artifacts for future generations.
3. Developing Open-Source Management Tools: Recognizing the community’s reliance on services like https://pinata.cloud for content management, we will create free, open-source alternatives. These tools will facilitate the easy setup and management of IPFS servers with integrated ENS support, democratizing access and control over decentralized web content.

Our service stands to be a cornerstone for researchers, historians, and the broader Web3 community, offering an insightful perspective into the evolution of decentralized web content. More than just an archival tool, the ENS Archive aims to become a dynamic platform that evolves with the community’s needs. By integrating features such as a leaderboard to highlight and prioritize key websites for archival governed by ENS tokenholders, we want to give power to the ENS DAO to signal what

Past experience working on ENS

We are the team behind the ENS Wayback Machine dApp, an innovative tool designed to archive and provide access to historical versions of content linked to ENS domains. Functioning similarly to the Internet Archive’s Wayback Machine, it allows users to explore and retrieve past iterations of websites and digital content associated with ENS domains.

To illustrate, if one wishes to track the transformation of Ethereum founder, Vitalik Buterin’s personal webpage, it’s as simple as accessing vitalik.eth on our dApp. Utilize the header to toggle between different site versions, allowing a chronological visualization of its evolution.

Thanks to the ENS funding we received, we’ve also launched our very own IPFS node. This addition improves how our service works, making it faster and more reliable, and enhancing the overall experience for our users.

You can access our IPFS node through the ens.site domain. This IPFS gateway follows a modern specification designed to work seamlessly with the security models of web browsers. You can easily access IPFS data by simply adding the IPFS hash right before the domain name, like so: https://ba…ky .ipfs.ens.site.

Additionally, we’ve created software to resolve ENS content hashes in a way similar to eth.limo. You can see this in action at:

• https://vitalik.ens.site
• https://wayback-machine.ens.site
• https://<your-ens-name>.ens.site

However, for daily use, we still suggest using eth.limo as it’s more optimized. Use ens.site mainly for accessing older IPFS content or if eth.limo is unavailable.

Size of the team and commitment

Our team has three members: a software engineer, a frontend developer, and a system administrator, each of them will work on the project part-time. We will also use the funding to pay for our servers to keep our services running. Additionally, we plan to use some of the funds to hire a designer on an as-needed basis to fill gaps in our team.

Links to documents with further information

Here there is more information about projects we built in the past:

https://blossom.software/

Conflict of interest statement

The ENS Wayback Machine has previously received funds from three Ecosystem Small Grants:

• Ecosystem Small Grants Round 8 - 0.7 ETH
• Ecosystem Small Grants Round 9 - 0.7 ETH
• Ecosystem Small Grants Round 10 - 5 ETH

And it is currently participating in the Ecosystem Small Grants Round 11.

Our team also received Public Goods ENS grants for another project (EVMcrispr):

• Public Goods Small Grants Round 8 - 1 ETH
• Public Goods Growth Grants - 10,000 USDC

10k Endorsement link

@Griff will endorse us in this thread.

Budget Requested

$200,000/y

[ENSPunks.eth]

NAME AND WEBSITE:

enslikeprotocol.eth
(enslikeprotocol.eth.limo)

POINT OF CONTACT:

enspunks.eth

WHAT DO YOU WANT TO BUILD ON ENS?

ENS Like Protocol (ELP) is a opensource DApp for liking content across the web using gasless ENS records. More generally, ELP will organize ENS records, and make records accessible and useful for users and developers.

Prior to ELP, ENSpunks launched LikeButton.eth as a way for ENS users to give other ENS users onchain representing “decentralized likes.” $:heart: was popular with both the ENS community and developers in the ENS ecosystem. For example, a developer from the ENS community created a chrome extension for giving on Twitter and eth.photos integrated into their ENS profile pages. However, network fees hurt widespread adoption and likebutton.eth otherwise operated as a public good but failed to obtain public goods funding.

ELP takes the lessons learned from likebutton.eth and will rebuild as a tokenless, gasless and permissionless protocol native to ENS using gasless IPFS+CCIP-Read+ENS Records (ICE). Between using gasless ENS records and focusing on organizing ENS records, and making records accessible and useful, ELP hopes to help ENS protocol scale to 1 millions users with unique text records set.

ENS Record Managers	Gas Free Records	IPFS+CCIP+ENS Record (ICE) DApps	ENS Record profile/Gateway
ens.domains	NameSys	Ethereum Like Protocol	eth.limo/Nimi
ens.vision			eth.cd
Rainbow.me			eth.xyz
Namesys.xyz			eth.co
			eth.photos
			Rainbow.me

Specs

• ❤️ Subdomain & ELP Gasless Resolver:

  Users will mint a subdomain on their own ENS name (Ex.: .enspunks.eth). The easiest method is the UI at enslikeprotocol.eth.limo to create a subdomain where the ELP resolver for gasless records will be set automatically. Users can also mint the subdomain on ENS.domains and manually change the ENS subdomain resolver to resolver.enslikeprotocol.eth.

• Creating ENS ❤️ Records :

  Users can manage (create and delete) gasless ENS records [: content link] on a user friendly UI at ..eth.limo.

• Organizing ❤️ Records and Making Them Accessible and Useable :

  ELP will organize the ENS records, and make the accessible and useable for users and developers. For example, users can view and manage ENS records through the user-friendly UI. Moreover, ELP will be open and interoperable with other protocols such as Ethereum Follow Protcol (EFP).

PAST EXPERIENCE WORKING ON ENS

ENSpunks.eth has been building in the ENS ecosystem for several years, projects ENSpunks worked on include:

BoredENSYachtClub.eth

BoredENSYachtClub.eth is an pre-namewrapper ENS subdomain collection built with IPFS, CCIP-Read and ENS Wild Card Resolution. Almost 1,000 subdomains were minted creating a ENS community sub-DAO where members discuss ENS DAO Small Grants, and vote their subdomains on snapshot collectively voting the community $ENS in the ENS DAO.

LikeButton.eth

LikeButton.eth the first experiment with a “decentralized like button” for the ENS community built with $❤️.

Searchd.eth

Searchd.eth, fromerly Geocities.eth, a .eth website search engine and general resource for ENS users.

SIZE OF TEAM AND COMMITMENT

• Pending funding, there will be 1 full-time member of the team (enspunks.eth), a part-time social media/community manager, and contract workers when required for front-end development and integrations.

FURTHER INFORMATION AND LINKS:

TWITTER/X: x.com/enslikeprotcol

GITHUB: github.com/ENSpunks/ENSLikeProtocol

CONFLICT OF INTEREST STATEMENT:

• Received 1ETH as a winner of the ENS Bug Bash

10k ENDORSEMENT LINK:

Snapshot

BUDGET REQUESTED:

$100,000 USD

[Zeptimus]

Name Provider: generalmagic.eth

Website: https://www.generalmagic.io/

Name of main point of contact:

Zeptimus.eth

What do you want to build on ENS?

Our proposal is split into two sections. The first section will be about supporting ENS grantees, and the second section will be about upgrading the ENS Grants experience.

1. Support ENS Granteee Integrations ENS

Objective / Strategy / Execution / Targets / Responsibilities

ENS is absolutely killing it! As one of the few DAOs that’s not only profitable but also successfully funding public goods inside and outside of their ecosystem, ENS stands out in both financial health and community impact. Recognizing this success, we’re eager to extend our support to all projects receiving grants from ENS grants. Our goal is to enhance their integration within the ENS ecosystem, ensuring we are leveraging the full potential of this thriving network.

We will conduct work at an hourly rate ($65/hour for junior staff and $95/hour for senior staff taken from any amount we earn from this Provider stream). All hours will be shared regularly on the forum, along with the progress of each project we work with.

Below are only a few examples of the type of work we would take on:

Unitap - https://unitap.app/

Unitap, along with other consistent Small Grants recipients, could easily be resolving ENS addresses in their header. It is surprisingly common how many Small Grants recipients don’t have this basic support.

Rotki - https://rotki.com/

Rotki, also a consistent Small Grants recipient has basic ENS support, but several other ENS integrations could be done, such as warning users that their ENS name will expire, or Supporting NameWrapper (once they add 1155 support).

Token Engineering Academy - https://tokenengineering.net/

At TE Academy, a Large Grant awardee, there’s an absence of Web3 login options for users. We see a wonderful opportunity here: to introduce students to Web3 login, enriched with ENS support.

The duration of this work will extend for 1 year, split into $100K increments over 6 months. Any amount paid for hours that are not used will be kept for future work and no additional funds will be requested until all funds are exhausted and we receive feedback that our work is appreciated.

How it will work
Before we begin working with a project, we will speak with their team to come up with a proposal, then assign those hours to be within the scope of this workstream. We will then post our proposed project plan on the ENS forum. If there are no objections, we will begin work and report on the hours work and progress on a monthly basis.

2. Small grants voting system upgrade and maintenance

We want to improve the user experience of how the ENS community votes on small grants (as well as other grants in the future). We will upgrade the ENS small grants voting system platform and be product owners with the goal of updating the UX and voting mechanism of the platform, to increase voter engagement.

We built a similar system for Optimism RetroPGF Round 3 voting (using Pairwise) to help badgeholders decide on their voter allocation. We believe that ENS grants are the perfect use case to upgrade to the pairwise voting experience for fairer more comprehensive decisions around how to allocate funds.

How it works

Voters will compare projects in pairs, choosing their favorite. They also have the option to choose ‘neither,’ in which case none of the projects will receive a vote. The algorithm used is similar to the ELO system found in games like League of Legends and chess.

The reason we compare two projects instead of just saying ‘yes’ or ‘no’ to a single project is that it leads to more informed decision-making. For instance, deciding whether to give funding to Rotki might be unclear in isolation. But comparing whether it’s better to support Rotki or Revoke.cash offers much clearer insight.

This system, which we call Pairwise, is an excellent tool for curating lists. These results can potentially be used in various ways. We will inform the ENS public goods working group of the multiple ways to use Pairwise, and tailor the design to their desired implementation.

Note: This screen represents the final result for the voter. They can edit the numbers according to their voting power.

In addition to upgrading the voting system with Pairwise, our vision for ENS small grants extends beyond this single upgrade. Working closely with the Public Goods Working Group, we plan to adapt to the evolving needs of the ENS community. Our goal with this proposal is not only to refine the voting process but also to provide comprehensive support to grantees, ensuring they can seamlessly integrate and thrive within the ENS ecosystem. This holistic approach signifies our dedication to fostering a robust and dynamic environment for all ENS participants.

Budget Requested: $100,000 USD

Duration: 1 year +

While building the new application, we will continue to maintain the current application hosted at ensgrants.xyz. The following roadmap does not explicitly mention that every month, but it is included in the budget. Operating the rounds however is not included; we are only building the software.

We understand that we will get a set stream, but this is the breakdown of our costs which vary month to month.

Month 1: Requirements Gathering and Planning

• Team: Project Manager, Governance Analyst

• Focus: Analyzing current voting system, gathering requirements

• Budget Allocation: $10,000

Month 2-3: Design and Prototyping

• Team: UX/UI Designer, Front-end Developer, Governance Analyst

• Focus: Creating design prototypes, initial UX flows

• Budget Allocation: $20,000 (over two months)

Month 4: Development Phase I

• Team: 2 Developers, UX/UI Designer, QA Tester

• Focus: Core functionality development, integration with existing systems

• Budget Allocation: $20,000

Month 5: Development Phase II

• Team: 2 Developers, UX/UI Designer, QA Tester

• Focus: Advanced features development, initial user testing

• Budget Allocation: $15,000

Month 6: User Testing and Iterations

• Team: QA Tester, 1 Developer (part-time), UX/UI Designer (part-time)

• Focus: Extensive user testing, UI/UX adjustments

• Budget Allocation: $10,000

Month 7: Deployment and Training

• Team: 1 Developer, Training Specialist

• Focus: Final deployment, training ENS staff and community

• Budget Allocation: $12,000

Month 8: Transition and Initial Support

• Team: 1 Developer (part-time), Support Specialist

• Focus: Monitoring, initial support, documentation

• Budget Allocation: $6,000

Month 9-12: Ongoing Maintenance and Support

• Team: Support Specialist, 1 Developer (on-call)

• Focus: Regular maintenance, updates, addressing any arising issues

Budget Allocation: $7,000 (for 3 months)

Past experience working on ENS

We previously built the ENS swag shop: https://ensmerchshop.xyz/, are working with the ENS team on some frontend work for the small grants portal and are exploring launching Pairwise with ENS as a public good.

Size of team and commitment

We have a team of 30+ devs, designers and project managers we can pull into this project. We love ENS and would pivot a large percentage of our team to work nearly exclusively on ENS projects if we can make that work.

Below are the main leaders of the team that will coordinate the work.

• markoprljic.eth - Design lead. Head of Design and Business Developer at General Magic. “Magic Marko” is a top notch designer and has been practicing his art on web2 and web3 projects for over a decade.
• griff.eth - Co-founder of Giveth, Commons Stack, General Magic, Dappnode.
• zeptimus.eth - Jack-of-All-Trades at General Magic. ZeptimusQ is the versatile dynamo behind General Magic, skillfully juggling fundraising, business development, product support, and comms.
• krati.eth - CTO at General Magic. With over a decade of tech experience, Krati expertly leads as CTO, blending her vast knowledge in Solidity, Rust, and mobile technologies.
• aabugosh.eth - CEO at General Magic. Steering the ship with a keen eye for eelegal and financial intricacies, Ahmad masterfully handles all aspects of the operations.

Links to documents with further information

Our website: https://generalmagic.io/

Conflict of interest statement

A few potential conflicts of interest are

• Griff.eth is a major delegate and a long time supporter of ENS
• We’ve been working closely with the ENSDAO team on the swag shop for the past year: https://ensmerchshop.xyz/
• We’re working on a couple of other proposals with ENS stewards including:
  • A proposal for Ongoing Development and Technical Support for ENS Small Grants.
  • Branding https://www.pairwise.vote/ as an ENS public good (in exchange for sponsorship from ENS), although this is not confirmed or finalized.

10k Endorsement link: Self-endorsement: Griff.eth

Budget Requested:

The total budget requested is: $300K.

1. Small grants voting system upgrade and maintenance ($100K)
2. Support ENS Granteee Integrations ENS ($200K)

[coolhorsegirl]

Tally

Name and website of provider: tallyxyz.eth
Website: https://tally.xyz

Name of main point of contact: coolhorsegirl.eth

At Tally, our commitment to the decentralized web is unwavering. We envision a future where the Internet operates on a foundation of credibly neutral Ethereum infrastructure, with ENS playing a pivotal role in this evolution. ENS has already marked a significant leap in enhancing Ethereum’s usability, yet we believe its potential is far from fully realized, and that’s a good thing. With features like subdomains and cross-chain ENS capabilities, there’s an enormous scope for ENS to expand its influence massively.

Our enthusiasm for integrating ENS into our application is matched by our dedication to supporting the ENS DAO. We’re excited to continue building ENS into our application and to continue supporting ENS DAO. We are proud to contribute to such an important part of the web3 world. We are proud to contribute to such a vital element of the web3 ecosystem.

What do you want to build on ENS?

Tally’s mission is to build tools that significantly contribute to the growth and sustainability of governance for decentralized organizations. But Tally itself is more than just a tool; it’s a dynamic ecosystem designed to empower operators, voters, and delegates, facilitating a more engaged, transparent, and effective decentralized governance environment. We have three key areas we are focusing on:

1. Frontend for governance of decentralized organizations

Tally provides an end-to-end decentralization stack, making it easy for teams to launch governance, ship software upgrades, and fund initiatives. You can learn more about Tally in our docs.

• For Operators: Tally acts as a comprehensive, one-stop platform, skillfully managing the intricacies of decentralized organization operations. This allows operators to devote their full attention to leading and growing their organizations, assured that the backend complexities are handled by Tally.
• For Voters: The platform offers a unified, intuitive interface for engaging with proposal voting. Voters gain access to a seamless experience that simplifies the process of understanding, evaluating, and participating in critical governance decisions, enhancing active participation in the governance process.
• For Delegates: Tally is a tool for expanding their influence within a DAO. It provides robust profile-building features and engagement tools, enabling delegates to effectively showcase their contributions and stances, and to connect with a broader audience. This not only elevates their visibility but also strengthens their impact in governance discussions.
• Educational Resources: Additionally, Tally’s docs serve as a comprehensive educational resource, offering in-depth insights into the nuances of governance in decentralized organizations. This repository of knowledge is invaluable for both newcomers and seasoned participants in the DAO space, fostering a well-informed and engaged community.

2. Create Proposal Lifecycle (view prototype)

Right now, 86% of onchain Governor DAOs are moving money through proposals on Tally. Our Create Proposal tool is top of mind, and we’re building an intuitive proposal creation interface with integrated features including temperature check, team commenting abilities on draft proposals (think comment abilities on Google Docs!), and risk checker. With this, we hope to foster a more dynamic and participatory governance environment for ENS and other decentralized orgs.

3. Delegate Discovery and Engagement (view prototype)

We believe that delegation is absolutely integral to the functioning of a healthy decentralized org, and we intend to aid with simple and clean delegate discovery and engagement. Our solution will offer advanced search and filter options, detailed delegate profiles, and interactive tools to facilitate better decision-making by tokenholders. Check out the funnel symbol in the demo—you will see the beginnings of the ways users will be able to filter delegates, by everything from issues to activity to a tailored formula to spotlight new and up-and-coming delegates. This will not only make the delegation process more transparent and efficient but also encourage wider participation in governance of ENS and other decentralized orgs.

Our vision at Tally is not just to build specific projects but to create a robust, dynamic ecosystem that supports the growth and adoption of governance for decentralized organizations. While we have clear goals and projects in mind, we also maintain the flexibility and creativity to develop new solutions as the governance ecosystem evolves. Our team is committed to driving innovation in this space, ensuring that our contributions have a lasting and positive impact on the ENS community and the decentralized organization ecosystem.

Past experience working on ENS

At Tally, we bring a wealth of expertise in developing tailored governance solutions for decentralized protocols. Operating since 2020, now over 86% of decentralized organizations that use Governor are making token-transfer proposals on Tally. The largest and most important decentralized organizations operate on Tally, including ENS, Arbitrum, Uniswap, Compound, and Gitcoin. Decentralized organizations have facilitated the transfer of over $250million worth of tokens via onchain proposals on Tally.

Specifically, Tally has a proven track record of contributions to the proliferation and maintenance of ENS protocol and ENS DAO. Here’s a summary of our key accomplishments:

• Comprehensive Governance App for ENS DAO: Our user-friendly governance application is extensively used by ENS DAO. It enables delegates and tokenholders to vote, delegate, create proposals, and conduct delegate research/discovery efficiently.

• Enhancing Transparency in ENS DAO Operations: We integrate seamlessly with ENS DAO’s operational frameworks, including working group members and activities. This is facilitated through our Safe integration, which also includes proposals involving treasury usage. For example, our tool was instrumental in a proposal where ETH was swapped for USDC earlier this year.

• Utility with the ENS Protocol: Our governance app is not just a management tool; it’s an extension of the ENS protocol itself, adding utility and functionality.

• Organizing Delegation Week: We collaborated with ENS DAO in hosting Delegation Week, which played a crucial role in increasing governance participation in DAOs across the ecosystem, and specifically ENS DAO, as we partnered with ENS to offer gasless delegation for the DAO.

• ENS Name Resolution Across Tally Platform: We have integrated ENS name resolution across our platform. This includes delegate profile URLs, voting records, recipients of proposal transfers, and Safe signers, replacing the traditional 0x addresses. This not only simplifies processes but also enhances the overall user experience.

Size of team and commitment

15 full-time team members

Links to documents with further information

ENS Create Proposal Prototype
ENS Delegate Discovery Prototype
ENS DAO’s Page on Tally
Delegation Week Website

Conflict of interest statement

None

10k Endorsement link

Service Provider Nominations Discussion

Hello all! I am looking to secure endorsement to nominate tallyxyz.eth to the service provider stream. Tally is a frontend for decentralized organizations and we’re happy to have supported ENS for a while now. We recently became aware of this fantastic opportunity to self-nominate as a service provider and we’re keen to expand our engagement with ENS! We will submit our nomination by EOD tomorrow, just in time Thanks all—we are looking forward to the possibility of contributin…

Budget requested

300,000/y

[auryn]

Gnosis Guild

Name and website of Provider**

gnosisguild.eth

Name of main point of contact**

auryn.eth

What do you want to build on ENS?

Our modular Zodiac stack currently powers the ENS DAO’s non-custodial treasury management of 32,000 ETH by Karpatkey. We plan to continue the development and maintenance of this core infrastructure, and further build out bespoke tooling for the ENS DAO.

Non-Custodial Treasury Management

Capital efficiency and active treasury management are crucial parts of a successful DAO strategy. Karpatkey has proven that our underlying tooling — the Zodiac Roles Mod and Pilot interface — is the most secure and efficient way to manage non-custodial treasuries. To continue supporting this domain, we plan to carry out targeted development for the ENS DAO and Karpatkey. Initial steps include: launching Roles Mod v2, enhancing the Roles App for Roles v2, and improving the Pilot Interface with streamlined permissions auditing. These advancements will collectively bolster transparency, security, and operational efficiency, fostering more active management and increased yields. Beyond these initiatives, we’ll work closely with Karpatkey to identify and build out infrastructure to meet the emergent treasury needs of the ENS DAO.

ENS DAO Governance and Operations

We plan to carry out needs-driven development for the ENS DAO to improve governance and onchain operations. Currently, the ENS DAO relies on largely social rules for Working Group operations, along with Safes for each group. We would like to minimize the need for constant Snapshot governance and cumbersome off-chain coordination by bringing these rules onchain using Zodiac modules. Working closely with Working Groups, we’d like to develop infrastructure such as onchain roles for Steward and Lead Steward functions, modules for streaming Working Group funds, modules for Working Group dissolution and return of assets, and modules that further expand and decentralize Working Groups. Additionally, we would like to work with the Meta-Governance Working Group to audit the three governance process phases for inefficiencies and implement optimizations.

ENS-Native Publications

To bolster ENS’s eminent role in decentralized naming, we will introduce custom ENS-native publications through Tabula. As a web3 publishing tool built for writers, DAOs, and any Ethereum-based account, Tabula pioneers the collective ownership of web3-native publications, allowing any agent or onchain community to post content, build their own interface, or even deploy their own instance. By adding the ability to link Tabula publications to ENS names, onchain entities utilizing ENS can instantly create and collectively maintain decentralized publications that are trust-minimized and censorship-resistant. This initiative will further exemplify ENS’s extensibility, showcasing the fundamental role of identity mapping for individuals and onchain networks in an ever-shifting communications landscape.

Past experience working on ENS

Gnosis Guild has been building public goods for the ENS and Ethereum ecosystem since 2021. Our infrastructure is now leveraged by 150+ onchain organizations securing over $2.5B in assets. Initially providing needs-driven development for GnosisDAO — supporting governance, treasury management, bridging, and custom products — we are now leveraging our expertise serving as independent core contributors to aligned protocols and ecosystems.

As the creators of the Zodiac Standard, we’ve grown a wide ecosystem of open-source modules used by leading DAOs and protocols. Our stack powers Karpatkey’s non-custodial ENS treasury management, relying on our Roles mod, Pilot extension, and custom tooling for secure and efficient onchain management.

Our growing product portfolio can be viewed here.

Size of team and commitment

We plan to allocate a full-time pod of three Gnosis Guild team members. This is typically made up of two engineers and one designer/PM, but flexible for other team members to rotate in and out depending on needs.

Links to documents with further information

Use this to post a link to a presentation or a pitch deck with more information. It can be your portfolio of past work or a detailed roadmap of your future work.

• Product Portfolio
• Gnosis Guild Overview Deck
• Website

Conflict of interest statement

Gnosis Guild is a small stakeholder in Karpatkey, which receives compensation from ENS DAO for their treasury management work. Gnosis Guild does not receive any compensation from Karpatkey’s ENS funding. We see this not as a conflict of interest, but as further proof of the alignment of our organizations.

10k Endorsement link

Budget Requested

$600k for a pod of three Gnosis Guild team members allocated full-time, in 2024, to the ENS related efforts detailed above.

[aabugosh]

Name and website of Provider:

generalmagic.eth

Name of main point of contact:

aabugosh.eth

What do you want to build on ENS?

ENS Referral Ambassador Program

We know that a referral system has long been discussed at ENS. Our team is ready to build an MVP that we can bring to market in just a few months to finally kick off this initiative!

We will create a referral system in which anyone can generate a unique personal link from the ENS site and earn a referral fee every time someone buys an ENS domain from their link. The ENS Referral Solution aims to incentivize and reward users for referring new participants to buy or renew ENS domains.

This solution has the following modules:

• Registration Module (Reg / Auth Module)
• Referral Link Creation and Validation
• User Dashboard
• Rewards Tracking and Calculations Module
• Reward Distribution Module
• Administrative and configs.

This system will not rely on cookies or web2 data. Instead, it creates a referral system where the purchaser signs a message indicating who referred them to the platform and on-chain data is reviewed to calculate the reward. Influencers that want to create a referral link can log in with Ethereum and can create referral links with their ENS domain to share, and when new users come to buy a domain they can type in the ENS domain of the person that referred them or if they are using a referral link, their referrer will be auto filled for them and the only extra user experience is a pop up asking them to sign a message. Then we’ll use a graph of users with relations of referrals and referrers 1:1.

For example, Alice can generate a referral link and share it with Bob to register his ENS domain. When Bob goes to buy an ENS domain via the link, he sees alice.eth as his referrer and signs a message to confirm that as part of the purchase process, and we later verify that Bob purchased ENS domains.

Rewards will be calculated in another module. We read the blockchain in transactions and update the user dashboard rewards in rounds (ex. a 2-week round or shorter). After every round, rewards will be distributed and a leader board published.

We built a similar system for Giveth in which all donors receive a portion of the donor rewards (every 2 weeks with GIVbacks) when they refer a donation through their link . We also took part in the ETHglobal Hackathon at Devconnect Istanbul, winning the Innovation Pool Prize (as Refer.eth. Other useful links: Design - Repos - SampleDashboard).

The architecture of the system is based on APIs and can eventually be added to the ENS app UI, but we suggest that for the initial development, we can have different registration UI under the ENS domain like: https://referrals.ens.domains/.

Total Budget: $200,000 USD

Duration: 1 year

Month 1: Requirements Gathering, Planning, Design and Prototyping

• Team: Project Manager, Governance Analyst, UX/UI Designer, and Front-end Developer
• Focus: Discuss with team and gathering requirements on:
  • The referral program flow: What will the flow of referral rewards look like.
  • Nature of rewards: What is the source of rewards (ex. Separately funded reward pool), currency of rewards (ex. ENS tokens) and how much rewards would be.
  • How to prevent bad actors: We will discuss this in depth, but we believe we can mitigate a lot of problems by designing the rewards to be at best a gas subsidy. Our working concept is to distribute rewards in ENS tokens, and cap the rewards to be no higher than 80% of the amount of gas spent or 20% of the value of the purchase (whichever is lower).
• Creating design prototypes, initial UX flows
• Budget Allocation: $25,000

Month 2-3: Development & MVP Launch

• Team: 2 Developers, UX/UI Designer, QA Tester
• Focus: Core functionality development (frontend and backend), and integration with existing systems.
• Advanced features development, and initial user testing
• MVP launched!
• Budget Allocation: $75,000

Month 4: User Testing and Iterations (A/B Testing and support)

• Team: QA Tester, 1 Developer (part-time), UX/UI Designer (part-time)
• Focus: Extensive User testing, UI/UX adjustments
• Budget Allocation: $10,000

Month 5: Deployment and Marketing Launch

• Team: 1 Developer, Marketing Specialist
• Focus: Public announcement, marketing to ENS staff and ENSDAO community
• Budget Allocation: $10,000

Month 6-12: Support, Marketing and Growth

• Team: 1 Developer (part-time), Monitoring & Support Specialist, DevOps, and Ongoing Marketing.
• Focus
  • Monitoring, initial support, documentation
  • Regular maintenance, updates, addressing any arising issues
  • Ongoing marketing campaigns (social media threads, video content , blog posts, outreach to top delegates and recruiting ENS ambassadors).
• Budget Allocation: $80,000 (for 6 months)

Past experience working on ENS

We previously built the ENS swag shop: https://ensmerchshop.xyz/, are working with the ENS team on some frontend work for the small grants portal and are exploring launching Pairwise with ENS as a public good.

Size of team and commitment

We have a team of 30+ devs, designers and project managers we can pull into this project. We love ENS and would pivot a large percentage of our team to work nearly exclusively on ENS projects if we can make that work.

Below are the main leaders of the team that will coordinate the work.

• aabugosh.eth - CEO at General Magic. Steering the ship with a keen eye for strategy, project management and financial intricacies, Ahmad handles all aspects for projects and operations.
• moenick.eth - Senior Technical Project Manager, with extensive experience in building successful web3 products, currently lead project manager for Giveth.
• markoprljic.eth - Design lead. Head of Design and Business Developer at General Magic. “Magic Marko” is a top notch designer and has been practicing his art on web2 and web3 projects for over a decade.
• griff.eth - Co-founder of Giveth, Commons Stack, General Magic, Dappnode.
• zeptimus.eth - Jack-of-All-Trades at General Magic. ZeptimusQ is the versatile dynamo behind General Magic, skillfully juggling fundraising, business development, product support, and comms.
• krati.eth - CTO at General Magic. With over a decade of tech experience, Krati expertly leads as CTO, blending her vast knowledge in Solidity, Rust, and mobile technologies.

Links to documents with further information

Our website: https://generalmagic.io/

Conflict of interest statement

A few potential conflicts of interest are:

• Griff.eth is a major delegate and a long time supporter of ENS
• We’ve been working closely with the ENSDAO team on the swag shop for the past year: https://ensmerchshop.xyz/
• We’re working on a couple of other proposals with ENS stewards including:
  • A proposal for Ongoing Development and Technical Support for ENS Small Grants.
  • Branding https://www.pairwise.vote/ as an ENS public good (in exchange for sponsorship from ENS), although this is not confirmed or finalized.

10k Endorsement link

Self-endorsement: Griff.eth

Budget Requested

The total budget requested is: $200K

[coolhorsegirl]

Just adding some videos we whipped up!

Delegate Discovery video walkthrough

delegation.mov

Create proposal video walkthrough

lifecycle-demo.mov

[Griff]

UNICORN.ETH

Name and website of Provider:

Unicorn.eth

Website: https://www.generalmagic.io/

Name of main point of contact:

griff.eth

What do you want to build on ENS?

Expect ENS adoption to moon. Unicorn.eth is coming hot and fast to significantly boost the number of ENS users by building the easiest onboarding in web3 where everyone gets an ENS subdomain by default, and uses its incredible functionality to the max!

No one wants to identify as 0xd1D04ac316fdCACe8f24f8110D60C86b810AB15A!

Unicorn.eth will demystify the crypto onboarding experience as an ENS powered Account Abstraction wallet that is natively managed at the wallet’s own subdomain.

1. Log in with Google, or other web2 normal login
2. Create a unicorn.eth subdomain i.e. name.unicorn.eth
3. You are done! Go to name.unicorn.eth.limo to manage your web3 experience!

No apps to download, no confusing and scary blockers, in a few clicks you have a smart wallet and a website!

Anyone will be able to enter the web3 space to receive crypto, collect NFTs, interact with dapps, and more – all without the complexities typically associated with blockchain technology. Our mission is to make onboarding as straightforward and approachable as any everyday online activity, and this is only possible with the power of ENS!

Step 1: Log in. Step 2: Choose your Unicorn domain. Step 3. Welcome to web3

And if someone doesn’t want to be a Unicorn, we have account.eth too ;-). We will deploy them both as 2 different portals for different types of users, but with the same infrastructure behind a more professional design.

This project is not just for Unicorns and Accounts. We will white label this solution and allow any ENS domain holder to easily onboard users with their own ENS domain. Either as a simple fork of Unicorn.eth (no code required) or as an integration into their own website/dapp. Also, as the subdomains are resolved off-chain, we will enable the user to purchase their subdomain, or even upgrade to their own TLD. They may start as a Unicorn, but we expect many to graduate to their own .eth domain.

We hope Unicorn.eth can build a new standard for web wallets, a standard that makes ENS-powered native web wallets the natural onboarding tool of choice.

How the web3 world will change after Unicorn.eth

Today if someone with no wallet gets a POAP, they would go to claim it, then realize they need a wallet, download Metamask, get confused and scared about seed phrases and forget about it.*

If instead, POAP integrated with Unicorn.eth, and the same person received a POAP, when they go to claim it, they would simply make their own poap.eth wallet! They would login with Google, create their noobie.poap.eth subdomain, and claim their POAP into their brand new wallet. This user will be able to go to noobie.poap.eth.limo to see their POAP, and other NFTs and tokens they collect on any chain and they can even share their wallet with their friends!

Unicorn.eth is uniquely positioned to take advantage of AA

• Owning unicorn.eth, account.eth, and many other great domains
• Having deep technical experience with AA via krati.eth
• Having strong trust and connections in the space via griff.eth
• Having an incredible design team via General Magic led by marko.eth
• Partnering with the other great service providers in this thread
• Sharing revenue with our integration partners
• Giving users their own website so they can easily share their crypto world to their friends and family

Unicorn.eth is well positioned to be a dominant player in the wallet space!

Innovative Features

• Web2 login instead of holding keys
• Personalized ENS subdomains
• Same address on almost every chain
• Simplified crypto wallet management
  • L2 bridging abstracted away
  • Swapping abstracted away
  • Withdrawing from multiple chains with 1 click
• User-centric fee structure
• Revenue sharing with partners for network effects
• Exportable private keys for advanced users
• ENS domain upgrade optionality
  • Purchase unicorn.eth/account.eth subdomains
  • Upgrade to personal .eth domain
• Security measures to prevent phishing, scams and mistakes that result in a loss of funds
• Frictionless onboarding, but strong security recommendations as accounts values rise
• AND MORE!

Vision

Our goal is to make ENS THE standard for onboarding into the web3 world. The default EVM experience must include an ENS domain name, just as the default website experience has a DNS domain name (and not 168.58.32.234).

Budget & Roadmap

Total Budget: $200,000 USD
Duration: 1 Year (12 Months)

While our initial budget of $200,000 from ENS is vital, what is even more important is the buy-in from the DAO into this product. We want to make this an extremely high quality consumer facing product, so our focus for the next 3 months will be to seek strategic investment from potential partners, build out a prototype and hire a rockstar marketing manager to round out our team.

Project Origins

Giveth has needed this since its inception. We have seen so many nonprofits blocked from using crypto by the complexities and risks of key management, swapping, bridging, etc. Even worse, we have seen nonprofits send money to the right address on the wrong chain, lose access to their keys, and many other classic mistakes. For months we were searching for an account abstraction wallet that provided the features Giveth wanted, but never found one, so we decided to take matters into our own hands. Our project plan was validated in Istanbul when Griff hacked with a local team on a project called Donat3, which included many of the features we will build into Unicorn.eth. It won 4 awards including the best use of ENS Subnames award!

Past experience working on ENS

We previously built the ENS swag shop: https://ensmerchshop.xyz/, are working with the ENS team on some frontend work for the small grants portal and are exploring launching Pairwise with ENS as a public good.

Size of team and commitment

We have a team of 30+ devs, designers and project managers we can pull into this project. We love this product and will dedicate whatever resources are needed to get it off the ground.

Below is the main team that will lead this project.

• griff.eth - Co-founder of Giveth, Commons Stack, General Magic, Dappnode
• krati.eth - CTO at General Magic. With over a decade of tech experience, Krati expertly leads as CTO, blending her vast knowledge in Solidity, Rust, and mobile technologies. Her work on account abstraction projects enhances her pivotal role in launching unicorn.eth
• markoprljic.eth - Design lead. Head of Design and Business Developer at General Magic. “Magic Marko” is a top notch designer and has been practicing his art on web2 and web3 projects for over a decade.
• sem-the-bee.eth - Solidity Maestro and OG Developer. With his deep expertise in Solidity and a rich history in blockchain development, Sem is a cornerstone of our technical innovation team. Github

Links to documents with further information

Our website: https://generalmagic.io/

Conflict of interest statement

A few potential conflicts of interest are

• Griff.eth is a major delegate and a long time supporter of ENS
• We’ve been working closely with the ENSDAO team on the swag shop for the past year: https://ensmerchshop.xyz/
• We’re working on a couple of other proposals with ENS stewards including:
  • A proposal for Ongoing Development and Technical Support for ENS Small Grants, which has been agreed to.
  • Branding https://www.pairwise.vote/ as an ENS public good (in exchange for sponsorship from ENS), although this is not confirmed or finalized.

10k Endorsement link:

Self-endorsement: griff.eth

Budget Requested:

The total budget requested is: $200K

* Note: POAP has a GREAT solution for people without wallets that allows them to claim their POAP someday in the future when they get a wallet by sending them a link to their email. That said, integrating a Unicorn.eth wallet directly into POAP would still be a major upgrade.

[maxi.eth]

Name and website of Provider

handle.eth & https://twitter.com/dothandle

If approved, funds should be sent to vault.maxi.eth

(hardware wallet, second hardware wallet dedicated to the project will be setup soon)

Website isn’t live yet, as that’s what a portion of the funds will be dedicated to.

Name of main point of contact

maxi.eth

What do you want to build on ENS?

handle.eth: free subdomains registry, an upcoming ens marketing powerhourse

At the time of our previous application in the 10th round of the ENS Small Grants, handle.eth was closer to an idea than a project, this has now changed as it is well in the works. This description will include more technical informations than before as I, maxi.eth, have been working on figuring out how to properly get this project up and running after having meetings with the founders of future handle.eth partners.

WHAT’S HANDLE.ETH?

I acquired handle.eth a couple months ago and will leverage it to build a full-on free, unruggable and decentralized subdomains network to onboard thousands of new users to ENS. The goal is nothing short of being the largest ENS subdomains network to date. To make things clear, .handle.eth subs will be absolutely free with no strings attached, will not have any renewal fees, the handle.eth fuses will be burned thus making the subdomains independant & unruggable, and the cherry on top, handle.eth will be sent to the burn address to decentralize the network. This way, all the “arguments” against ENS we usually see on social media about renewals, good domains being already taken, etc… and pretty much any associated friction is circonvented and users will be able to secure an ENS (sub)domain for free. Also, subdomains minting will be limited to 1 per wallet so that a handful of people do not mint thousands of subs and the network can grow organically.

PARTNERING WITH NAMESPACE & 1W3

Time for the fun stuff. All these objectives will not be achievable simply by enabling subs minting on an existing platform or marketplace. Therefore, handle.eth will have its own custom-made front-end and will use the NameSpace tech in the back-end. After discussing a potential collaboration with thecap.eth, the synergies between NameSpace and handle.eth became pretty clear and we will work together to make our goals a reality. The .handle.eth subdomains will be issued on L1 at launch and will later on be on L2 as the tech is being built. The (much smarter than me) devs at NameSpace will pretty much be our technical advisors as we will use the tech they’ve been building for the past year to run our registry. Since we will be targeting new users, which by definition may not be aware of ENS features, the handle.eth website will walk them through those and get them to easily set the subdomain as their primary name if they wish to do so, set an avatar, edit various records, etc… I had a meeting with hidayath.eth and we will also be partnering with 1W3 to create a decentralized website automatically generated with the sub’s records. NameSpace & 1W3 will be our first launch partners, with more coming soon by the time we launch in Q1 2024.

MARKETING & INTEGRATIONS

All the community members I talked to have been very supportive of this project and I’m grateful for that! The launch will come with waves of support and will quickly reach NFT degens way beyond the current ENS community. I will be reaching out to multiple big accounts which already supported and promoted ENS and am confident they would gladly share such a free subdomains network. I will not name these accounts here but you can easily guess who I’m talking about. Also, the biggest deal for us will be to get the registry integrated in existing dapps, platforms and projects from wallets and messaging to gaming and web3 socials. With handle.eth being burned forever by the time we launch, integrating a decentralized public good like handle.eth will be a no-brainer for them and this is what I will spend most of my time on.

WHY IS FUNDING REQUIRED?

I think this is pretty clear by now, handle.eth is being built as a public good/infrastructure project and will not be monetized. We will solely run on grants to fund the project’s development and marketing activations. Most of the initial funding will be used to develop a quality custom-made front-end. After launch, our main recurring cost will be the NameSpace $1/minted sub fee which we will take on according to our mission to make subdomains free for users (except gas fees but those will be neglible once subs will be issued on L2). Therefore, the more succesful this registry is, the more fees will have to be paid to NameSpace.

Past experience working on ENS

I, maxi.eth, have been into ENS for the last 2 and a half years, and this protocol pretty much changed my life. I previously founded a small web2 startup a couple years before getting into crypto and always wanted to launch a project in this space as well. I had quite a few ideas over the years but nothing felt quite right until now. With ENS being the epicenter of my professional life, I want to accelerate the protocol’s growth, starting within the current web3 ecosystem, and I sincerely believe handle.eth is the ideal project to achieve that and onboard a lot of new users. Disclaimer: I am not a technical guy in this space and really can’t code or anything like that as I’m marketing/business development guy, so I will focus on those tasks to accomplish the project’s mission. As explained above, I talked with brilliant devs and will work closely with the NameSpace team for anything tech-related.

Some of my ENS accomplishments would be being the one behind the hublot.eth campaign (I used to work for a consulting firm and was in charge of their campaign, secured the domain(s), transfered it to them, wrote the tweets, managed influencer relationships, etc…). I also worked with Place Vendome jewelry brand COURBET on leveraging their domain, reached out to the Wrangler team to let them know wrangler.eth was available at a fair price on premium, was involved in the farfetch.eth private sale to Farfetch (while I was still working for the same consulting firm mentionned previously), sold gho.eth to the AAVE team, etc…

Size of team and commitment

1 full-time employee + a couple freelancers for short-term missions (dev, marketing, etc…)

I will make this my full-time job until the handle.eth subdomains registry is widely adopted and integrated in major dapps, platforms and projects.

Links to documents with further information

We’ll publish regular updates on https://twitter.com/dothandle

Conflict of interest statement

There is no conflict of interested as none of the handle.eth affiliates are part of the ENS DAO or ENS delegates. However, our partners NameSpace and 1W3 did receive funding from previous ENS Small Grants rounds.

10k Endorsement link

https://twitter.com/seekmine/status/1730778672779661420
https://twitter.com/garypalmerjr/status/1730717690887553057
Snapshot was broken while I tried to create a proposal so here are tweets from Gary & master.eth

Budget Requested

$100.000/year

Other notes

As previously mentionned, handle.eth will be sent to the burn address in order to decentralize the network and prevent it from ever being manipulated/exploited/profited from.

[alextnetto.eth]

Name and website of Provider: blockful.eth | blockful.io
Name of the main point of contact: alextnetto.eth | telegram

What do you want to build on ENS?

Our vision is to improve ENS in 4 ways

• User experience [UX]: Lower the barrier and complexity for users.

• Developer experience [DX]: Make onboarding for developers easier and reduce costs/time to build on ENS.

• Platform sustainability [PS]: Create a positive-sum situation by having more incentives for platforms so they can grow together with ENS.

• Governance [Gov]: Improve transparency and security on governance.

[UX + PS] 1-step registration for .eth domains

This feature was done in past experimentation from Blockful in the ENS core contract. This feature is mentioned in our article as “commit with payment”.

Today, when a user wants to register a name, he does 2 transactions (commit and register). The idea here is the user does only the commit transaction, and the Dapp does the register transaction. With that flow, it’s not just improving the UX (no need to keep staring at your screen for 60 seconds for the commit to be valid) but also creating a revenue opportunity for Dapps (as shown in the following diagram).

Our goal here would be to push forward this feature to ENS core contracts, being the first contribution outside ENS Labs to the core protocol and contributing to the narrative of decentralizing the development. If that’s not feasible, we’ll do this feature in an external contract, the cons for that is the user paying a little more gas for a much better experience.

This feature unlocks high value, not just for the user but also for the platform implementing it, creating a revenue opportunity by providing a better UX and then increasing the registrations. The evolution of this is creating a backend that all platforms can use to batch, optimize gas costs, and reduce implementation costs.

There is also the opportunity to improve gas costs by adding batching features on commit, register, renew, and fuse operations. The deliverable is the whole system working, from frontend to backend and smart contracts.

[UX + DX] Improving ENS off-chain features

The CCIP-read (EIP3368) is a great standard created by Nick, unlocking huge potential for adoption. It enables creating subdomains and records (like setting your avatar) for free.

As mentioned on ENSIP-16 by Makoto and Jeff Lau: “With EIP-3668 subdomains already starting to see wide adoption, it is important that there is a way for frontend interfaces to get important metadata to allow a smooth user experience.”

We are talking with a big fintech (+50M users) to integrate ENS into their crypto wallet and create off-chain subdomains and forward resolution. This made us realize some improvement points.

Today, we have the standards for reading the data but not for writing. The R&D in this idea is around creating a standard for “minting”, transferring off-chain subdomains, and updating off-chain records. That means being able to change your avatar on cb.id through another ENS dapp, for example, creating a unified experience across platforms and also reducing development complexity.

Note: The scope here is specific to off-chain domains using centralized databases, not L2. The deliverable is the whole system working, from frontend to backend and smart contracts.

[DX] ensdk: a lightweight library to integrate the Ethereum Name Service and features that will be developed here in the proposal.

The value of all the proposed features gets unlocked when there is an easy way to use it. ENS is growing, and for the next level, we also need a variety of ENS SDKs.

The idea for this started at the beginning of October (repo, npm).

[Gov] Security review for executable proposals

As discussed in multiple working group meetings, it would be great to have a third party verifying executable proposals. At Blockful, we also do security reviews (audits).

In the last executable proposals, we have been checking and going after decoding and understanding the code to be executed by the DAO (e.g. keeping in touch with Karpatkey for related proposals). This was an informal way to have a third party help because we used the free hours we had, so there is no deep dive or formal report.

We would like to do it in a proper way and help secure the DAO. More eyes on executable proposals are never bad.

Note: We’re building some DAO tooling to benefit the whole ecosystem. It’s out of the scope of this proposal, but I’m sure ENS DAO will benefit from it.

Past experience working on ENS:

In mid-2022, I was still a golang backend engineer on a fintech. When I got the opportunity to work on my first experimentation around ENS, I quit my job, dropped out of computer science (CS), and started Blockful.

Today, we are a team of 10 (8 engineers from fintech, web3 communities, CS. 1 PMM and 1 operations/BD). We never raised capital. We slowly and organically grew through the bear market, providing services for founders and DAOs across the space.

I’m grateful for how ENS kickstarted all of this and changed not only my life but also the lives of our brilliant team.

Today, Blockful has become one of the to-go service providers for projects to integrate and use ENS because of our expertise in ENS architecture, product, and smart contract experience.

Our first contribution towards ENS was exploring innovative features (that came from Avsa’s ideas) on the old ETHRegistrarController. Here is a detailed article about it. Since then, we have started working with different teams to build and understand ENS.

When the new ETHRegistrarController (with support to NameWrapper) was launched, we adapted these features to the update. Here is a detailed article about it.

Size of team and commitment

Being passionate builders, our team has won 6 hackathons (from ETH Global, Chainlink, and ETH events) until now.

The feedback we got in past client deliveries and the goals we engage with demonstrate our work principles:
Avsa’s post about past experimentations in ENS contracts tweet: “My experience with Blockful has been incredible. They underpromised and over-delivered at every step”

Zen Dragon, grants manager at Balancer tweet: “The team is highly motivated and innovative, making them the exact type of group we get joy from funding.”

For the scope we proposed here to be production-ready, we’ll need 3 full-time devs
1 Fullstack
2 Backend / Smart Contract (including myself)

Links to documents with further information

The contribution that got Blockful started (github)

Small grant for this contribution

Small grant for updating the new ETHRegistrarController with these features:

Balancer article and tweet about our contribution.

Conflict of interest statement

Since we created Blockful (a year and a half ago), we worked with several teams and founders across the space, from the ENS ecosystem to top DeFi protocols (like Balancer).

One of the teams we worked with was NameHash, which will also apply for this program and is one of the most brilliant and serious teams we worked with. We are happy to help teams build on top of ENS and use our technical expertise to advance.

10k Endorsement link: (Snapshot)

Budget Requested

$300,000/year

This represents a 40% discount over the rate we charge our usual clients. Our goal here is not to profit. It’s to dedicate to bigger achievements for ENS in a sustainable way.

We provide world-class engineers to provide services. Blockful’s purpose is to reinvest the profit from our operations into building open-source and contributing to protocols and ideas we identify with. ENS and governance are one of those.

Independent of the result here, we’ll continue to contribute and develop some of the ideas proposed here because we think it’s worth it for our efficiency to help people integrate on ENS and improve DAOs decision-making and governance.

[lightwalker.eth]

Summary

Imagine if Metamask, Uniswap, Farcaster, OpenSea, WalletConnect, Etherscan, etc. all became “Frontend Registrars” that directly onboard their users into ENS. We help ENS grow by integrating ENS onboarding into web3 wallets, apps, and games where millions of people already are. To advance these goals we’re building NameKit, NameGuard, and advancing a (proposed) ENS Referral Program.

We have a 15 person team that is working day and night to help ENS grow. The opportunity to become an ENS Service Provider means the world to us. Thank you for your heartfelt support.

Provider

NameHash Labs (namehashlabs.org)

namehashlabs.eth

Point of contact

lightwalker.eth

What we’re building for ENS

We help ENS grow by integrating ENS onboarding into web3 wallets, apps, and games where millions of people already are. To advance these goals we’re building NameKit, NameGuard, and advancing a (proposed) ENS Referral Program.

The problem and opportunity

ENS has achieved a special milestone in its growth: the majority of ENS names are now issued through “Frontend Registrar” apps other than app.ens.domains. For example, Coinbase Wallet alone has issued more than 4 million ENS names. Rainbow Wallet is another example.

The future of ENS growth will predominantly be driven by this trend. Our biggest growth opportunity is persuading more “Frontend Registrar” apps to issue ENS names directly to their audiences. Persuading apps that already have millions of users is especially valuable.

We have a problem though. The current incentives for an app to become a “Frontend Registrar” for ENS aren’t so good.

Let’s take a technology perspective. Where does NameKit fit in?

There’s a lot of great focus by other teams in the ENS ecosystem at the smart contract layer. For example, with name issuance strategies on L2 or offchain. Some helpful libraries also exist. These are awesome !

However, from the perspective of an app that’s considering becoming an ENS “Frontend Registrar”, there’s still a big hole in the middle of their ENS Tech Stack. “ENS Frontend Registrars” have to build all of the “Advanced ENS User Journeys’’ mostly from scratch themselves.

Some might ask if it is truly a lot of work to build these “Advanced ENS User Journeys”? Well let’s consider the official ENS Manager app. This is how big? Approximately 100,000 lines of code? All written by the most experienced ENS dev team (ENS Labs) over the course of years ! Should each “Frontend Registrar” build and maintain their own version of all this logic?

The analogy above of course isn’t perfect, but the point is that if an app wants to become a “Frontend Registrar” with a great UX that handles all the edge cases and continuously keeps up with all the innovation in the ENS ecosystem there’s a lot of work to do it well!

NameKit will include:

• Open source libraries that anyone can run in their own app / infrastructure.

• Public hosted cloud services (for those who don’t want to run their own infrastructure).

• Client SDKs.

• UI Kits.

• Figma Design Templates.

• Rich documentation.

• Ability to integrate with ENS Name Issuance strategies built by other teams on L1, L2, or Offchain.

• … and more!

“Frontend Registrar” UX - Challenges & Opportunities

When the majority of ENS names are being registered on 3rd party apps it’s important that we make it easy for these 3rd parties to do an amazing job with all these UX details.

Key products under development

Product	Summary	Current Dev Status
NameKit	Enable every app to easily build amazing ENS onboarding and profile management.	v0.1 alpha
NameGuard	Guard your users from heartbreak and encourage best practice usage of ENS.	v0.8 beta
ENS Referral Program (proposed)	Provide financial incentive to businesses, builders, and storytellers to invest their efforts into the growth of ENS.	Preliminary temp check

We’ve put a big effort into these products already, but there’s still a big journey ahead. It will take a lot of resources to get there.

With your support for NameHash Labs to become an official ENS Service Provider we will bring these innovations to life and make big impacts to help ENS grow !

Why vote for us?

Why vote for NameHash Labs?

Here’s 3 key reasons why:

1. Our Principles

Let’s work together to achieve the best results for ENS !

2. Our Mission & Direction

“Help ENS Grow” is the mission that fills our minds each day.

To this end, we do not define ourselves in terms of advancing a specific technical feature. We aren’t interested in building technologies that might be fun as an engineer, but have little market impact. We are focused on working backwards from the goal of “Help ENS Grow” and then doing our best to build the technologies we believe will best advance that.

Today, we believe the best opportunity to “Help ENS Grow” is achieved through NameKit and the ENS Referral Program proposal that we are advancing.

3. Our Team & Long-Term Commitment to ENS

Our team has been working for more than 2 years to build big things for ENS !

Product	Summary
NameKit	Enable every app to easily build amazing ENS onboarding and profile management.
NameGuard	Guard your users from heartbreak and encourage best practice usage of ENS.
ENS Referral Program (proposed)	Provide financial incentive to businesses, builders, and storytellers to invest their efforts into the growth of ENS.
ENS Normalize Python & contributions to the ENSIP-15 standard	Python implementation of the ENS name normalization standard.
ENS Label Inspector	A detailed X-ray into the attributes of labels in ENS names.
ENS Font Data	Metadata for graphemes that may appear in ENS names.
NameKit Contracts	Contracts that help “Registrar Frontends” earn additional revenue for helping ENS grow.
NameGuard Client SDK	TypeScript client SDK for making API calls to NameGuard.
NameGuard React UI Kit	React components for creating great UX with NameGuard data.
NameGuard Figma UI Kit	Customize NameKit user experiences to match your unique app.
ENS Name Parser	Utilities for parsing ENS names from user input.
NameGuard Cloud Deployment Automations	Easily deploy your own instance of NameGuard into the cloud.

About us

NameHash Labs is represented by a team of 15 working day and night to help ENS grow.

We’re proud of our talented team and will be announcing multiple opportunities to come meet them and ask any questions in scheduled Google Meet calls prior to the commencement of Service Provider voting.

Backgrounds in our team range from experienced technology entrepreneurs to Computer Science PhDs who are at the cutting edge of their fields.

To date, all expenses to support this 15 person team have come at the personal expense of our two founders. It adds up to a lot. All we have built has always been 100% ENS exclusive. We believe these personal investments represent an unrivaled proof of commitment to ENS.

Everyone on our team appreciates support from the ENS community for NameHash Labs to become an ENS Service Provider. This funding will be critical to support the salaries of our team and their ongoing work to help ENS grow.

We look forward to a long future as dedicated members of the ENS community.

Further information

Our team:

• NameHash Labs

Our key projects:

• NameKit

• NameGuard

• ENS Referral Program (proposed)

Conflict of interest statement

We have no conflicts of interest.

10k endorsement

Endorsement

Budget requested

$600,000 / year

With such a large team, this amount falls short of covering all our costs, but we are betting big on ENS. How big? Our founders have been completely unpaid for all of their work on ENS over the last 2 years. Additionally, the salaries for all work produced by our team to date has been funded by our founders.

The opportunity to become an ENS Service Provider means the world to us. Thank you for your heartfelt support.

[Raphael_StableLab]

One paragraph summary

@Raphael_StableLab

We’re looking to build a procurement platform for DAOs.

ENS names could be the basis of on-chain resumes or profiles, that service providers use to bid on Requests For Proposals (RFPs) on the DAO procurement platform we want to build.
Our platform would help DAOs find the best applicants because it would collect RFPs from many different DAOs. Research and guidelines on tender processes would help DAOs draft the best Requests for Proposals possible. The platform would also include tools that help move applicants along the pipeline. Less work for DAO operators, more clarity for applicants.

[harithk17]

Summary for Snapshot vote:
Etherscan is a leading block explorer for the Ethereum ecosystem that has supported ENS since May 2017. Having access to ENS names on leading block explorers is vital for the continued usage and adoption of ENS.

Name and website of Provider:
etherscan.eth
https://etherscan.io/

Name of main point of contact:
harith.eth

What do you want to build on ENS?
This proposal is for funding the on-going development, support, and associated hosting fees of ENS on Etherscan and relevant block explorers run by the team.

Having access to ENS names on leading block explorers is vital to the continued usage and adoption of ENS. The following are useful features that Etherscan could build as part of this proposal, on top of ongoing support:

1. Extending the current support of ENS names on Ethereum L1 to Ethereum L2 explorers (including Optimism, Arbitrum, Polygon, Base, Linea, Scroll and others listed here).
2. Extending the current support of .eth names to other domains such as .xyz and .art.
3. Support of off-chain names using CCIP such as .cb.id including address name tags and lookup in URL bar.
4. Support of DNS-based names such as .com.
5. Improved display of normalised ENS names.

Past experience working on ENS:
On top of running a leading block explorer for the Ethereum ecosystem since the network’s inception, Etherscan has contributed the following to the ENS ecosystem:

1. Support of ENS name forward resolution search and auctions list since May 2017.
2. Support of ENS address name tags since May 2021.
3. Support of ENS names in Blockscan Chat since February 2022.
4. Support of Wildcard Resolution (ENSIP-10) since July 2022.
5. Support of new ENS Reverse Registrar contracts (EP3.5) since June 2023.
6. Support of Normalization Standard (ENSIP-15) since July 2023.
7. Other features related to ENS such as:

• Warning for expiring and expired ENS names.
• Lookup of ENS name directly in the URL bar.
• Auto-lookup of ENS names in the search bar.

Size of team and commitment
The Etherscan team is made up of 40+ employees. The team as a whole will support ENS initiatives across product development, infrastructure maintenance, education, and user support.

Links to documents with further information
Some examples of ENS integration on Etherscan may be found here:

Ethereum Name Service Lookup

Ethereum Name Service | Etherscan

https://etherscan.io/name-lookup-search?id=vitalik.eth
https://etherscan.io/address/vitalik.eth

Conflict of interest statement
Etherscan does not have any conflict of interest with ENS DAO. The team previously received a donation of 46,296.3 ENS tokens from ENS in November 2021.

10k Endorsement link:
https://snapshot.org/#/ens-streams.eth/proposal/0x90603a72e5a1ceea1adfff5f98301187c222e84d0e63401938475931b5f79f83

Budget Requested:
$1,000,000.00 / year