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.

[BSV x402] Implement 'noSend' and abort on server rejection for custom x402 path

Addresses a 'phantom UTXO' issue in the custom x402 path by proposing to implement 'createAction({ noSend: true })' and aborting the transaction if the server rejects, preventing committed-but-unaccepted transactions from creating phantom change outputs.

Original Source

@@sgbett | 0 pts | 2d ago

## Problem Same phantom UTXO issue as #103, but in the custom X402 path (`defaultConstructProof` in `src/x402-fetch.ts`). `defaultConstructProof` calls `window.CWI.createAction()` with `noSend: false` (default), broadcasting immediately before the server confirms acceptance. If the server rejects, the wallet has phantom change outputs from a committed-but-unaccepted transaction. ## Approach Mirror the BRC-105 fix from #103: 1. `createAction({ noSend: true })` via `window.CWI` 2. Send proof to server via `X402-Proof` header 3. Server 200 → done 4. Server error → `window.CWI.abortAction({ reference: txid })` to release UTXOs `abortAction` is one of the 28 BRC-100 wallet methods, so any compliant wallet should support it. ## Context - #103 fixed this for the BRC-105 path (`Brc105Wallet`) - This is the general-purpose path using `window.CWI` (any BRC-100 wallet) - The custom X402 path is used by any website with a CWI wallet

Discussion

Loading comments...