[Case Study] POAP: In-app ENS Usernames with Namespace

Most identity systems in crypto still feel bolted on. They exist, but they do not feel native to the product.

That is what made the POAP collaboration interesting.

POAP already had real distribution, a clear product, and a strong brand. The goal was not to fix something broken. It was to upgrade a working experience by migrating from a previous subname infrastructure provider to Namespace, without downtime, without user friction, and without introducing operational risk.

The result was simple on the surface and meaningful underneath: POAP users could claim a free username directly inside the POAP app, and that username could function as their identity both inside the app and across the broader Ethereum ecosystem.

At a Glance

Client: POAP
Start date: June 20, 2025
What Namespace provided: offchain ENS subname infrastructure, migration support, API integration guidance, and ongoing reliability
Implementation: direct integration of Namespace's offchain subnames API into the POAP app
Names used: onpoap.eth, poap.xyz, and withpoap.eth
Outcome: 5,000+ subnames issued, smooth migration, no downtime, and no reported issues post-migration

The Opportunity

POAP is one of the most recognizable products in onchain culture.

It turns meaningful participation into collectible digital records. But as products mature, user expectations change. People no longer want to interact through raw wallet addresses alone. They want identities that feel human, portable, and native to the product they are already using.

That created a clear opportunity for POAP:

give users a free username directly in-app
make identity easier to understand and use
strengthen the product experience without adding friction
extend POAP's brand presence into the naming layer
do it all in a way that works across Ethereum, not just inside one app

This is where ENS subnames made sense.

Why POAP Chose Namespace

The initial ask was straightforward: migrate POAP's existing subname setup from a previous infrastructure provider to Namespace.

But migrations like this only look simple when they go well.

Behind the scenes, the real requirement was higher: move an existing naming system into new infrastructure, preserve continuity, avoid downtime, and make the transition invisible to users.

Namespace was selected to handle that migration and power the next version of the experience.

Using Namespace's offchain subnames API, POAP integrated direct subname issuance into its app. Users could open the app, choose a free username, claim it, and immediately use that ENS-based identity as their official handle inside POAP and across the broader Ethereum ecosystem.

From a product perspective, that matters because usernames are not just decoration. They make the app more legible. They make identity more social. And they turn a wallet address into something people can actually remember and use.

What Namespace Delivered

Namespace's role was not just to provide infrastructure in the background. We worked closely with the POAP team throughout the migration and implementation process.

That included:

migrating POAP from its previous subname infrastructure provider
enabling offchain ENS subname issuance inside the POAP app
supporting issuance across onpoap.eth, poap.xyz, and withpoap.eth
helping ensure the migration happened cleanly and on time
providing technical guidance directly with the POAP team during implementation
maintaining the system after launch with no reported issues

The technical architecture was intentionally simple from the user's point of view. POAP integrated Namespace's offchain subnames API directly into its application, allowing free username claims without forcing users through a complicated flow.

That simplicity is part of the product value.

The Result

The most obvious result is adoption: POAP has issued more than 5,000 subnames through the integration.

That number matters, but the stronger signal is what it represents.

It shows that ENS can work well inside consumer-facing apps when it is implemented thoughtfully. It shows that identity can be embedded into the user experience without turning into a crypto-native obstacle course. And it shows that products do not need to choose between polish and interoperability.

Just as important, the migration itself happened with:

no downtime
no disruption to users
no reported reliability issues
no support signals indicating something broke after launch

For infrastructure, that is the real standard.

When naming is part of the product, reliability matters as much as the feature itself. If identity breaks, the product feels broken. In POAP's case, the rollout happened the way these things should happen: quickly, quietly, and correctly.

Why This Matters Beyond POAP

On paper, adding ENS usernames to an app may not always look like the most direct monetization feature.

In practice, it often signals something more important: product maturity.

When an app gives users portable, human-readable identity, it says a lot about how that team thinks. It says they care about user experience. It says they understand that Web3 products should feel coherent, not fragmented. And it says they are building for a broader ecosystem, not just a closed interface.

POAP understood that.

The collaboration is a good example of how branded ENS subnames can create value in three ways at once:

Migration success: replacing legacy infrastructure without downtime or disruption
Better UX: giving users a simple, in-app identity claim flow
Production-grade reliability: proving that offchain ENS infrastructure can support real usage at scale

That combination is exactly why more wallets, apps, communities, and ecosystems are starting to treat naming as product infrastructure rather than a side feature.

A Word from POAP

As Patricio Worthalter, Founder of POAP, put it:

"We have found in Namespace an efficient partner that quickly understood our needs and provided very solid solutions".

That is the kind of outcome we aim for.

Not flashy infrastructure for its own sake. Solid solutions that fit the product, move quickly, and keep working.

Closing

POAP did not need naming for the sake of novelty. It needed a better identity layer inside a product people already use.

Namespace helped make that happen by migrating the underlying system, enabling in-app ENS username claims, and supporting a rollout that has already reached thousands of users.

If you are building a wallet, app, community product, or onchain platform, the lesson is simple: ENS usernames work best when they feel native to the experience. That requires the right product decision and the right infrastructure partner.

If you want to bring ENS usernames into your product: