Jupiter Lend DEX $JUP

$JUP — staking docs disagree: 30 days or 7 days?

Jupiter's own pages give two different unstaking periods. The DAO FAQ (June 2025 edition, still live) says unstaking JUP takes 30 days, designed to stop holders gaming ASR. But vote.jup.ag now says unstaking triggers a 7-day cooldown, during which you can't claim ASR.

One of these is stale. New stakers reading the FAQ will expect a month-long lock and may stake less — or skip staking entirely.

Could the team either update the FAQ or add a banner pointing to the current 7-day rule? A single canonical staking page would end the confusion.

Sources:
https://discuss.jup.ag/t/jup-dao-faq-june-2025-edition/38967
https://vote.jup.ag

$JUP I checked Jupiter's home page on 6 October 2026 without connecting a wallet.

I noticed that the swap screen — the first thing a new user sees — sits directly next to 250x leverage perpetuals, a Gacha pack opening feature (up to 32x), and prediction markets. All of these are high-risk, and none of them carry a visible risk warning on the home page.

This matters because Jupiter is Solana's front door. A first-time user from a country where a failed transaction is real money will not know that 250x leverage can wipe an account in seconds, or that Gacha packs are gambling-style products, not investments.

Suggestion: add a one-line risk label to the Perps, Gacha, and Prediction Market tiles on the home page — something like "High risk — can lose your full deposit." It's a small change that protects new users without changing the product.

Question: is there a first-time-user mode that hides leverage and Gacha until the user has completed at least one swap?

$JUP- I'm a self-taught dev from Afghanistan. Before putting real money in a wallet, I clicked through jup.ag on my phone, because for me a failed tx fee is lunch money.

The swap screen is the cleanest on Solana. Route hops and price impact sit right there.

But two things stopped me. The slippage box shows a bare 0.5% and assumes you know if it's safe. I had to google it. A "what is slippage?" link would save new users that trip.

Bigger issue: no way to practice. No dry-run with fake numbers. My first real swap will be my first lesson, paid for in SOL I can't afford to lose. A practice mode would open this to scared users in poor countries.

Jupiter is Solana's front door. It just needs a small sign for first-timers.

I checked Jupiter’s Trigger docs, not the swap screen. On $JUP, Trigger V2 can partial-fill, but the output amount is not guaranteed: the trigger is a USD price, then the swap runs at the live pool rate. V1 guaranteed a fixed pool rate and did not partial-fill. Easy to miss if you only read “limit order.”

The useful gap is expired or cancelled price orders. Funds stay in the vault. Getting them back is two steps: initiate the cancel, then sign the withdrawal and confirm. A DCA cancel returns the unfilled remainder in one step. I could not find a user-facing line that says an expired price order is not sent home automatically.

If I were shipping the order card, I would add: “Expired. Funds still in vault. Withdraw needs a second signature.” That one line stops people treating a dead order as already returned.

Source: https://dev.jup.ag/docs/trigger
Read from the docs. No order placed.
$JUP

Tested $JUP 's limit order and DCA execution pathways on Solana: While the liquidity routing across DEX pools ensures optimal pricing with sub-second execution, the current DCA interface lacks granular slippage customization per individual execution order.

During high-volatility market bursts, orders that trigger under default slippage constraints often experience execution dropouts without clear push or in-dApp notifications detailing which exact micro-order failed to land. Implementing dynamic priority fee auto-adjustments specifically for DCA and limit orders—alongside an exportable CSV execution log for tax and portfolio tracking—would significantly improve the power-user experience and retention for active DeFi traders.

I opened a 50x SOL long on $JUP through the perps API from a wallet holding $10.60, mostly to see where the edges are. Three things worth knowing if you build on it. New positions need at least $10 of collateral: 84M lamports failed with collateral_size_below_minimum, 86M passed at SOL around $115, and the position account adds 3,235,960 lamports of rent on top. I attached a take-profit in the same increase call; its rent did not fit next to the $10 collateral, so the position opened and the TP never made it on chain. I only noticed from GET /v1/positions. Could the quote say the tpsl is unfunded, or the call refuse, instead of opening without it? Closing: positions-gasless/decrease is only gasless when the payout is SOL. Paying out in USDC makes the wallet the sole signer and it needs about 0.0037 SOL for rent, which a wallet like this one no longer has. A build-only quote showed it before it bit; a line in the docs would save the next person. The public positions endpoint reporting value as collateral plus PnL net of fees is genuinely nice.

