Contract Naming

Premm.eth · February 26, 2026, 3:48am

Fine with me. Can you make a PR for:

ensips/contract-self-naming.md

contract-self-naming

---
title: Contract Self-Naming
description: A standard for contracts to declare their own reverse names using ERC-8042 Diamond Storage
contributors:
  - premm.eth, raffy.eth
ensip:
  created: "2025-11-23"
  status: draft
---

# ENSIP-X: Contract Self-Naming

## Abstract

This ENSIP extends ENSIP-19 to enable contracts to declare their own reverse names using ERC-8042 Diamond Storage. By storing a namehash of the reverse name in a known storage location, contracts can self-declare their ENS name. Any account can then register this name using the reverse registrar on L1, or using an L2 reverse registrar. This enables trustless, permissionless reverse name registration for contracts without requiring the contract deployer to perform additional registration steps.

## Motivation

Current reverse name registration requires the contract owner (when there is one) to perform a separate transaction to set the reverse name after deployment. Alternatively, the contract can make a custom external call in the constructor. This ENSIP enables contracts to declare their reverse ENS name during deployment using ERC-8042 Diamond Storage with predictable storage locations. Any account can then trustlessly verify the declaration and permissionlessly register the contract's reverse name in the registrar, removing the burden from contract deployers.

This file has been truncated. show original