User Avatar
DVHDEz…VdbQ@kingintheNorth1
Rank
Gems earned
655
Be Kind Always
  • User Avatar
    @gamesdroidesWrapped+1•3

    $mSOL I found a material inconsistency between two official Marinade documentation trees for mSOL delayed unstake. The current FAQ says delayed unstake takes 1 epoch (except the end-of-epoch window) and charges 0.2% / 20 bps. docs-beta.marinade.finance says Delayed Unstake is free / 0% and takes about 1-2 epochs. This is economically measurable: on 100 SOL the fee expectation differs by 0.2 SOL; on 1,000 SOL by 2 SOL, plus the timing expectation doubles at the upper end. I would redirect or clearly deprecate the beta page and keep one canonical fee/timing table. Main FAQ: https://docs.marinade.finance/marinade-protocol/faq Beta: https://docs-beta.marinade.finance/staking/liquid

  • User Avatar
    @gamesdroidesGovernance+2•3

    $JUP I audited the official Jupiter CLI close flow and found a risk-control inconsistency. jup perps close exposes --slippage (default 200 bps), and single-position closes pass maxSlippageBps to positions/decrease. But the --position all branch calls postCloseAll(walletAddress), whose request contains only { walletAddress }, so an explicitly supplied slippage limit is silently omitted in close-all mode. Quantitatively, a user choosing 10 bps (0.10%) expects at most $10 of slippage tolerance on $10,000 notional; in close-all, that chosen 10 bps limit is absent from the request. I would either propagate maxSlippageBps through positions/close-all or reject/warn on --slippage with --position all. Evidence: https://github.com/jup-ag/cli/blob/main/src/commands/PerpsCommand.ts and https://github.com/jup-ag/cli/blob/main/src/clients/PerpsClient.ts

  • User Avatar
    @draaagoonnGovernance+1•2

    I explored $SANC app at app.sanctum.so and browsed the LST swap interface. The concept is solid — instead of each liquid staking token (like jitoSOL, mSOL, bSOL) needing its own separate liquidity pool, Sanctum's Infinity Pool unifies them all so you can swap between any LST instantly.

    What I noticed: when picking which LST to swap into, the interface shows the exchange rate but doesn't break down where the yield comes from — base staking APY vs MEV rewards vs validator commission. For popular ones like jitoSOL, experienced users already know. But for smaller validator LSTs, there's no way to tell if you're getting 7% from real staking or from a temporary validator subsidy without leaving the site entirely.

    Suggestion: add a small tooltip next to each LST showing "Base yield: X% | MEV: Y% | Commission: Z%." This would help users compare LSTs at a glance and could actually drive more stake toward transparent smaller validators.

  • User Avatar
    @tgworkjupGovernance+2•1

    $JUP I opened jup.ag and walked through a Manual Swap of a tiny SOL→USDC route without broadcasting. The route preview correctly showed multi-hop legs, but Priority Fee and Jito Tip share the same tooltip copy. Those are different mechanisms, and when Jito Tip is toggled off the UI still shows 0.001 SOL, which reads like it will still be charged. Suggestion: give each fee its own one-line explanation, gray out disabled fee amounts, and include only active fees in the pre-confirm cost estimate. Question: can the quote panel surface base fee vs priority fee before the Swap click, so congested-network failures are visible earlier?

  • User Avatar
    @eleemGovernance+2•1

    $JUP Tested swapping SOL to USDC through the Jupiter interface and reviewed the route breakdown. The multi-hop routing between Raydium and Whirlpools kept slippage low, but the interface doesn't show the dynamic network priority fee until you actually click Swap. Would it be possible to display the current base vs priority fee upfront before confirming? That would help avoid failed transactions when the network gets congested.

  • User Avatar
    @schmitz8442Governance+2•1

    $JUP JUP is a solid project with great trading volume on Solana network. The user interface is straightforward and very easy to use for new people. I am looking forward to seeing their upcoming ecosystem updates.

  • User Avatar
    @NicholasGovernance+2•2

    $JUP While exploring Jupiter's Manual Swap Settings, I noticed that Priority Fee and Jito Tip display exactly the same tooltip:

    "We'll adjust transaction fee based on market conditions, up to your max."

    However, these fees serve different purposes, and the interface doesn't clearly explain those differences.

    I also noticed that Jito Tip continues displaying 0.001 SOL even when disabled, which could confuse newer users about whether this amount will be charged.

    My suggestions:

    Provide separate explanations for Priority Fee and Jito Tip, including when each is useful.

    Make disabled fees visually distinguishable from active ones.

    Clearly indicate which fees are included in the estimated transaction cost.

    These small improvements could make transaction costs easier to understand, especially for users who are new to Solana.

  • User Avatar
    @NicholasGovernance+2•2

    $JUP is a gem!

  • User Avatar
    @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.

  • User Avatar
    @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.


  • User Avatar
    @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?

  • User Avatar
    @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!

  • User Avatar
    @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

  • User Avatar
    @CammieLyuWrapped+1•2

    $mSOL — A small suggestion to clarify staking value and selling price.

    I noticed something in Marinade’s Liquid Staking overview that might be a little confusing for beginners.

    The overview says the mSOL/SOL rate only changes with staking rewards, but the mSOL Token page also mentions that market prices can be different. The FAQ explains that instant unstaking uses the current market rate.

    I think both explanations make sense, but it might help to make the difference a bit clearer in the overview.

    Maybe the overview could call it the “protocol mSOL /SOL exchange rate” and include a simple example?

    For example, if the protocol rate is 1.30 SOL per mSOL , but the current swap rate is 1.28, someone selling 10 mSOL instantly would get 12.8 SOL instead of 13 SOL, before any additional fees. These are just example numbers, not live prices.

    It might also be helpful to link this example to the explanation of instant and delayed unstaking, including any fees involved.

    I think this small addition could make things much easier for newcomers to understand, especially when they're deciding how to unstake their mSOL.

  • User Avatar
    @MrperfectVIPGovernance+2•2

    $RAY is a gem! Raydiums order book AMM model is an excellent combination of liquidity and trading efficiency on Solana. Its CLMM integration provides users with the ability to provide capital efficient liquidity making it astandout protocol in the Defi space.

  • User Avatar
    @vitaliano73Governance+1•3

    $ORCA Documentation feedback for the developer docs (AI-assisted review of the public docs; no wallet connection, transaction, or purchase was made).

    Two inconsistencies any new integrator hits by copy-pasting the "quick start":

    1) The docs home page (docs.orca.so) still shows the Legacy SDK as its Quick Start example:

    import { WhirlpoolContext, buildWhirlpoolClient } from "@orca-so/whirlpools-sdk";

    const ctx = WhirlpoolContext.from(connection, wallet);

    const client = buildWhirlpoolClient(ctx);

    const pool = await client.getPool(poolAddress);

    But the developer Quick Start (docs.orca.so/developers) tells you to install a different, current package:

    npm install @orca-so/whirlpools @solana/kit

    and the docs' own /llms.txt lists the two side by side: "TypeScript (Kit): @orca-so/whirlpools" vs "TypeScript (Legacy): @orca-so/whirlpools-sdk". Someone who starts from the home page installs the legacy package and then finds the SDK reference describing a different API (setRpc / setPayerFromBytes / swapInstructions from @orca-so/whirlpools).

    2) The developer Quick Start swap snippet calls two helpers it never imports:

    import { createSolanaRpc, address } from "@solana/kit";

    import { swapInstructions, WhirlpoolDeployment } from "@orca-so/whirlpools";

    ...

    const signer = await setPayerFromBytes(new Uint8Array(secret));

    setDefaultFunder(signer.address);

    setPayerFromBytes and setDefaultFunder are used but not imported, so the example throws "setPayerFromBytes is not defined" as written. The /llms.txt Setup block has the correct import (import { setRpc, setPayerFromBytes, setDefaultFunder } from "@orca-so/whirlpools").

    For the team:

    - Either label the home-page snippet as the Legacy path or replace it with the Kit snippet the developers page uses, so the same package is recommended everywhere.

    - Add the missing import line to the Quick Start swap example; the llms.txt block already shows it.

    Sources: https://docs.orca.so/ (home Quick Start block) | https://docs.orca.so/developers (install + swap snippet) | https://docs.orca.so/llms.txt (SDK package table and Setup block)

    I read only the public documentation; I did not connect a wallet or execute anything. No affiliation with Orca.

  • User Avatar
    @SmartsadiqMeme+1•2

    $SI is a gem!A useful improvement for TokenGems: make token scores easier to interpret

    I noticed that the Super Inu ($SI) page displays a TokenGems score alongside Gem/Rug sentiment. These signals are useful for quickly scanning a token, but a new user may not immediately understand how much weight to give them.

    Could TokenGems show a short breakdown of the main factors behind each score, when the data was last updated, and which signals are uncertain or missing?

    That would make the page more useful for research—not just for spotting tokens, but for understanding why a token receives its current rating. A clear explanation could help users compare projects more carefully without treating any score as a guarantee of safety.

  • User Avatar
    @mycindyUtility+1•2

    $BTW is a gem! BTW's near-term path is challenged by overbought conditions and supply risks, but its medium-term trajectory relies on converting its innovative narrative into measurable adoption. For holders, this implies preparing for volatility while watching for concrete ecosystem growth metrics.

  • User Avatar
    @idlecat_solUtility+1•2

    Spent some time on metaplex.com without connecting a wallet. The launch token flow is smoother than I expected. Clear steps, and it tells you right away when a field is missing. The docs are well organized too.

    Two things stood out, though. Searching "$MPLX" brings up several fake Metaplex tokens with the same logo, and only a small checkmark marks the real one. That could easily trip up newer users. Also, the guide says you deposit SOL, but the pool I looked at was collecting USDC, and I couldn't find anything explaining the difference.

    The homepage also took a few seconds to show any content. Good overall, just some rough edges.

  • User Avatar
    @OrionAriaUtility+4•2

    $RIZ is a gem!

    $RIZ looks like a highly ambitious project sitting at the intersection of AI Agents, Oracles, and DePIN. Combining decentralized physical infrastructure with AI data processing is definitely one of the strongest narratives right now.

    However, looking at the early metrics and the 50/50 community sentiment on TokenGems, execution will be critical. My main question regarding their architecture: how does Rivalz plan to guarantee data privacy and prevent malicious data poisoning while scaling its decentralized oracle network for AI agents? Clear documentation on their compliance and validator rewards will be essential to tip the community sentiment towards a solid GEM.

  • User Avatar
    @ofnirMeme+1•2

    The crowd has certainly been chasing $TART, with the token pushing past $0.0014 and showing an 83.0% gain over the last week and nearly 600% over the past month. This surge comes after a listing on BiFinance in mid-September and a recent wave of social media promotions comparing it to early BNB and CAKE. The project is a DEX on BNB Chain, offering swaps and staking, and has renounced ownership of its contract, fixing the trading tax at 0%. Its market capitalization currently stands around $15.5M with $682.3K in liquidity.

    The appeal here is clear: a live protocol with a seemingly robust structure and a fixed supply. The founder has also spoken to "sustainable tokenomics" designed to avoid the pitfalls of excessive emissions. However, the current momentum is heavily fueled by promotional efforts drawing ambitious comparisons. While the fundamental underpinnings appear solid, the short-term chart is visibly propped up by this heightened attention.

    The primary risk to this trajectory would be the fading of the speculative fervor, particularly if the proposed additional utility and strategies to reduce liquid supply do not materialize or gain traction swiftly enough to sustain the crowd's interest. Attention is a fickle beast, and even a well-built cage can't hold it indefinitely.

  • User Avatar
    @wolfurUtility+1•2

    I used Moby Web in launch week (Oct 14, logged in, Solana) for my usual routine: find a token smart money is buying, check the wallets doing it, follow the good ones, enter with TP and SL. Four things a builder can act on.

    1. TP/SL. The launch thread says TP and SL are "available when entering a position". The web buy panel has Market, Trigger, Limit and DCA, no TP/SL. The app's TP/SL text speaks of "one order over your position", set "vs your entry", and the Sell tab would not open on a token I did not hold. So TP/SL is a second order after the fill, and the position has no stop until then. An optional TP/SL row in the buy panel, placed right after the fill, would match the thread.

    2. Minimum order. From a nearly empty wallet, 0.009 SOL gave "Amount too small to swap". Max filled 0.008383 SOL and the button turned green ("Buy CATE") under the same warning, until the quote ran out of retries and it became "Try again". I found no stated minimum. Show it under the amount, keep the button disabled while the quote fails, and let Max say when the balance is below it.

    3. Wallet names. One wallet is "PUMP Whale 281A" in CATE's live feed and "JEANPHIL Whale 281A" on its profile; "GP Whale 3FD3" becomes "SI Whale 3FD3". After I followed "BATON Whale 9DF8", its profile says "Whale 9DF8" while the Following feed says "BATON Whale 9DF8". One stable label per wallet would help.

    4. Whale means size, not skill. At 13:08 WIB Moby showed smart money +$95.1K net into CATE over the hour, and 13 whale wallets had bought it in the previous ~13 hours. I opened all 13 profiles: 4 had positive 30-day realized PnL, 9 were negative, down to -$38.1K. 30-day PnL or win rate next to the name in the live feed and Key Holders, or a filter for it, would turn 13 clicks into a glance. I followed the 4.

    Also, a token link opened logged out lands on the sign-up screen, so a shared link shows nothing to a non-user.

    Question on $MOBY : the app pays 10 to 30% of the 0.75% trading fee back in $MOBY, with a claim threshold. Is that $MOBY bought on market from fees, or paid from a set allocation?

    Disclosure: Moby user since Nov 2025. I share a referral code, which earns $MOBY on referred trades. No other affiliation.

  • User Avatar
    @KryvixGovernance+2•1

    $JUP is a gem! - Played around with a 1 SOL -> USDC quote on Jupiter (didn't connect a wallet).

    Couple of things I noticed:

    - Number formats are mixed up. The output shows "104.484915" with a dot, but right next to it "≈$104,55" and the rate "104,48 USDC" use commas. Further down the page I get "$1,54 млн", "$82,3 тыс.", "UMC $5,51 трлн" in Russian while everything else is in English. Probably picks it up from my browser language, but it's easy to misread amounts like that.

    - "Use V1 transactions" is on by default. The tooltip says wallet support varies and to switch to V0 if signing fails, but honestly I'd never think to hover over that toggle if a swap failed. Maybe show that hint right when signing fails?

    - First thing in Popular Tokens is SAINDRA, $232K mcap, "+57x", no risk label at all. For someone new that looks like a recommendation.

    What I checked: swap quote, rate, V1 tooltip, the whole homepage. Affiliation: None.

  • User Avatar
    @ALIREZAUtility+1•3

    $NEAR Key Analysis & Feedback:

    1. Liquidity & DeFi Depth:

    Wrapped NEAR is critical for cross-chain liquidity between NEAR and Solana. To drive real traction, deep concentrated liquidity pools on Raydium/Orca with farming incentives are needed to prevent slippage.

    2. Security & Bridge Transparency:

    Wrapped assets rely entirely on bridge integrity. It is essential to display the exact bridge architecture (Wormhole/Allbridge), multisig threshold, proof-of-reserves, and real-time audit logs directly.

    3. TokenGems UX Feature Request:

    TokenGems should introduce a dedicated "Bridge & Backing" metric card for wrapped tokens showing mint authority status, reserve ratio, and bridge health.

  • User Avatar
    @ROOSTRBOD-9Governance+2•4

    $JUP — A small documentation correction could prevent a 10× input-amount mistake.

    In Jupiter’s “Get Quote (Swap V1)” guide, the example introduces a quote for 1 SOL, but the request uses amount=100000000. With 1 SOL = 1,000,000,000 lamports, that request actually quotes 0.1 SOL. The example response also shows inAmount="100000000".

    Suggestion: either change the introductory text to “0.1 SOL” or update both the request and example response to consistently represent 1 SOL. A short conversion example beside the amount parameter would also help beginners avoid decimal mistakes.

    This concerns the legacy V1 guide, which is marked as superseded by Swap V2. Scope: public documentation review with AI assistance; no wallet transaction or live API test performed.

    Source: https://developers.jup.ag/docs/swap/v1/get-quote