- @andrewsaul.solGovernance+2•1
$RAY we need to do something about the comments on Launchpad tokens! It's a great feature but a couple of things are making it hard to use well
- tell us the max image size, right now uploads just timeout so it's a guessing game as to what the max size
- let us delete our own comments and let the dev wallet on each token have the ability to delete any comment
- if you post a link the UI says it successfully posted then the post doesn't show up on the token page. Either explicity ban links and say so before people post or allow them. The current 'silent fail' is bad UX
$RAY🦐 Shrimp - @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.
- @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?
- @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.
- @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!
- @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?
- @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.
- @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?
- @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.
- @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. - @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?
- @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.
- @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.
- @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
- @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 - @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.
- @bharath1070Wrapped+1•2
Marinade Liquid: make the disconnected staking preview clearer
I checked https://app.marinade.finance/earn/liquid/ without connecting a wallet and entered 1 SOL in the Stake tab. The screen calculated an annual growth estimate of 0.0502 SOL at the displayed 5.02% APY, while Receive stayed at 0 mSOL ($0.00), with no explanation beside that value.
The useful rewards preview makes the zero receive amount particularly confusing: a newcomer cannot tell whether the quote is unavailable, still loading, or actually zero. Please show an indicative mSOL amount using the protocol exchange rate, or replace zero with “Connect wallet to load quote.” If loading fails, show a retryable status rather than a plausible-looking zero.
This is feedback from the disconnected preview only; no deposit or staking transaction was made. $mSOL
- @Xiu_web3Lending•3
$KMNO Borrowing USDC against SOL and JUP on Kamino Lend today, and ran into a real UX friction point around rate spikes.
When pool utilization pushed past the 85% kink, the borrow APR jumped from ~5% to over 30%. Because of that rate surge, my Health Factor degraded noticeably faster over a 48-hour window—purely from compounding debt accrual, not underlying price drop. Right now, the borrow modal only quotes an instantaneous APR percentage. For anyone holding a carry or swing position, there's zero visual projection showing the actual dollar-cost decay or how fast an ongoing rate spike will eat into your collateral over 24h/72h.
Another pain point with multi-asset collateral: if you deposit both SOL and JUP to back a single loan, there's no visibility into which asset the liquidation bot seizes first during a partial liquidation. I'd much rather have the protocol liquidate more volatile tokens before touching core yield-bearing SOL, but currently there’s no way to set a priority preference.
A simple daily debt-decay estimator inside the position view, plus a user-defined liquidation hierarchy for multi-collateral loans, would make risk management 10x clearer for active borrowers. Curious if the team has ever considered letting users set an automated rate cap to partially deleverage before borrow spikes get out of hand.
- @Discipline_GuyLending•2
$KMNO
Explored Kamino's Automated Concentrated Liquidity Vaults (kTokens) and range rebalancing mechanics on Solana.Specific Observation: Kamino's automated vault strategies rebalance LP ranges to keep capital actively earning swap fees. However, during choppy or mean-reverting market phases, frequent auto-rebalancing introduces substantial "rebalancing drag"—effectively selling the depreciating asset near the bottom of the range and re-buying at the top to re-center liquidity. While the vault dashboard clearly highlights gross fee APY, it lacks a dedicated metric disclosing historical rebalancing drag (realized inventory loss from auto-swaps) across 7-day and 30-day windows.
Constructive Suggestions:
Introduce a "Net Strategy Yield vs Static Range" metric on each liquidity vault card, explicitly subtracting auto-rebalance slippage and swap fees from gross fee rewards.
Provide a user-selectable "Rebalance Sensitivity" toggle (e.g. Tight Range vs Wide Volatility Buffer) allowing depositors to tailor rebalancing frequency to prevailing market volatility.
Question for the Team: Is the Kamino risk and quant team considering dynamic rebalancing thresholds that automatically widen during elevated Solana volatility regimes to reduce unnecessary turnover during sharp whipsaws?
- @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.
- @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.
- @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?
- @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.
- @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!
- @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!