How do I integrate ENS in a DAPP? Understand the three main methods

The original title: "the best practices of introducing | integrated ENS"

Original source: makoto_inoue

A Jian

More than 200 services now have ENS integrated, so this article wanted to show how dApps can take advantage of ENS.

In our documentation, we list three main ways to integrate ENS. We're going to use the same statement here.

Parsing the ENS domain name

The first step to supporting ENS in your application is to make your application understand the ENS domain name and support it everywhere you need to use the address. This is especially useful for wallet services.

See the parsing results at meyetherwallet.com

Etherscan is one of the most commonly used Ethereum related sites where you can review all your transactions and account balances. In addition to searching for ENS domain names, a lesser-known feature is that their URLs also support ENS domain names, so you can just type "/address/matoken.eth" into the address bar.

When someone asks me for my Ethereum address, I always give them my ENS domain name, but not everyone knows what ENS is and how to use it. If you have multiple Ethereum addresses, giving the full Etherescan URL with your domain name is a good way to bridge the knowledge gap. It's easy for you to type in or copy a URL with your domain name, you don't have to keep track of which address is used for what, and the people you interact with don't need to know what ENS is.

Reverse DNS

The second level of ENS integration is reverse resolution, which displays the ENS domain name where your application displays the address.

This feature can be implemented on three levels.

Display the ENS name when the user is logged in

Uniswap will display your ENS name as if it were your user name. This is another example of how ENS can help users distinguish between multiple Ethereum addresses, as it is clear which account you are using.

Shows the ENS name of the asset owner/creator

This feature is closely related to the NFT market. Each NFT marketplace has its own user name system, but your Foundation user name will not be displayed on other NFT platforms such as OpenSea and Rarible.

But the ENS name displayed on the KnowNorigin platform can also be displayed on the OpenSea. In other words, the ENS name is a portable user name.

Not all NFT platforms do this, however, but it can be very useful for NFT artists who need to build their brand and identity on the chain.

If you're playing on an NFT platform that doesn't already have ENS integrated, suggest that they integrate ENS, because that's your autonomous identity! No ENS, no names on the chain!

Display the ENS name in a series of Ethereum addresses

The list of Ethereum addresses could be a history of the transaction, or a list of asset owners, a list of DAO members, a list of voters, and so on.

Snapshot gives preference to the user name chosen by the user on their platform when displaying the voting results, but returns the ENS name if such a dedicated user name is not available.

Let the user name it himself

The final step in the comprehensive ENS integration is to help users associate the ENS domain name with the resources that your application creates or manages. It can take two forms:

Domain name registration

By giving your product an ENS name and making it easy for users to register subdomains, your users will be able to name the resources created in your dApp.

Many wallet services such as Argent and Authereum have helped users create subdomains under their product domain names, but the recent spike in gas/eth prices has made the whole thing unsustainable as they have to pay for gas for their users (we are working on the L2 specification to ease this difficulty). Status, instead of giving users a domain name for free, sells it to users for SNT tokens.

A more novel approach comes from Decentraland. Not only do they distribute subdomains under the main dcl.eth domain, but they also convert them into NFT, like.eth top-level domains, which users can buy and sell on secondary markets such as OpenSea.

Domain name update

Give users an easy way to point their existing domain names to resources created in your application so they can reassign their domain names.

Snapshot also makes use of ENS in this way, for examplehttps://snapshot.org/#/gnosis.eth.

They use ENS plain text recording wherever you specify an IPFS endpoint.

Others: Cross-chain support

Although we already support resolution of 100 blockchain address types, we still need the wallet service to integrate our functionality so that users can use it.

TrustWallet is one of the first multi-chain specific wallets to support us, so you can send BNB to vikmeup.eth.

Another use of ENS support is when your application is deployed on side chains /L2.

Nifty. Ink is an NFT doodle service that is deployed on the XDAI side chain, and they have integrated ENS.

We're working on L2, and the nice thing about this architecture is that anyone can look up the ENS name on L1, but update the ENS record on L2 to save gas.

Although we have not yet found an easy way to update ENS records from the side chain, the ability to read ENS information directly on L1 is a good way to integrate.

conclusion

We showed several examples of dApps that integrate ENS to provide a good experience for end users. Although it is difficult to support all three levels, all wallets should support "1. Resolves ENS domain name", and all DeFi projects should support "2.1 Display ENS name when user is logged in", All NFT platforms should support "2.2 Display the ENS name of the asset owner/creator".

Source link:medium.com

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia