@ensdomains/ens-contracts

ENS

For documentation of the ENS system, see docs.ens.domains.

npm package

This repo doubles as an npm package with the compiled JSON contracts

import {
  BaseRegistrar,
  BaseRegistrarImplementation,
  BulkRenewal,
  ENS,
  ENSRegistry,
  ENSRegistryWithFallback,
  ETHRegistrarController,
  FIFSRegistrar,
  LinearPremiumPriceOracle,
  PriceOracle,
  PublicResolver,
  Resolver,
  ReverseRegistrar,
  StablePriceOracle,
  TestRegistrar,
} from '@ensdomains/ens-contracts'

Importing from solidity

// Registry
import '@ensdomains/ens-contracts/contracts/registry/ENS.sol';
import '@ensdomains/ens-contracts/contracts/registry/ENSRegistry.sol';
import '@ensdomains/ens-contracts/contracts/registry/ENSRegistryWithFallback.sol';
import '@ensdomains/ens-contracts/contracts/registry/ReverseRegistrar.sol';
import '@ensdomains/ens-contracts/contracts/registry/TestRegistrar.sol';
// EthRegistrar
import '@ensdomains/ens-contracts/contracts/ethregistrar/BaseRegistrar.sol';
import '@ensdomains/ens-contracts/contracts/ethregistrar/BaseRegistrarImplementation.sol';
import '@ensdomains/ens-contracts/contracts/ethregistrar/BulkRenewal.sol';
import '@ensdomains/ens-contracts/contracts/ethregistrar/ETHRegistrarController.sol';
import '@ensdomains/ens-contracts/contracts/ethregistrar/LinearPremiumPriceOracle.sol';
import '@ensdomains/ens-contracts/contracts/ethregistrar/PriceOracle.sol';
import '@ensdomains/ens-contracts/contracts/ethregistrar/StablePriceOracle.sol';
// Resolvers
import '@ensdomains/ens-contracts/contracts/resolvers/PublicResolver.sol';
import '@ensdomains/ens-contracts/contracts/resolvers/Resolver.sol';

Accessing to binary file.

If your environment does not have compiler, you can access to the raw hardhat artifacts files at node_modules/@ensdomains/ens-contracts/artifacts/contracts/${modName}/${contractName}.sol/${contractName}.json

Contracts

Registry

The ENS registry is the core contract that lies at the heart of ENS resolution. All ENS lookups start by querying the registry. The registry maintains a list of domains, recording the owner, resolver, and TTL for each, and allows the owner of a domain to make changes to that data. It also includes some generic registrars.

ENS.sol

Interface of the ENS Registry.

ENSRegistry

Implementation of the ENS Registry, the central contract used to look up resolvers and owners for domains.

ENSRegistryWithFallback

The new implementation of the ENS Registry after the 2020 ENS Registry Migration.

FIFSRegistrar

Implementation of a simple first-in-first-served registrar, which issues (sub-)domains to the first account to request them.

ReverseRegistrar

Implementation of the reverse registrar responsible for managing reverse resolution via the .addr.reverse special-purpose TLD.

TestRegistrar

Implementation of the .test registrar facilitates easy testing of ENS on the Ethereum test networks. Currently deployed on Ropsten network, it provides functionality to instantly claim a domain for test purposes, which expires 28 days after it was claimed.

EthRegistrar

Implements an ENS registrar intended for the .eth TLD.

These contracts were audited by ConsenSys Diligence; the audit report is available here.

BaseRegistrar

BaseRegistrar is the contract that owns the TLD in the ENS registry. This contract implements a minimal set of functionality:

• The owner of the registrar may add and remove controllers.
• Controllers may register new domains and extend the expiry of (renew) existing domains. They can not change the ownership or reduce the expiration time of existing domains.
• Name owners may transfer ownership to another address.
• Name owners may reclaim ownership in the ENS registry if they have lost it.
• Owners of names in the interim registrar may transfer them to the new registrar, during the 1 year transition period. When they do so, their deposit is returned to them in its entirety.

This separation of concerns provides name owners strong guarantees over continued ownership of their existing names, while still permitting innovation and change in the way names are registered and renewed via the controller mechanism.

EthRegistrarController

EthRegistrarController is the first implementation of a registration controller for the new registrar. This contract implements the following functionality:

• The owner of the registrar may set a price oracle contract, which determines the cost of registrations and renewals based on the name and the desired registration or renewal duration.
• The owner of the registrar may withdraw any collected funds to their account.
• Users can register new names using a commit/reveal process and by paying the appropriate registration fee.
• Users can renew a name by paying the appropriate fee. Any user may renew a domain, not just the name's owner.

The commit/reveal process is used to avoid frontrunning, and operates as follows:

• A user commits to a hash, the preimage of which contains the name to be registered and a secret value.
• After a minimum delay period and before the commitment expires, the user calls the register function with the name to register and the secret value from the commitment. If a valid commitment is found and the other preconditions are met, the name is registered.

The minimum delay and expiry for commitments exist to prevent miners or other users from effectively frontrunning registrations.

SimplePriceOracle

SimplePriceOracle is a trivial implementation of the pricing oracle for the EthRegistrarController that always returns a fixed price per domain per year, determined by the contract owner.

StablePriceOracle

StablePriceOracle is a price oracle implementation that allows the contract owner to specify pricing based on the length of a name, and uses a fiat currency oracle to set a fixed price in fiat per name.

Resolvers

Resolver implements a general-purpose ENS resolver that is suitable for most standard ENS use cases. The public resolver permits updates to ENS records by the owner of the corresponding name.

PublicResolver includes the following profiles that implements different EIPs.

• ABIResolver = EIP 205 - ABI support (ABI()).
• AddrResolver = EIP 137 - Contract address interface. EIP 2304 - Multicoin support (addr()).
• ContentHashResolver = EIP 1577 - Content hash support (contenthash()).
• InterfaceResolver = EIP 165 - Interface Detection (supportsInterface()).
• NameResolver = EIP 181 - Reverse resolution (name()).
• PubkeyResolver = EIP 619 - SECP256k1 public keys (pubkey()).
• TextResolver = EIP 634 - Text records (text()).
• DNSResolver = Experimental support is available for hosting DNS domains on the Ethereum blockchain via ENS. The more detail is on the old ENS doc.

Developer guide

Prettier pre-commit hook

This repo runs a husky precommit to prettify all contract files to keep them consistent. Add new folder/files to prettier format script in package.json. If you need to add other tasks to the pre-commit script, add them to .husky/pre-commit

How to setup

git clone https://github.com/ensdomains/ens-contracts
cd ens-contracts
bun i

How to run tests

bun run test

How to publish

bun run pub

L2 contracts

The only contract in this repo deployed on L2s is L2ReverseRegistrar (and its dependency UniversalSigValidator).

Anyone can deploy this contract onto any L2, however the contract has functionality which allows using one signature across multiple L2s. Given this functionality, and EIP-191's requirement for the intended validator address in the signature, the contract address needs to stay the same between all networks.

To allow for a unified contract address, a Safe and a helper CREATE3 contract are used in the deployment process. The contract can be deployed outside the process, but it means that it will lack the multi-chain signature functionality.

Testnet Safe address: 0x343431e9CEb7C19cC8d3eA0EE231bfF82B584910 Mainnet Safe address: 0x353530FE74098903728Ddb66Ecdb70f52e568eC1

Release flow

Deployment

When readying a new deployment of certain contracts, bump the deploy script version number to the appropriate new version. Doing this ensures that the new deployment script will run for each network.

Deployment scripts can be run for any specified network found in the config, with the following:

bun hh --network <network_name> deploy

Only scripts that haven't been run on the specified network before will be run.

Deployment testing

To test deploying contracts and the functionality of them after deployment, there are two basic paths for forking:

• Run an anvil fork, useful for testing locally and iterating. (anvil --fork-url <url>)
• Use a Tenderly Virtual TestNet, useful as a staging environment.

When access to the owner account is available (testnet only - owner on mainnet is the DAO), you can deploy straight to the fork by replacing the forked network's URL in the hardhat config with your RPC:

const config = {
  // ... existing config
  networks: {
    targetNetwork: {
      // ... other network config
      url: 'tenderly-or-anvil-url-here',
    },
  },
}

Without access to the owner account, you can deploy via the impersonation script, which makes impersonated accounts from an external node available to hardhat.

./scripts/deploy-with-impersonation.ts --rpc-url <url> --accounts <addr1> [addr2 ...] [--tags <tags>]

# Testnet usage
./scripts/deploy-with-impersonation.ts --rpc-url <url> --accounts 0x0F32b753aFc8ABad9Ca6fE589F707755f4df2353

# Mainnet usage
./scripts/deploy-with-impersonation.ts --rpc-url <url> --accounts 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7

Release flow

• Create a feature branch from staging branch
• Make code updates
• Ensure you are synced up with staging
• Code should now be in a state where you think it can be deployed to production
• Create a "Release Candidate" release on GitHub. This will be of the form v1.2.3-RC0. This tagged commit is now subject to our bug bounty.
• Have the tagged commit audited if necessary
• If changes are required, make the changes and then once ready for review create another GitHub release with an incremented RC value v1.2.3-RC0 -> v.1.2.3-RC1. Repeat as necessary.
• Deploy to testnet. Open a pull request to merge the deploy artifacts into the feature branch. Create GitHub release of the form v1.2.3-testnet from the commit that has the new deployment artifacts.
• Get someone to review and approve the deployment and then merge. You now MUST merge this branch into staging branch.
• If any further changes are needed, you can either make them on the existing feature branch that is in sync or create a new branch, and follow steps 1 -> 9. Repeat as necessary.
• Make a deployment to ethereum mainnet from staging. Create a GitHub release of the form v1.2.3 from the commit that has the new deployment artifacts.
• Open a PR to merge into main. Have it reviewed and merged.

Cherry-picked release flow

Certain changes can be released in isolation via cherry-picking, although ideally we would always release from staging.

• Create a new branch from mainnet.
• Cherry-pick from staging into new branch.
• Deploy to ethereum mainnet, tag the commit that has deployment artifacts and create a release.
• Merge into mainnet.

Emergency release process

• Branch from main, make fixes, deploy to testnet (can skip), deploy to mainnet
• Merge changes back into main and staging immediately after deploy
• Create GitHub releases, if you didn't deploy to testnet in step 1, do it now

Notes

• Deployed code should always match source code in mainnet releases. This may not be the case for staging.
• staging branch and main branch should start in sync
• staging is intended to be a practice main. Only code that is intended to be released to main can be merged to staging. Consequently:
  • Feature branches will be long-lived
  • Feature branches must be kept in sync with staging
  • Audits are conducted on feature branches
• All code that is on staging and main should be deployed to testnet and mainnet respectively i.e. these branches should not have any undeployed code
• It is preferable to not edit the same file on different feature branches.
• Code on staging and main will always be a subset of what is deployed, as smart contracts cannot be undeployed.
• Release candidates, staging and main branch are subject to our bug bounty
• Releases follow semantic versioning and releases should contain a description of changes with developers being the intended audience