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

$SWCH I reviewed the Switch Board ($SWCH) listing, and the idea of an OpenAI-compatible AI inference router that can auction requests to find cheaper and more reliable LLM execution is interesting, especially for developers who want one API instead of managing multiple models. However, I noticed a few areas that could make the project easier to trust and understand. The $SWCH name and ticker can easily be confused with Switchboard ($SWTCH), so clearer branding or verification on TokenGems would help prevent users from mixing up the two projects. I also couldn’t find enough visible developer documentation, such as a live API demo, SDK quickstart, or clear benchmarks, to easily verify the inference-routing concept. Finally, the utility of $SWCH itself isn’t clearly explained—there’s no obvious information showing whether the token is used for inference fees, staking, governance, or developer benefits. Adding clearer product documentation and explaining the token’s role would make the project much easier for both developers and new users to evaluate.

$TNSR I tested Tensor as a first-time user through the Stonk Cats collection, and overall the core trading experience felt smooth, especially the execution and balance checks when placing a buy or bid. However, I noticed a few areas that could make the experience much better for new users. The biggest issue was the Crossmint card checkout, which immediately failed with a “previously deleted API key” error while the payment form still remained open. If card payments are meant to help non-wallet users onboard, this could create a major drop-off. I also couldn’t clearly understand what holding $TNSR actually provides from the marketplace experience, so adding a simple explanation of its utility or benefits could help connect the token with the product. Finally, clearer verification badges in collection search would help users distinguish official collections from similarly named ones. These are relatively small changes, but fixing them could make Tensor more accessible and less confusing for first-time users.

I explored $PAYDAY through TokenGems and followed its linked social accounts to verify the project information. The X link from the TokenGems listing points to @getpaydayfun, but X shows that this handle was changed 7 days ago and directs users to @owedfun instead. I also checked $Payday documentation, where @getpaydayfun is still referenced. Could the project update its TokenGems X link and documentation to reflect the current X handle, so new users don't end up on an “account doesn't exist” page?

$TNSR I used tensor.trade as a new user (Stonk Cats), without buying.

The homepage is already a trader table (floor, sell now, mcap). Lite vs Pro is asked only after you open a collection. Rewards is Tensorians / Referrals / Gib Back — the word TNSR never appears. TokenGems' website icon goes to tensor.foundation, not the marketplace. I still cannot tell what holding TNSR does versus using the app.

Search for "Mad Lads" lists Mad Scientists, Mad Lassies, Mad Skull, Mad Ladios and others with no clear verified mark.

The wallet modal lists MetaMask twice.

Price filter default max on Stonk Cats was 101010 SOL (floor was ~2.1).

Sweep → Pay with Crossmint opened hosted checkout for 21 items / ~54 SOL and failed immediately: "The API key provided was previously deleted, please create or use a valid key." Popup stayed on the card form anyway. If card checkout is meant to onboard non-wallet users, a dead API key is a hard stop.

Buy/bid Execute correctly blocked me at 0.0019 SOL (listing 2.07, royalty 2.5%, taker 0.040). Could Rewards or the token page state in one line what TNSR is for, and can Crossmint be hidden until the key works?$TNSR is a gem!

$GEM is a total gem! 💎

Just checked out the analytics on tokengems.ai and the on-chain metrics look incredibly solid. The holder distribution score is wide and the 24h trading volume shows massive organic momentum.

@Kodec

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

$MNDE

Was checking out Marinade Liquid today. Connected my wallet (MetaMask, Solana) but haven't staked anything yet. The first thing I wanted to know was how much it costs to get out, and the Unstake tab just says "No positions to unstake". So you can't see the exit fee or how long it takes until you've already deposited. Kind of odd when the homepage says "instantly unstake... no platform fees".

Then I went to the docs and found two answers. The Instant Unstake page says delayed unstake is free for Native, but the Fees and Pricing table says 0.003 SOL flat for Native delayed unstake. Which one is right?

Would be nice to see the fees on the Unstake tab even with an empty wallet (0.2% and about 1 epoch for mSOL delayed, plus the rough instant range), and to fix one of those docs pages. Also a small thing: the same APY shows as 5.01% on the chart and 5,01% in the stake box.

$HNT public-site walkthrough (AI-assisted; no trade): TokenGems links to Helium, and the Solana mint here matches Helium's HNT docs. The HNT page clearly explains carrier offload → HNT burns → deployer rewards. One practical break: its “Buy or sell HNT” button opened https://www.helium.com/plushttps://www.coinbase.com/en-pt/price/helium, which showed “Page Not Found” when checked on September 29. The URL appears to concatenate a Helium path with a Coinbase URL. Please point the button to the intended destination and check it from the public page; if availability varies by country, explain that beside the button. No purchase or trade was made. Reproduction steps and screenshots: https://github.com/Tiee7/tokengems-helium-feedback

$PAID

Your Capital Flow page shows the 20% protocol allocation moving through several stages before becoming a buyback and burn. I like that the flow separates these steps instead of presenting the allocation as an already completed burn. How do you handle periods where fees are accumulated but market conditions or execution constraints delay the buyback?

