$SI

I noticed there are multiple tokens using the Super Inu name and $SI ticker across different chains, while the Solana version has its own distinct contract. That creates a genuine verification problem for new users because a search for “Super Inu SI” can surface different assets. Could you make the official chain and contract address a permanent part of the project’s primary identity across the website, X and exchange listings, perhaps with a single canonical verification page?

The $XCAT token is currently priced at $0.00000006003, with a market capitalization around $191.9 million and $56.8 million in liquidity. This token has been steadily losing its grip, down nearly 30% in a day and over 43% in the last week. Looking further back, it has shed over 56% in a month and is down more than 98% from its all-time high. This kind of sustained drift suggests the crowd that once chased $XCAT has largely moved on.

The joke for $XCAT seems to have run its course, with little in the way of recent developments to incite renewed attention. There hasn't been a significant new listing, exploit, or governance event that might explain a sudden shift in buying interest. The chart reflects a steady egress rather than a temporary dip, and identical animal tokens launch every week hoping to catch a flicker of the same light. The only thing that would make this call incorrect is a genuine and unexpected surge of fresh attention, rather than just a brief dead cat bounce.

Been following Jito for a while now. The staking rewards are cool with $JitoSOL - it will be great if they circulate the gas fee and tx fee back to the holders which contributes to circulating supply. Tokenisation is already in and JITO being the invisible layer for Solana network is making the smart money move!

My take on $STREAM :

Explored Streamflow around their 70% supply burn (699.99M $STREAM burned Sep 23, verifiable on Solscan — supply now capped at 300M). What stands out: a token-operations platform serving 40K+ projects and $660M+ TVL, whose whole pitch is on-chain transparency — yet this token page doesn't surface the burn transaction or the team's vesting schedules. That's the exact proof their product exists to provide.

Suggestion: link the burn tx and live vesting contracts directly on the token page. It would turn the page into a working demo of the product itself.

Question for the team: with the 6-month xSTREAM swap window running, what's the plan for $STREAM liquidity for holders who don't go through verification?

Something I noticed about $NVDAx 👀

It currently has 165K+ holders, but only 4 posts on its TokenGems page.

What caught my attention is that its TokenGems score is 71.77, even with relatively little discussion on the page.

Since TokenGems’ score considers price performance, holder distribution, trading volume and community activity, I’m curious:

How much does community activity actually influence the final score?

A breakdown showing how each factor contributes could make the score much easier to understand.

$ORCA I tried a SOL → USDC swap on orca.so/trade as a first-time user (3 Oct 2026, Windows laptop, Chrome, Phantom connected with 0 SOL and 0 USDC, no trade).

What I noticed: with 1 SOL entered, a red message says "You need at least 1.0045 SOL to make this purchase". But the details panel shows Estimated Fees "<$0.01" (Liquidity Provider <$0.01, Network <$0.01). The extra 0.0045 SOL is about $0.54 at today's price, so the fees shown don't explain it, and I couldn't find anything on the page that does.

Why it matters: a new user with exactly 1 SOL can't tell how much extra to keep, or whether that 0.0045 SOL is spent or stays in the wallet.

Suggestion: add one line to the details panel, for example "Extra SOL needed: 0.0045 SOL", with a short tooltip saying what it's for and whether any of it comes back.

Small extra: the Route row shows "SOL → USDC (0%)". I couldn't tell what the 0% means (pool fee? price impact?). A tooltip would help here too.

Question: is part of the 0.0045 SOL the rent for creating my USDC token account (about 0.002 SOL), which I'd get back if I close that account later?

Feedback on TokenGems research pages, verified live today on $NOS and $USDT:

What genuinely works:

- $NOS token page renders full analyti

Issues found live:

- The score FAQ text is cut off mid-sentence ("A 0-100 quality rating computed from price performance, h...") and clicking the question does not expand it, so the full scoring methodology cannot be read. No methodology link sits near the score widget either.

- FAQ sections read as thin auto-generated filler - e.g. "Nosana token is on Solana." / "Tether USD from Ethereum is on Pulse." - on both token pages I checked.

