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), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[x402] Enable EIP-4337 smart wallet / UserOperation support

Proposes an extension to the x402 protocol to add first-class support for smart contract wallets (account abstraction) and EIP-4337 style 'UserOperation's, enabling clients using smart wallets to generate and submit payment payloads.

Original Source

@@takasaki404 | 5 pts | 11/13/2025

# Enable EIP-4337 Smart Wallet / UserOperation Support in x402 Protocol ## **1. Summary** We propose an extension to the x402 protocol that adds first-class support for smart contract wallets (account abstraction) and EIP-4337 style `UserOperation`s. This enhancement enables clients using smart wallets (rather than simple EOAs) to generate and submit payment payloads conforming to x402 flows, including verification and settlement of UserOperations, thus making x402 compatible with next-gen wallet models and on-chain UX patterns. ## **2. Motivation** Currently, x402 supports payments via “wallet signing” of a payment payload, typically by an externally-owned account (EOA) transferring tokens via a facilitator. While effective, this model does not fully support smart contract wallets, meta-transactions, account abstraction flows, or bundler/Paymaster models. With the rise of smart wallets (e.g., those created via SDKs like Alchemy Account Kit and Coinbase Smart Accounts) and the bro

Discussion

Loading comments...