Jupiter token $JUP

Jupiter: make the disconnected quote's fee state explicit

I explored Jupiter's Market swap page on desktop Chrome on 30 September 2026, with AI assistance. This was a read-only product check: no wallet connection, signature or trade.

Reproduction: open https://jup.ag/, keep USDC as Sell and SOL as Buy, enter 1 USDC, then expand the rate details. I could preview roughly 0.00835 SOL and inspect the route before connecting a wallet. That is useful for understanding the flow without first granting wallet access. The displayed output and route changed as quotes refreshed; this is a snapshot, not a promised execution result.

In the expanded details, Platform Fee showed 0.02%, while Network Fee showed a dash. As a disconnected newcomer, I could not tell from that row whether the dash meant zero, an estimate unavailable before connection, or a fee included elsewhere. For a small swap, that distinction matters when comparing the displayed output with the total cost.

Could the fee row explain what this state means? A short label such as "estimate unavailable before connection"—if that is the actual reason—would be clearer than a dash. It would also help to state whether the displayed buy amount already includes the platform fee, and show the separate network cost when an estimate becomes available. A quote timestamp would make the changing preview easier to interpret.

The Ultra V3 settings explain automatic price, landing and slippage optimization. I did not test those execution claims. This feedback is about the public preview's clarity, not a claim that fees were charged incorrectly or a recommendation to buy JUP. Prepared for the TokenGems feedback bounty; any award depends on judging.

$JUP

$JUP is up 61% in 30 days to $0.33, a $1.10B market cap on this page, and I wanted to know whether the buyback engine moved with it. It did not. Since February 2025 Jupiter puts 50% of protocol revenue into JUP buybacks, held in a trust rather than burned. DefiLlama's holder-revenue series says those buybacks were $3.13M in the last 30 days: $1.88M from the aggregator, $0.99M from perps, the rest from Lend, jupSOL, DCA and Studio together. That is a run-rate near $38M a year, 3.4% of the market cap and 1.7% of the $2.29B fully diluted value, with 48% of supply still not circulating. The trend under it points the other way: protocol revenue was $6.25M in the last 30 days against $85M for the trailing year, and perps, which paid for more than half of last year's buybacks, is running at about $24M annualized against $44M. Prediction keeps no fees yet and Lend is still small. So the month's move is not revenue-led; at $1.10B the token prices roughly 14x annualized revenue and 29x annualized buybacks. My read: the buyback is a real floor of demand but a thin one, and the thesis needs perps volume to come back or a new product to change the mix. Which of those is the bet here?

$JUP is a gem!

One thing I find useful about Jupiter's TokenGems page is that it brings holder numbers, market data, and community sentiment together in one place. However, a high score or large holder count doesn't automatically mean a token is safe, especially when holder concentration and liquidity can affect how easily someone exits a position.

A useful improvement would be to show a clearer breakdown of the main risk indicators alongside the overall score, including liquidity depth, concentration among the largest holders, and how each metric affects the rating. How often is the score recalculated, and can users see which factors contributed most to a change?

$JUP — a clearer checklist for recreating a DCA order

Jupiter's DCA V2 guide already explains cancellation, order parameters and the absence of pause/resume. Could its Managing Orders section bring those details together in a short recreation checklist?

Suggested checks: choose the amount and number of suborders still intended, rather than automatically reusing the original totals; review the token pair, interval and optional price range; confirm the funds available for the new allocation; and highlight the timing of the new first suborder. The guide describes an immediate first suborder, while price checks and retry conditions still govern execution.

This would help someone changing a partially completed schedule distinguish the remaining plan from a fresh allocation. If the app already offers a prefilled recreation flow, linking it from this section would also help.

Scope: a documentation suggestion prepared with AI-assisted research. No wallet connection, order, cancellation, withdrawal or swap was tested; this is not a reproduced app bug.

Sources:

https://docs.jup.ag/user-docs/trade/spot/recurring-orders

