@csvensson
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 👇
1 reply
0 recast
0 reaction