$ORCA — Orca: positive Total PnL can still underperform holding

The Position History & PnL guide says Total PnL compares a position with its deposits, not with holding those tokens outside the pool. It also says unharvested fees and rewards are included in unrealized PnL where supported data is available.

Illustrative example: deposit value $1,000; current LP value including unharvested yield $1,080; previously harvested yield $20; same original tokens simply held would now be worth $1,150. Ignoring other costs, the LP gained $100 versus its deposit but lagged holding by $50. Adding the unharvested yield again would double-count it.

Could Orca add an optional "versus holding" comparison beside Total PnL, using the original token quantities and handling later deposits/withdrawals consistently? Keep the existing PnL metric, and label the comparison's assumptions and excluded costs.

For incomplete history or missing prices, show N/A with the reason rather than an apparent zero. The guide already uses N/A for unavailable existing metrics.

Question: could a worked example like this be added to the guide so newcomers can distinguish fee income, absolute PnL, and performance versus holding?

Source (reviewed 7 Oct 2026):

https://docs.orca.so/liquidity/manage/position-history

AI-assisted documentation review; no liquidity transaction performed for this review.

$KMNO — Kamino Earn: distinguish position value from immediately withdrawable liquidity

The Earn withdrawal guide says larger withdrawals may require recalling capital from reserves, and high utilization can delay availability. The vault mechanics page describes a typical 5-10% unallocated buffer. That percentage describes a shared vault buffer, not a personal withdrawal quota or guaranteed exit capacity.

Could the withdrawal preview show three separate figures: requested amount, amount supported by the current liquid buffer, and amount dependent on reserve liquidity? Include a timestamp or slot, because other depositors can consume the buffer before execution.

Illustrative example: a 1,000,000 USDC vault with 50,000 USDC unallocated has a 5% buffer. A 60,000 USDC withdrawal exceeds that buffer by 10,000 USDC, but might still complete if reserves have sufficient recallable liquidity. "Above buffer" should therefore not automatically mean "withdrawal unavailable."

Question for the team: when liquidity is insufficient, is the request queued on-chain, partially executable, or rejected so the user must retry? The user guide explains the liquidity dependency but does not specify these transaction outcomes.

A worked example and explicit retry/queue behavior would make "Withdraw" easier to interpret before depositing.

Sources (reviewed 7 Oct 2026):

https://kamino.com/docs/learn/lend/withdrawing-assets

https://kamino.com/docs/products/lending-vaults/how-it-works

AI-assisted documentation review; no deposit or withdrawal performed for this review.

$AIOZ Network positions itself as a DePIN infrastructure for a decentralized content delivery network (dCDN) and Web3 AI computation, leveraging a global network of peer-to-peer nodes. It claims to offer faster, more secure, and cheaper content streaming and AI processing by distributing the workload. This is a category still stretching its legs, and the promise of a truly decentralized infrastructure for both content and AI is compelling, if also incredibly ambitious. The market cap sits at $149.6M with daily liquidity of $1.67M, making it small enough for sharp moves but large enough to have some operational footprint.

What's verifiable is the network's existence and its node count, which is easily observed on its dashboard. The actual economic efficiency and performance claims, however, are harder to objectively audit without direct, large-scale comparisons to centralized alternatives. Recent movements include a substantial 74.4% rise over the last month, suggesting some renewed interest. My GEM relies on the continued narrative traction of decentralized AI and content delivery; a significant slowdown in network adoption or a failure to attract real-world users for its claimed benefits would quickly flip my lean.

$HNT

@seimoji

I think $HNT has an interesting advantage: its value can be tied to something people actually use in the real world, not just speculation. As Helium’s network grows, I’d love to see a simple metric showing how much real-world connectivity each $HNT-related network activity enables.

That would make the project’s growth much easier to measure—and give users a clearer reason to care beyond the token price.

I had $DRIFT staked in Drift's insurance fund when the protocol was paused on April 1, so on Oct 4 I went through the claim at dfx.drift.trade. Connected the wallet, one transaction, 318.655528 DRIFT back, cost 0.0027 SOL (rent for the claim record and token account). It works. The on-chain side is the useful part.

