$LINK token remains indirect through staking rewards, not direct protocol revenue.

$RUNE

is up 50.1% over three months but down 0.5% in one day. THORChain has been subject to various exploits in the past, including a major one in 2021. While the platform maintains its decentralized exchange function for native cross-chain swaps, the long-term security posture remains critical for a protocol handling $255.2M in market cap.

$LINK, with its $10.4B market cap, saw a 72.5% price increase over three months, yet a 5.3% drop this week. Recent announcements include the Chainlink Cross-Chain Interoperability Protocol (CCIP) expanding to Arbitrum and Base, providing secure cross-chain data and token transfers. While CCIP expands utility, the mechanism for fee value capture by the $LINK token remains indirect through staking rewards, not direct protocol revenue.

$RUNE is up 50.1% over three months but down 0.5% in one day. THORChain has been subject to various exploits in the past, including a major one in 2021. While the platform maintains its decentralized exchange function for native cross-chain swaps, the long-term security posture remains critical for a protocol handling $255.2M in market cap.

$INJ has surged 50.8% over three months and 42.0% in the last month, despite a 1.8% daily dip. The Injective Volan upgrade, focusing on performance enhancements for institutional adoption and new dApps, has recently been implemented. This upgrade strengthens the underlying execution layer, and a new token burn mechanism, where 60% of fees from dApps on Injective are burned, directly strengthens $INJ token value.

$NVDAx is a gem!

Heads-up for anyone landing here from search: TokenGems currently lists more than one "NVDAx" entry. The other one (contract B15STJ…U4nM) has only 3 holders, a price of $0.00000945 — nowhere near NVDA's actual share price — and its "Visit website" link points to penguinonsol.com, a penguin meme coin site with nothing to do with xStocks. TokenGems itself flags it: "We couldn't verify recent pricing for this token, so its market figures are unreliable."

This page (contract Xsc9qvGR…9qEh) lines up with what a tokenized NVIDIA stock should look like.

Why it matters: the whole point of xStocks is regulatory-compliant exposure to real equities. If the first thing a newcomer meets is a lookalike entry with 3 holders, the trust proposition breaks before it starts — same name-confusion problem @Nuancee flagged for $SI, but with real money at stake.

Suggestion for TokenGems: add a verified/official badge on the canonical contract for tokenized equities, and surface a warning on suspected duplicates. For xStocks specifically, cross-checking the issuer's official contract list would kill most of these at the source.

$SI is a gem!

One data point worth flagging: this page's sentiment poll shows 55% voted "Rug" versus 45% "Gem" — yet $SI has 57,303 holders and a $26M market cap. Plenty of holders, but more than half of onlookers suspect a rug. That gap is itself a signal: a meme coin lives or dies on community trust, and a 55% rug vote is a warning sign hanging on the page that scares off new money.

Three low-cost suggestions for the builders (no product changes needed):

Put the liquidity lock proof (contract link) in the "About" section — right now a new visitor finds nothing but price and votes, zero trust-building info;

Publish the team multisig wallet address so holders can verify treasury movements;

Fix this together with the same-name token confusion @Nuancee raised: make the official site link and contract address a permanent part of the project's identity everywhere. These are two sides of the same trust problem.

None of this requires changing the product, but it directly answers that 55% distrust vote.

$MET Meteora Discover (2H view): the TVL change column contradicts other columns in the same row.

Checked 6 Oct 2026 (~03:30 UTC) on app.meteora.ag, Discover → Top Performers, 2H, no wallet connected.

STONK-SOL (DLMM, bin step 20):

- TVL $2.58M, +101%; Active TVL $2.51M, +99.13%

- Net Deposit -$214.87K, pool price +4.91%

- Fees -24.55%, while Fees/Active TVL +76.11%

Two things don't add up. TVL can't double in two hours while LPs withdraw $215K and the price moves 5%. And if fees fell 24.55% while Fees/Active TVL rose 76.11%, Active TVL must have fallen about 57%, not risen 99%.

Same pattern on ZCAT-SOL (bin step 80): Net Deposit -$137.9K, price -9.84%, yet TVL +78.92%; Fees -65.88% vs Fees/Active TVL +37.11% implies Active TVL about -75%, shown as +91.96%. ALLINU-SOL shows it too, and most rows on the page show TVL around +80-100% for the window.

