Give your smart contracts a real identity

Leading ecosystem projects including Nouns DAO, Liquity, Cork Protocol, and Giveth use Enscribe to name their contract infrastructure using ENS.

Smart contracts on Ethereum are still identified by hex addresses. That's fine for machines, but not people. ENS can name smart contracts, but most teams never operationalise it at protocol scale. Enscribe gives you the infrastructure to name and manage your contracts using ENS, ensuring your protocol's identity is onchain, not buried in stale documentation.

We support networks where ENS is deployed, including Ethereum, Base, Linea, Arbitrum, Optimism, and Scroll.

Yes. If you already have deployed contracts, you can assign ENS names through Enscribe using your own ENS names or one of ours.

Enscribe makes it simple to attach ENS names to smart contracts. You can use the Enscribe App to deploy and name a smart contract atomically in a single transaction. For existing contracts, set ENS subnames to resolve to deployed addresses. Names are written onchain and can be verified by anyone using ENS resolution.

For established protocols, naming existing onchain infrastructure takes planning. A Contract Naming Audit is a structured review the Enscribe team undertakes of your deployed contracts and operational wallets. We create a consistent onchain naming scheme using ENS. The output is a complete onchain directory of your protocol that's easier to verify and maintain over time.

No. Enscribe uses the manager role for an ENS name. You retain full ownership and can override or delete any actions performed by the service at any time.

Just like with domain names, if your ENS name lapses and someone else takes ownership of it, the subnames issued by Enscribe are no longer valid. We recommend keeping your ENS names renewed.