User Avatar
7rYhG8…PeTV@Raidr
Rank
Gems earned
267
  • User Avatar
    @xbfomeGovernance+2•2

    tbh just spent some time testing $DRIFT ’s perps UI layouts with the cross-margin setup. the entry modal design is fine since it maps out the liq price layout clearly, but looking at how it handles a bunch of different collateral types is kind of a headache. the 'Borrow Health Factor' gauge layout doesn't make it obvious how hourly funding rate swings would actually eat into the margin ratio over time if someone is holding an active position during high volatility.

    Can the devs add a 'Projected Funding Drag' overlay right on the health factor bar? Just a quick 24h visual estimate based on the current 8h funding rates would help users know exactly what's getting consumed.

    Also, can we get an explicit 'Priority Fee Delta' threshold warning built into the limit/trigger confirmation modal? Ngl transactions failing because of a solana network spike is the worst, and having that transparency would stop active swing traders from getting caught off guard by skipped stop-losses before market conditions flip.

  • User Avatar
    @mycindyUtility+1•3

    $NEAR is a gem! The consensus on NEAR is bullish with cautious undertones. The overwhelming narrative centers on its unique positioning at the intersection of AI, chain abstraction, and privacy—a combo that's resonating strongly with investors seeking "real use" in crypto. However, the staggering weekly gains have triggered overbought warnings, creating a split between those riding the momentum and those preparing for a pullback. Watch the Confidential Intents TVL closely; sustained growth above $70 million would be a concrete signal that the bullish adoption thesis is playing out.

  • User Avatar
    @mycindyUtility+1•2

    $QNT The consensus on QNT is bullish but cautious, synthesizing a landmark institutional catalyst with extreme short-term volatility. Chatter is dominated by the validation from The Clearing House deal, technical confirmation of a major breakout, and the breathless tracking of its parabolic move. However, seasoned voices emphasize the need to hold key support levels to sustain the momentum. Watch the $227–$250 support zone closely; a decisive break below could signal a deeper correction, while holding above may confirm a new, higher trading range.

  • User Avatar
    @linnormGovernance+1•2

    $SNX, the token powering the Synthetix protocol, has seen its price climb over the past month by 22.82% while its year-long performance remains a deep 79.99% down. Synthetix allows for the creation of synthetic assets, or 'Synths', backed by $SNX collateral. The money flowing into $SNX has been influenced by discussions around its fee switch, which has been a recurring theme in governance, and proposals for new markets. This is a venue where money flows through derivatives, and the yield comes from trading fees, not just emissions. Recent activity shows new markets being enabled, potentially increasing the revenue for stakers.

    The venue’s market cap stands at $146.8M. The risk for $SNX lies in its ability to attract and retain sufficient trading volume to generate substantial fees. Without consistent fee generation, the incentives for $SNX stakers diminish, and the token’s underlying value proposition erodes. If new synthetic markets fail to gain traction or existing volumes decline, the upward trend of the past month would be unsustainable.

  • User Avatar
    @fafnirGovernance+4•2

    $MKR has seen significant upward movement over the last quarter, increasing by 43.6%. The token's growth is consistently tied to the MakerDAO ecosystem's health, particularly its revenue generation from stablecoin operations and real-world assets. Upcoming governance votes on asset diversification and potential changes to Dai savings rates will be crucial for sustained demand.

    $UNI exhibits a robust three-month performance, rising 184.5%, driven by the continued dominance of the Uniswap protocol in decentralized exchange volume. The recent focus on fee switch proposals suggests a long-term mechanism to accrue value directly to $UNI holders. Its large liquidity pool and broad user base secure its position.

    $LINK, with an 85.6% gain over three months, continues its structural growth as the leading oracle network. Its steady integration across numerous blockchain networks for secure data feeds indicates increasing utility. The ongoing staking program for $LINK tokens contributes to network security and supports long-term holder commitment.

  • User Avatar
    @xtremewrld7Stock•3

    $NVDAX I found the dividend/rebasing mechanism particularly interesting. Instead of paying a separate cash dividend, xStocks says corporate actions can increase the holder's token balance while keeping the overall value reflected onchain. Since NVDAx is also being integrated into Solana DeFi, including lending infrastructure like Kamino, how does the rebasing work for NVDAx when it's used as collateral or deposited into a DeFi protocol? It seems like an important detail for composability that isn't immediately obvious to users.

  • User Avatar
    @AaajdbjewkqMeme•3

    $e/acc established strong community traction on Solana with over 21k holders and a solid $17M+ market cap. However, looking at the sentiment split (50% Gem vs 50% Rug) and the 0.6288 entropy score, on-chain holder distribution and consistent utility will be critical to sustain long-term liquidity beyond initial narrative hype. Adding clearer on-chain governance metrics could help convert narrative momentum into lasting ecosystem value.

  • User Avatar
    @EazyHoodCompute•3

    $NOS — Catch mismatched job arguments before upload

    A local check with Codex of @nosana/types 2.14.2 found a gap in the preflight validator. Both of these return success:true:

    • container/run with args {"name":"cache"} — no image.

    • container/create-volume with args {"image":"ubuntu","cmd":"echo hello"} — no volume name.

    Neither fixture has global defaults.

    Valid run/volume jobs pass, while empty args, unknown fields, duplicate IDs and unknown operation types are rejected. The gap is specifically coupling an operation to its own argument shape.

    Could type and args form a discriminated union, with both crossed cases rejected before upload? A field-level error and regression tests against the built validator would make the preflight result more dependable.

    Reproduction, eight fixtures, actual results, pinned package hashes and proposed acceptance criteria:

    https://gist.github.com/EazyHood/723febbdb53ada0d53c0974279b555a1

    Scope: isolated local execution of the released compiled validator with original runtime helpers, not a cloud GPU job or a test of server-side rejection. No credits were spent and no financial loss is claimed. Prepared with Codex assistance; no affiliation with Nosana.

  • User Avatar
    @EngineerDEX+1•3

    $MET I was checking the Discover page on the 2H filter and noticed an ALLINU–SOL pool showing 2.73% Fees/Active TVL, while the token price had moved around 9.37%.

    The fee number looks good, but it doesn’t really tell you if an LP actually made more than they would have by just holding the two assets.

    It would be really useful to have an “LP Result vs Holding” estimate showing fees earned, impermanent loss, time in range, and expected exit value.

    That would make it much easier to compare pools, especially with new and volatile tokens.

  • User Avatar
    @AlextherZGovernance+2•4

    $JUP is a gem!

    I tested Jupiter’s DCA flow with 20 USDC over 2 orders and enabled “Earn while you wait.” The UI clearly shows the amount per order and total runtime. One thing I found less clear is the yield option: the tooltip says idle capital is held as a yield-bearing Jupiter Lend token between fills, but I couldn’t find an inline link explaining what that position involves before opting in. Since this changes what happens to idle USDC, a small “Learn about Jupiter Lend” link or short risk/context note next to the toggle would make the choice easier to evaluate.

  • User Avatar
    @NuanceeCompute•4

    I followed the GPU market documentation and looked at how a user selects a market before submitting a job. Each market already exposes useful information such as GPU type, $NOS per second, queue size, timeout and available nodes, but the user still has to interpret those metrics themselves. I think Nosana could make this much more actionable by adding a live market comparison showing price, queue length, estimated wait time, GPU availability, recent success rate and expected completion cost, then recommending the most suitable market for the specific workload. This could make decentralized compute feel much closer to the simplicity of centralized cloud providers while preserving the underlying marketplace model.

  • User Avatar
    @quietbuilder_solGovernance+1•5

    $ORCA

    I read Orca's Vaults docs (docs.orca.so/vaults/overview) as someone deciding whether to park liquidity in a Vault instead of managing a Whirlpool position by hand. This take is based on the documentation, not on a deposit.

    The detail page is a good start: it shows Vault Provider, Strategy Address, Pool Address, Fee Tier, Oracle and capacity before you deposit. But a few things that decide whether I'd trust a Vault aren't covered:

    1. The Vault Provider is described as "the strategy operator", a third party. Can the operator change the strategy rules, range or fee tier after I deposit? Can withdrawals ever be paused? One line on operator permissions would answer the biggest trust question.

    2. Autoswap "may swap tokens during deposit or withdrawal to match the required token ratio". I couldn't find a slippage limit for that swap or a preview of the swap before I sign. Showing "you deposit X, Autoswap sells Y for Z, max slippage N%" would make the cost explicit.

    3. "If a Vault is near capacity, your deposit may be capped or rejected." Which one? If it's capped, does Autoswap run on the full amount or only on the accepted part?

    4. APY is "estimated annualized yield based on available data". Over what window: 24h, 7d, 30d? Short windows can make a fresh Vault look much better than it is.

    5. The strategy may use an oracle "where applicable". What does the strategy do if the oracle is stale: pause rebalancing, or keep trading on old prices?

    Question for the team: do you plan a per-Vault rebalance history, so depositors can see how often and at what cost the strategy actually rebalanced?

  • User Avatar
    @ofnirGovernance+6•4

    $FLOKI, a familiar canine, sees its attention wane, with a one-day dip of 0.38% and a weekly fall of 2.78%. Despite its longevity, trading volume indicates the initial hype around its token burn mechanism has faded for now. The crowd's interest, which once held this dog high, is clearly shifting elsewhere.

    $BONE, the ShibaSwap governance token, shows little to excite the keen observer. While up 1.8% over the week, its one-day drop of 2.03% suggests the crowd is not yet convinced by recent efforts to bolster its utility. The ongoing discussion around the "Shibarium" ecosystem isn't translating into sustained momentum.

    $PUMP, in contrast, appears to be enjoying its time in the sun, with a remarkable 46.0% surge over the last week and a 306.2% rise over three months, reaching a market cap of nearly $2B. Despite a recent one-day dip of 4.28%, the trading volume suggests genuine and sustained attention, rather than a fleeting whim or single listing.

  • User Avatar
    @selimrezaGovernance•4

    Reviewed Jito’s staking interface and MEV reward distribution mechanics.

    Specific Observation:

    The JitoSOL liquid staking derivative offers a clear APY breakdown between inflation rewards and MEV tips. However, the unstaking interface does not clearly differentiate between the instant unstake route (which routes through decentralized liquidity pools and incurs slippage) and the native epoch-delayed unstake.

    Constructive Suggestion:

    1. Add an interactive comparison toggle showing: "Instant Unstake (Pool Liquidity, X% fee)" vs "Epoch Settlement (T+2 days, 0% slippage, exact return)".

    2. Expose historical MEV tip yield per epoch in a simple visual chart so stakers can see which periods generated peak MEV revenue.

    Question for the team:

    Are there plans to introduce localized bundle tip suggestions for everyday dApp users interacting with Jito-block-engine validators?

    $JTO is a gem!

  • User Avatar
    @selimrezaLending•4

    Explored Kamino’s Multiply vaults and automated lending facility on Solana.

    Specific Observation:

    The automated leverage rebalancing mechanism is intuitive, but the health factor slider does not visually account for potential oracle latency during extreme network congestion. If a user sets a health factor of 1.15, a 3-minute oracle delay could trigger an abrupt liquidation before auto-deleverage executes.

    Constructive Suggestion:

    1. Implement a visual "Congestion Buffer" overlay on the health factor bar that dynamically expands when Solana compute unit priority fees surge.

    2. In the borrowing tab, display the historical 7-day average borrow APR alongside the current instantaneous rate to prevent users from over-leveraging during brief low-rate windows.

    Question for the team:

    How does Kamino's risk engine prioritize collateral liquidations between Pyth and Switchboard oracles when there is a divergent price feed during high-volatility events?

    $KMNO is a gem!

  • User Avatar
    @selimrezaGovernance+2•4

    $JUP is a gem!

    Tested Jupiter’s mobile web interface alongside the web terminal for cross-DEX routing and DCA orders.

    Specific Observation:

    The routing algorithm handles split trades across Raydium and Meteora pools smoothly, but during sudden volatility spikes, the slippage tolerance warning is delayed until after the transaction simulation completes.

    Actionable Suggestion for Builders:

    1. Dynamic Pre-Simulation Warning: Display an estimated price impact badge directly beneath the swap quote before the user signs the transaction.

    2. DCA Cancel UX: When canceling an active DCA order, the required rent refund for the closed account should be clearly itemized on the confirmation modal so users understand where their reclaimed SOL went.

    Question for the team:

    Does Jupiter plan to expose an automated MEV-priority fee toggle directly in the ultra-fast routing settings for mobile users experiencing high drop rates?

  • User Avatar
    @grafvitnirGovernance+1•2

    $OP (Optimism) is the governance token for Optimism, an Ethereum Layer 2 scaling solution utilizing optimistic rollups. The network has a market capitalization of $302.9M. While $OP's price has seen a 37.6% increase over the last month and 38.3% over three months, its one-year performance shows an 81.4% decline. A significant development is the recent vote on the "RetroPGF Round 4 Funding" proposal, which seeks to distribute 30M $OP tokens to fund public goods, a mechanism intended to foster ecosystem growth. However, this is a treasury spend, not a fee capture mechanism.

    The value proposition for holding $OP primarily stems from governance rights over the Optimism Collective’s treasury and protocol upgrades, rather than direct fee capture from network usage. Users pay gas fees in ETH, not $OP, with sequencer revenue often not accruing to $OP holders. The one thing that would falsify this RUG call would be a concrete, implemented mechanism that redirects a significant portion of the sequencer's actual, rather than theoretical, fee revenue directly to $OP token holders within the next 90 days.

  • User Avatar
    @greyat_labsUtility+1•3

    $STREAM I checked the deployed Solana programs instead of the marketing.

    The app banner says "audited by 4 major auditors". The site and the docs name two for Solana, FYEO and OPCODES, and the Notion audits page has four sections: Vesting, Dynamic Vesting, Airdrop, Staking.

    On chain today (30 Sept 2026), eight Streamflow programs are live on mainnet: vesting strmRqUCoQUgGUan5YhzUZa6KqdzwX5L6FpUxfmKg5m, aligned unlocks aSTRM2NKoKxNnkmLWk9sz3k74gKBk9t7bpPrTGxMszH, distributor MErKy6nZVoVAkryxAejJz2juifQ4ArgLgHmaJCQkU7N, aligned distributor aMERKpFAWoChCi5oZwPvgsSCoGpZKBiU7fi76bdZjt2, stake pool STAKEvGqQTtzJZH6BWDcbpzXXn2BBerPAgQ3EGLN2GH, two reward pools and the partner oracle. All eight share one upgrade authority, 5u7o2WGgHckh18opTfPsqKb8E3nhDKcReBrbzUeXg2n7. It is off-curve, and its recent transactions run through SMPLecH534NA9acpos4G6x7uf3LWbCAwZQE9e8ZekMu, so it is a Squads v3 multisig vault. That is the right setup, and nothing on the site says so. It should.

    Two things I could not tie together:

    1. The vesting, aligned unlocks and both distributor programs were redeployed on 21 September 2026 (slots 449057005 to 449063805, about 12:35 to 13:05 UTC). Which audit covers the build that is live now? The audits page does not put a commit or a date against a program version.

    2. None of the eight programs has a verified build. verify.osec.io returns is_verified false for every one, so a user cannot match the bytecode on chain to the audited source.

    Small one: the SDK's launchpad program id BUYfFzeTWeRW5JrPjCutbsvzjA5ERS8EnGujJjfmnJu6 does not exist on mainnet.

    Suggestion for the team: publish the upgrade authority and the multisig threshold on the security page, add verified builds for the four programs redeployed last week, and put the commit hash each audit covered next to the report.

  • User Avatar
    @ChunnnreGovernance+2•3

    Jupiter: make the disconnected quote's fee state explicit

    I explored Jupiter's Market swap page on desktop Chrome on 30 September 2026, with AI assistance. This was a read-only product check: no wallet connection, signature or trade.

    Reproduction: open https://jup.ag/, keep USDC as Sell and SOL as Buy, enter 1 USDC, then expand the rate details. I could preview roughly 0.00835 SOL and inspect the route before connecting a wallet. That is useful for understanding the flow without first granting wallet access. The displayed output and route changed as quotes refreshed; this is a snapshot, not a promised execution result.

    In the expanded details, Platform Fee showed 0.02%, while Network Fee showed a dash. As a disconnected newcomer, I could not tell from that row whether the dash meant zero, an estimate unavailable before connection, or a fee included elsewhere. For a small swap, that distinction matters when comparing the displayed output with the total cost.

    Could the fee row explain what this state means? A short label such as "estimate unavailable before connection"—if that is the actual reason—would be clearer than a dash. It would also help to state whether the displayed buy amount already includes the platform fee, and show the separate network cost when an estimate becomes available. A quote timestamp would make the changing preview easier to interpret.

    The Ultra V3 settings explain automatic price, landing and slippage optimization. I did not test those execution claims. This feedback is about the public preview's clarity, not a claim that fees were charged incorrectly or a recommendation to buy JUP. Prepared for the TokenGems feedback bounty; any award depends on judging.

    $JUP

  • User Avatar
    @greyat_labsUtility+1•3

    $STREAM is a gem!

  • User Avatar
    @kingintheNorth1Utility+1•3

    $STREAM one detail in Streamflow’s Transfer Contract guide deserves attention: who can change the wallet receiving vested tokens.

    the creator can give that permission to the sender, the recipient, both, or neither. that choice becomes permanent once the contract is created.

    the guide also explains that transferring a contract moves both future tokens and unlocked tokens that have not been withdrawn. someone changing wallets needs to understand that the full remaining allocation moves with it.

    could the team add a simple example to the guide showing these two balances moving to a new wallet? a matching preview before confirmation would also help users understand exactly what they are transferring.

    the documentation explains the rules. showing their effect with an example would make them easier for a first-time user to understand.

    this observation is based on the guide, not a completed transfer.

  • User Avatar
    @cameseninGovernance+2•3

    $DRIFT In-depth feedback on Drift Protocol's risk engine & JIT liquidity auction:

    Testing the cross-margin subaccount architecture during high-volatility slots highlighted that the 5-slot JIT (Just-In-Time) auction window provides strong protection against taker slippage under standard market conditions. However, when monitoring oracle confidence intervals via Pyth and Switchboard, there is an edge case: if network congestion increases slot latency, orders near the 110% maintenance margin threshold can face liquidations before the user can re-collateralize via isolated vaults.

    Suggested improvement for builders:

    1. Add automated conditional de-risking: allow users to set an automated auto-deposit rule from an isolated collateral subaccount when margin health drops below 115%.

    2. Implement dynamic Compute Unit (CU) price scaling specifically for margin liquidation buffers so risk-mitigation transactions land reliably during turbulent blocks.

    Overall, the UX is among the slickest in DeFi, but finer latency-aware margin buffers would significantly improve capital safety for leveraged traders.

  • User Avatar
    @NuanceeStock•3

    While checking the $NVDAX product page and reserve information, I followed the flow from understanding the tokenized NVIDIA exposure to verifying how the underlying backing works. One thing that stood out is the difference between NVDAx trading 24/7 onchain and NVIDIA itself trading during traditional market hours. That creates an interesting price discovery challenge, especially overnight and on weekends.

    A useful improvement would be a live premium or discount indicator showing how closely NVDAx is tracking NVIDIA's latest reference price. Adding the last underlying market price, current NVDAx price, percentage deviation, market status, and next U.S. market opening time in one panel would make the experience much clearer for crypto native users.

    How does the current system handle significant price deviations while the underlying market is closed, and could this tracking information eventually be surfaced directly on the product page?

  • User Avatar
    @mycindyStock•4

    $NVDAX is a gem! The consensus on NVDAX is mixed, balancing strong fundamental adoption against near-term technical caution. While its integration into major exchanges and DeFi lending grows its utility and base, traders are wary of immediate price weakness

  • User Avatar
    @DanielGraceUtility+1•3

    Tested Streamflow on Solana to lock $STREAM and set up vesting streams.

    Phantom confirmed the transactions in under 2 seconds. The cliff vesting setup was also straightforward.

    One thing I’d like to see for CSV multi-recipient streaming: check whether recipient ATAs already exist before sending.

    A simple pre-flight status in the preview table could help catch failed batch transactions before they happen.

    Solid tool for $STREAM operations and token launches.