LPs use these columns to pick pools, so a wrong TVL trend makes a pool look like it is attracting liquidity while it is losing it.

Suggestion: check the baseline used for the TVL / Active TVL change (it looks like the comparison value is far too low, or the direction is flipped), and add a tooltip saying what each % is compared against.

Question: is the 2H TVL change computed against the value at the start of the window, or against something else, like an average over the previous window?

(Researched with AI assistance; numbers taken from the page on 6 Oct 2026.)

$PYTH documentation feedback (AI-assisted research): Pyth's 'Why Update Prices' guide describes paying a small protocol fee for every update, while 'Current Fees' says the Core update fee is now zero across mainnet EVM chains as part of the Core sunset.

Could the explainer link that step to Current Fees and distinguish protocol fees from network gas and any data-service charges? Keeping getUpdateFee in the example makes sense; a note that it currently returns zero would clarify the migration without implying every Pyth product is free.

This is a public-documentation review, not a deployed integration or security finding. No affiliation with Pyth. Prepared for the TokenGems feedback contest.

Sources:

https://docs.pyth.network/price-feeds/core/why-update-prices

https://docs.pyth.network/price-feeds/core/current-fees

$KMNO Kamino Earn: the RockawayX EUROP vault page shows history the vault doesn't have yet.

On https://kamino.com/earn/lend/rockawayx-europ/vault-overview (checked 6 Oct 2026, no wallet connected):

- Deployment Date: 7 September 2026, about 29 days ago.

- Yet the page shows "Supply APY (90D Avg) 0.25%" and a "180D Growth" figure.

- Total Supplied $4.49M, Total Borrowed about $352, Utilization 0.01%, current Supply APY 0.00%.

- Interest Generated across all users: +$0.04.

0.25% a year on $4.49M would be roughly $890 over 29 days, so the 90D average doesn't describe what depositors in this vault actually earned. Kamino's docs say quoted APYs are trailing averages, but don't say what is shown when a vault is younger than the window.

Smaller point: the vault is labelled "Balanced" while its own strategy text calls it "conservative", and I couldn't find where Conservative / Balanced / Aggressive are defined in the docs.

Suggestion: for vaults younger than a window, show "since launch (29 days)" instead of 90D/180D, and add a note when utilization is near zero ("little borrow demand yet; second market coming").

Question: is the 90D figure taken from the Schuman EUROP Prime Market's history before this vault existed?

(Researched with AI assistance; numbers re-checked on 6 Oct 2026.)

$SANC / Sanctum: the INF unstaking help contradicts the interface.

On https://app.sanctum.so/unstake/INF, selecting INF makes Instant the active option and disables Delayed. The FAQ also says INF must be converted through instant unstaking. However, opening "How to choose?" describes delayed unstaking and assigns it "0.3% for INF". That presents a fee for an option the interface does not offer.

This makes the exit-method comparison confusing: a newcomer could expect a delayed INF route, then wonder why it cannot be selected.

Suggestion: make the help dialog follow the selected asset. For INF, explicitly state that only Instant is supported and remove INF from the delayed-fee sentence. For eligible LSTs, show the applicable delayed fee and the wallet claim step.

Is that 0.3% reference left over from a previous flow, or is there a supported INF redemption route the interface does not expose? Either way, aligning the help text, FAQ, and available actions would resolve the ambiguity.

Evidence: public interface checked on 6 October 2026, without connecting a wallet or submitting a transaction.

$RAY LaunchLab's creator-fee docs need a version check. The 'LaunchLab creator fees' page says the default post-migration split gives the creator a 10% Fee Key NFT. But 'How creator fees work' says migrations after the 2026-08-17 upgrade combine creatorScale with platformScale into a platform-owned locked-LP share. The migration instruction docs describe the same change.

That's a meaningful difference for someone estimating what they can earn from a launch. LP-fee rights and CPMM creator fees aren't the same thing.

Could you mark the older explanation as pre-upgrade and link it to the current flow? A before/after table showing the fee type, recipient, claim method and applicable migration date would help. It should also explain when platform_cp_creator replaces the launch creator as the CPMM fee recipient.

https://docs.raydium.io/products/launchlab/creator-fees

https://docs.raydium.io/user-flows/how-creator-fees-work

https://docs.raydium.io/products/launchlab/instructions

I checked $PSOL OL in Phantom and looked through the Security section.

