Initial ENS resolver

[barlock]

Overview

This is the foundational part of the architecture (#1). It's simply a smart contract that follows the ENS abi with some added features specifically for hyperlane.

Reference

Resolver reference implementation

Acceptance

• Resolver adheres to EIP 1577 - contentHash field
• ens records resolve to the contentHash field as an ipfs location /ipfs/Qm...
• contract keeps track of every website revision
• contract defines aliases which map to revisions
• contract defines rev.0 as a dummy website for grins 😁
• smart contract always resolves the ipfs location of the latest alias
• contract automatically updates the latest alias to be the last added revision (the largest int)

Tasks

• Modify reference contract with described features
• Ensure coverage and linting

Assumptions

• Migrations will be done with truffle, cli comes later
• Alias swapping and user defined aliases will be handled later, this is more of a POC to test the whole thing e2e