Enscribe
Launch App

Name Your Smart Contracts At Deployment

Enscribe's Contract Deployment Service assigns an ENS name at contract creation ensuring you can resolve it by name from day one

Launch AppDocumentation
Enscribe ENS integration illustration

Key Features

Enhanced Trust

Associate human-readable ENS names with smart contracts, boosting user confidence and transparency.

Automatic ENS Integration

Seamlessly create ENS records for smart contracts at deploy time, eliminating manual post-deployment steps.

Multi-chain Support

Deploy contracts to multiple ENS-supported chains with appropriate naming for each, expanding your reach.

Bring Your Own Name

Enscribe supports using your own ENS name or you can use one of our own.

You Own Your Contracts

Contracts deployed with Enscribe are owned by the deployment account not the service, ensuring you remain in control of your app contracts.

Third Party Integrations

We're going to be launching some neat third-party integrations soon to make using the Enscribe Contract Deployment Service event more seamless.

How It Works

Input

  • ENS subname for contract deployment
  • Contract bytecode to be deployed

Output

  • Deployed contract with ENS subname as primary name
  • Optional locked ENS subname record for enhanced security
Complex Contract Address
0x3e71bC0e1729c111dd3E6aaB923886d0A7FeD437
Human-Readable ENS Name
v5.contracts.enscribe.eth
Enscribe automatically creates and links ENS names to your smart contracts, making them more accessible and trustworthy for users.

Frequently Asked Questions

Ethereum has a thriving DApp ecosystem, but developers and users still rely on smart contract addresses to address contracts. ENS names can be used to name smart contracts, but few take advantage of this functionality. The Enscribe service changes this and enables developers to name their smart contracts at deploy time with no additional coding.
We support all networks that ENS is deployed to, including Ethereum, Base and Linea
When you deploy a contract using Enscribe it creates a new ENS subname you specify that resolves to the address of the newly deployed contract. Enscribe does this as an atomic transaction, so if contract deployment succeeds you will always have an ENS name you can refer to the contract with.
Enscribe caters for contracts that implement ERC-173: Contract Ownership Standard or the Ownable interface. However, you can use the service to issue names for already deployed contracts.
Whilst every effort has been made to ensure that our contracts cannot be exploited, we have yet to have them formally audited whilst we're in beta. The Enscribe service does require an ENS 2LD or subname with manager authority, but as long as you retain the Owner privilege, you can always delete subnames issued by the service.
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.
No! Enscribe uses the manager role for an ENS name, you retain full ownership of the ENS name and can choose to override or delete any actions performed by the service.

Eliminate Contract Addresses For Your Users

Join the growing community of developers using Enscribe to deploy their smart contracts, enhancing trust and transparency in their web3 apps.

Launch App

Join the growing community of developers using Enscribe to name their smart contracts