ENS Contract Naming Standard or Nomenclature

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





Option 2




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.


how would you select how much to send?

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

so essentially the name becomes a proxy contract in itself?

Yes that’s correct!

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

I think it’s a really interesting idea!

1 Like

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.