- @HarryzonalGovernance+2•3
$JUP is a gem
One thing I noticed about $JLP is the contrast between its 72.18 TokenGems score and the nearly split Gem Hunters sentiment (52% Gem, 48% Rug). A high score doesn't necessarily mean low risk. It would be useful to see how the score weighs liquidity, holder concentration, and the risks of providing liquidity to perpetual trading. More transparency here could help users make better-informed decisions.
- @n3vrrmoreGovernance+2•3
$JUP is a gem!
I explored Jupiter's SOL to USDC swap interface using a 1 SOL quote without connecting a wallet.
One thing I noticed is that the JIT routing label (such as "BisonFi +3") changes as quotes refresh.
I also read Jupiter's JIT Swap documentation. The statistics are interesting: 26.89% of swaps used a different set of pools, and 57.82% of same-pool swaps had their allocations rebalanced.
However, the interface doesn't clearly explain what "+3" represents or how users should interpret the changing provider names.
My suggestion would be to add an expandable breakdown of the candidate venues, along with a short explanation of how JIT routing affects execution compared with the displayed quote.
This could make a technically impressive feature much easier for everyday users to understand.
- @SolanoDEX+1•2
$MET is a gem! I checked MET on-chain before trusting the labels on this page, and two of them I can't interpret or reproduce.
What's verified: both the mint authority and the freeze authority are renounced (None / None), and total supply is 997,732,177.39 MET. So the ~$379M market cap here is total supply x price, i.e. fully diluted. That confirms @alessiosol's suspicion from yesterday: the docs put roughly 480M circulating at TGE, so FDV is doing a lot of work in a number most readers will take as float value.
Two labels I couldn't act on:
1. "Entropy 0.261". The FAQ says the 0-100 score is computed from price performance, holder distribution, trading volume and community activity - but "Entropy" isn't defined anywhere I could find, so the score can't be reproduced. Is it a Gini, a top-10 share, or an entropy over holder buckets? And are AMM pool vaults excluded? On a token whose liquidity sits in DLMM bins, vault balances are not whales, and including them would move the number a lot.
2. "Gem Hunters Sentiment: Gem 52% / Rug 48%". On a token with both mint and freeze authority renounced, a 48% rug reading is surprising enough that I want to know what it measures - how many wallets voted, over what window, and what a "Rug" vote means here (contract risk? price? team?). If it's a handful of votes, presenting it as two large percentages beside a 75/100 score implies far more signal than exists.
Smaller one: the token list shows $2.82M of 24h volume for MET, while across the 30 MET pairs on DexScreener I measure about $19.2M - including $8.7M in a single MET/JUP pool holding only ~$200k of liquidity. If that row is scoped to DAMM v2 pools only, it doesn't say so, and someone screening by volume would read MET as roughly 7x less traded than it is.
(On-chain figures read from the Solana RPC, DEX figures from DexScreener, with AI assistance on the data collection.)
- @qwdfmMeme•4
$Moolah is tagged "Meme", but the concept ties back to ListaDAO's mascot, and the posts here describe a studio subsidy program in internal beta. That's an odd mix — meme as distribution, DAO as retention.
The problem: nothing on this page lets a reader verify which part is real. No link to the DAO, no treasury address, no doc. With sentiment sitting at 52/48, the market is clearly unsure too.
Can you add a source link and one plain line on what's actually live?
- @gamesdroidesCompute•1
$NOS The official Endpoints tutorial has a reproducibility mismatch in its market selection. Step 2 posts the Ollama job to market 97G9NnvBDQ2WpKu6fasoMsAKmfj63C9rhysJnkeWodAf, but the sample CLI output directly below points to 7AtiXMSH6R1jjBxrcYjehCkkSF7zvYWte63gwEDBcGHq. Nosana's Quick Start explicitly calls 7Ati... "Market 3060", while the Stable Diffusion RTX 4090 example resolves the nvidia-4090 market to 97G9....
Because the market controls GPU class and NOS/s price, a reader can follow the command but see output for different hardware and cost assumptions.
Suggestion: regenerate the Endpoints sample output from the same 97G9... market and show a stable GPU label (RTX 4090 / RTX 3060) beside each market address.
Question: which market is intended for this tutorial today - 97G9... or 7Ati...?
- @AddushaMeme+1•2
$SI is a gem! The on-chain metrics layout for $SI on TokenGems is very clear, especially having the entropy score (0.625) and holder distribution (51.9k) directly visible next to sentiment. It would make user analysis even better if there was a direct link to check top 10 wallet concentration or liquidity lock status on Solana directly on this dashboard. Overall, clean UI and responsive data tracking!
- @gamesdroidesGovernance•1
$JTO I compared Jito's official (Re)staking docs and found a fee mismatch that can change a user's exit-cost estimate. The (Re)staking Overview lists a 0.1% (10 bps) withdrawal fee under program fees, while the Withdrawal Guide says a standard withdrawal incurs both a 0.1% withdrawal fee and a 0.1% program fee - 0.2% total - before any additional vault-specific withdrawal fee. The Deposit Guide also says a 0.10% program fee applies on withdrawals.
On a 1,000-unit withdrawal, that is the difference between budgeting 1 unit and 2 units before vault-specific extras. Suggestion: use one canonical fee breakdown everywhere - program fee + vault withdrawal fee + any additional vault fee - and show a worked example with the current values.
Question: is 0.2% the intended standard baseline, or is the Withdrawal Guide double-counting one 10 bps fee?
- @kingintheNorth1Meme•2
$HYPE is a gem!
- @NerionDevGovernance+2•4
$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
- @mujahid-devWrapped+1•5
$hSOL Note: The only Helius page on TokenGems is for $hSOL, so I'm reviewing Helius the company's developer infrastructure (RPC + DAS API) here. My feedback is about their RPC product, not the staking token itself.
$HELIUS — tried the RPC + DAS API as a developer, with PowerShell and a free key (Oct 12, 2026). Three things stood out:
1. Error response format is inconsistent between protocol and auth failures.
A malformed JSON-RPC request returned proper structured JSON:
{"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"}
But an invalid API key returned HTTP 401 with a plain-text body — literally just "Unauthorized", 12 bytes, no JSON, no error code, no docs link. Client SDKs handling auth failures have to string-match instead of reading a status code. A structured {"error":{"code":401,"message":"Invalid API key","docs":"..."}} on the auth path would make error handling consistent across the API.
2. DAS getAsset works on the free tier — but the docs don't say so clearly.
I tested getAsset for USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v) and got the full asset response: interface=FungibleToken, last_indexed_slot, full token metadata. It worked. But when signing up, I couldn't tell whether DAS was available on Free or gated behind a paid plan — the pricing page says "Enhanced APIs" without a per-method breakdown. A one-line note ("getAsset, getAssetsByOwner, and X other DAS methods are available on Free") would save devs from guessing.
3. The free tier is more permissive than the docs imply.
I ran 30 sequential getAsset calls and then 20 concurrent getAsset calls on the free plan. All 50 returned 200. No 429, no Retry-After, no throttling. Either the limit is higher than expected or it's enforced differently than the docs suggest. Publishing the actual RPS ceiling per plan on the Usage page would let devs build confidently instead of guessing whether a burst will fail.
Question for the Helius team: Is the free tier's DAS rate limit enforced per-second, per-minute, or only on credit consumption? And can the auth error path be upgraded to return structured JSON like the rest of the RPC?
Scope: public RPC via PowerShell Invoke-RestMethod + free-tier dashboard + docs, Oct 12, 2026. Free plan API key used, no paid upgrade. No affiliation with Helius.
Tagging $hSOL since this is its token page — the review itself is about Helius's developer products, not the staking token's mechanics.
- @MR_DUCK123oUtility+1•5
$HONEY
I reviewed Hivemapper's documentation. Came across an interesting problem with mapping areas that don't get much attention.People who contribute might take pictures in places where not many others go. Checking those pictures can take more time because there aren't enough other pictures to compare with.
My idea is to create a visible contribution-status dashboard that shows if imagery is waiting to be checked, needs to be reviewed for quality, or has already been approved for rewards.
This would help people who contribute understand why there are delays without revealing how the anti-fraud systems work.
Does Hivemapper have a way now to tell the difference between delays caused by verification and issues related to quality?
This is based on reading the documentation, not on using the camera myself. I'm not part of any project.
- @bdrexBridge•5
I explored Wormhole $W because of its ability to transfer assets between Solana and other supported networks, and my experience was encouraging. My transfer on Solana arrived in less than a minute, making the process feel fast and straightforward.
I also explored WormholeScan, which provides useful visibility into cross-chain transactions, transfer volumes, popular protocols, and frequently transferred assets.
One thing I appreciated was how Wormhole combines cross-chain transfers with tools for exploring network activity. The explorer makes it easier to understand what's happening across different networks rather than treating every transfer as an isolated transaction.
I also learned that some stuck CCTP transfers cannot be redeemed through Portal because another application or smart contract has exclusive permission to complete them. In such cases, users need to return to the original application to finish the transfer.
Could $W Wormhole improve this recovery experience by explaining why Portal cannot complete a particular transfer and directing users to the application responsible for finalizing it? This could help users understand what went wrong and what to do next, especially when moving assets between Solana and other supported networks.
Overall, I appreciate the work the Wormhole team has put into making cross-chain transfers accessible and providing visibility into activity across different networks. My experience with the fast Solana transfer was positive, and clearer recovery guidance could make an already useful experience even better.
Thank you to the Wormhole team for building and continuing to improve cross-chain infrastructure.
- @LinMaloneGovernance+2•4
$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.
- @kirivchUtility+1•4
$PSOL Today I spent more time finding Phantom’s browser than connecting my wallet.
I already had Phantom installed on my iPhone. When I tried connecting from TokenGems on my computer, I ended up on the Chrome extension page. So I switched to the phone, opened Phantom and started looking for a browser tab, a globe icon, or anything that suggested I could open a website.
I couldn’t find it.
Only after checking the instructions did I understand that Explore/search is also the browser and accepts website addresses. Once I pasted tokengems.ai there, the actual connection was quick and painless.
This is probably obvious to an experienced Phantom user, but it wasn’t obvious to me as someone setting it up for the first time. Nothing was technically broken; I simply had no idea where to enter the URL.
Even a small wording change such as “Search tokens, apps, or paste a URL” would have helped. A visible “Open website” shortcut would be clearer still. An iOS “Open in Phantom” share action could also prevent users from being sent to an extension installation page when the mobile wallet is already installed.
I’m posting this under $PSOL because it’s the Phantom-related Solana page available on TokenGems. This is feedback about the mobile wallet experience, not PSOL’s price. I only tested the connection and did not deposit, trade, or make a transaction.
- @Asghar.10xMeme•3
$baton I've been digging into the Score since it's the first thing my eyes go to on the leaderboard. On this page it shows 58.18, and credit where due — the FAQ does list the inputs: price performance, holder distribution, trading volume, and community activity. But that's where it stops: no weights, no refresh cadence, nothing on whether it's backtested. For a metric positioned as the headline "alpha" signal, I still can't tell how much each input matters or how fresh the number is. Publishing even rough weights plus the refresh interval would turn the Score from something I stare at into something I can actually reason about. (Side note: /docs on this domain still 404s, and the footer DOCS link goes to an external placeholder page.)
- @Asghar.10xMeme•3
$baton Small data-quality thing I noticed on this page: the header shows 22,982 holders, but the post below it quotes 22,938, and the FAQ rounds the price to $0.02 while the header shows $0.01548. None of these alone is a deal-breaker, but together they leave me unsure which number is current. A tiny "updated Xs ago" timestamp per metric — or at least consistent rounding rules — would go a long way on a platform whose whole pitch is reliable token data.
- @Asghar.10xUtility+1•4
$ZEUS The ENTROPY figure (0.3947 here) caught my eye because I'm not sure what I'm supposed to do with it. There's an info icon next to the label, but hovering/clicking it surfaced no explanation, and I couldn't find entropy defined anywhere in the FAQ. A raw number with no one-line plain-English definition — and no companion metric like top-10 holder share — doesn't help me judge distribution risk. The leaderboard even calls this same metric "HOLDER DISTRIBUTION", so the naming itself seems unsettled. One line of explanation next to the figure would make it 10x more useful.
- @BoldnfaMeme+3•5
$BORT The part of BORT I like most is the custody design. Putting funds in each agent’s ERC-6551 wallet, with capped, expiring, revocable spend grants, means the worst case is bounded by what the owner granted. My question is about the layer those caps don’t cover. Hunter agents read signals from public Telegram groups and X, then trade on them, a pump group or a coordinated account can post a “signal” written to push a model into buying a token. So what sits between a scraped signal and an executed trade?
Is there a minimum liquidity or holder-distribution check before a buy?
Is there a per-token position cap that’s separate from the overall spend cap?
Can an owner require manual approval above a set size?
The docs say a third-party audit hasn’t been published yet. I appreciate that honesty. When it happens, I’d like the scope to cover the runtime and signal-handling logic, since that’s where most of the risk is.
- @ofnirGovernance+9•4
My last call on $XCAT was a RUG at $0.00000006003, and it fell to $0.0000000441. With liquidity at $31M and a flat week, $XCAT remains a RUG.
I called a RUG on $BONE at $0.05139008422130166, yet it rose to $0.06049794440738539. It has held its price this week but liquidity is under $2M, so I still see $BONE as a RUG.
My RUG call on $FLOKI at $0.000027591087459612185 was accurate as it settled at $0.000026161871496268518. Despite $260M market cap, its price is down this week. $FLOKI is a RUG.
I called a RUG for $TRUMP at $2.1379981426208357, and it fell to $2.0460662132859038. With $93.7B liquidity and a -6.2% week, $TRUMP remains a RUG.
My RUG call on $PEAR at $0.039865904381739634 proved correct as it dropped to $0.03144950048622106. Its -11.7% weekly decline continues; $PEAR is a RUG.
- @bdrexMarketplace•3
$WHALES Market allows users to trade token allocations before TGE through its Pre-Market, with collateral and settlement rules governing how these transactions are completed.
I explored the REYA market, opened the Resell section, and reviewed the Resell Position documentation and settlement rules to understand how buyers can exit positions before settlement.
I like that Resell gives buyers another option instead of having to wait until settlement. However, I noticed a potential risk: according to the documentation, if a token's liquidity pool is never created and trading is cancelled under the specified circumstances, a buyer who purchased a resold position could receive less than they paid.
The documentation illustrates this with a buyer paying $900 but receiving only $500 back, resulting in a $400 loss.
My suggestion is to display a clear warning before buyers confirm a resell purchase, explaining this cancellation scenario and the potential financial loss. This would help users understand the risks before committing their funds.
Overall, I appreciate how Whales Market provides more flexibility for trading token allocations before launch. The Resell feature is a useful addition, and making its risks clearer could make the experience even better for users.
Thanks to the Whales Market team for building the platform and giving users more ways to participate in pre-market trading.
- @1cwtGovernance+2•2
$JUP — I previewed a 100 USDC → SOL swap on desktop without connecting a wallet and toggled “Use V1 transactions.”
The tooltip explains that V1 can change routes and estimated output, and recommends switching to V0 if signing fails. With the switch off, the visible label still says “Use V1 transactions.”
Suggestion: show “Transaction format: V0” when off and “V1” when on, alongside a wallet-compatibility help link. This would make the active format and fallback clearer before connecting.
Read-only review; no swap or signing attempted. AI assisted with wording.
- @arbeiter•3
$BBSPre-launch is a gem!
Checked the BlackBitSwan eAI launch page and docs.A few practical notes from testing the flow:
- The signal preview shows automated triggers, but doesn't specify default slippage or which DEX router it uses (Jupiter vs Raydium). On Solana during high volatility, failed txs will be an issue without clear execution guards.
- The utility tiers for $EAI could be clearer upfront. Would be great to see past backtesting data for the AI signals directly on the demo page so users can actually verify accuracy before staking.
What I checked: launch page, docs, demo layout.
Affiliation: None.
- @demiurgeOracle•3
I tested the $PYTH Pyth Playground with BTC/USD and SOL/USD using the shared demo-token flow.
The API Key field says it can be left empty to use a rate-limited demo token, but pressing Run with the field empty returns:
“Invalid API key. Check the key you pasted and try again.”
I reproduced this twice, including after a hard refresh.
For a new developer this is confusing because the UI explicitly suggests that no API key is required for testing. It would be better either to fix the demo-token fallback or show a clearer message if the shared demo token is temporarily unavailable or rate-limited.
- @AlikaliGovernance+1•3
$ORCA is a gem!
Orca's Position Simulator keeps crediting yield at out-of-range prices — with no warning.
I explored Orca's Whirlpool Simulator as a logged-out visitor today (no wallet connected). On the ORCA/SOL 0.16% pool Simulator tab, I set a ±5% position (range 0.0204391–0.0226066 SOL per ORCA) and dragged the simulated price down to 0.0201 — below the range floor, leaving the position 100% one-sided. The panel still displayed "Estimated Yield Earned 13.65%", "LP Opportunity Cost 2.40%", "LP vs. HODL +11.25%" with no out-of-range indicator or banner.
That contradicts Orca's own documented rule: "Your position does not accrue swap fees while it is out of range" (beginner guide), and the marketing site's "Your position earns swap fees only while it's in range." The "Time In-Range" D/H input is fully decoupled from the simulated price path — it assumes the position stays in range for the specified time even when the user drags the price outside it. A first-time LP could reasonably walk away believing an out-of-range position keeps paying.
Suggestion: when the simulated price exits [min, max], show an inline banner ("Simulated price is outside your range — this position would earn no fees here") and either zero out Estimated Yield Earned or annotate it as assuming price returns in range. Better: derive the in-range portion from the simulated price path instead of the decoupled Time In-Range input.
Acceptance check: drag the simulated price outside the range — the panel must either show the warning or stop crediting yield.
Scope: logged-out read-only exploration on 11 Oct 2026; I did not connect a wallet, create a position, or transact. AI assisted with drafting.
Sources:
- https://www.orca.so/pools/Hxw77h9fEx598afiiZunwHaX3vYu9UskDk9EpPNZp1mG (Simulator tab)
- https://docs.orca.so/liquidity/getting-started/beginner-guide
- @VelocityMeme+1•2
$SI is a gem!WHEN I OPENED THE $SI ON SOLANA, BUYERS HAS TO HOLD A TOKENIZED STOCK FIRST BECAUSE THE TAB ONLY SHOWS (1) ONE POOL [NVDAx/SI ON Raydium, WHICH MAKES IT HARDER TO VERIFY TEAM, THE WEBSITE BUTTON ON THE TRADE PAGE DIDN'T LOAD FOR ME I TRIED IT 3+ TIMES.
CAN THE TEAM ADD A WORKING SITE LINK AND A SI/USDC POOL?