Snip3d

Screenshots

Problem Statement

ENS is your onchain identity to navigate the ETH ecosystem. But there's more to it than just your '.eth' domain and token value that it's predominantly used for today.Start your ENS journey. Get your first ENS.We've enabled a social bio layer to add other aspects of your social presence (GitHub, Discord, Telegram, Twitter, PFP etc..) and connect that your ENS handle to truly represent who you are across all spectrum. 'Think linktree with just your ENS domain'.NLQL layer. Use natural language queries to auto generate categories of ENS domains and view realtime trends.Trade analytics for verified and unverified categories.Buy/Sell/Trade ENS across integrated marketplaces.Snipe your favourite ENS domains that are about to expire.Get notified on activity, trends and availability around ENS domains of your choice over Telegram.Discover Utility layer built for the ENS holders.

Solution

No proper documentation and/or implementation around EIP-634 (https://eips.ethereum.org/EIPS/eip-634). NLQL has its own set of challenges that come with any query layer. No support for regex patterns through Subgraph. Integrating multiple marketplaces is a pain.