The claim is a Jito merkle distributor. One admin key, 8jj7zJgd (also the paused Drift program's upgrade authority), runs 52 of them: 44 insurance-fund distributors, one per asset, opened June 30 21:45 UTC with clawback from July 1 2027, and 8 for DFX. Insurance fund, Oct 7: 19,547 eligible wallets, 1,521 claimed (7.8%) in three months. Big wallets went first: USDC 83.8% of 16.13M claimed by 5.4% of its 6,243 wallets; SOL 50.1% of 14,369 by 2.5%; DRIFT 43.0% of 19.10M by 14.1% of 4,763. "Returned in full" is in tokens: DRIFT was $0.068 on April 1, $0.016 when claims opened, $0.019 today.

DFX: 298.96M allotted, 101.28M claimed by 3,405 wallets in six days. The recovery pool ledger (data.velocity.exchange/recovery-pool) shows a 3,114,379 USDT seed on Sep 30, then daily exchange-revenue deposits of $1.55, $0.66, $5.96, $0.68, $2.30, $3.97, $0.52. All-time pool share of Velocity fees: $44.85. Redemptions took out about $2,729. Pool today 3,111,697 USDT against 299.5M of verified losses, 0.0104 USDT per DFX. No Tether or partner deposit in the ledger yet. Velocity's five perp markets did $22.4k of volume in 24h.

For the team:

1. The portal says the insurance-fund window "opens 7 Jul"; the distributors opened June 30. Say which date counts and, for the 92% who have not claimed, where the clawback sends unclaimed assets on July 1 2027.

2. Put the daily deposit figure on the DFX page next to the pool balance. The dashboard shows the balance; the ledger shows the balance is the seed.

3. State the Tether matching formula. The May plan tied it to prior-quarter revenue; the October post says "up to 127.5M" and nothing else.

Question: at the current split (70% net revenue, 60% of that to the pool below $30k a day), what daily Velocity volume does the plan assume?

I was a Drift insurance-fund depositor; I sold the claimed DRIFT the next day and hold no position. No other affiliation.

Someone asked here what a $JTO holder votes on today. I read this year's three proposals from the Realms program (Oct 7, 03:50 UTC). The answer: where the DAO's revenue goes, and so far it has gone to validators, not to the token.

JIP-37 (June) sent 100% of protocol revenue to the BAM validator subsidy through Sep 30 and had the Cryptoeconomics subDAO cover holders with buybacks from its own treasury for Q3. JIP-38 (voted Sep 15 to 22) calls Jito "token-centric" but commits only JTX fees to buyback and burn. JIP-39 passed the same week, 10.60M approve to 0.71M deny: subsidy at 100% of protocol revenue through Q4 2026, then halving every 10 epochs from January until it ends in June 2027; non-JTX revenue returns to the DAO from Q3 2027. The vote closed Sep 22, the FinalizeVote transaction landed Oct 6 at 22:37 UTC, and all three proposals carry zero executable instructions.

Turnout: 11.3M JTO, 1.15% of supply, deciding the routing of about $400k a month (DefiLlama DAO revenue: $402k in September, $428k last 30 days). Holder revenue on every Jito adapter is $0.

Two checks on what holders were promised. JIP-37 required a Q3 buyback plan on the forum within 14 days and a CSD end-of-term report in July; neither is there. The last CSD post is JIP-26 from October 2025 (2.15M JTO bought at an average $1.52; price today $0.53). JIP-38 promises "all acquired JTO burned" from JTX, live since July 14. Mint supply was 986,523,002.9 at the JIP-37 vote, 986,522,509.5 at the JIP-38 vote, 986,522,447.6 today: 555 JTO gone in four months, 62 since Sep 15, about $300. The incinerator holds 0.04 JTO.

For the team:

1. Publish the Q3 par-buyback numbers JIP-37 mandated: JitoSOL spent and JTO bought, per epoch, with transactions.

2. Give the JIP-38 epoch report a fixed URL. Until then the mint supply is the only public check, and it shows no burn at any visible scale.

3. Post the execution transactions for JIP-39 (delegation move, new subsidy curve) when they happen; nothing on-chain marks the start.

Question: between now and June 2027, is any JTO buyback funded by anything other than JTX fees?

No affiliation with Jito.

$JUP — staking docs disagree: 30 days or 7 days?

Jupiter's own pages give two different unstaking periods. The DAO FAQ (June 2025 edition, still live) says unstaking JUP takes 30 days, designed to stop holders gaming ASR. But vote.jup.ag now says unstaking triggers a 7-day cooldown, during which you can't claim ASR.

One of these is stale. New stakers reading the FAQ will expect a month-long lock and may stake less — or skip staking entirely.

Could the team either update the FAQ or add a banner pointing to the current 7-day rule? A single canonical staking page would end the confusion.

Sources:
https://discuss.jup.ag/t/jup-dao-faq-june-2025-edition/38967
https://vote.jup.ag

$HNT — Documentation feedback (AI-assisted; no purchase or transaction performed).

Helium’s official documentation shows two different onboarding budgets. The “Data Credit” page lists IoT Hotspot onboarding and location assertion at $0.50 each. “Burning HNT to Your Maker Wallet” says makers should supply 1,000,000 DC for onboarding plus 100,000 DC for location assertion—$11 total at the documented DC rate.

These may apply to different onboarding paths or protocol versions. Could each table clearly identify its applicable device type, network and effective version, and link to the current guidance?

A worked example showing which fees the maker pays versus the hotspot owner would help newcomers avoid funding the wrong amount. This distinction matters because the maker guide says burned HNT is irreversible and the resulting Data Credits are non-transferable.

Sources:
https://docs.helium.com/tokens/data-credit/
https://docs.helium.com/hotspot-makers/become-a-maker/burn-hnt-to-maker-wallet/

$JUP first-time Swap onboarding observation

I tested Jupiter Swap as a first-time user with a connected wallet holding 0 USDC.

After entering 10 USDC as the sell amount, the SOL quote was easy to understand. The point where I got stuck was the next step: the CTA changed to “Insufficient USDC,” appeared disabled, and clicking it gave no response.

I then spent about two minutes looking around the interface for a way to resolve this, but I still could not tell whether I was supposed to buy USDC, deposit it into my wallet, or use another Jupiter feature first.

For a zero-balance user, this feels like a dead end. An inline “Get USDC / Add funds” action, plus a short note such as “Swap uses assets already held in your connected wallet”, could make the first-time flow much clearer.

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

ChainLink Token (

$LINK

) has seen significant price appreciation over the last three months, up 37.79%. Recent data shows continued adoption of its Cross-Chain Interoperability Protocol (CCIP) across various chains, signaling actual utility and transaction fees for oracle services. The increasing integration solidifies its role in securing cross-chain value transfer. Its core mechanism for value capture through oracle fees remains intact.

Immutable zkEVM (

$IMX

) has depreciated by 15.25% over the last three months, despite a 14.88% bounce this month. While the Immutable Passport aims to streamline user onboarding for web3 games, and Immutable zkEVM itself is focused on scaling for gaming, evidence of substantial fees paid to the

$IMX

token directly remains limited. The focus on future ecosystem growth often delays direct token value accrual.

THORChain DEX (

$RUNE

) has performed strongly, up 38.27% over three months, driven by its permissionless cross-chain swaps. The platform recently enhanced its lending protocol, providing non-liquidating, fixed-term loans for native assets, which increases protocol utility and potential fee generation. This expansion directly translates to more swap volume and fees captured by

$RHEA

stakers.

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.

$JUP I checked Jupiter's home page on 6 October 2026 without connecting a wallet.

I noticed that the swap screen — the first thing a new user sees — sits directly next to 250x leverage perpetuals, a Gacha pack opening feature (up to 32x), and prediction markets. All of these are high-risk, and none of them carry a visible risk warning on the home page.

This matters because Jupiter is Solana's front door. A first-time user from a country where a failed transaction is real money will not know that 250x leverage can wipe an account in seconds, or that Gacha packs are gambling-style products, not investments.

Suggestion: add a one-line risk label to the Perps, Gacha, and Prediction Market tiles on the home page — something like "High risk — can lose your full deposit." It's a small change that protects new users without changing the product.

Question: is there a first-time-user mode that hides leverage and Gacha until the user has completed at least one swap?

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

$UNI is a gem! The consensus on UNI is bullish, driven by a powerful confluence of institutional adoption, regulatory clarity, and real-world utility expansion. The narrative has shifted from pure DeFi speculation to Uniswap's role as critical infrastructure for the tokenization of global assets. Watch the $10.30–$10.96 resistance zone; a sustained breakout could validate the current optimism and open the path toward higher price targets.

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

$PSOL I checked the Phantom Staked SOL page in Phantom's Chrome extension (5 Oct 2026, wallet with 0 SOL that has never staked).

What I noticed:

Under a "Native Stakes" heading, the page shows "You haven't earned SOL yet" and a "Stake More" button. I've never staked, so this reads like I already have a stake that isn't earning. And PSOL is liquid staking, which Phantom's Help Center describes as different from native staking.

The ⓘ next to it says rewards are "calculated in near real-time based on the price change between SOL and PSOL". But the Help Center says PSOL rewards typically update at the start of each epoch (about 2–3 days), and earnings only appear once they exceed the 0.1% exit fee. A new staker could see "You haven't earned SOL yet" for days and think something is wrong.

Suggestion: if the wallet has no PSOL, show "Stake SOL to start earning" with a plain "Stake" button, under a "Liquid staking" label. In the tooltip, add one line: "Updates each epoch (~2–3 days). Earnings show after they pass the 0.1% exit fee."

Question: is "earned" based on PSOL's market price or on the stake pool rate? If it's market price, can it go negative when PSOL trades below its pool value?

Called a RUG on $PEAR at $0.0398, and it fell to $0.0314, confirming expectations; with a 2.2% fall today, the crowd is moving on. Our GEM call on $ZCAT at $0.1307 missed as it dropped to $0.0773; it has shed 14.8% today, suggesting further decline. The RUG on $ZIMOMO at $472.86 missed as it edged up to $480.60; with trading flat over the week, attention remains absent. My RUG on $COMPUTECAT at $0.000008355 missed as it rose to $0.00001912; its market cap is now barely $62,723, and liquidity is thin.