https://docs.jup.ag/user-docs/trade/spot/limit-orders#vault-access

$JUP — A small documentation correction could prevent a 10× input-amount mistake.

In Jupiter’s “Get Quote (Swap V1)” guide, the example introduces a quote for 1 SOL, but the request uses amount=100000000. With 1 SOL = 1,000,000,000 lamports, that request actually quotes 0.1 SOL. The example response also shows inAmount="100000000".

Suggestion: either change the introductory text to “0.1 SOL” or update both the request and example response to consistently represent 1 SOL. A short conversion example beside the amount parameter would also help beginners avoid decimal mistakes.

This concerns the legacy V1 guide, which is marked as superseded by Swap V2. Scope: public documentation review with AI assistance; no wallet transaction or live API test performed.

Source: https://developers.jup.ag/docs/swap/v1/get-quote

$JUP is a gem! $JUP — “Gasless” should make costs easier to understand, not harder.

Based on Jupiter’s Swap V2 documentation, configuring a payer different from the taker restricts routing to Metis. The documentation also distinguishes the total fee from the platform fee when gasless-support costs are recovered.

My suggestion: before signing, show a compact summary of who pays the network fee, which routers remain eligible, the total fee and its token, and the expected net output.

This would help beginners understand that sponsored network fees do not necessarily mean zero cost. Does Jupiter already provide a standard breakdown that integrators can display?

Source: https://developers.jup.ag/docs/swap/order-and-execute

Prepared with AI assistance from official documentation. No swap was executed and no savings were measured.

Testing the @tokengems alpha feed and $SOL

execution flow. Two critical observations

regarding UX and routing efficiency:

1. Slippage & Routing Transparency: When tracking

tokens like $JUP and cross-DEX volume, the

natural language prompt handles multi-hop swaps

well. However, during high volatility spikes on

Solana, the estimated output in the interface

occasionally deviates from on-chain settlement by

~1.2%. Adding a live simulation breakdown showing

which liquidity pool was tapped (e.g. Raydium vs

Meteora) directly in the confirmation card would

drastically increase user trust for larger size orders ($500+).

2. Mobile State Persistence: On mobile browsers

via Phantom, switching tabs during transaction

confirmation occasionally resets active chat context. Caching the prompt state locally before signing prevents users from re-typing complex DCA/order commands.

Overall: Strong consumer-grade execution abstraction. Great work @tokengems team! $SOL $JUP

$JUP is a gem!

Tokengems shows the score of crypto clearly. For example, $JUP is 74.68, which is above average. The score is symbol of safety and high quality.

$JUP — make transaction-format compatibility visible before signing

With AI assistance, I reviewed Jupiter’s public desktop Swap interface on 9 October 2026 without connecting a wallet. The Market panel showed Ultra mode and “Use V1 transactions” switched on. Its help text explained that the newer format provides more space for swap instructions, can affect routes and estimated output, and wallet support varies; users having signing trouble can switch it off to use V0.

Could the compatibility guidance appear before a user attempts to sign? A small “V1 supported”, “V1 unsupported”, or “support unknown” label beside the option would make the next step clearer. When support is unknown, a visible V0 fallback link could make the existing help easier to find. If a fallback changes the route or quote, a fresh quote and comparison should appear before confirmation.

Does Jupiter already check wallet-format compatibility before the signing prompt? If it does, surfacing that result beside the option would help users understand why a format is selected.

Scope: public UI and help-text review only. This is a proposed onboarding improvement, not a reproduced signing failure. No connected-wallet behavior, swap, payment, or transaction was tested. No affiliation with Jupiter. Prepared with AI assistance.

Source: https://jup.ag/

$JUP is a gem!

I tested Jupiter’s DCA flow with 20 USDC over 2 orders and enabled “Earn while you wait.” The UI clearly shows the amount per order and total runtime. One thing I found less clear is the yield option: the tooltip says idle capital is held as a yield-bearing Jupiter Lend token between fills, but I couldn’t find an inline link explaining what that position involves before opting in. Since this changes what happens to idle USDC, a small “Learn about Jupiter Lend” link or short risk/context note next to the toggle would make the choice easier to evaluate.