$SOLCAT is a gem!I compared a few small Solana tokens on TokenGems and Solana Cat (SOLCAT) stood out: it shows about $208,621 of 24h volume against a market cap of roughly $144,032. That is more than 100% of its market cap traded in a single day, which usually means either a very active community or heavy short-term churn and bot activity.

With 3,290 holders and a holder-distribution score of 0.61 the base looks wide and spread, but the page does not tell me which of the two explanations is true. A simple turnover metric (24h volume / market cap) plus a unique-traders count would make it obvious whether the activity is organic. Is that something the page could show?

I price prediction markets that settle on $PYTH spot, so today I went to pull XAU/USD and SOL/USD from Hermes at a few weekend timestamps to see how the metals feed behaves while COMEX is closed. I never got that far. hermes.pyth.network, hermes-beta, benchmarks.pyth.network and the upgraded pyth.dourolabs.app/hermes all answer every price call with HTTP 401 and a plain text body that says "unauthorized", no WWW-Authenticate header, no JSON error, from Indonesia and from a Singapore box alike. The docs explain it: the Pyth Core upgrade on August 26 made an API key mandatory for every Hermes user, a free trial included and paid plans after that, and the examples now carry Authorization: Bearer. Two things for the team. /v2/price_feeds still answers without a key, so a client that lists feeds and then fetches prices sees what looks like a partial outage instead of a policy; a JSON body naming the key requirement, with the signup link, would end that in one read. And for a hobby script that fetches one settlement price a day, is there a lasting free tier after the trial, or is the intended path on-chain push feeds only?

$SOS is a gem!I compared several Solana tokens on TokenGems and Solana Swap (SOS) stood out for an unusual reason: it shows around 16,647 holders, but only about $1,400 of 24h volume against a $211K market cap. That combination usually means a wide, possibly airdropped holder base with almost no trading activity rather than organic demand, and its holder-distribution score of 0.73 points the same way.

What I would like to see on the page is a simple holder-activity split: how many of those wallets have traded in the last 30 days, plus the top-10 concentration. That single chart would separate a real community from a passive snapshot. Could that be added?

I built a browser NFT drop tool on an SVM chain that runs Token Metadata at the same program id (Cookie Chain), so this is your $MPLX program, tested off Solana mainnet. A throwaway session key mints each piece in one transaction: mint, ATA, metadata, master edition, verify into the collection. Two findings. Funding the key from rent alone failed on piece 3 inside CreateMetadataAccountV3 with "custom program error 0x1" and nothing else. The cause was the 0.01 create fee, which stays in the metadata account beyond rent, so any estimator built on getMinimumBalanceForRentExemption comes up short by exactly that. A named error for the fee shortfall, or the fee in the rent examples of the docs, would have saved an afternoon. SignMetadata costs 12.4k to 12.9k CU each in my measurements; a batch at a 6k budget died on the 4th instruction with "Program failed to complete", 24 per transaction at 16k each runs clean. I could not find CU figures in the docs. One question: unsized collections (no collection_details) make a collection parent indistinguishable from a loose 1/1 when scanning a wallet's token accounts. Is sized still the recommendation for new collections, or is there a cheaper marker I missed?

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.

$HONEY : I searched Abuja, Nigeria in Hivemapper’s Coverage Explorer. The map centered correctly and I could see coverage around Wuse, Garki and Gwarinpa, but the sidebar only showed global numbers like 785M km mapped, 38% global road coverage and 23M unique km.

Since HONEY rewards depend on regional progress and tile freshness, it would be useful to see more local data after searching a location — things like local coverage %, imagery age and the current tile reward multiplier. A “plan a high-priority route” option would also be useful for contributors who want to know where their next drive could add the most value.

$PYTH

I trade XAUUSD, so I went through Pyth Terminal's two gold feeds: XAU/USD (spot, "Regular" coverage) and the GOLD 24/7 Pyth Index.

1. Holidays are hidden in the UI. The XAU/USD "Data Coverage" panel only shows the weekly schedule (Mon-Thu 00:00-17:00 & 18:00-24:00 NY, Fri to 17:00, Sun from 18:00). But the feed's JSON has the real exceptions: 26 Nov closes 14:30, 27 Nov closes 14:45 with no evening session, 24 Dec closes 13:45, 25 Dec and 1 Jan closed, 26 Mar closed. A perp or lending protocol reading only the panel would miss these. Suggestion: add an "Upcoming session changes" row under the schedule.

2. The GOLD 24/7 index is marked always open with min_publishers = 1, and the page shows a disclaimer but no methodology link. Questions for the team:

- When spot gold is closed (Fri 17:00 to Sun 18:00 NY), what inputs set the weekend price?

- At the Sunday reopen, does the index jump to XAU/USD, or converge over time? Weekend gaps are exactly where leveraged gold positions get liquidated.

- What does min_publishers = 1 mean here: one data source, or one aggregator?

A short methodology page linked from the feed would make this index much easier to trust for gold perps on Solana.

$UNTAXED is a gem!I looked at $UNTAXED on TokenGems. The promise is zero-fee trading on Solana, and the page shows the metrics clearly: market cap around $3.8K, 361 holders and an entropy score of 0.13.

The question I could not answer is how the project earns money if trading is free. Is it spread-based, or is there a paid tier or token utility? A short "how we earn" section would make the zero-fee claim much more credible.

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