Fun fact: Between 2020 and 2021 the number of registered ENS domains doubled…so far this year, the number of registered ENS domains has increased nearly 300% from 2021, and it’s only July.
Today, we’re excited to announce a highly requested feature: ENS resolution! Now you can seamlessly add support for ENS domains to your product to provide an even more user-friendly experience to the growing number of people using ENS domains.
Mnemonic’s API now accepts ENS names directly as wallet or contract addresses. In addition, we’ve added 4 new endpoints to resolve current and historical ENS domains from their connected wallet addresses (and vice-versa).
Before we jump into the what’s and how’s of our new ENS resolution capabilities, let’s address why ENS resolution is critical for your Web3 application.
About ENS domains
But what is ENS and why does it matter to Web3 builders?
ENS, or Ethereum Name Service, is a distributed, open, and extensible naming system based on the Ethereum blockchain. ENS allows you to map human-readable names like vitalik.eth to machine-readable identifiers such as Ethereum addresses, other cryptocurrency addresses, content hashes, and metadata (similar to DNS).
ENS domains make interacting with Web3 applications easier for end users, and as ENS domains become more widely used in the Web3 space, native support for them is considered a table stakes capability by many builders creating Web3 experiences.
Bringing native ENS support to your product
Mnemonic’s ENS resolution capabilities ensure builders can seamlessly support ENS domains within their products without the extra legwork of interacting with ENS to do reverse and forward lookups.
The following API endpoints now support ENS domain resolution:
- Contract Details
- (New) Transfer Insights
- Transfers Between Addresses
- Transfers By Address
- Transfers by Contract
- Transfers By Tx Hash
- Transfers by Token
- NFTs by the Contract
- NFTs by the Minter (for both minter_address + contract_address)
- NFTs by the Owner (for both owner_address + contract_address)
- Token Metadata (for contract_address)
- NFT Owners
- List of current owners by contract
- Owner count by contract
- Token supply by contract
- Prices by contract
- Sales volume by contract
Previously, these endpoints only accepted wallet addresses or contract addresses, so if you wanted to support ENS, you needed to get the ENS name, make a call to ENS to look up the name and return its corresponding wallet or contract address before calling our API. Now, you can get all the information you need directly via Mnemonic’s API, meaning you can add native support for ENS names to your product with ease.
ENS resolution API
In addition to bringing ENS resolution to existing endpoints, we’ve added 4 new endpoints for forward and reverse lookup of current and historical ENS records. You can now retrieve current ownership details with the GetEntityByName (forward lookup) and GetEntityByAddress (reverse lookup) endpoints.
In situations where you need historical records for a given name or wallet address, the GetHistoricalEntitiesByName and GetHistoricalEntitesByAddress endpoints retrieve the full history of the ENS names associated with a wallet address (or vice-versa). This enables ENS names to be used for use cases that require an accurate historical view of past and current ENS name assignments.
Let's take a quick look at an example query and response. We'll use GetHistoricalEntitiesByAddress to look up the ENS record details for a wallet address. Below is an example request and its response:
Ready to give it a try?
Whether you’re keen to add support for ENS to your product right now, or simply just want to explore the possibilities, here are a few resources to get you started.
- API reference for new ENS resolution endpoints
- Tutorial: How to lookup the wallet address for a given ENS name (Reverse Lookup)
- Tutorial: How to look up the ENS name(s) for a given wallet address (Forward Lookup)
🤗 We love feedback from our community!
ENS resolution is yet another capability we’ve added based on feedback from our community. Have more ideas for us? We’d love to hear them so we can continue improving our product.