Writing a Registrar

Search…

Technical Documentation

Writing a Registrar

A registrar in ENS is simply any contract that owns a name, and allocates subdomains of it according to some set of rules defined in the contract code. A trivial first in first served contract is demonstrated below:
1
contract FIFSRegistrar {
2
    ENS ens;
3
    bytes32 rootNode;
4
​
5
    function FIFSRegistrar(address ensAddr, bytes32 node) {
6
        ens = ENS(ensAddr);
7
        rootNode = node;
8
    }
9
​
10
    function register(bytes32 subnode, address owner) {
11
        var node = sha3(rootNode, subnode);
12
        var currentOwner = ens.owner(node);
13
​
14
        if (currentOwner != 0 && currentOwner != msg.sender) throw;
15
​
16
        ens.setSubnodeOwner(rootNode, subnode, owner);
17
    }
18
}
Copied!
You may wish to set custom rules for the allocation of new names to your users; the rules you set are entirely up to you.
You should also bear in mind that as long as you retain ownership of the parent name - either directly or through another contract - your users have no guarantee that you will not take back ownership of their names and change what they resolve to. You may wish to consider committing ownership of the name to a contract that restricts your ability to control it. For an example of this, see ENSNow.

Contract Developer Guide - Previous

Writing a Resolver

Next - ENS Migration (February 2020)

Guide for DApp Developers

Last modified 3mo ago

Copy link

Edit on GitHub