$JUP I tested the SOL to USDC Market flow and tried to start from a fixed USDC receive amount, but the swap only accepts the sell-side amount. Jupiter support docs say ExactOut was removed because it often gave worse pricing. A useful middle ground could be a target receive planner: enter 100 USDC, show the estimated SOL needed or range, then execute through the normal optimized route. That keeps pricing protection while making payments and rebalancing easier to plan.

$JUP is consolidating a massive amount of structural value because its aggregator layer has effectively turned into the primary execution gateway for the entire Solana ecosystem. The platform captures direct, non-speculative revenue flows regardless of which specific narrative or meme is pumping at any given moment. I do wonder if its heavy reliance on a single underlying network leaves it overly exposed to L1 structural risks, but its sheer volume distribution is undeniable.

$JUP A suggestion for improving TokenGems' token metrics

While exploring Jupiter ($JUP) on TokenGems, I noticed its overall score is 74.55 and its entropy value is 0.3069.

The score tooltip says it's based on multiple factors, but doesn't explain which factors or how they're weighted. The entropy tooltip explains that higher values indicate more decentralized ownership, but doesn't explain the scale.

I also tried clicking the score to find more information, but it didn't open a breakdown.

My suggestion: make these metrics expandable, showing the score components, how to interpret entropy, and when the data was last updated.

This would help users understand the numbers instead of relying on them without context. The existing tooltips are a useful start, and a detailed breakdown would make TokenGems even better for researching Solana projects.

$JUP is a gem!One thing that would make the data on this page much more usable: the token tables rank projects by a "Score" (values like 85.99) and show a "Holder Distribution" figure (like 0.79) and a "Mc/Rev" column that is mostly blank — but I could not find a legend or tooltip anywhere on the page explaining what any of these three numbers actually measure, what range is good or bad, or how the Score is calculated.

As a newer reader, that matters: the Score is the column the ranking is sorted by, so it is effectively TokenGems' main quality signal, yet I have to guess whether a 0.79 holder distribution means concentrated or well spread out. A one-line tooltip per column — definition, range,and what a high/low value implies — would turn these from decorative numbers into something a reader can actually act on.

(Scope: based on exploring TokenGems' public pages on Oct 13; no

wallet actions or trades were made for this take.)

$JUP Jupiter Lend makes the USDC yield very easy to understand: 9.6% APY and even a clear example showing $1,000 growing to about $1,096 in one year.

One UX improvement: before “Connect to Deposit”, I would show an equally visible explanation of where the yield comes from, how variable the APY is, and the main risks. The projected earnings are very prominent, while the risk/context is much less visible.

A small “Why this APY?” or “Risk & yield details” section beside the projection could improve trust without making the interface more complicated.

$JUP The swap routing and slippage customization on Jupiter are very smooth, making token swaps fast and low-cost. However, during periods of high network volatility, the limit order execution status takes a few extra seconds to update in the UI. Adding a real-time RPC latency indicator right inside the swap card would give users much better visibility before placing trades.

$JUP I opened jup.ag and walked through a Manual Swap of a tiny SOL→USDC route without broadcasting. The route preview correctly showed multi-hop legs, but Priority Fee and Jito Tip share the same tooltip copy. Those are different mechanisms, and when Jito Tip is toggled off the UI still shows 0.001 SOL, which reads like it will still be charged. Suggestion: give each fee its own one-line explanation, gray out disabled fee amounts, and include only active fees in the pre-confirm cost estimate. Question: can the quote panel surface base fee vs priority fee before the Swap click, so congested-network failures are visible earlier?

$JUP Tested swapping SOL to USDC through the Jupiter interface and reviewed the route breakdown. The multi-hop routing between Raydium and Whirlpools kept slippage low, but the interface doesn't show the dynamic network priority fee until you actually click Swap. Would it be possible to display the current base vs priority fee upfront before confirming? That would help avoid failed transactions when the network gets congested.

$JUP JUP is a solid project with great trading volume on Solana network. The user interface is straightforward and very easy to use for new people. I am looking forward to seeing their upcoming ecosystem updates.

