hood.Launch appYour guide to names on Robinhood Chain — how to register, manage, and resolve .hood names. New here? Start with the basics and work down.
A .hood name is a human-readable identity for your wallet on Robinhood Chain. Instead of sending money to 0x7Ac4…d3F9, people can send it to robin.hood. One name replaces the long address — and it works across every app that supports the standard.
Under the hood it's an ENS-standard on-chain record you own: an ERC-721 NFT that points to your address, plus a profile you control. Register it once and it's yours for as long as you keep it renewed.
one name for your wallet, your profile, and your money — readable by humans, understood by apps.
.hood names live on Robinhood Chain — a fast, low-fee Arbitrum-based network built for everyday transactions. Because names are stored on-chain, you hold them in your own wallet as a token: no company can take them back, and you can move or sell them freely.
Transactions settle in a couple of seconds and cost a fraction of a cent, so registering, renewing, or transferring a name feels instant and cheap.
Open the app and tap Connect Wallet in the top-right. Pick Robinhood Wallet, MetaMask, Coinbase, or WalletConnect.
Type the name you want. We check availability live on-chain and show the yearly price instantly.
Choose how many years and confirm. A commit-reveal keeps it un-snipeable, and the name mints to your wallet in seconds.
Names are registered for a yearly term. Registering mints a fresh ERC-721 record that points to your wallet. You pick the length up front (1–100 years) and can always extend later.
Valid names use lowercase a–z, numbers 0–9, and hyphens, with a 2-character minimum. The .hood ending is added automatically — you type the part in front.
Anti-snipe by design: registration is commit-reveal — a hashed commit, then a reveal ~10s later — so bots can't front-run the name you're claiming on this FCFS chain.
Shorter names are rarer, so they cost more. Pricing is per year, USD-denominated, and shown live as you search. Everything 5 characters and up is a flat, friendly $5 a year.
Same tiers as ENS — but on Robinhood Chain gas is cents, not tens of dollars, so the all-in cost is far lower.
Every name has an expiry date. As long as you renew before it lapses (plus a 90-day grace period), the name stays yours. In My Names, each name shows its expiry and an Extend +1y button — one tap adds another year.
If a name fully expires past its grace period, it returns to the pool and anyone can register it again — so extend names you care about ahead of time.
You can own many names, but one is your primary — the identity apps and wallets display instead of your address (reverse resolution). It's what people see when you send a payment or show up in an activity feed.
Set it in My Names with Set primary. Switch it anytime; only one name is primary at a time.
A name carries a small profile you own: the wallet address it resolves to, an avatar, and optional text records like a website or social handles. Apps read these to show a richer identity than a bare address.
Records live with the name, so they travel with it — if you sell or transfer a name, the new owner sets their own.
The Marketplace surfaces the most-wanted short and culture names — 3 and 4 character names, number clubs, and icons — with live on-chain availability. It's the fastest way to spot a premium name that's still unclaimed.
Use the length filters to narrow the grid. Anything still available can be claimed on the spot at its registration price.
Browse the market and hit Register on a name you want.
Connect your wallet if you haven't yet, then pick your term and review the price.
Confirm. The name mints to your wallet and shows up in My Names.
Your wallet is how you pay, sign, and hold your names. Tap Connect Wallet and choose Robinhood Wallet, MetaMask, Coinbase Wallet, or WalletConnect. Approve the connection and you're in.
Your address appears top-right — tap it to disconnect anytime. Disconnecting never affects the names you own, which live on-chain regardless.
A .hood name is an ERC-721 token in your wallet — you truly own it. You can hold it, point it at any address, set its records, make it primary, or sell/transfer it. Nobody can move it without your signature.
When a name transfers, ownership and control pass entirely to the new holder, who then manages its records and renewals.
Never share your seed phrase. No one from hood will ever ask for it.
Check the name and amount in every transaction before you confirm.
Watch your expiry dates and renew names you want to keep.
.hood is a full ENS-standard stack, deployed and immutable at the registry level (upgradeable registrar/resolver/controller behind proxies). All live on Robinhood Chain (id 4663):
Any app resolves a .hood name in one call to the UniversalResolver. Forward: name → address. Reverse: address → primary name (with anti-spoof verification).
import { resolveHood, reverseHood } from '@hoodag/sdk';
const addr = await resolveHood('robin.hood');
// '0x45aa14…'
const { name, verified } = await reverseHood(addr);
// { name: 'robin.hood', verified: true }Same ABIs as ENS — point any ENS SDK at registry 0x3E717dc8… on chain 4663 and it just works.
No dependencies at all? One eth_call to the UniversalResolver does it — resolve(string) is selector 0x461a4478, reverse(address) is 0xe30bd740. See llms-full.txt for the raw request.
The @hoodag/sdk package wraps resolution so you don't hand-encode calldata. Zero dependencies (uses global fetch, browser & Node 18+), with optional viem helpers.
npm install @hoodag/sdk
import { resolveHood, reverseHood, resolveTextHood } from '@hoodag/sdk';
const addr = await resolveHood('robin.hood'); // '0x45aa14…' | null
const { name, verified } = await reverseHood(addr); // { name:'robin.hood', verified:true }
const x = await resolveTextHood('robin.hood', 'com.twitter');Every function takes an optional rpcUrl as its last argument if you run your own node.
AI agents — Claude, Cursor, and any Model Context Protocol client — can resolve .hood names as first-class tools. All calls are read-only: no keys, no writes. Connect either way:
1 · Hosted (over URL, nothing to install)
Point any Streamable-HTTP MCP client (e.g. Cursor) at the endpoint:
{
"mcpServers": {
"hood": { "url": "https://www.hood.ag/api/mcp" }
}
}For stdio-only clients (Claude Desktop), bridge the URL with mcp-remote:
{
"mcpServers": {
"hood": { "command": "npx", "args": ["-y", "mcp-remote", "https://www.hood.ag/api/mcp"] }
}
}2 · Local (npm package)
npx @hoodag/mcp
Register it in your client (Claude Desktop / Claude Code .mcp.json, or Cursor .cursor/mcp.json):
{
"mcpServers": {
"hood": { "command": "npx", "args": ["-y", "@hoodag/mcp"] }
}
}Either way the agent gets these tools:
For agents that just read the web, hood. publishes a machine-readable overview at /llms.txt (concise) and /llms-full.txt (full context: contracts, ABIs, selectors, registration model). Both are linked from robots.txt and are the fastest way for an LLM to learn how to resolve .hood without reading the whole site.