- @Misagang04Governance+2•3
$JUP is a gem!$JUP UI & Swap Execution Analysis
Jupiter is the core liquidity routing layer for Solana DeFi. The Ultra V3 panel gives great visibility into slippage and MEV protection metrics.
Technical Observation / Suggestion: Adding real-time RPC latency indicators or a direct execution-time breakdown directly inside the swap modal would improve UX for fast scalping on high-volatility tokens. Overall, solid infrastructure with seamless Phantom integration.
- @jamieLending•4
$KMNO docs llms.txt only works on the canonical host**
Kamino has an LLM index and the Buildkit page (docs.kamino.finance/docs/build/agentic-finance/building-with-llms) tells agents to use it. Problem is the link kinda doesn't work. Checked 17 Oct 2026 with curl, no wallet connected:
- `https://docs.kamino.finance/llms.txt` with a normal client (`Accept: */*`) gives a 200 `text/html`, an 830 KB app shell, then bounces you to `https://kamino.com/docs`. No file.
- Same URL with `Accept: text/plain` gives a 200 `text/markdown` (53 KB), but it's got raw MDX in it, like `export const CopyBtn = ({text}) => { ... useState ... }`.
- `https://kamino.com/docs/llms.txt` is totally fine. Clean 56 KB `text/plain`.
So an agent that copies the link from the docs gets HTML or junk MDX. It would have to already know the other host and the magic Accept header, which kinda defeats the point of having an LLM index.
Can be fixed by a 301 `docs.kamino.finance/llms.txt` to `kamino.com/docs/llms.txt` (or serve the same bytes on both), always as `text/plain; charset=utf-8`, and strip the MDX/JSX out of the index., but is docs.kamino.finance even supposed to be a docs host, or should it just always redirect to kamino.com/docs?
- @akira_501501Governance+2•3
$JUP
Jupiter Ultra V3: make benchmark freshness visible
On 17 October 2026, Jupiter's public Swap Settings -> Ultra V3 panel displays "+0.6bps average slippage vs -14bps elsewhere" and "up to 34x" MEV protection, but the panel has no measurement window or source link.
Jupiter's official Ultra V3 launch article dates its slippage sample to 7-14 October 2025 and its MEV source to 15 October 2025. Are today's panel figures those historical benchmarks, or continuously refreshed measurements? The panel alone doesn't resolve that question; this is not a claim that the numbers are wrong.
Suggestion: put a compact "as of" date or rolling measurement window beside each metric, linked to its methodology and comparison set. The automatic-execution explanation is useful. Making its evidence one click away would help users distinguish a dated benchmark from current execution performance when choosing Ultra V3 or Manual.
Scope: public interface and documentation only; no wallet connected to Jupiter, swap executed, or performance benchmark run.
Interface: https://jup.ag/
Source: https://developers.jup.ag/blog/ultra-v3
- @ranimth07Utility+1•3
$GEOD I looked at GEODNET from the side of a would-be RTK customer in Indonesia: docs → trial → coverage. No hardware, no account created.
1) Coverage gaps are invisible, and StableHex isn't aimed at them. Your FAQ says 2 cm needs a base station within 25 km. Using your public coverage_stations API, Jakarta has 9 non-offline stations within 25 km and Surabaya has 10. Balikpapan has 0, and the nearest is ~338 km away. That's right next to IKN, Indonesia's new capital, which is under construction. On the coverage map, searching "Balikpapan" drops a pin but stays zoomed out to the whole world. The trial form asks for an exact test location, but nothing checks it against coverage.
GIP-13 says StableHex (6×) targets "remote area, no existing coverage". Yet the StableHex Center lists 1,072 active hexes and none are in Indonesia. By H3 base cell, most are in North America (~600) and Europe (~320). How are StableHex locations picked, and can customers or operators request one?
2) A quick fix: on rtkdocs.geodnet.com, the "Free RTK Trial" button under "How to obtain an account" goes to geodnet.com/free, which is a 404. The working page is /free-rtk-trial.
3) A Solana question. GIP-7 promised Solana Location NFTs, Solana governance and Solana revenue-splitting before Polygon support ends in March 2027. Today the console docs still say "Polygon wallet (required)" for Location NFT, staking and revenue share, with Solana optional. The Location NFT rules still require a Polygon address, and voting is MetaMask-only. With about 5 months left, is there a timeline for the Solana NFT airdrop?
Suggestions: make map search zoom in and show "nearest station: X km, expected accuracy". Show StableHexes on the public coverage map. Publish a GIP-7 migration checklist.
Checked in my browser with help from an AI agent.
- @SudamaGovernance+2•3
$JUP Feedback- Making swaps easier to understand
One thing I like about Jupiter is that it brings different swap routes together instead of making users compare multiple DEXs manually. But I think the experience could be even better for beginners.
My suggestion: Make the final swap summary more informative by clearly showing the expected amount received, total fees, price impact, and minimum amount the user could receive if the price moves before execution — all in one simple view.
These details matter because the best looking quote isn't always the best real outcome once fees and price movement are considered. A simple breakdown would help users compare routes more confidently, especially when swapping less familiar tokens.
I'd also like to see a short explanation whenever a swap has unusually high price impact or a route requires multiple steps. Instead of just showing a warning, explain in plain language what it means for the user's trade.
Jupiter already solves a difficult routing problem. Making the risks and final costs easier to understand could make that power more accessible to everyday Solana users.
- @traderteezanGovernance+1•3
$ORCA example was observed for this
Feature & Engagement Improvements
Recommendation: Nuanced Sentiment Voting
Feedback: The Gem vs. Rug binary sentiment voting is a good start but it’s too limited.
Improvement: Consider adding a Market Outlook tag system (e.g Bullish, Bearish, Neutral and Accumulate).
Why: Users rarely think in binary terms. Allowing them to tag a token as "Accumulate" or "Take Profit" provides more valuable community data than just Gem" or "Rug.
- @luquetafpsOracle•2
$PYTH One interesting aspect of Pyth Network is that its price feeds include a confidence interval, not just a price. This matters for DeFi lending and liquidation systems, where uncertainty in price data can affect risk decisions.
A question for the team: what safeguards do you recommend when a confidence interval becomes unusually wide relative to the reported price? A practical example of how developers should handle this scenario would be valuable for protocols integrating Pyth.
- @eomenaiDEX+1•2
$MET Feedback!
Walked through Meteora’s DLMM (Dynamic Liquidity Market Maker) pool setup flow. Selecting between Spot, Curve, and Bid-Ask volatility strategies uses clean visual bin distribution histograms, which helps visualize concentrated liquidity. The biggest UX hurdle for a newer LP is right after choosing a strategy: the interface shows the bin step and fee tier, but doesn't simulate what happens to your position when price moves completely outside your active bin range (zero fee accrual + 100% single-sided asset conversion). Is there a plan to add a simple interactive "Out-of-Range Preview" slider inside the deposit modal before signing the transaction? - @eomenaiCompute•2
$NOS Feedback!
Tested the Nosana Explorer and GPU Market dashboard (dashboard.nosana.com) to see how clear the workflow is for an AI developer deploying an inference job. The live market view shows active GPU nodes (like RTX 4090s vs 3090s) and hourly pricing clearly, which builds immediate trust. One UX friction point I noticed: while the node telemetry is great for hardware hosts, a developer coming from Web2 cloud platforms doesn't see an interactive "Cost & Latency Calculator" before connecting a wallet to deploy a job template. How does the job builder handle automatic failover if a consumer GPU node drops offline mid-inference? Surfacing that fallback state right in the deployment UI would really boost developer confidence. - @eomenaiGovernance+1•2
$SANC - Exploring Sanctum’s Infinity Pool and LST swap interface from a UI/UX perspective: abstracting unified LST liquidity into a simple swap card makes onboarding much cleaner than traditional DeFi pools. However, when comparing dozens of validator LSTs in the Explore tab, a first-time user can see the APY% immediately, but can’t easily compare validator delinquency history or unstake fee edge cases (instant vs. delayed epoch unstaking) without clicking into separate views. Adding a compact risk/unstake-time badge directly inside the token selector modal would make choosing between LSTs much faster for non-technical users.
- @darylbuildsGovernance+2•1
$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.
- @daniokd777Governance+2•2
$JUP is a gem!
Fr Man
Tried Jupiter’s limit order on mobile and and noticed -2.36% . Down 2.36% from what exactly? I knew the answer to my question but what if I was a newbie
Just label it “USD difference” or something on mobile as on the desktop version. Small fix, less confusion and anxiety, beginner friendly.
And yeah, no wallet connected, tested the preview.
- @NOVAGovernance+2•2
$JUP is a gem!Testing the latest limit order and DCA features on Jupiter's mobile view. The UI responsiveness during high network congestion is noticeably smoother than before. However, when placing a limit order for low-liquidity SPL tokens, the estimated price impact calculation occasionally lags by a few seconds before updating. Adding a manual refresh button specifically for the price impact widget on mobile would make trade execution even more reliable for fast-moving assets
- @bigfatcaracalGovernance+1•2
$SANC — the public app page describes two different security models for the same downloadable product.
On sanctum.so/app, the security section says each wallet is a three-key multisig (device, cloud backup, and email sign-in), every transaction gets device + cloud signatures, and two remaining keys can replace a lost one. But that entire section is labeled ‘Coming soon.’
The FAQ on the same page answers ‘How does Sanctum keep my money safe?’ differently: current access is an email one-time code through Turnkey, with an optional recovery email and App Lock. It does not say whether the downloadable iOS/Android app currently uses one key, two signatures, or the three-key scheme.
For an app asking users to hold SOL/USDC and buy assets, this boundary matters. Suggestion: add a ‘Current security’ box with today’s key/signature model and move the three-key design into a clearly labeled roadmap section. A small table—feature, current status, recovery path, and who can sign—would let users understand the custody and recovery model before funding.
Question: which exact signing and recovery model is active in the public app today?
Scope: public product page and FAQ checked 16 Oct 2026; no funds were deposited and no transaction was attempted.
Source: https://sanctum.so/app
- @rodrigopweb3Governance+2•3
$JUP $JUP | Jupiter Spot UX Feedback
I tested Jupiter Spot by previewing a 100 USDC → SOL swap without connecting a wallet.
What works well: The interface immediately displays the estimated SOL output and its USD equivalent. Previewing a swap without connecting a wallet is useful for beginners.
What could improve: A negative percentage appears beneath the estimated output. Initially, I couldn't tell whether it represented slippage, fees, or a price difference.
Hovering over it reveals that it represents the estimated difference between input and output USD values.
My suggestion: Label this indicator "USD value difference" directly in the interface, with an optional breakdown distinguishing fees, slippage, and price impact where applicable.
This could also improve clarity on mobile devices, where hovering isn't available.
I tested the quote preview only. No wallet was connected and no trade was executed.
- @wangzhushi1234Governance+2•1
$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.)
- @HunterRecoveryGovernance+2•1
$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.
- @WEB3Governance+2•1
$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.
- @CharonivWrapped+1•1
$mSOL
mSOL Unstake Audit: Claim Ticket PDA Hazards, Epoch Rollover & Net-SOL Disparity
I reviewed Marinade’s liquid unstake flow (app.marinade.finance/earn/liquid/?action=unstake) and on-chain mechanics for mSOL. Two technical and UX hazards create measurable capital drag for stakers:
1. The Ticket PDA & End-of-Epoch Rollover Hazard:
When a staker selects Delayed Unstake, mSOL is burned and a Claim Ticket PDA is initialized (locking ~0.0015 SOL for rent exemption). Two edge cases compound here:
• The Rollover Trap: If unstaking within the final ~2 hours of an epoch (the validator cooldown window), deactivation cannot settle at the immediate epoch transition. It rolls into Epoch N+2, ballooning the expected ~36h wait to over 80+ hours without warning.
• The Idle Capital Trap: Once the target epoch settles, SOL does not auto-return. The stake sits de-activated, earning 0% APY, while the ticket PDA remains open. Unsuspecting users who close the tab leave both principal and rent-exempt lamports orphaned indefinitely.
2. Hidden Cost Asymmetry (Instant vs. Delayed):
Instant unstake dynamically routes between secondary DEX swaps and Marinade’s LP reserve (0.10%–1.5% fee). During periods where mSOL trades at even a minor discount (0.2–0.4%) on secondary markets, an instant exit can silently cost 1.2%–1.8% more net SOL than the 0.20% delayed protocol fee. The modal shows an output quote, but lacks a side-by-side net-realized SOL comparator against the delayed route.
Recommended Fixes:
• Dynamic Epoch Warning Banner: When epoch progress is >95% (last ~2h), display: "Notice: Current epoch settling soon. Delayed unstakes submitted now will mature at Epoch N+2 (~80h). Wait [XX mins] to target Epoch N+1."
• Side-by-Side Route Comparison: Show an explicit delta panel: [Instant Exit: X.XXXX SOL immediately] vs [Delayed Exit: Y.YYYY SOL after Epoch N (Net +Z.ZZ SOL)].
• Ticket Maturity Alerts & Auto-Crank: Display exact target epoch/countdown on open tickets, and explore a keeper/crank option to sweep matured tickets back to user wallets upon request.
Acceptance Check:
A staker initiating a delayed unstake within the cooldown window is explicitly prompted before signing. Stakers can immediately benchmark instant slippage vs. the delayed 0.2% protocol fee.
Scope: Public web application flow (app.marinade.finance) and official documentation review (docs.marinade.finance). No wallet transactions signed.
- @geeGovernance+2•4
$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?
- @tdonMeme+1•3
$SI an AI meme related narrative that gain traction following the discussion of super intelligent by the American State president.
$SI being the first super intelligent meme narrative on the Solana Blockchain is mind blowing and believe you're considered an early adopter of this new narrative because we're heading to billions in mcap 🚀🚀🚀
- @itprog3rGovernance+2•3
$JUP is a gem)
Testing Jupiter’s routing and DCA engine reveals impressive liquidity aggregation, but there is still an edge case worth addressing regarding micro-slippage on volatile Solana pairs. During sudden network volatility, the dynamic priority fee estimation sometimes lags behind true validator tip thresholds, leading to partial fills or delayed routing execution on non-standard SPL tokens. Implementing a transparent 'worst-case execution breakdown' directly in the swap confirmation modal - showing the exact split between route slippage, priority fee tier, and potential AMM price impact - would significantly improve UX for algorithmic and high-frequency retail traders. - @LunaaGovernance+2•3
$JUP Product Review & UX/Technical Feedback on Jupiter:
1. Real-Time Liquidity & Price Sync on TokenGems:
While tracking $JUP liquidity depth and volume spikes via the TokenGems terminal, I noticed minor polling lag between Solana slot finality and the UI price ticker. Implementing WebSocket accountSubscribe listeners for $JUP/USDC Raydium/Orca pool accounts directly would ensure zero-latency order book updates during heavy volatility.
2. Swap Execution & Anchor Error Handling:
Testing Jupiter’s swap routing through the embedded flow revealed that when a transaction fails due to tight slippage (e.g., Anchor error 0x1771 or program execution error 6001), the modal surfaces a generic execution failure. Mapping program log errors to clear, human-readable UI alerts ("Slippage exceeded — increase tolerance by 0.5%") will dramatically improve conversion for retail traders.
3. Developer & Ecosystem Integration:
Does Jupiter or TokenGems plan to offer an open TypeScript SDK snippet directly on this page for quick API routing calls? Allowing builders to copy a localized pre-configured swap route snippet for $JUP directly from this token page would add massive value for developers exploring Solana gems.
- @Damon688czGovernance+2•3
$JUP — AI-assisted public-interface review.
I checked Jupiter's public USDC-to-SOL quote screen without connecting a wallet or executing a swap. The “Use V1 transactions” switch was on, and its help text explained that V1 can change available routes and estimated output, while wallet support varies. The fallback instruction to turn it off for V0 is useful. Could the option be labelled “New transaction format — wallet support varies,” with a link to supported wallets beside it? That would make the compatibility trade-off visible before someone reaches signing. I did not test the connected-wallet flow, so this is a suggestion about the public screen, not a report of a failed transaction.
- @pinyopattMeme+1•3
$chimp Exploring Mojo AI's intent-driven execution on Solana: The natural language translation to DEX aggregation routes drastically simplifies multi-hop swaps.
However, two architectural observations for the team:
1. Slippage & Route Fallback: When an intent executes during high-volatility spikes (e.g. priority fee surges), does the simulated transaction enforce dynamic compute budget re-bidding, or does it fail-safe and abort without consuming gas fees?
2. Multi-hop Partial Refunds: If a multi-leg routing fails midway through an intermediary pool, is the partial unswapped balance automatically unwrapped/refunded to the user's primary token account atomically, or is manual recovery needed?
Adding an explicit execution telemetry preview (simulated price impact vs realized on-chain execution) would give institutional and retail users complete confidence in autonomous agent routing.