$JUP is a gem! - Played around with a 1 SOL -> USDC quote on Jupiter (didn't connect a wallet).

Couple of things I noticed:

- Number formats are mixed up. The output shows "104.484915" with a dot, but right next to it "≈$104,55" and the rate "104,48 USDC" use commas. Further down the page I get "$1,54 млн", "$82,3 тыс.", "UMC $5,51 трлн" in Russian while everything else is in English. Probably picks it up from my browser language, but it's easy to misread amounts like that.

- "Use V1 transactions" is on by default. The tooltip says wallet support varies and to switch to V0 if signing fails, but honestly I'd never think to hover over that toggle if a swap failed. Maybe show that hint right when signing fails?

- First thing in Popular Tokens is SAINDRA, $232K mcap, "+57x", no risk label at all. For someone new that looks like a recommendation.

What I checked: swap quote, rate, V1 tooltip, the whole homepage. Affiliation: None.

$JUP a small correction to the Swap V1 docs could help developers handle expired swaps.

The Send Swap Transaction guide calls confirmTransaction with only {signature}, leaving out the original transaction’s blockhash and matching lastValidBlockHeight.

An AI-assisted offline reproduction using the published @solana/web3.js 1.99.0 SDK found that this object entered the durable-nonce path with an undefined nonce account. Under mocked expired-transaction conditions, it stayed pending without checking block height.

Including the original blockhash and matching lastValidBlockHeight selected the correct confirmation path and returned TransactionExpiredBlockheightExceededError.

Could the guide update this example and include expiry handling? That could help integrators show a clear Expired status when a dropped swap cannot be confirmed.

Scope: legacy Swap V1 documentation and an offline SDK reproduction. No live Jupiter swap or app failure was tested.

Source: Jupiter Swap V1 guide

I reviewed Jupiter's ( $JUP ) legacy Swap V1 Get Quote guide. It describes a quote for 1 SOL, but the example uses amount=100000000. Since 1 SOL is 1,000,000,000 lamports, the code requests 0.1 SOL—one tenth of the described amount.

This could confuse beginners copying the example. Could the guide change the description to 0.1 SOL or use amount=1000000000? If the latter, the sample response should also be updated consistently.

The guide already says V1 has been superseded by V2. This feedback is based on documentation review and unit conversion; I did not execute a swap. Prepared with AI assistance.

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

$JUP I tested Jupiter’s Trigger/Limit Order flow on mobile without placing or signing an order.

One UX detail stood out: when using USDC as the trigger mint, the interface lets me configure the order and only then shows: “Trigger mint is not supported: Limit Orders does not support stablecoin trigger mints.”

Changing the trigger mint to a supported token removes the warning.

I think this could be clearer earlier in the flow. For example, disabling unsupported stablecoins in the trigger-token selector, or showing a short explanation before the user fills out the order, would prevent users from configuring an order that cannot be created.

Source: Jupiter Trigger docs — https://dev.jup.ag/docs/trigger

Tested on the Jupiter web interface; no order was placed.

Clarify missed installments in Recurring Orders

Jupiter’s support FAQ says failed Recurring Orders retry at the next scheduled interval. Could you clarify whether a missed installment is skipped, added to the next installment, or extends the schedule? A worked example—such as a four-installment order where the second execution fails—would make the resulting purchase amounts and completion date much easier to understand. Showing the next retry time and remaining installment count in the order status would also help users distinguish a delayed purchase from a stopped order.

Source: https://support.jup.ag/

This feedback is based on reviewing the documentation; no order was placed. Prepared with AI assistance. $JUP

$JUP

Tested Jupiter Perpetuals and analyzed JLP (Jupiter Liquidity Provider) pool mechanics on Solana.

Specific Observation: Jupiter's perpetual exchange effectively utilizes the JLP multi-asset pool to serve as the counterparty to leveraged traders. When market directional bias becomes heavily asymmetrical (e.g. 85%+ open interest long SOL during an aggressive rally), borrow fees ramp up aggressively on an hourly basis to incentivize rebalancing. However, for a trader opening a position in the order interface, the borrow fee is quoted as a single static APR percentage. There is no inline breakdown showing the projected cumulative collateral erosion across common holding durations (1 day, 3 days, 1 week) under current pool utilization.

Constructive Suggestions:

Embed an interactive "Holding Cost Estimator" directly inside the Leverage slider modal. Showing an estimated daily and 3-day dollar decay on the user's collateral at current pool utilization would drastically improve position sizing decisions for swing traders.

In the JLP performance tab, provide a transparent yield attribution chart showing what percentage of weekly pool yield originates from organic trading volume vs. borrow fees vs. liquidation penalties.

Question for the Team: Given that JLP frequently hits utilization limits during sustained directional trends, does Jupiter plan to introduce dynamic leverage caps that scale downward automatically as asset-specific pool utilization crosses 90%?