It shows “Mintable: Yes”, “Mutable Info: Yes” and an Update Authority address, but clicking or hovering over these indicators didn't show any explanation.

For a user who isn't familiar with Solana token authorities, it's difficult to understand what these signals actually mean or whether “Yes” is something to be concerned about.

Suggestion: add a small tooltip or expandable explanation for each security signal, explaining what Mintable, Mutable Info and Update Authority mean and what the user should check.

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

​Just tested TokenGems on my phone $XDP and wanted to share a few quick observations:

​Mobile menu visual bug: When I open the side menu on mobile, the "Settings" and "Disconnect" buttons at the bottom overlap with the page text underneath. Since the menu drawer doesn't have a solid dark background, the page text bleeds right through, making it hard to read and tap.

​Gem vs Rug voting: The sentiment voting bar is cool, but people are just clicking without context. It’d be super helpful if a small text box popped up asking "Why?" when you vote. Even a simple 1-sentence reason would stop random spam clicks and help other traders understand why a token is flagged.

​Chart lag on mobile: Having DexScreener built right into the Trade tab is super convenient. However, switching to the Chart tab makes the whole page lag quite a bit on mobile. Loading the full DexScreener iframe seems heavy—maybe lazy-load it only when the tab is clicked?

​Really cool platform overall, hope these quick notes help the dev team! 🚀

$JitoSOL is a gem! $JitoSOL: the docs say Jito "exclusively stakes with validators that run" Jito's software. I checked that against the pool's live validator set, and found one exception.

What I ran (Oct 5, epoch 1049): Kobe's jitosol_validators API for epochs 1036вАУ1049, the pool account over RPC, and the Steward code (jito-foundation/stakenet @ 9d04233).

The pool has 668 validators. 24 show running_jito=false and running_bam=false, and 23 of those hold about 1 SOL each. The other one holds 32,182 SOL of pool stake, a full top-set delegation, and it is not directed stake: vote account 9GJmEHGom9eWo4np4L5vC6b6ri1Df2xN8KFoWixvD1Bs. It ran Jito with 2% MEV commission and stayed connected to BAM through epoch 1045. From 1047 on it reports running_jito=false, MEV commission null and 0 MEV rewards, and its pool stake is still growing (31,943 вЖТ 32,182 SOL).

Why it isn't unstaked, from programs/steward/src/score.rs:

- Instant unstake: calculate_instant_unstake_mev_commission does filter_map(..).max().unwrap_or(0), so a missing MEV commission counts as 0% and passes.

- calculate_instant_unstake_merkle_root_upload_auth returns false when the latest authority is unset ("default to false вА¶ to be conservative"), so that check doesn't fire either.

- There is no BAM or running-Jito check in instant unstake. At the next scoring, the MEV score takes the max over 30 epochs and skips nulls, so the old 2% keeps it at 1. Only the BAM rule (connected in 6 of the last 10 epochs) can remove it. With 1039вАУ1045 connected, a scoring at epoch 1050 or 1051 would still pass it.

In pool terms this is small (0.31% of 10.33M SOL). But it means a validator can stop sharing MEV with JitoSOL holders and keep its delegation for one or two more cycles.

Suggestions:

1. Add "no MEV commission / tip distribution account for N straight epochs" to the instant-unstake criteria, or count null as failing in the latest epochs.

2. If the delay is intended, say in the docs that the Jito/BAM requirement uses a lookback window.

Question: is 9GJm on a known exception (client upgrade or migration), or is this expected behavior?

Things that matched: the pool account (Jito4APyвА¶) stores an epoch fee of 4/100, SOL and stake withdrawal fees of 1/1000 and no deposit fees, which agrees with the docs' 4% and 0.1%. The 30-day realized yield from Kobe's stake_pool_stats rate (1.29951 вЖТ 1.30462) is 4.89%, against the 4.86% APY on the stake page. One doc nit: the glossary says the 0.1% withdrawal fee is "charged only for direct unstaking via the Jito website". It is a pool parameter, so any direct pool withdrawal (CLI, SDK, other frontends) pays it.

Disclosure: no affiliation with Jito. Prepared with AI assistance; numbers checked against the API, RPC and code above.

$MISTAKE is up 96.4% in 24H, but the more interesting signal is the volume.

$11.66M in 24H volume against a $10.67M market cap means the token is seeing trading activity exceeding its entire market value.

