Ethereum

GM!

Seriously, users have no idea what they're interacting with when all they have is a hex contract address.

There are effectively two types of #ENS name you can have for a smart contract using @ensdomains — a primary name and a forward resolving name.

TLDR; you should always set the ENS primary name if you can. To understand why, keep reading.👀

A primary name is what you should have, this is where you have an ENS name that resolves to an address, and the address resolves back to the ENS name.

E.g. For our @enscribe #smartcontracts, we have two records:

- Forward resolving name: http://v0.app.enscribe.eth -> 0xD14360D477EF49182B5141952FE67b007688725A
- Reverse resolving name: 0xD14360D477EF49182B5141952FE67b007688725A -> http://v0.app.enscribe.eth

This means that http://v0.app.enscribe.eth is the primary name for 0xD14360D477EF49182B5141952FE67b007688725A, and you can see this in the Enscribe App at https://app.enscribe.xyz/explore/1/0xD14360D477EF49182B5141952FE67b007688725A.

ctd 👇

Your web3 username | Join the chat in /ens

Learn more: ens.domains | Register: app.ens.domains

Fixing #Ethereum #UX one #smartcontract at a time. 🔨 Easily name your smart contracts with #ENS names at https://app.enscribe.xyz🌟

Unfortunately, it's not always possible to set primary names, so in some cases you can only have the forward resolving name, which would be the first record in the above.

E.g.

- http://v0.app.enscribe.eth -> 0xD14360D477EF49182B5141952FE67b007688725A

The challenge with this is that apps typically present users with a contract address, so if a primary name is not set, there's no way for infrastructure such as a wallet to infer the ENS name from the wallet address alone.

This is why primary names are so important for ENS names. But as they typically require an additional transaction to create, they are often overlooked by ENS owners.

This is especially acute with smart contracts, as historically it required interacting manually with ENS smart contracts on Etherscan to accomplish.

Enscribe does fix this, but not all smart contracts can have their primary names set. For more on why this is check out https://enscribe.xyz/docs/introduction/naming-contracts.

ctd 👇

On a mission to fix #Ethereum #UX @enscribe ⛓️🔎 Founder @chainlens web3labs 📘 Author http://amzn.to/3DO4ZL5 & #Web3j ⛏

With Enscribe, we want you to name your contract, regardless of if a primary name can be set or just a forward resolving record only. Some name is better than no-name.

As an aside, with DNS, where people  set forward resolving DNS names, which map to an IP address. It is possible to set reverse DNS records too, using the DNS PTR record which you can read more about at https://cloudflare.com/en-gb/learning/dns/dns-records/dns-ptr-record/.

DNS is typically used to find websites and apps from a domain name, with ENS we use it in a similar way for mapping human-readable names to wallet addresses. 

However, we also want to use ENS for smart contracts, and they are typically used via wallets which need to find an ENS name from a contract address, which is why primary names are so important for increasing trust and #UX for users.

Hence we need to ensure primary names can flourish for smart contracts to fulfil our mission of making #Ethereum the safest decentralised web3# ecosystem for users.