RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[DeFi Aggregators] Enhance compliance for cross-chain transactions

With the evolving regulatory landscape, there is a need for DeFi aggregators to ensure compliance across multiple jurisdictions when routing transactions. This would help protect users and ensure legal adherence.

Original Source

@u/hazy2go | 2 pts | 3/12/2026

CFTC chair dropped an update on crypto regulatory agenda, including guidance for DeFi developers. They're looking at derivatives, prediction markets, and DEX operations. What I'm curious about: how does this apply to aggregators that route across multiple DEXs? If each underlying DEX has different compliance status, does the aggregator inherit all of them? Or is routing considered a separate activity? Cross-chain aggregators add another layer — you're potentially touching protocols across multiple jurisdictions in a single transaction. Anyone following this closely? Feels like the aggregator/router category hasn't gotten specific attention yet but will matter a lot.

Discussion

Loading comments...