Era Name Service

Ditch long hexadecimal strings when moving value on zkSync Era. With Era Name Service, you register a clear, memorable handle and point it to your zkSync address in a few clicks. Start by searching an available name, confirm the on-chain registration, then set it as your primary entry so wallets and apps can look you up. From there, share your handle anywhere you would normally paste an address. If you rotate wallets, just update the record—your handle stays the same and your contacts don’t need to learn a new string.

Use it for everyday transactions: request funds from friends, add your handle to an invoice, or post it in your profile so supporters can tip you. Before sending, type a recipient’s handle instead of a hash and let resolution fetch the destination address. Double-check the resolved address preview, then confirm the transfer. This flow reduces copy-paste errors, speeds up checkout in dApps, and makes recurring payments simpler. For extra safety, save frequently used handles in your wallet’s address book and rely on resolved previews to avoid look‑alikes.

For teams and operations, standardize payouts with shared naming conventions. Assign distinct handles for payroll, grants, and vendor disbursements, and keep a single internal list of recipients by handle. When a contributor changes their wallet, they update their handle’s target once; your payout spreadsheets and scripts don’t change. During audits, match transfers by handle and resolved address to produce clear, human-readable records. If you manage community distributions or rebates, collect handles from participants and resolve them in batch before submission, cutting down on manual address validation.

Developers can integrate resolution directly into forms and transaction flows. Accept a handle anywhere you accept a zkSync address, resolve it to an address on submit, and show the user a confirmation of the resolved target. Add a reverse check to display a connected wallet’s primary handle in headers and receipts. Cache results briefly for performance, but always resolve before signing to catch updates. Validate input formatting, provide a plain-address fallback, and warn users if a handle resolves to a new address since their last interaction. These small UI touches make identity clearer, reduce failed transfers, and improve trust across your app’s payment, minting, and withdrawal experiences.