Would love to see the score methodology fully readable (or a docs link next to the score) so researchers can judge how scores are weighted.cs: price $0.5841 (-2.9% 24h), $59.45M market cap, 48,137 holders, entropy 0.5326, TokenGems score 78.3, Gem/Rug sentiment 58/42, plus community posts.

- $USDT (Tether USD from Ethereum, bridged on PulseChain) shows price $0.9999, $4.43M market cap, 12,932 holders - no missing or zero pricing.

$ROUTER is a gem!
I noticed that Solrouter's privacy model differs depending on the feature being used. Regular chat and the sealed inference path protect prompts with client-side encryption and TDX, but the Notion and GitHub connectors in Agent mode currently run outside the enclave. It would be useful to make this distinction especially prominent in the UI before users connect private workspaces, perhaps with a per-tool "sealed/unsealed" indicator. That would make the privacy guarantees easier to understand when switching between agent features.

I like the simplicity of connecting with $KNICKS culture. The next step could be giving holders something to actively participate in.

A prediction market for each game, with points and collectible rewards could create engagement beyond trading.

Could this be integrated directly into the project?

$BP is a gem!

Only issues i ever got is that I can't rely backpacks transaction history 😐 and then the lil hiccups when it crashes (sometimes)

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

$JitoSOL Staking SOL into JitoSOL today, and noticed a couple of friction points around unstaking and yield visibility that could use improvement.

When unstaking, users choose between "Instant Unstake" (routing through DEX liquidity pools) and "Delayed Unstake" (waiting for the Solana epoch boundary). For Instant Unstake, the UI shows estimated received SOL, but during volatile hours or shallow pool liquidity, it doesn't clearly display the dynamic DEX pool fee and slippage compared to the protocol's true underlying redemption rate. A user can easily take a 0.8% haircut without realizing a delayed unstake would preserve 100% of capital.

For Delayed Unstake, once you initiate the withdrawal, there's no native in-dApp countdown timer or estimated Solana epoch completion timestamp showing exactly when the stake account becomes deactivated and claimable. You basically have to track Solana epoch progress on a third-party explorer.

Lastly on yield: JitoSOL’s APR combines baseline staking rewards with MEV tips. It would be super helpful to break that headline APY into a transparent two-part split (e.g. 6.8% Base Inflation Yield + 1.4% MEV Tip Yield), so users can see how much MEV is actually contributing week-over-week.

$KMNO Borrowing USDC against SOL and JUP on Kamino Lend today, and ran into a real UX friction point around rate spikes.

When pool utilization pushed past the 85% kink, the borrow APR jumped from ~5% to over 30%. Because of that rate surge, my Health Factor degraded noticeably faster over a 48-hour window—purely from compounding debt accrual, not underlying price drop. Right now, the borrow modal only quotes an instantaneous APR percentage. For anyone holding a carry or swing position, there's zero visual projection showing the actual dollar-cost decay or how fast an ongoing rate spike will eat into your collateral over 24h/72h.

Another pain point with multi-asset collateral: if you deposit both SOL and JUP to back a single loan, there's no visibility into which asset the liquidation bot seizes first during a partial liquidation. I'd much rather have the protocol liquidate more volatile tokens before touching core yield-bearing SOL, but currently there’s no way to set a priority preference.

A simple daily debt-decay estimator inside the position view, plus a user-defined liquidation hierarchy for multi-collateral loans, would make risk management 10x clearer for active borrowers. Curious if the team has ever considered letting users set an automated rate cap to partially deleverage before borrow spikes get out of hand.

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.

The limited information available for the exact $EIDOVERSE contract made me think about the onboarding experience for someone discovering the token for the first time. Before considering the asset itself, a user needs to answer basic questions: What does $EIDOVERSE do, who is building it, which contract is official, where is the liquidity, and what can the token actually be used for? A simple “Start Here” page answering those questions, with every important claim linked to an onchain source where possible, would significantly reduce the research burden.

I explored your request lifecycle and noticed that Switch Board doesn’t simply route each request to the cheapest model. It combines price, latency, measured reliability and provider stake, then can fail over to another provider when a request fails. I like the attempt to balance cost with reliability. How do you prevent the staking component from becoming too influential in the auction, where a provider with a large $SWCH bond could consistently outperform a technically better provider offering lower prices or better measured performance?

$JTO page mixes up Jito's two tokens

