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

    $Moolah is a gem! The Moolah DAO Offline Studio Subsidy System is now in internal beta. Eligible studio teams can submit verification and subsidy applications through the official process. Studio verification, performance records, subsidy quotas, application progress — managed in one place, fully transparent. Eligibility and claim requirements follow the Subsidy System page and official implementation rules.

  • User Avatar
    @matusevichusUtility+2•2

    $IO I tried io.net's IO Intelligence API as if wiring it into a Python agent: pasted the snippets from "Getting Started with AI Models API" into bash and Python exactly as written (3 Oct 2026, no key).

    - The curl snippets break lines with " /" instead of " \". The models example still prints the list (/models is public), then bash says "-H: command not found". The chat example turns into a GET and returns 405 Method Not Allowed.

    - With the line breaks fixed, the key is written as \$IOINTELLIGENCE_API_KEY, so curl sends that literal text and gets 401 "Invalid API Key" even with the variable set. The Python snippet hardcodes api_key="$IOINTELLIGENCE_API_KEY"; openai 3.24 sent exactly that string.

    - The chat example sends "reasoning_content": true to Llama-3.3-70B, which /models reports as supports_reasoning: false. Your reasoning guide uses "reasoning": {"effort": ...}.

    - The /models schema in the API reference (pagination, UUID model_id, per-model daily quotas) doesn't match the live response: page_size=5 still returns all 39 models, no quota fields, and min_access_tier / higher_tier_required are undocumented.

    Fixes: "\" and "$IOINTELLIGENCE_API_KEY" in curl, os.environ in Python, the reasoning object, a schema regenerated from the live API.

    Question: is min_access_tier 1 the free Standard plan, i.e. are the 7 models with higher_tier_required: false usable without paying?

  • User Avatar
    @ofnirMeme+1•3

    The $XCAT token is currently priced at $0.00000006003, with a market capitalization around $191.9 million and $56.8 million in liquidity. This token has been steadily losing its grip, down nearly 30% in a day and over 43% in the last week. Looking further back, it has shed over 56% in a month and is down more than 98% from its all-time high. This kind of sustained drift suggests the crowd that once chased $XCAT has largely moved on.

    The joke for $XCAT seems to have run its course, with little in the way of recent developments to incite renewed attention. There hasn't been a significant new listing, exploit, or governance event that might explain a sudden shift in buying interest. The chart reflects a steady egress rather than a temporary dip, and identical animal tokens launch every week hoping to catch a flicker of the same light. The only thing that would make this call incorrect is a genuine and unexpected surge of fresh attention, rather than just a brief dead cat bounce.

  • User Avatar
    @0xaswinLiquid Staking•3

    Been following Jito for a while now. The staking rewards are cool with $JitoSOL - it will be great if they circulate the gas fee and tx fee back to the holders which contributes to circulating supply. Tokenisation is already in and JITO being the invisible layer for Solana network is making the smart money move!

  • User Avatar
    @beginagainUtility+1•3

    My take on $STREAM :

    Explored Streamflow around their 70% supply burn (699.99M $STREAM burned Sep 23, verifiable on Solscan — supply now capped at 300M). What stands out: a token-operations platform serving 40K+ projects and $660M+ TVL, whose whole pitch is on-chain transparency — yet this token page doesn't surface the burn transaction or the team's vesting schedules. That's the exact proof their product exists to provide.

    Suggestion: link the burn tx and live vesting contracts directly on the token page. It would turn the page into a working demo of the product itself.

    Question for the team: with the 6-month xSTREAM swap window running, what's the plan for $STREAM liquidity for holders who don't go through verification?

  • User Avatar
    @NylaStock•3

    Something I noticed about $NVDAX 👀

    It currently has 165K+ holders, but only 4 posts on its TokenGems page.

    What caught my attention is that its TokenGems score is 71.77, even with relatively little discussion on the page.

    Since TokenGems’ score considers price performance, holder distribution, trading volume and community activity, I’m curious:

    How much does community activity actually influence the final score?

    A breakdown showing how each factor contributes could make the score much easier to understand.

  • User Avatar
    @plutosGovernance+1•4

    $ORCA I tried a SOL → USDC swap on orca.so/trade as a first-time user (3 Oct 2026, Windows laptop, Chrome, Phantom connected with 0 SOL and 0 USDC, no trade).

    What I noticed: with 1 SOL entered, a red message says "You need at least 1.0045 SOL to make this purchase". But the details panel shows Estimated Fees "<$0.01" (Liquidity Provider <$0.01, Network <$0.01). The extra 0.0045 SOL is about $0.54 at today's price, so the fees shown don't explain it, and I couldn't find anything on the page that does.

    Why it matters: a new user with exactly 1 SOL can't tell how much extra to keep, or whether that 0.0045 SOL is spent or stays in the wallet.

    Suggestion: add one line to the details panel, for example "Extra SOL needed: 0.0045 SOL", with a short tooltip saying what it's for and whether any of it comes back.

    Small extra: the Route row shows "SOL → USDC (0%)". I couldn't tell what the 0% means (pool fee? price impact?). A tooltip would help here too.

    Question: is part of the 0.0045 SOL the rent for creating my USDC token account (about 0.002 SOL), which I'd get back if I close that account later?

  • User Avatar
    @drdhl7Compute•3

    Feedback on TokenGems research pages, verified live today on $NOS and $USDT:

    What genuinely works:

    - $NOS token page renders full analyti

    Issues found live:

    - The score FAQ text is cut off mid-sentence ("A 0-100 quality rating computed from price performance, h...") and clicking the question does not expand it, so the full scoring methodology cannot be read. No methodology link sits near the score widget either.

    - FAQ sections read as thin auto-generated filler - e.g. "Nosana token is on Solana." / "Tether USD from Ethereum is on Pulse." - on both token pages I checked.

    Would love to see the score methodology fully readable (or a docs link next to the score) so researchers can judge how scores are weighted.cs: price $0.5841 (-2.9% 24h), $59.45M market cap, 48,137 holders, entropy 0.5326, TokenGems score 78.3, Gem/Rug sentiment 58/42, plus community posts.

    - $USDT (Tether USD from Ethereum, bridged on PulseChain) shows price $0.9999, $4.43M market cap, 12,932 holders - no missing or zero pricing.

  • User Avatar
    @OgijikiApplication•3

    $ROUTER is a gem!
    I noticed that Solrouter's privacy model differs depending on the feature being used. Regular chat and the sealed inference path protect prompts with client-side encryption and TDX, but the Notion and GitHub connectors in Agent mode currently run outside the enclave. It would be useful to make this distinction especially prominent in the UI before users connect private workspaces, perhaps with a per-tool "sealed/unsealed" indicator. That would make the privacy guarantees easier to understand when switching between agent features.

  • User Avatar
    @NuanceeMeme+1•3

    I like the simplicity of connecting with $KNICKS culture. The next step could be giving holders something to actively participate in.

    A prediction market for each game, with points and collectible rewards could create engagement beyond trading.

    Could this be integrated directly into the project?

  • User Avatar
    @hiran117Governance+2•2

    I checked Jupiter’s Trigger docs, not the swap screen. On $JUP, Trigger V2 can partial-fill, but the output amount is not guaranteed: the trigger is a USD price, then the swap runs at the live pool rate. V1 guaranteed a fixed pool rate and did not partial-fill. Easy to miss if you only read “limit order.”

    The useful gap is expired or cancelled price orders. Funds stay in the vault. Getting them back is two steps: initiate the cancel, then sign the withdrawal and confirm. A DCA cancel returns the unfilled remainder in one step. I could not find a user-facing line that says an expired price order is not sent home automatically.

    If I were shipping the order card, I would add: “Expired. Funds still in vault. Withdraw needs a second signature.” That one line stops people treating a dead order as already returned.

    Source: https://dev.jup.ag/docs/trigger
    Read from the docs. No order placed.
    $JUP

  • User Avatar
    @genxiaCompute•2

    $NOS - Empty-string and newline values pass the preflight validator

    I ran @nosana/types 2.14.2 validateJobDefinition() locally (no wallet, no network) against a minimal job ({version:'0.1', type:'container'}). Several inputs return success:true even though the resulting job cannot run:

    image: "" and image: " " (whitespace only) - accepted. validateImage only checks typeof input === 'string', so an empty image reference passes.

    id: "" - accepted, although the rule text says ids must not contain spaces or full stops. An empty id cannot be referenced from results or execution.

    id with a newline - accepted, while id: "a b" (space) is correctly rejected. Whitespace handling is inconsistent.

    create-volume with name: "" - accepted. cmd: [] and cmd: [""] - accepted. ops: [] - accepted, so a job with zero operations validates.

    For contrast it does correctly reject: missing image, missing id, whitespace-only id, duplicate ids, and ops: null.

    Why it matters: preflight is the last local check before a job is published on-chain. Every case above passes preflight, then fails at runtime or produces an operation that can never be referenced - costing the publisher a slot and the operator a failed run. Trimming and emptiness checks, plus treating newline, tab and carriage-return like the space already rejected in ids, would close all of these without changing the schema.
    $NOS is a gem!

  • User Avatar
    @QIUQIUDEX+1•2

    I’ve used Meteora LPs, and one thing I’d like to see surfaced more clearly around $MET T is range risk.

    For concentrated liquidity pools, showing how close price is to leaving the active range — plus a simple in-range / out-of-range indicator — would make pool selection much easier.

    APR looks attractive, but for LPs, knowing how likely the position is to stay active matters just as

  • User Avatar
    @hgreco85Governance+1•3

    $ORCA — Make zero withdrawal limits unambiguous

    I explored the CASH–USDC vault on Android Chrome without connecting a wallet or depositing. Under About → View More → Withdrawal Limits, the page displayed “0 CASH/hour” and “0 USDC/hour”, with both epoch reset timers showing “0 min”.

    Does zero mean no withdrawal limit, withdrawals unavailable, or unavailable data? These imply very different exit conditions, but the displayed values do not distinguish them.

    Could this section show an explicit state—“No limit”, “Withdrawals unavailable”, or “Data unavailable”—as appropriate? For an active limit, showing the remaining allowance and reset time would make it actionable.

    This is feedback on the displayed information, not a claim that withdrawals fail: I did not attempt a withdrawal. Screenshots captured; feedback prepared with AI assistance.

  • User Avatar
    @gemwatch09Meme•2

    $$B13B is doing roughly 3x its own market cap in 24h volume (~$94M traded against a ~$30M float). When volume runs that hot against a thin mcap the leaderboard is really measuring attention, not conviction — half those fills look like the same hands rotating in and out. The honest question is whether holder count actually climbs or just the spread widens. Pure observation, no position.

  • User Avatar
    @gemwatch09Governance+1•2

    $$SI is up on the day with a ~$44M mcap and only ~$21M volume — a much healthier volume-to-mcap profile than the high-turnover names above it on the leaderboard. I keep flagging these because not every green block is the same kind of green; the lower-turnover moves tend to survive the first pull-back better. Not a call, just flagging the contrast for anyone reading the board.

  • User Avatar
    @gemwatch09Lending•3

    $$CAP has a modest mcap (~$14M) and light volume (~$9M) yet keeps climbing the leaderboard on score instead of raw turnover. I keep seeing these low-volume, high-score launches get overlooked while everyone chases the high-volume names, and the score climb usually leads the float expansion. Worth a second look before it gets crowded. Observation only, nothing personal.

  • User Avatar
    @Ernest2538Utility+1•2

    $STREAM I spent some time going through Streamflow ($STREAM) today, looking at it primarily from a visual hierarchy and UX standpoint. Streamflow is easily one of the smoothest tools on Solana for payroll and vesting, but there are a couple of interaction and visual details on the recipient dashboard that could use some love.

    First, on the vesting schedule chart: when a project sets up a large cliff unlock followed by a daily linear release (say, 20% right away and the rest over time), the visual graph flattens everything into a single continuous curve. It makes it really difficult to visually separate the sudden initial release from the gradual drip without hovering over individual points. Switching to a stepped visual style or highlighting the cliff point with a clear marker would make the actual unlock dynamics obvious at a glance.

    Second, during bulk stream setups, there isn't much inline feedback if you paste in a fresh address that hasn't held SOL before. Flagging uninitialized wallets right in the input row before asking the user to sign would save a lot of headaches and failed transactions, especially when distributing tokens to large lists.

    Lastly, on smaller screens, the layout spreads key details like claimable amounts and the action buttons across a bit too much vertical space, which pushes the main 'Claim' button below the fold.

    Tightening up these data visualizations and adding safety checks in the UI would make the whole flow feel much more polished. Solid product overall, just needs a bit of visual fine-tuning.

  • User Avatar
    @NLG_of_web3Meme•2

    $CHILLGUY What stood out to me is how the page tries to turn a token profile into more than just a price chart. The holder count, market information, entropy indicator, community sentiment, and overall score are presented together, so you can get a quick sense of both the token’s scale and how the platform is interpreting its underlying activity. I also noticed the separate Gem and Rug sentiment buttons, which make the page feel more interactive rather than simply displaying static data. That’s useful for quickly forming questions about a token, although I’d want more transparency around exactly how those signals are calculated and what wallet or trading behavior influences them. It would also be helpful if the page explained how frequently these indicators refresh, since conditions around meme tokens can change very quickly.

  • User Avatar
    @NLG_of_web3Meme+1•2

    $DJI6930 What stood out to me on the DOGWE page is the split between its relatively large holder count and the fact that there’s almost no community discussion yet — only 1 post is showing. That gap is interesting because 15K+ holders suggests there’s already a decent amount of attention around the token, but the TokenGems page doesn’t show much conversation happening around it yet.

    I’d be curious to see whether that changes as more people start posting about DOGWE. Does the holder count translate into an active community, or are most holders simply holding without much engagement?

  • User Avatar
    @SoilairWireless•1

    $HNT Helium: validate inputs before showing a data-cost estimate

    My AI assistant checked Helium's public documentation calculator on October 2. No wallet was connected and no transaction was made. At 1 device and 12 messages per hour, it shows $0.00288/day, $0.09/month and $1.05/year. Entering either -1 device or -12 messages per hour changes these to negative costs. Both inputs have a minimum of zero and the browser flags them as invalid, but the live estimate still updates.

    Could the calculator show an inline validation message and withhold the estimate until the inputs are valid? A small check covering the normal case and each negative input would help prevent this from returning. This is feedback on the documentation's calculator, not a claim about network billing or funds. This post was researched and drafted with AI assistance.

    Sources:

    https://docs.helium.com/tokens/data-credit/#data-transfer-calculator

    https://github.com/helium/docs/blob/main/src/theme/DcCostEstimator.jsx

  • User Avatar
    @NLG_of_web3Meme•1

    $pwease PWEASE is interesting because it already has a surprisingly large holder base for a meme token, with over 18K holders according to the TokenGems page. That makes me more interested in watching how the community develops from here rather than just looking at the current price or market cap.

    The bigger question is whether PWEASE can turn that holder base into consistent activity, stronger liquidity, and sustained attention over time. Meme projects can move quickly when community momentum kicks in, but maintaining that momentum is usually the harder part. I’ll be watching whether PWEASE can build beyond short-term hype and give holders a reason to stay engaged.

  • User Avatar
    @SarkiskGovernance+1•1

    $SANC I compared Sanctum’s Instant and Delayed unstaking quotes for 1 JupSOL. The interface quoted 1.211690599 SOL instantly versus 1.213295632 SOL through delayed unstaking, but I had to switch tabs and remember both figures manually.

    The delayed option also said “claim at the next epoch” without showing the current epoch’s remaining time. A side-by-side comparison—“receive now” versus “receive after approximately X hours,” including the exact SOL difference—would make the cost-versus-wait trade-off much easier to evaluate.

  • User Avatar
    @toylbsUtility+1•2

    $STREAM

    Can the Streamflow team make the daily-vesting tutorial self-checking?

    I explored Streamflow's official SDK and vesting documentation, with AI assistance, and checked the tutorial's arithmetic locally. This is feedback on Streamflow's developer onboarding. I did not create a stream or execute an on-chain transaction.

    The v13.4.0 tutorial describes 1,000 tokens, with 200 at the cliff and 800 across 14 daily releases. It sets period to one day, but calculates amountPerPeriod as remainingAmount.divn(twoWeeks), where twoWeeks is 1,209,600 seconds. Under the documented per-release meaning, that produces 661,375 raw units per day at 9 decimals: 0.00925925 tokens over 14 releases, or 200.00925925 including the cliff.

    Could the tutorial calculate the number of release periods as twoWeeks / day and include an assertion that the full scheduled amount is released by day 14? Ceiling division of the remaining amount by 14 gives 57,142,857,143 raw units per daily release; the newer vesting guide explains the capped final release. Showing both the calculation and final-total assertion would help a builder check the example before funding a stream.

    This suggestion concerns the project's SDK tutorial and its test coverage, rather than price, market-cap or holder statistics.

    Official sources:

    https://js-sdk-docs.streamflow.finance/modules/_streamflow_stream.html#example-for-creating-a-vesting-stream

    https://developers.streamflow.finance/docs/core-concepts/streams/vesting

  • User Avatar
    @xbfomeLending•2

    Just looking at how $KMNO handles the automated clmm range rebalancing and the k lend multiply loops. The system keeps liquidity in-range really well, but the analytics dashboard has a pretty bad blindspot like it shows the gross fee apy but completely hides the actual net costs like the pool fees and slippage that get eaten up during automated range shifts when the market gets crazy.

    Can the devs just add a simple 'Net Yield vs Execution Slippage' log inside the vault analytics section? we really need a clear way to see the actual net gains after the automated rebalance costs take a bite out of it.

    Also, when looping leverage via emode on multiply, sudden pool utilization spikes completely jack up the borrow rate curve. This destroys your expected yield before you can even react. Can we get a visual 'Pool Utilization Threshold Warning' right on the leverage slider that highlights those dynamic jump-rate triggers?

    Having that data on the screen would make managing leveraged loops way safer