That suggests strong short-term attention and rotation into the asset.

The key question now isn’t whether it already pumped.

It’s whether buyers can sustain this volume without the move turning into a sharp reversal.

Momentum is strong. Confirmation matters.

$Agency caught my attention today.

+60.4% in 24H with $38.99M in volume against a $17.47M market cap.

That’s a lot of activity for a token this size.

The move is already significant, so I’m more interested in whether the volume keeps following the price.

If the activity holds, Agency could stay interesting. If volume dries up, the current momentum may not last.

$LCX earns money buy hype, catching liquidity, followed by a dump. Too consistent and predictable. The company feeds employees on retail fomo money.

$HONEY: I explored Hivemapper's Regions page and opened "Texas Remainder". It shows 24% overall progress, 287,869 km of total road mapped but only 45,853 unique km, with 174 contributors. That means roughly 16% of the mapped distance is unique roads, so most of the driving repeats roads already covered.

That made me wonder how rewards work for a new contributor there. The page shows "Multiplier 1x" and "Weight 1.0657%", but I couldn't find on the page what these mean or how they change what a driver earns. I also noticed Activity at 10%, Coverage at 18% and Resilience at 100%, and it isn't clear how these three combine into the 24% overall figure.

Suggestion: a short tooltip or one-line explanation next to Multiplier, Weight and each progress bar, plus a note on whether driving already-mapped roads earns less than covering new ones, would help new contributors choose where to drive. Also, is "Texas Remainder" the area outside the big metro regions like Austin? A short description would help.

Orca's docs give the xORCA rate as $ORCA in the vault divided by xORCA supply, and link the vault. I ran that on Oct 4: the vault (Ce5j11WAsSzM3nkzrw4Kw6v6ic3nbyqpv5eywjYKeKc5) holds 9,465,616 $ORCA against 4,544,582 xORCA, which gives 2.083. The stake page shows 1 xORCA at about 1.678 ORCA, and the stake page is right: stakes that day minted at 1.678. The staking program keeps a counter of ORCA owed to wallets that have unstaked, 1,839,631 today, and its math subtracts that before dividing. So 19% of the vault is an exit queue, and anyone pricing xORCA with the docs formula, say a lending market, would be 24% high.

I listed the queue from the program's accounts: 326 tickets from 257 wallets, summing to the counter exactly. The 116 still in the 7-day cooldown hold 1.75M ORCA, 2.9% of circulating supply, all withdrawable by Oct 11. One of them is 1,000,088 ORCA and matures Oct 5 at 16:57 UTC. The other 210 (92,144 ORCA) have matured and were never withdrawn, the oldest (0.001 ORCA) since Oct 6, 2025.

The buyback that feeds the rate swings day to day. In my replay of the vault's transactions the buyback bot added 13,294 ORCA on Sep 29 and 3,864 on Oct 3. The stake page shows 18.43% APR. On the 7.626M staked, Oct 3 alone annualizes to 18.5% and Sep 29 to about 64% (my arithmetic), so the APR looks like a one-day figure.

On control, the xORCA docs say 3-of-5 signatures. On chain, one Squads vault (GwH3Hiv5mACLX3ufTw1pFsrhSPon5tdw252DBs4Rx4PV) is the ORCA mint authority, the upgrade authority of Whirlpools and of the staking program, and the staking update authority. Its multisig needs 5 approvals from 9 voting members, with a 24-hour time lock. The tokenomics page calls the 75M supply fixed while that mint authority is live.

For the team:

1. Correct the docs formula, and publish the escrow total with its maturity dates next to the rate.

2. Update the multisig line, and either renounce the mint authority or say why it stays.

My question: what window is the APR computed over?

Note for TokenGems: the FAQ here answers "What is Orca DEX?" with one word, "AMM".

$STREAM - Thorough technical review of on-chain primitives and protocol architecture: 1. Multisig & Vault Architecture: The migration to Squads v4 execution for Foundation vaults demonstrates enterprise-grade operational security. The recent treasury burn of 699,994,595 STREAM executed via Squads v4 (SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf) calling SPL Token Program burn instruction confirms clean verifiable state management. Revoking mint authority to null provides strong immutability guarantees. 2. Streaming Contract Efficiency: The core value proposition of per-second linear streaming on Solana significantly lowers compute unit (CU) consumption compared to EVM equivalent vesting contracts. However, for DAOs managing thousands of concurrent streams, batch cancellation or claim operations under network congestion spikes should implement dynamic priority fee escalators (via Helius/Jito bundles) to prevent tx dropouts. 3. Developer Suggestion: The SDK documentation is solid, but adding native Model Context Protocol (MCP) tool bindings or Solana Agent Kit actions for autonomous agent payroll/vesting would enable AI agents to automate contributor stream distributions seamlessly.