The page title reads "Jito Restaking $JTO" and the tags are Liquid Staking + Restaking. The mint shown, jtojtomepa8beP8AuQc6eXt5FriJwfFMwQx2v2f9mCL, is the JTO governance token: Jupiter's verified list names it JITO/JTO, and the Jito Foundation's constitution calls it "The Jito Governance Token (JTO)". The liquid staking token is JitoSOL, a separate mint (J1toso1uCk3RLmjorhTtrVwY9HJ7X8V9yYac6Y7kGCPn). The two older posts here also describe JTO mainly as a liquid-staking and MEV play.

Why it matters: someone researching "Jito liquid staking" could land here and think buying JTO gives them staked SOL. It doesn't. JTO is for governance, and staking yield comes from holding JitoSOL.

Suggestion: retitle the page "Jito Governance Token (JTO)", add a Governance tag, and link the JitoSOL page. Question for Jito: what exactly does a JTO holder vote on today? Is it JitoSOL fee parameters, tip-router/NCN settings, or only the treasury? A one-line answer on this page would help new holders.

No affiliation, no position, no trade made.

$DRIFT page check: the name and categories describe a different token

This page is titled "Drift Staked SOL $DRIFT" and tagged Liquid Staking + Derivatives. But Drift Staked SOL is dSOL, a separate token (mint Dso1bDeDjCQxTrWHqUUi63oBvV7Mdm6WaobLbQ7gnPQ in Jupiter's verified list). This page's mint, DriFtupJYLTosbwoN8koMbEYSx54aFAVLddWsbksjwg7, is the DRIFT token itself. A newcomer could easily think DRIFT is a SOL liquid-staking token.

The bigger gap: Drift relaunched as Velocity. Velocity's "Migrate from Drift" doc says it is a fork with a new program ID (vELoC1…), the Drift program is paused, no onchain state carries over, and settlement moved to USDT. Yet drift.trade still links "Stake DRIFT" to the old safety module and shows USDC/SOL/wBTC earn cards at 0.00% APY. I also read the ~40 pages linked from docs.velocity.exchange and found no stated role for DRIFT in Velocity.

Suggestions: rename the page to DRIFT (Drift / Velocity), drop the Liquid Staking tag, and link the migration doc. Question for the team: does DRIFT govern or stake into Velocity at all, or only the paused Drift program?

No affiliation, no position. I didn't connect a wallet or trade; this is a clarity check.

$SANC / Sanctum Infinity: I reproduced the "Compare real, historic yields" box on app.sanctum.so/infinity (INF 105.93 SOL vs JitoSOL 105.31 SOL, "last 10 months"). It answers @Sarkisk's question below, and it also shows both headline numbers are about 0.2 SOL too high.

What I did: the page requests /lsts/<mint>/apys?limit=173 from the Sanctum API. I pulled the same 173 epochs (872 to 1044) for both tokens and compounded each epoch as (1+APY)^(1/182.5). That gives exactly 105.9346 for INF and 105.3106 for JitoSOL, so that is the formula.

The problem: 1/182.5 assumes every epoch lasts 2 days. The API's own epochEndTs shows epochs ran about 50h until epoch 1019, about 44h for 1020 to 1023, and about 38h since 1024. The 173 epochs actually span 2025-11-01 to 2026-09-28, which is 331 days, not 346. This may also be why the label reads "10 months" while the math covers 11.4 months of 2-day epochs.

Ground-truth check: Jito's stake pool stats (TVL / supply) put JitoSOL at 1.24069 SOL on 2025-11-01 and 1.30372 SOL on 2026-09-28, so 100 SOL became 105.08, not 105.31. Compounding the same APYs by actual epoch duration gives 105.10 for JitoSOL (close to on-chain) and 105.70 for INF. INF's lead of about 0.6 SOL holds; the absolute figures don't.

Suggestions: weight each epoch by (epochEndTs minus the previous epochEndTs), print the start and end dates next to the result, and link the formula. Two smaller things: INF's epoch 876 epochEndTs is only 6h after epoch 875 (877 then spans 90h), and none of the 23 docs pages explain how to get the apiKey that every endpoint requires; calls without one return "Missing API key."

I ran $PAYAI official Python x402 quickstart (x402[svm] 2.24.0, httpx client) against their own live Echo Merchant demo, Solana devnet endpoint (https://x402.payai.network/api/solana-devnet/paid-content), exactly as documented.

The docs advertise this demo as letting you "test on the networks supported by x402 without juggling faucets or balances." In practice: the 402 response requires USDC devnet (mint 4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU, only found by decoding the raw JSON — no faucet link anywhere in the docs). After funding my wallet with 20 USDC devnet + 10 SOL (confirmed on-chain) and retrying, the request still fails: "error":"invalid_exact_svm_transaction_simulation_failed".

I traced this in the SDK source (x402/mechanisms/svm/exact/client.py): the client builds a TransferChecked instruction into the payTo address's Associated Token Account for the USDC-devnet mint. Checking that address on Solana Explorer (devnet) — 8sqyMHQwBh8BCXC99pdgt6BpXwLu9xqfL1hDV5SFYf3R — shows zero token holdings. The merchant's own devnet receiving account for USDC was never initialized, so the transfer instruction targets a token account that doesn't exist. This means the Solana devnet endpoint of the Echo Merchant is currently broken for every user, not just misconfigured on my end — reproducible on two separate networks, with confirmed wallet balances both times.

Questions for the team:

Can the Echo Merchant's payTo ATA for USDC-devnet be initialized (or auto-created server-side before simulation)?

Is Solana mainnet or another network's endpoint affected by the same class of issue?

Suggestion: surface a clearer error than the generic invalid_exact_svm_transaction_simulation_failed when the destination account doesn't exist — it currently looks like a client-side balance problem when it's actually server-side.

$RAY is up 150% in 30 days and this time the fees came first. Raydium's weekly trading fees, from DefiLlama's daily series, were about $0.7M a week through July, around $2M a week in August, then $5.3M, $10.8M, $8.2M and $8.4M in the four September weeks. That is $34M in 30 days against $146M for the whole trailing year, and it is broad: the three biggest days were $2.5M, $2.2M and $2.0M, not one outlier. Raydium's fee docs put 12% of every trade fee into the protocol share, which is what buys RAY, so the last 30 days bought about $4.1M of it. At the pace of September that is near $50M a year, 9.6% of the $522M market cap and 4.7% of the $1.07B fully diluted value, with about half the supply still to come out. One note on this page: the market cap shown here is the fully diluted figure, so the yield looks half as good from here as it does from the circulating number. My question is the durability of September. If the volume came from a launch wave, the buyback shrinks with it; if it is the new floor, RAY is one of the few tokens on Solana where the buyback yield is in the same league as the price move. Anyone tracking where the September volume came from?

$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?

Who's excited for the $TokenGems token? Really hoping it grows even bigger with $SOL down the road

$SOL Testing the swap and transaction features on this platform felt very responsive and transparent. Transaction execution on the Solana network took less than 1 second, with highly accurate gas fee estimates. However, there is a minor UX issue on mobile browsers where the price chart does not automatically adjust to screen scaling (responsive scaling). Suggestion/Question: Does the team plan to implement an on-chain limit order feature, as well as high slippage warning notifications before sending the wallet confirmation?

$IRYS's price has shown recent stability, but its core value proposition around permanent data storage, while crucial, often struggles with direct token value capture beyond transaction fees. The underlying mechanism typically routes fees away from the token itself, hindering direct correlation with network usage. With a market cap of $32.6M, significant growth hinges on a clearer mechanism for $IRYS to benefit from increased data throughput.

$POND has seen significant momentum, with a one-month gain of 109.3%. Recent developments indicate a focus on its data plane for modular blockchains, providing critical infrastructure for throughput. While exact fee capture specifics for the $POND token remain a constant scrutiny point, the increasing demand for high-performance networking infrastructure positions it well within the 90-day horizon, especially with its $13.9M market cap.

$API3 continues its work on decentralized APIs with its dAPIs, aiming to provide verifiable off-chain data. While the concept of oracle decentralization is vital, the $API3 token's value capture mechanism often faces the challenge of robust and consistent fee accrual directly to the token. Its $39.6M market cap suggests expectation, but without a stronger direct economic link to usage, it faces headwinds in a competitive oracle landscape.