ENS Contract Naming Standard or Nomenclature

šŸŒ± ENS Ecosystem
1

Hello frens, Iā€™m Igor Co-founder of Onthis (onthis.xyz).

Some quick context on who we are and what we do and then Iā€™ll move onto the ENS Contract naming standard.

Mission: Make onchain actions simple and safe.

Product: Shortcuts

Send ETH to human-readable contracts to bridge, swap, stake, mint, and more directly from your wallet.

Examples (Send ETH from Mainnet)

  • toArbitrum.eth: Instant bridge to Arbitrum.
  • toBase.eth: Instant bridge to Base.
  • stake.onLido.eth: Earn yield via Lido + Curve.
  • ETHtoUSDC.eth: Swap ETH for USDC.

We now have 40+ Shortcuts, you can check them out here: Discover Shortcuts ā€¢ onthis.xyz.

ENS Domain Shortcut Nomenclature:

How do we create a naming system that works well today and is future-proof?

Step 1: Define Core Categories

  • DeFi Actions: buy/sell (swap), stake/unstake, mint/burn, borrow/lend
  • Company/Protocol Names
  • L2 or Alt Chain (where are the funds going? This is separate from subdomain resolvers of L2s e.g. op.eth, poly.eth, base.eth, etcā€¦)
  • Assets accepted

Iā€™ve created a spreadsheet that attempts to enumerate all the possible scenarios. Click here to view.

Step 2: Establish Naming Conventions

  • Primary Domain (name.eth)
  • Subdomain (subdomain.name.eth)
  • Subdomain of Subdomain (subdomain.subdomain.name.eth)

Step 3: Pattern Creation

Option 1

[action].[company].eth

stake.onLido.eth

[asset].[action].[company].eth

stETH.stake.onlido.eth

Option 2

[company].[action].eth

lido.stake.eth

[asset].[company].[action].eth
stETH.lido.stake.eth

The advantage of Option 1 is that it is more natural to read type stake.onlido.eth (verb->company)

The advantage of Option 2 is that you can utilize subdomains to name all the companies without issue e.g. coinbase, lido, etc.

Step 4: Evolution Proofing

How do we ensure that the naming convention stands the test of time? It must work with prompt-based automation tools and even voice-to-text.

Thank you for your thoughts and contributions to this conversation, Iā€™ll be joining the eco ENS call Jan 25th and would love to discuss in more detail then.

5 Likes
2

how would you select how much to send?

3

You send any ETH amount.

For example, if you wanted to bridge toarbitrum.eth, any ETH amount you send will auto-bridge and appear on your destination chain in your wallet (i.e MetaMask).

1 Like
4

so essentially the name becomes a proxy contract in itself?

5

Yes thatā€™s correct!

6

Hi Igor,

What is it that you are proposing or querying here? Your product is cool. If I recall correctly you built it at a hackathon and previously demoed it?

Regarding standardisationā€¦ do you own the 2LD names that you want to base this standardisation on? And what do you mean by standardisation in this case? It seems like a cool business idea for you/others to build out and monetise as you see fitā€¦

1 Like
7

I think itā€™s a really interesting idea!

1 Like
8

Thanks for the response Thomas, currently we do own the 2LD but that doesnā€™t have to be the case in the future.

another approach is to base the ā€œrootā€ 2LD off of ā€œonthis.ethā€ and use subdomains to create a directory of all available actions you can take with a ā€œConnectionless/Headlessā€ dapp.

I was gauging the thoughts from you guys on what might be an intuitive approach here. This Thursday Iā€™ll join the ENS community call to expand on this idea.