What is Lime.dev?
Lime.dev is Web3 identity infrastructure built on the Ethereum Name Service (ENS). We run a hybrid ENS resolver that issues free, ENS-compatible subnames—no gas, no registration fees—while offering enterprise-grade infrastructure for companies that need to onboard users at scale.
For users: Claim yourname.lime.dev in seconds. Sign once, no transaction.
For companies: API-driven subname issuance, namespace management, zero-gas onboarding for L2s, wallets, exchanges, and Web3 platforms.
Why Lime Exists
Human-readable names are essential for Web3 adoption. Raw Ethereum addresses (0x1234...) are unusable for mainstream UX. ENS solved this with names like alice.eth, but the onchain-only model creates friction: every claim and update costs gas. Lime removes that friction by moving issuance and updates offchain, while keeping full ENS compatibility and optional onchain permanence.
How It Works: Hybrid vs Onchain
| Feature | Hybrid (Lime) | Onchain ENS |
|---|---|---|
| Claim & manage | Free, signature only | Registration fee + gas |
| Updates | EIP-712 signature, no gas | Gas per update |
| Renewal | None | Annual fee + gas |
| API updates | Yes | No |
| Onchain permanence | Optional, user choice | Required |
Resolution uses CCIP-Read (EIP-3668): the resolver contract reverts with an offchain lookup URL; the client fetches signed data and calls back. Offchain records are signed with EIP-712 and verified onchain. When you want a permanent record, you write it to Ethereum—gas applies only then.
What Lime Provides
Architecture
| Layer | Description |
|---|---|
| Issuance | Offchain subname issuance and record storage |
| Updates | EIP-712 signed updates (nonce + timestamp for replay protection) |
| Resolution | CCIP-Read (EIP-3668) gateway |
| Onchain | Optional onchain record publishing |
For Individuals
Free subnames — Claim yourname.lime.dev in seconds. Add addresses, text records, contenthash—all via signature. No gas until you explicitly write onchain.
For Enterprises
REST API — Namespace management, bulk subname issuance, identity lifecycle, spoofing protection. Use cases: L2 user onboarding, wallet usernames, exchange deposit addresses, DAO memberships. Projects can issue names for activities (e.g. rewards, campaigns) as a marketing tool. Projects can also assign names to their own wallets to simplify operations and user interactions.
How Lime Protects Users with ENS
Lime uses ENS resolution to protect users from address spoofing. Raw addresses are easy to confuse: a common fraud pattern is when users send funds to a legitimate address (e.g. an exchange or a friend), such as 0x2ff063db6ab14babe8d6aa1d2603657503971eb0. Fraudsters then send transactions from a similar-looking address, for example 0x2ff0639a2dcde90535a881f0906b02fa97971eb0. Users copying from transaction history may accidentally send a second payment to the wrong address.
Why users get tricked: Interface limits (truncation, small fonts) force users to copy addresses partially and only check the first and last characters—which spoofed addresses can match. Malware can also swap addresses in the clipboard when you paste. Human-readable names protect against both: you type or paste bob.lime.dev, not a hex string that can be silently replaced.
Compare the two addresses (matching prefix and suffix in green, differing middle part in red):
- Legitimate: 0x2ff063db6ab14babe8d6aa1d260365750397971eb0
- Spoofed: 0x2ff0639a2dcde90535a881f0906b02fa97971eb0
Lime leverages ENS to eliminate this risk. When you send to bob.lime.dev, the ENS resolver always returns the correct address—no copy-paste from history, no typos, no spoofing, no clipboard malware. Lime’s hybrid infrastructure lets individuals claim free names and lets enterprises (exchanges, wallets) issue names to users and bind them to deposit addresses: user123.exchange1.com or leon_bit.exchange2.xyz. Human-readable names, resolved via ENS, protect users from address confusion and fraud.
ENS Namespaces: First-Level and DNS Domains
Lime supports hybrid resolution for both ENS first-level names (name.eth) and traditional domains via the ENS DNS Registrar . Connect your existing domain (e.g. company.com) and issue ENS-compatible subnames (alice.company.com) without migrating to .eth. Light by default—offchain storage, gasless updates—with optional onchain fixation when permanence matters.
Next Steps
- Quick Start Guide — Claim your free ENS subname
- What is ENS? — ENS protocol overview
- Hybrid vs Onchain — When to use offchain vs onchain records