@shirogameGovernance+1•2$TNSR I tested Tensor as a first-time user through the Stonk Cats collection, and overall the core trading experience felt smooth, especially the execution and balance checks when placing a buy or bid. However, I noticed a few areas that could make the experience much better for new users. The biggest issue was the Crossmint card checkout, which immediately failed with a “previously deleted API key” error while the payment form still remained open. If card payments are meant to help non-wallet users onboard, this could create a major drop-off. I also couldn’t clearly understand what holding $TNSR actually provides from the marketplace experience, so adding a simple explanation of its utility or benefits could help connect the token with the product. Finally, clearer verification badges in collection search would help users distinguish official collections from similarly named ones. These are relatively small changes, but fixing them could make Tensor more accessible and less confusing for first-time users.
@sandeepMeme•2I explored $PAYDAY through TokenGems and followed its linked social accounts to verify the project information. The X link from the TokenGems listing points to @getpaydayfun, but X shows that this handle was changed 7 days ago and directs users to @owedfun instead. I also checked $Payday documentation, where @getpaydayfun is still referenced. Could the project update its TokenGems X link and documentation to reflect the current X handle, so new users don't end up on an “account doesn't exist” page?
@KoltrognarekGovernance+1•3$TNSR I used tensor.trade as a new user (Stonk Cats), without buying.
The homepage is already a trader table (floor, sell now, mcap). Lite vs Pro is asked only after you open a collection. Rewards is Tensorians / Referrals / Gib Back — the word TNSR never appears. TokenGems' website icon goes to tensor.foundation, not the marketplace. I still cannot tell what holding TNSR does versus using the app.
Search for "Mad Lads" lists Mad Scientists, Mad Lassies, Mad Skull, Mad Ladios and others with no clear verified mark.
The wallet modal lists MetaMask twice.
Price filter default max on Stonk Cats was 101010 SOL (floor was ~2.1).
Sweep → Pay with Crossmint opened hosted checkout for 21 items / ~54 SOL and failed immediately: "The API key provided was previously deleted, please create or use a valid key." Popup stayed on the card form anyway. If card checkout is meant to onboard non-wallet users, a dead API key is a hard stop.
Buy/bid Execute correctly blocked me at 0.0019 SOL (listing 2.07, royalty 2.5%, taker 0.040). Could Rewards or the token page state in one line what TNSR is for, and can Crossmint be hidden until the key works?$TNSR is a gem!
@OrenrotGovernance+2•5$JUP is a gem!
I looked through the JUP page and Jupiter's token docs without making a trade. The Solana mint shown here, JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN, matches Jupiter's official JUP address. That's a useful check because search results also include unrelated tokens called Jupiter. One point of friction for a newcomer: this page tags JUP as DEX, Governance and Derivatives, while Jupiter's docs describe JUP specifically as its governance token. Could the project page explain more plainly what holding or staking JUP lets someone do, versus what Jupiter's swap and perps products do? A direct link to the official JUP token FAQ beside the mint would make that distinction easier to check. I haven't tested the trading flow, so this is a clarity suggestion, not a trading or price review.
@LumenIGovernance+1•4$MNDE
Was checking out Marinade Liquid today. Connected my wallet (MetaMask, Solana) but haven't staked anything yet. The first thing I wanted to know was how much it costs to get out, and the Unstake tab just says "No positions to unstake". So you can't see the exit fee or how long it takes until you've already deposited. Kind of odd when the homepage says "instantly unstake... no platform fees".
Then I went to the docs and found two answers. The Instant Unstake page says delayed unstake is free for Native, but the Fees and Pricing table says 0.003 SOL flat for Native delayed unstake. Which one is right?
Would be nice to see the fees on the Unstake tab even with an empty wallet (0.2% and about 1 epoch for mSOL delayed, plus the rough instant range), and to fix one of those docs pages. Also a small thing: the same APY shows as 5.01% on the chart and 5,01% in the stake box.
@TieeWireless•4$HNT public-site walkthrough (AI-assisted; no trade): TokenGems links to Helium, and the Solana mint here matches Helium's HNT docs. The HNT page clearly explains carrier offload → HNT burns → deployer rewards. One practical break: its “Buy or sell HNT” button opened https://www.helium.com/plushttps://www.coinbase.com/en-pt/price/helium, which showed “Page Not Found” when checked on September 29. The URL appears to concatenate a Helium path with a Coinbase URL. Please point the button to the intended destination and check it from the public page; if availability varies by country, explain that beside the button. No purchase or trade was made. Reproduction steps and screenshots: https://github.com/Tiee7/tokengems-helium-feedback
@NuanceeMeme•4$PAID
Your Capital Flow page shows the 20% protocol allocation moving through several stages before becoming a buyback and burn. I like that the flow separates these steps instead of presenting the allocation as an already completed burn. How do you handle periods where fees are accumulated but market conditions or execution constraints delay the buyback?
@SherkhanMMUtility+1•3$STREAM
Checked the STREAM burn on-chain and then the Transparency block on streamflow.foundation. The burn is real: tx 4rbViHbm…hchZNv (23 Sep) burned 699,994,595 STREAM, and the mint now shows supply 299,999,952 with mint authority and freeze authority both null. So the 300M cap is enforced by the token itself, not by a promise.
But the Unlock Schedule chart right under "Total Supply: 300M" has not caught up. Hovering the chart: "Now" shows Total Unlocked 237,417,698 STREAM, and the last point (16 Dec 2027) shows 339,864,227 — more than the whole supply. The pie above it says 61.96% unlocked, which is about 185.9M. Looks like the schedule was not rebased after the burn and the founder's allocation return.
Two questions for the team:
1. Could you link the actual vesting contract IDs for the Investors (27.07% locked) and Contributors (10.71% locked) buckets? Streamflow sells verifiable vesting, so letting holders check the remaining locks themselves would be the strongest proof.
2. The pie shows 61.96% unlocked but 48.52% in circulation. What is the ~13.4% (~40M STREAM) that is unlocked but not circulating, and is it under any lock?
@ndt0208Lending•3$KMNO I explored Kamino's automated liquidity vaults and multiply lending loops on Solana. The automated rebalancing mechanism across concentrated liquidity pools is effective at minimizing impermanent loss during sideways volatility. However, during rapid directional price expansions, the vault rebalancing frequency suffers from slight compute-budget throttling on Solana, leading to temporary unhedged exposure before target pool weights sync. Introducing dynamic priority fee adjustment hooks based on live network congestion metrics would significantly tighten execution precision for high-volume vaults.
@langyan41Utility+1•2$MPLX I tested Metaplex's no-code token launch wizard as "Myself" up to the image step. The biggest issue was silent progress loss: after entering a name, ticker and description and reaching the image step, I refreshed the page. It returned to the first screen without a warning, and continuing again showed all three fields empty. Saving a browser draft or warning before reload would prevent users from re-entering their launch details.
I also noticed that Summary presents "Supply: 1,000,000,000" as editable, but clicking it returns to Token details, where no supply control exists. The Genesis docs say supply is currently fixed at 1B, so this row should be read-only and explain the constraint.
I stopped before image upload or Metaplex sign-in; no token was created. Docs: https://www.metaplex.com/docs/dev-tools/cli/genesis/launch
@beejayolodUtility+1•2$STREAM
I reviewed Streamflow's token vesting and streaming infrastructure for Solana projects on the TokenGems dashboard.
While the underlying contract architecture for immutable linear vesting is structurally solid, there is an explicit UX and operational accounting friction point when handling multi-sig cancellation and clawback updates. Currently, if a project sets up a revocable stream for a developer and terminates it prematurely, the unvested balance routes back to the sender's treasury. However, the transaction ledger on Solscan does not clearly separate the recipient's accrued-unclaimed assets from the clawed-back treasury funds without complex manual logs parsing. Introducing a dedicated, on-chain event log distinguishing 'claimed_to_recipient' from 'clawed_back_to_treasury' would drastically optimize reporting workflows for decentralized operations.
Furthermore, allowing contributors to delegate their SPL governance voting power during a standard 6-month cliff period without unlocking token liquidity would heavily advance user utility.
@MinusMedleyMeme•2$NPC one of the few meme coins staying true to it nature, the NFT approach is the best alternative definition of a non-playable-character.
@MAILUtility+1•2$PAYAI I tested the Solana x402 flow and found the 402 payment requirement easy to understand once the flow is set up.
What I liked: the payment requirement is exposed directly through the HTTP response, which makes the underlying payment flow easier to reason about.
One thing that could improve the developer experience is showing the full request → 402 → payment → settlement → response flow in the demo itself. That would make it easier for someone new to x402 to understand where PayAI's facilitator fits in.
One question: could the demo also expose the settlement result or transaction reference after a successful test payment? That would make it easier to verify what happened without checking separately.
- @MinusMedleyUtility+1•2
Oy $POP stands for proof of prompt, the crypto space has been driven into a collective delusion because of VC funded hype projects. Everyone wants to be an AI middleman, even when the entire user-to-AI slop machine funnel has been established and sufficiently monopolized for years now.
@seanxin6Utility+1•2$STREAM is a gem!
Reviewed Streamflow’s token vesting and streaming infrastructure for Solana projects. The contract architecture for immutable linear vesting is solid, but here is a critical UX and operational friction point during real multi-sig management:
1. Cancellation & Clawback Transparency: When a project sets up a revocable vesting stream for an employee or contributor via Squads multi-sig, if the stream is prematurely cancelled, the unvested balance is automatically returned to the sender. However, the transaction receipt on Solscan doesn't clearly delineate between accrued-unclaimed tokens vs. returned clawback tokens in the event logs without manual parsing. Adding an explicit on-chain event log showing "claimed_to_recipient" vs "clawed_back_to_treasury" would drastically simplify accounting for corporate treasuries.
2. Cliff Period Partial Unlocks: Currently, if a stream has a 6-month cliff, the recipient cannot interact with the stream at all. It would be valuable to allow users to delegate voting power (SPL governance) during the cliff period without unlocking token liquidity. Has the team considered integrating SPL Governance voter weight plugins natively into Streamflow lock contracts?
