Skip to content

feat: switch to Jupiter V3 price API & add timeframe limitation filter#36

Open
HkSolDev wants to merge 1 commit into
ronnyhaase:mainfrom
HkSolDev:feat/timeframe-and-jupiter-price-fix
Open

feat: switch to Jupiter V3 price API & add timeframe limitation filter#36
HkSolDev wants to merge 1 commit into
ronnyhaase:mainfrom
HkSolDev:feat/timeframe-and-jupiter-price-fix

Conversation

@HkSolDev

@HkSolDev HkSolDev commented Jul 5, 2026

Copy link
Copy Markdown
solfees.mp4

Summary of Changes

This PR addresses two main improvements:

  1. Upgraded SOL price feed to Jupiter V3: The deprecated Jupiter V2 API (lite-api.jup.ag/price/v2) was returning a 404. I implemented a secure server-side proxy route at /api/price that fetches from Jupiter V3 with the secret API key. The client hook useSolPrice.ts now calls this proxy, protecting private keys from being exposed in client-side code.
  2. Added Timeframe Limitation Filter (Issue Add possibility to limit the timeframe #27): Added a pills selector (1 Hour, 24 Hours, 7 Days, All Time) to the main form. The fetching loop now calculates the cutoff timestamp in hours and breaks the loop early to avoid downloading thousands of transactions for highly active wallets.
  3. Real-time scanning updates: Switched the transaction aggregator to run dynamically as batches arrive, updating stats (SOL fees, USD fees, average) in real-time while displaying a pulsing loading banner at the top of the Results card.
  4. Prevented Empty-Timeframe Crashes: Initialized firstTransactionTS to 0 when there are no transactions (preventing range errors in JS Date) and displaying a friendly warning when no transactions are found.

@vercel

vercel Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

@HkSolDev is attempting to deploy a commit to the haaseBUILD Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant