Give your users a name, not an address.
HoodFi issues lifetime ENS names on Robinhood Chain. If you run a wallet, an exchange, an app or a fleet of agents, there is a version of that worth doing together — tell us which one and a person will answer.
Same destination, both times. One of them your customer can read back over the phone.
Three shapes, so far.
Names in your product
Your users mint a name from inside your app and it resolves everywhere ENS does — your interface, block explorers, every wallet that reads the standard. The registry is public, so nothing about it is only ours to read.
Your own namespace
A parent name of your own, with subnames issued under it on whatever terms you set. Free for your users, priced, invite-only, or handed out with an account. You keep the parent.
Agents, not just people
An MCP server already lets an agent check, price and register a name with no key held on our side. If your platform runs agents that need a stable identity, that path is built and live.
None of them is a menu. If what you have in mind is a fourth thing, that is the more interesting email — and if you just want to ask a question, this form reaches the same inbox. How the names work.
Start the conversation.
Everything here is read by a person, and answered by one. There is no form-filling stage after this and nothing gets added to a list.
The contracts, the gateway and the MCP server are all public. You can read the whole thing before you write to us.