$JTO - Architectural breakdown of MEV block engine infrastructure, bundle auctions, and tip economics: 1. Block Engine & Bundle Auction Mechanics: Jito's out-of-protocol blockspace auction provides critical protection against public mempool spam on Solana. Bundles guarantee sequential atomicity across transactions. However, searchers running high-frequency arbitrage against decentralized AMMs face latency spikes when connecting to non-localized Block Engine endpoints. Documenting optimal geolocated relay connections (e.g. Frankfurt vs NY) directly in the developer portal would reduce bundle drops during volatility peaks. 2. Tip Account Settlement & Validator Routing: The tip-payment instruction routing funds across 8 rotating Jito tip accounts avoids state hotspot contention. For decentralized applications and autonomous agent runtimes, integrating dynamic tip estimation based on the rolling 20th/50th percentile of landed bundles prevents both overpayment and starvation during high congestion spikes. 3. Restaking & Node Consensus: With Jito's Restaking protocol expanding trust-minimized validation, integrating slashing condition telemetry and node operator uptime benchmarking into the analytics dashboard would significantly assist institutional delegators evaluating risk-adjusted APY.

The $POD token, Dolphin, has shown significant price appreciation over the past quarter, with a 119.5% gain over three months. This move follows a substantial surge over the last month and week, indicating persistent buying interest. With a market capitalization of $428.9M, $POD is a token of considerable size. The consistent upward trajectory suggests that structural demand is absorbing supply, rather than a short-term positioning play.

The underlying mechanism for $POD's strength appears to be its positioning within the ecosystem of a major Layer 2 solution. Recent developments include increased adoption and integration of $POD, which translates into higher utility and potential fee revenue capture for holders. This demand is likely driven by institutional players recognizing its role in scaling capabilities and overall network throughput, ensuring a sustained marginal buyer base. The claim for $POD to outperform would be wrong if this broader Layer 2 adoption stalls, reducing the long-term utility and demand for the token.

The category pages say there are $1.29T of stablecoins. There aren't.

I was sizing sectors on the categories page today and the totals stopped me cold:

- Stablecoin: 312 tokens, $1.29T market cap. The actual stablecoin market is ~$290B (USDT $184B + USDC $74B + everything else). That's 4.4x reality.

- Wrapped: 340 tokens, $432.96B. The real wrapped-token market is on the order of $60B. That's ~7x reality.

- Meme: $182.39B vs ~$60–80B actual — 2–3x.

There are not $1.29 trillion of stablecoins in existence. Something in the aggregation is badly off.

The likely culprit is double-counting multi-chain instances. Your own Wrapped FAQ describes the model — "one instance [of WBTC] on Avalanche (0xa86a)... another on Ethereum (0x171)" — and I verified that per-chain instances carry the full native market cap, not a pro-rated slice (both $NPC leaderboard rows show ~$177M against a $177M real total). Sum those instances and every multi-chain asset gets counted N times.

This one matters more than a single bad row: a researcher sizing a sector from this page walks away with a fantasy number, and it's checkable against any aggregator in 30 seconds. Two possible fixes: dedupe per underlying asset when rolling up (count each asset's mcap once), or stop calling the column "market cap" if it's really "sum across all tracked instances".

Checked on the public categories page 2026-10-04, no login, reproducible on reload.

$Amiko is a gem! I checked the instant and delayed unstaking quotes for the same amount and noticed that the main decision is not simply about which option is “better”. It depends on whether the user needs liquidity immediately or is willing to wait for a different outcome. The current flow provides the necessary information, but it could communicate this trade-off more directly. A side-by-side “now vs later” comparison with the amount received and waiting time would make the decision much easier.

$PSOL is quietly interesting.

~$158M mcap for Phantom’s liquid staking token, up 45% this month.

Real SOL yield, liquid across DeFi, and distribution through one of the biggest wallets.

Not a narrative bet.

Just growing Solana infrastructure.

@ofnir what do you think about $NPC?