There wasn’t a single moment when onchain identity broke. There was no loud event, no dramatic fork, no announcement. Just a slow drift, hidden inside well-intentioned onboarding flows.

A Slow Shift No One Saw Coming

I didn’t truly see it until it blindsided me during an ordinary day. Someone messaged me:

“I sent you something. Did you get it?”

I opened the wallet I always check. Nothing. I opened another one I sometimes check. Still nothing. Then I remembered that the app they used had created a separate wallet for me during signup. I dug through my apps, found it, and there it was — a small balance sitting somewhere I never look.

That single moment opened a door. Suddenly I noticed little pools of value scattered across different identities I had accumulated without meaning to. A trading profile I hadn’t opened in months. A social account that quietly generated a signing key for me. An AI agent with a tiny balance locked behind an OAuth login. It was all harmless individually, but the pattern was unmistakable.

Onchain identity had stopped being one thing. It had become many things. And none of us had noticed.

How Onboarding Fragmented Identity

We used to bring our own wallets.
Now apps hand us one automatically.
🚪➡🔑

It was a huge UX win. Seed phrases disappeared. People could act instantly. Crypto finally felt accessible.

But every invisible wallet came with a hidden side effect.

Every new signup gives you:

• A new identity

• A new wallet capable of receiving value

Even if you never return to the app, the wallet remains active. It can hold funds, and it often does.

The issue isn’t having multiple identities. People manage plenty of those in Web2. The issue is that onchain identities can receive money, and that requires clarity. When someone sends value, they’re picking whichever version of you they see first or remember most. Sometimes it’s your main wallet. Sometimes it’s not.

Nothing is stolen. Nothing disappears.
But it does get scattered.

A frictionless future created a fragmented present.

The Old Model: One Name, One Wallet, One Destination

For years, onchain identity relied on a simple assumption:
one person = one canonical wallet.

ENS and similar naming systems were built for that world. A name mapped to a destination. You shared the name, received the funds, and everything worked.

It was elegant.
It was reliable.
And it matched how people used crypto at the time.

But onboarding changed, and usage changed with it. Most modern wallets aren’t created intentionally. They appear automatically inside sign-in flows. And while ENS can store multiple addresses, that means one address per chain, not one address per app generated wallet. Fragmentation today isn’t cross-chain — it’s within the chain itself.

Even highly organized users who structure ENS subdomains still end up managing more names than they planned for, simply because each new app introduces another one. It is no longer a matter of personal discipline. The environment simply produces more identities than the tools were designed to handle.

It’s like forwarding all your mail to a single house…
even though you now, unintentionally, have several.

The Modern Reality: A Constellation of Identities

Today, most people end up with far more onchain identities than they expect. Each new app, network, or interaction introduces another account or wallet, and over time these accumulate into a broad constellation that reflects the full range of a person’s activity. None of this is inherently negative — it’s just the natural outcome of an ecosystem that gives users more ways to participate, often automatically.

What’s surprising is how quickly this constellation grows and how little awareness people have of its size. What once felt like a single presence onchain now spans multiple contexts, each representing a different moment of engagement. The apps aren’t forgotten; the identities simply multiply faster than anyone keeps track of. And once you notice it, it’s hard not to see it everywhere.

The Real Problem Isn’t Identity. It’s Routing.

Identity can be complex. Humans can handle that. Payments can’t.

What we actually need is simple:

• One place people can send value with confidence

• One place that understands every identity we’ve accumulated

• One system that routes funds where we want them to go

Not another naming system.
Not another wallet format.
Not another identity.

We need a layer above all of it — a routing layer.
🔀

Something that brings order to the constellation and gives people a single, dependable payment surface, even when their underlying identities are spread across the ecosystem.

That missing layer is what we decided to build. A unified entry point for value that lets you decide how incoming payments flow through your different identities.

If you want to see how it works, visit handle.ee.

What Happens Next

We’re not going back to the one wallet, one name era. That moment in crypto history is gone. As onboarding expands, people will accumulate more identities, more keys, more app wallets, more usernames.

This is good. It means adoption is growing. But people still need consistency. They need a single payment anchor. They need a dependable point of truth others can send to, no matter where an identity originated.

Identity will keep multiplying.
Wallets will keep multiplying.
Routing must become unified.

That is the missing piece. And that is the part we are solving.

The constellation isn’t the problem.
The lack of a map is.