{"type": "project", "title": "Faster API for resolving ENS names and avatars for web3 projects", "logoImg": "bafkreibgiznmys6i7gtmtea7yasjmvty6fwf2ofc6twuwx76jarald3y5m", "website": "https://ensideas.com/about", "createdAt": 1673502520905, "userGithub": "holic", "credentials": {}, "description": "I've integrated ENS resolving into several projects now (both my own and as a contributor/collaborator), but found the standard approach of querying ENS contracts directly to be quite slow for most use cases, and can quickly eat up Alchemy/Infura node resources if you're not careful.\n\nTo help with this, I built an incredibly fast API (thanks to Cloudflare's edge caching) for resolving and reverse-resolving ENS names and addresses and avatars (30-50ms with a warm cache).\n\nAPI docs are here: https://ensideas.com/about\n\nAnd open source code here: https://github.com/holic/ens-ideas\n\nExamples:\nhttps://api.ensideas.com/ens/resolve/0xc9c022fcfebe730710ae93ca9247c5ec9d9236d0\nhttps://api.ensideas.com/ens/resolve/frolic.eth\n", "logoImgData": {}, "projectTwitter": "frolic"}
Faster API for resolving ENS names and avatars for web3 projects
I've integrated ENS resolving into several projects now (both my own and as a contributor/collaborator), but found the standard approach of querying ENS contracts directly to be quite slow for most use cases, and can quickly eat up Alchemy/Infura node resources if you're not careful.

To help with this, I built an incredibly fast API (thanks to Cloudflare's edge caching) for resolving and reverse-resolving ENS names and addresses and avatars (30-50ms with a warm cache).

API docs are here: https://ensideas.com/about

And open source code here: https://github.com/holic/ens-ideas

Examples:
https://api.ensideas.com/ens/resolve/0xc9c022fcfebe730710ae93ca9247c5ec9d9236d0
https://api.ensideas.com/ens/resolve/frolic.eth

Faster API for resolving ENS names and avatars for web3 projects