NameHashLabs.eth

Dedicated to helping ENS grow. Open source infrastructure.

[NameHashLabs.eth @NamehashLabs]

1/ Reminder: the ENS Referral Program is LIVE.

Up to a 50% revenue share for any apps, wallets, creators, and communities that drive .eth registrations and renewals.

Two paths in: generate a referral link in 30 seconds, or integrate .eth registration directly into your app.
https://t.co/6ydnIYdpJX

[NameHashLabs.eth @NamehashLabs]

Builders: add ENS renewal reminders to your app. Your users will be eternally grateful 🙏

https://t.co/0cYGIk3cME

[Lefteris Karapetsas @LefterisJP]

A rotki user just renewed their ENS before expiration.

Not in their calendar. Didnt remember the date. rotki did.

The app analyzes your history, finds your ENS names and reminds you to act. Same for bridges, vesting etc

Your identity shouldnt expire because you forgot a date!

[NameHashLabs.eth @NamehashLabs]

Put your .ETH on people.

[Lou3e @lou3ee]

Put your .ETH on people.

[NameHashLabs.eth @NamehashLabs]

7 ways you can use your ENS name today 👇

[ens.eth @ensdomains]

Most people think ENS names are just easier wallet addresses.

But people are already using ENS for payments, communities, fundraising, brands, identity, and much more.

7 ways you can use your ENS name today 🧵

[ens.eth @ensdomains]

ENSv2 introduces role-based permissions for ENS names.

Instead of one wallet controlling everything, access can be split across different roles.

One role might manage records, another might update resolver data, another might control higher-level ownership or admin settings.

[NameHashLabs.eth @NamehashLabs]

2/ ENSv2 introduces a multichain namespace, a new registry architecture, and a permissions system that doesn't exist in v1. The Subgraph can't model any of this.
The data layer that powers every ENS-enabled app needed to be rebuilt from the ground up...

[NameHashLabs.eth @NamehashLabs]

ENSv2 is coming. Names will live across mainnet and other chains. The data layer underneath every ENS app needs to handle that.

The ENS Subgraph can't. ENSNode can. And it's ready now.

👉https://t.co/hTVi7PEzYN

[Marc Andreessen 🇺🇸 @pmarca]

What you need to know about the CLARITY Act.

[NameHashLabs.eth @NamehashLabs]

Your users know a great ENS integration when they see one. Primary names resolve correctly on mainnet and L2s. Contracts are named. Avatars render. Records display consistently everywhere.

ENSAwards helps builders close the gap. Every app scored. Every benchmark documented.

The best part: the leaderboards are open for public contribution. Have a favorite app that should be benchmarked? Add it. Want your own app scored? Request it.

https://t.co/aPft701w09

[NameHashLabs.eth @NamehashLabs]

"wow there's a chain-agnostic naming system that already exists with hundreds of app integrations, time to build our own that only works on one chain"

[NameHashLabs.eth @NamehashLabs]

👇

[ens.eth @ensdomains]

ENS is no longer a niche tool for crypto power users.

Millions of names now exist across ecosystems, wallets, apps, and DNS integrations.

ENSv2 is designed to support that kind of scale without losing the openness that made ENS useful in the first place.

[NameHashLabs.eth @NamehashLabs]

ENSNode is the full-stack development platform for ENSv2. Not just an indexer. A complete stack:

ENS Omnigraph API, ENSApi, ENSDb, ENSIndexer, ENS Rainbow for services. enssdk, enskit, enscli, ensskills for packages.

ENSv2 is the most significant upgrade in ENS history. ENSNode is how builders prepare for it.

[NameHashLabs.eth @NamehashLabs]

The ENS referral live feed is streaming registrations and renewals in real time. Agent names. Human names. All onchain. All attributed.

Watch the latest snipes as they stream in: https://t.co/smcCVE6RYL

[NameHashLabs.eth @NamehashLabs]

Builders: the ENS Referral Program leaderboard is live. Apps are already earning from every .eth registration and renewal their users make. The integration is easy. The revenue is real. The question is why you're not on it yet. https://t.co/b5jdO0XrnX

[NameHashLabs.eth @NamehashLabs]

Building an app that displays .eth names? Whether you know it or not, you're making rendering decisions. How you handle Unicode normalization, confusable characters, and label display affects what your users see and whether they can trust it.

ENS Rainbow makes these inconsistencies visible so builders can fix them and users see the same name everywhere.
https://t.co/LY5SKGFJQ8

[NameHashLabs.eth @NamehashLabs]

How well does your favorite app integrate ENS?

ENSAwards benchmarks integrations across the ecosystem. Resolution. Display. Registration. Renewals. Subname support. All ranked. All public.

The leaderboards are open for contribution. Know an app that should be on the board? Add it today.
https://t.co/15iR8q8yVR

[NameHashLabs.eth @NamehashLabs]

https://t.co/uKbeb5n3E4

[NameHashLabs.eth @NamehashLabs]

Most .eth registrations today happen because someone went looking for a name. Imagine what happens when apps start asking "do you want one?"

A wallet during onboarding. A game when you create a character. A social app when you set up a profile.

That's what the ENS Referral Program was built for. Revenue share for any app that makes it happen.

[NameHashLabs.eth @NamehashLabs]

Builders: apps are already earning from this. The integration is easy. The revenue is real. Don't sleep on it.
https://t.co/b5jdO0XrnX

[NameHashLabs.eth @NamehashLabs]

Every app that displays your ENS name could warn you when it's about to expire.

This should be standard. It isn't. Yet.

The ENS Referral Program now pays apps to build it.

[NameHashLabs.eth @NamehashLabs]

Took one agent prompt. not one sprint. not one quarter. one prompt.

Earn up to 50% revenue share on every .eth registration and renewal your users make. Your users get identity. You get a new revenue line. https://t.co/b5jdO0XrnX

[happysingh.eth @HAPPYS1NGH]

Most devs don't know the ENS registrar has a referrer fee built in.

Pass your wallet address → earn ETH every time a user registers a name through your app.

I built the whole flow in one agent prompt.