$JUP is a gem!

Tested Jupiter’s mobile web interface alongside the web terminal for cross-DEX routing and DCA orders.

Specific Observation:

The routing algorithm handles split trades across Raydium and Meteora pools smoothly, but during sudden volatility spikes, the slippage tolerance warning is delayed until after the transaction simulation completes.

Actionable Suggestion for Builders:

1. Dynamic Pre-Simulation Warning: Display an estimated price impact badge directly beneath the swap quote before the user signs the transaction.

2. DCA Cancel UX: When canceling an active DCA order, the required rent refund for the closed account should be clearly itemized on the confirmation modal so users understand where their reclaimed SOL went.

Question for the team:

Does Jupiter plan to expose an automated MEV-priority fee toggle directly in the ultra-fast routing settings for mobile users experiencing high drop rates?

$JUP is a gem!

I looked through the JUP page and Jupiter's token docs without making a trade. The Solana mint shown here, JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN, matches Jupiter's official JUP address. That's a useful check because search results also include unrelated tokens called Jupiter. One point of friction for a newcomer: this page tags JUP as DEX, Governance and Derivatives, while Jupiter's docs describe JUP specifically as its governance token. Could the project page explain more plainly what holding or staking JUP lets someone do, versus what Jupiter's swap and perps products do? A direct link to the official JUP token FAQ beside the mint would make that distinction easier to check. I haven't tested the trading flow, so this is a clarity suggestion, not a trading or price review.

$JUP UP showing increasing transaction count with steady liquidity depth.

Momentum building without extreme volatility.

That balance is usually healthier than parabolic spikes.

$JUP sitting at $0.16 — down 92% from its $2.00 ATH, yet it recorded $112K in fees and nearly $4.5K in revenue in the last 24 hours alone.

$JUP is a gem! The ecosystem around JUP is amazing. anticipating a great pump this year

Jupiter, especially with its recent product suite expansion, looks like it's consolidating its lead on Solana. The sheer volume flowing through the $JUP aggregator shows significant stickiness. Execution is there, just need to see if sustained momentum follows new launch cycles.

$SOL down 4-5% today but $JUP is still being called Solana's flagship DeFi Superapp for a reason. Smart routing across Raydium and the entire Solana DEX ecosystem — this isn't just another aggregator. When $SOL recovers, $JUP leads the DeFi charge.

$JUP processed more DEX volume than Uniswap last month and most people still sleep on it. Best aggregator UX in crypto, growing liquidity, and a community that actually shows up. Don't say you weren't told.

Was exploring $JUP on TokenGems and I appreciate how clean the token breakdown is.

The chart feels responsive and the quick metrics snapshot at the top saves time.

Still testing everything, but for early beta this feels polished.

Interested to see how they expand analytics for ecosystem tokens.

$JUP is the gem!

$JUP Riding the Solana wave, but don't get washed out.

Jupiter remains the central liquidity hub for Solana's fast-paced, high-beta ecosystem. Every time a new memecoin pumps or a fresh yield-farm drops, $JUP sees increased volume, driving its fee accrual and creating a narrative bid. We're seeing solid activity spikes, suggesting retail is piling back into SOL plays, and $JUP is their gateway. It's a high-leverage play on Solana's degen appetite, capturing value from the entire ecosystem's trading frenzy.

Reality Check: $JUP is a direct proxy for Solana's health and retail sentiment. If SOL takes a hit, $JUP will likely amplify that downside, becoming exit liquidity for many. The "fundamentals" here are largely based on speculative volume and airdrop farming, not deep institutional integrations. Be ready for sharp corrections and front-running if the broader market turns sour or if a new competitor emerges with better incentives. Don't treat it like a blue-chip.