BASENAMES

This repository contains code for minting and managing ENS subdomains on the Base network as base.eth subdomains.

It supports:

• Registering base.eth subdomains on Base natively
• Managing the name with a public resolver, allowing an owner or operator to set address records, text records, dns records, etc.
• ERC721 subdomain tokens (Opensea)

OVERVIEW

Basenames are a core onchain building block that enables anyone to establish their identity on Base by registering human-readable names for their address(es). They are a fully onchain solution which leverages ENS infrastructure deployed on Base.

CONTRACT ADDRESSES

Ethereum Mainnet

Base Mainnet

Sepolia

Base Sepolia

Functional Diagram

The system architecture can be functionally organized into three categories:

1. An L1 resolver enabling cross-chain resolution for the base.eth 2LD.
2. An ENS-like registry/registrar/resolver system deployed on Base enabling *.base.eth subdomains to be registered and managed.
3. An off-chain gateway for serving CCIP requests required to comply with ENSIP-10.

ARCHITECTURE

The core functionality of Base Usernames should look familiar to anyone that's looked under the hood at the ENS contracts. We implement a slimmed down fork of the ENS contracts here.

In addition to replicating the base behavior of the ENS protocol, we are offering a series of promotional discounts associcated with various Coinbase product integrations. As such, the Base Usernames Registrar Controller allows users to perform discounted registrations while passing along integration-specific validationData. Each discount leverages a common interface:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.23;

/// @title Discount Validator Interface
///
/// @notice Common interface which all Discount Validators must implement.
///         The logic specific to each integration must ultimately be consumable as the `bool` returned from
///         `isValidDiscountRegistration`.
interface IDiscountValidator {
    /// @notice Required implementation for compatibility with IDiscountValidator.
    ///
    /// @dev Each implementation will have unique requirements for the data necessary to perform
    ///     a meaningul validation. Implementations must describe here how to pack relevant `validationData`.
    ///     Ex: `bytes validationData = abi.encode(bytes32 key, bytes32[] proof)`
    ///
    /// @param claimer the discount claimer's address.
    /// @param validationData opaque bytes for performing the validation.
    ///
    /// @return `true` if the validation data provided is determined to be valid for the specified claimer, else `false`.
    function isValidDiscountRegistration(address claimer, bytes calldata validationData) external returns (bool);
}

The various implementations can be found in this directory.

Usage

Build

$ forge build

Test

$ forge test

Format

$ forge fmt

Gas Snapshots

$ forge snapshot

Help

$ forge --help
$ anvil --help
$ cast --help