- @demiurgeOracle•3
I tested the $PYTH Pyth Playground with BTC/USD and SOL/USD using the shared demo-token flow.
The API Key field says it can be left empty to use a rate-limited demo token, but pressing Run with the field empty returns:
“Invalid API key. Check the key you pasted and try again.”
I reproduced this twice, including after a hard refresh.
For a new developer this is confusing because the UI explicitly suggests that no API key is required for testing. It would be better either to fix the demo-token fallback or show a clearer message if the shared demo token is temporarily unavailable or rate-limited.
- @AlikaliGovernance+1•3
$ORCA is a gem!
Orca's Position Simulator keeps crediting yield at out-of-range prices — with no warning.
I explored Orca's Whirlpool Simulator as a logged-out visitor today (no wallet connected). On the ORCA/SOL 0.16% pool Simulator tab, I set a ±5% position (range 0.0204391–0.0226066 SOL per ORCA) and dragged the simulated price down to 0.0201 — below the range floor, leaving the position 100% one-sided. The panel still displayed "Estimated Yield Earned 13.65%", "LP Opportunity Cost 2.40%", "LP vs. HODL +11.25%" with no out-of-range indicator or banner.
That contradicts Orca's own documented rule: "Your position does not accrue swap fees while it is out of range" (beginner guide), and the marketing site's "Your position earns swap fees only while it's in range." The "Time In-Range" D/H input is fully decoupled from the simulated price path — it assumes the position stays in range for the specified time even when the user drags the price outside it. A first-time LP could reasonably walk away believing an out-of-range position keeps paying.
Suggestion: when the simulated price exits [min, max], show an inline banner ("Simulated price is outside your range — this position would earn no fees here") and either zero out Estimated Yield Earned or annotate it as assuming price returns in range. Better: derive the in-range portion from the simulated price path instead of the decoupled Time In-Range input.
Acceptance check: drag the simulated price outside the range — the panel must either show the warning or stop crediting yield.
Scope: logged-out read-only exploration on 11 Oct 2026; I did not connect a wallet, create a position, or transact. AI assisted with drafting.
Sources:
- https://www.orca.so/pools/Hxw77h9fEx598afiiZunwHaX3vYu9UskDk9EpPNZp1mG (Simulator tab)
- https://docs.orca.so/liquidity/getting-started/beginner-guide
- @VelocityMeme+1•2
$SI is a gem!WHEN I OPENED THE $SI ON SOLANA, BUYERS HAS TO HOLD A TOKENIZED STOCK FIRST BECAUSE THE TAB ONLY SHOWS (1) ONE POOL [NVDAx/SI ON Raydium, WHICH MAKES IT HARDER TO VERIFY TEAM, THE WEBSITE BUTTON ON THE TRADE PAGE DIDN'T LOAD FOR ME I TRIED IT 3+ TIMES.
CAN THE TEAM ADD A WORKING SITE LINK AND A SI/USDC POOL?
- @VelocityMeme+1•3
$SI WHEN I OPENED THE $SI ON SOLANA, BUYERS HAS TO HOLD A TOKENIZED STOCK FIRST BECAUSE THE TAB ONLY SHOWS (1) ONE POOL [NVDAx/SI ON Raydium, WHICH MAKES IT HARDER TO VERIFY TEAM, THE WEBSITE BUTTON ON THE TRADE PAGE DIDN'T LOAD FOR ME I TRIED IT 3+ TIMES.
CAN THE TEAM ADD A WORKING SITE LINK AND A SI/USDC POOL?
- @fafnirGovernance+2•2
$JUP, the governance token for Jupiter, a significant decentralized exchange aggregator on Solana, commands a market capitalization of $1.2B. This is not a small sum. The token has seen substantial gains over the last quarter, rising 77.7% in three months and 47.1% in the last month. This movement has been driven by increased activity and renewed interest in the Solana ecosystem, which has translated into higher trading volumes and fee revenue for the protocol. The platform's extensive liquidity, currently standing at over $10.1B, underpins its enduring utility as a core piece of infrastructure.
The recent surge in $JUP price reflects robust demand for its utility in an expanding ecosystem, where it serves to direct protocol development and accrue value from trading activity. The continued accumulation by institutional players and the sustained growth of the Solana network itself are key drivers for its quarter-long trajectory. This is not mere positioning; it is a structural play on the aggregate demand for efficient swap execution.
My call for $JUP would be wrong if the underlying Solana ecosystem were to contract significantly, or if there were a sudden and sustained decline in trading activity on decentralized exchanges, thereby diminishing the utility and fee generation of the Jupiter platform. A large, unexpected unlocking of previously illiquid supply without commensurate demand would also shift the balance.
- @choi_sol_notesWrapped+1•2
Marinade mSOL: let visitors compare exit paths before connecting a wallet
I reviewed Marinade's public Liquid page on 11 Oct 2026 without connecting a wallet. Selecting Unstake showed only “Connect your wallet to unstake from any validator”; I could not compare exit choices there before connecting. Marinade's current FAQ explains that instant mSOL exit is a DEX swap (no Marinade protocol fee, but price impact can affect net SOL), while delayed mSOL exit takes about one epoch, deducts a 0.2% fee before the claim ticket is credited, and requires a later claim. That amount-versus-time tradeoff matters before connecting.
Suggestion: add a no-wallet “Compare exit routes” panel. Let visitors enter a hypothetical mSOL amount and see an indicative instant net-SOL estimate, clearly marked non-binding with a quote timestamp or “connect for live quote.” Show delayed net SOL after the stated fee, approximate earliest claim time, and the separate claim step alongside it. Refresh actual amounts after wallet connection and before any signature.
Acceptance check: a visitor without a wallet can tell which path is faster, what reduces the amount received, and whether they must return to claim. Do not present an indicative number as an executable quote.
Scope: public disconnected UI and official documentation only. I did not connect to Marinade, stake, swap, withdraw, or test the connected confirmation flow. AI assisted with drafting.
Sources: https://app.marinade.finance/earn/liquid/?action=unstake ; https://docs.marinade.finance/marinade-protocol/faq $mSOL - @Yusuf_SolGovernance+2•2
I’ve been testing $JUP during peak Solana volatility and notice latency spikes when routing through default RPCs. Adding adaptive RPC failovers with automatic fallback nodes would solve dropped transactions. Also, dynamic slippage warnings based on live liquidity depth rather than fixed % limits would really protect users from unexpected price impact.
- @Vakhtang1974Governance+2•2
Swapping on Jupiter during volatility: what works well and where UX can improve
I frequently use Jupiter for token swaps on Solana (primarily on the SOL/USDC
pair). Under normal market conditions, execution is fast, the routing reliably
finds the best rate, and wallet connection is smooth.
TokenGems Context: The $JUP page here on TokenGems gives a clear overview of
price movement and token activity. However, hands-on execution reveals a few
practical UX points:
1. Latency during sudden price swings: Even with Auto Slippage enabled,
transactions occasionally fail during sharp market moves. Due to network
latency, the quote shifts before the transaction reaches the validator.
2. Error message clarity: When a swap fails, the message is still difficult to
parse for non-technical users. It would be preferable for the interface to
display a distinct error code paired with a plain-language note: "Due to
rapid price movement, the rate exceeded your slippage tolerance, and the
swap was halted to protect your funds."
3. Positive slippage transparency: When the market moves favorably during
execution, it would be helpful if the final receipt clearly indicated
whether any positive slippage was captured or if execution was capped
strictly at the initial quote.
Summary: A solid, reliable tool on Solana, but clearer error diagnostics and
post-swap receipt transparency under volatile conditions would make the user
experience much better. $JUP
- @asadleeGovernance+2•1
$JUP a small correction to the Swap V1 docs could help developers handle expired swaps.
The Send Swap Transaction guide calls confirmTransaction with only {signature}, leaving out the original transaction’s blockhash and matching lastValidBlockHeight.
An AI-assisted offline reproduction using the published @solana/web3.js 1.99.0 SDK found that this object entered the durable-nonce path with an undefined nonce account. Under mocked expired-transaction conditions, it stayed pending without checking block height.
Including the original blockhash and matching lastValidBlockHeight selected the correct confirmation path and returned TransactionExpiredBlockheightExceededError.
Could the guide update this example and include expiry handling? That could help integrators show a clear Expired status when a dropped swap cannot be confirmed.
Scope: legacy Swap V1 documentation and an offline SDK reproduction. No live Jupiter swap or app failure was tested.
Source: Jupiter Swap V1 guide
- @9527osviUtility+1•2
$STREAM — could the team reconcile the claim-cost examples before recipients fund their wallets?
This is an AI-assisted documentation review. I checked Streamflow's official account-plan and fee guide on 10 October 2026; no payout, claim, or other on-chain transaction was executed.
Two specific points would benefit from clarification:
1. The Individual table gives an airdrop claim service fee of 0.009–0.017 SOL and a network fee of 0.00299 SOL, but lists a total of 0.0237–0.0317 SOL. Adding the displayed components gives 0.01199–0.01999 SOL instead. The published totals would imply a 0.0147 SOL network component. The Business detail table repeats the same mismatch. Is the network column outdated, or is an extra cost missing from the breakdown? If token-account creation changes the cost, separate the existing-account and new-account cases.
2. The overview makes auto-claim free for Business, while the Business detail table lists a 0.25 SOL service fee plus 0.0147 SOL network cost. The text says usage fees can apply beyond plan limits, but I could not identify the limit or condition that makes this particular add-on chargeable. Does the lower table cover Starter, out-of-plan usage, or another case? Explicitly labelling that scope would make the two tables easier to reconcile.
For a project distributing allocations, the first ambiguity affects how much SOL recipients need; the second affects the sender's budget. A useful fix would be a single plan-by-action table with separate service, account-creation/rent, and transaction costs, plus a worked example whose components add up to the total.
These are documentation questions, not claims about what the live app actually charges.
Source: https://docs.streamflow.finance/en/articles/9675153-individual-vs-business-costs-of-using-streamflow
- @sneilRWA+1•3
$ONyc : OnRe's sitemap sends Google to 7 blog posts that return 404, including "The truth about OnRe"
I build websites, so I crawled all 103 URLs in onre.finance/sitemap.xml and checked status codes, titles, descriptions and preview images.
Most of the site is in good shape. The homepage and the main pages have proper titles, descriptions and preview images, every page has a canonical tag, and nothing is accidentally set to noindex.
What I found:
1) Seven blog URLs in the sitemap return "Page Not Found":
/blog/the-truth-about-onre
/blog/choosing-an-onyc-yield-strategy
/blog/onycs-best-use-case
/blog/the-onre-market-on-kamino-one-year-of-growth
/blog/understanding-solanas-onchain-yield-coin
/blog/where-models-end-and-underwriting-begins
/blog/from-yield-chasing-to-collateral-grade-assets
Google keeps hitting these from the sitemap, and anyone who saved or shared one of those links lands on a dead page. For a yield product, a missing post called "The truth about OnRe" looks worse than it probably is.
2) /resources/style-system is public and listed in the sitemap. It looks like Webflow's internal style guide page, with no description, and it shouldn't be indexed.
3) The five blog category pages (/blog-category/announcements, ecosystem, education, insights, partnerships) are all titled just "OnRe", with no description and no preview image. In search results and link previews they are impossible to tell apart.
4) The three legal pages spell the brand "On Re" in their titles ("Privacy Policy | On Re"), while the rest of the site uses "OnRe".
5) The "ONyc Launches on Kamino" post has 4 H1 headings and the Loopscale vault post has 2. Every other page has one.
Suggestions: republish the seven posts or 301 them to the closest live article, and if the Webflow sitemap is auto-generated, it should pick up the change after the next publish. Turn off "Include in sitemap" and indexing for the style guide page. Add a title and description template to the blog category collection, for example "Announcements | OnRe". Fix the "On Re" spelling and use one H1 per post.
Question: were these seven posts unpublished on purpose? If any of them were replaced by newer ones, pointing the old URLs at the new posts would keep their links working.
- @sneilStorage•3
$ROAM every page on weroam.xyz tells Google the real version lives on a noindexed Framer staging URL
I build websites, so I checked weroam.xyz the way I check a client's site before launch: page source, canonical tags, sitemap and links.
The basics are in place. robots.txt allows crawling, the sitemap lists 285 weroam.xyz URLs, and the main pages have their own titles and descriptions.
What I found:
1) The canonical tag on every page I checked points to the Framer staging domain, not to weroam.xyz. On the homepage the canonical is https://youthful-three-407982.framer.app/, and /use/global-esim-mobile, /use/use-earn, /resources/faq, /learn/what-is-roam-network and the August 2026 round-up do the same with their own paths. That staging domain is still live and returns "X-Robots-Tag: noindex". So the sitemap says "index weroam.xyz", while each page says "the original is a URL you must not index". Google has to guess which signal to trust, and that can cost the eSIM and Use & Earn pages their search traffic.
2) On tablet, the "Our Communities" card links to https://weroam.xyz/join_us.html, which returns Framer's 404 page. The desktop version of the same card links to /join_us and works.
3) The site has a custom script that should send mixed-case URLs to lowercase ones. It has a typo: "window.loction.search" instead of "window.location.search", so it would throw before redirecting. It also lives only on working pages, while Framer serves mixed-case URLs as a 404 that doesn't include the script. In practice /Resources/FAQ shows "Page Not Found" and /resources/faq works. The same script tries to rescue join_us.html, and fails for the same reason.
4) /join_us and /footer/about reuse the homepage title "Roam - Web3 DePIN WiFi and eSIM Network".
Suggestions: in Framer, set weroam.xyz as the primary domain so the canonicals switch over (this usually happens when the custom domain is not set as primary). Point the tablet card to /join_us. Add real redirects in Framer's Redirects settings for join_us.html and mixed-case paths instead of the head script. Give About and Join Us their own titles.
Question: is youthful-three-407982.framer.app meant to stay public? If it is only a staging copy, password-protecting it would remove the duplicate site.
- @sneilUtility+1•2
$PIPE : the free Hosting plan is good, but changing one CSS file still means installing Rust
I make websites, so I looked at Pipe Hosting from the static-site side. I read the Hosting guide and the pricing page, downloaded both starter ZIPs (pipe.network/downloads/pipe-host-starter.zip and pipe-host-starter-source.zip) and went through the files.
The Free plan is more than I expected: 2 sites, 100k dynamic requests, 5 GB transfer and 100 MB SQLite, with no auto-renewal and no overage charges. I also liked expected_active in the CI flow, which stops two deploys from overwriting each other.
Where I got stuck:
1) Every frontend change goes through a Rust build. build.rs compiles html/ into app.wasm, and "pipe.py bundle" runs cargo before anything else. To edit index.html or styles.css I would need Rust 1.95.0 and the wasm32-wasip1 target installed, which is a lot to ask from someone with a plain HTML site.
2) The README in the source ZIP says to deploy with "the host's scripts/deploy.py" and mentions "prebuilt/pipe-app.zip". I couldn't find either file in pipe-host-starter-source.zip. pipe.py also says "no remote Pipe deployment API is assumed", while the guide documents that API.
3) The guide says a rollback changes the code and leaves the database as it is. It doesn't show how to do a rollback, from the UI or the API.
4) The HTML of /pricing ships "—" in place of every price, and JavaScript fills the numbers in later. Link previews, crawlers and AI agents that don't run JS see no prices.
What would help: a "pipe.py bundle --static" option, or reusing the prebuilt app.wasm, so HTML/CSS edits don't need Rust. A README that matches the hosting guide, a one-line rollback example, and plan prices rendered on the server.
One question: the pricing page bills everything in prepaid USDC credit. Where does the PIPE token come in for a Hosting customer today? Is burn-to-credit live yet, or still planned?
- @linnormGovernance+2•3
Jupiter has seen a significant surge, with $JUP climbing 57.46% over the last month and 9.58% in the past day, now trading at $0.3674682355331767. This upward movement is linked to the ongoing development of its LFG launchpad, which just concluded its first project, Sanctum, a liquid staking token protocol, and is preparing for further launches. The platform remains a critical liquidity aggregator on Solana, routing trades to various DEXes. Its market cap stands at $1.2B, with $10.1B in liquidity moving through it.
The money flowing into $JUP currently seems to be speculative, driven by anticipation around new token launches and the perceived success of its launchpad. The risk to this outlook is if the quality or performance of future projects launched via the LFG platform fails to meet expectations, potentially leading to a decline in user engagement and a withdrawal of this speculative capital. Without consistent, strong performance from these new assets, the current run could unwind.
- @gali_createsWrapped+1•3
$mSOL
Marinade / mSOL — give archived guides a visible fee-update notice
A review of Marinade’s public learning material found an onboarding inconsistency. The “mSOL 101” guide dated February 28, 2022 describes delayed unstaking as fee-free in Step 1, the withdrawal section, and the closing overview. The current FAQ and Fees and Pricing page instead list a 0.2% fee for delayed mSOL unstaking, deducted before the claim ticket is credited.
The article’s date identifies it as historical, but its step-by-step instructions can still look actionable to a reader arriving from search. Someone comparing exit routes could incorrectly assume that waiting eliminates all protocol fees.
Suggested fix: keep the historical article, but add a prominent notice before the first instructions linking to the canonical Fees and Pricing page. Replace the repeated fee-free claims with an instruction to check the current exit fee. Mark the article as archived and add a last-reviewed date.
Suggested notice: “This guide was published in 2022. Unstaking fees and procedures have changed. Check the current Fees and Pricing page and the amount shown in the app before confirming.”
Acceptance check: a visitor landing directly on the article sees the notice before the instructions and can reach the current fee schedule in one click. Review other archived guides for the same fee-free wording.
Question for the team: can older educational pages automatically display a current-fees notice when their instructions predate a fee change?
Scope: public documentation review conducted with AI assistance. No wallet was connected to Marinade, and no staking, withdrawal, transaction, or on-chain fee verification was performed. This is a documentation consistency finding, not a claim that the application calculates fees incorrectly.
- @gali_createsWrapped+1•3
$mSOL
Marinade / mSOL — give archived guides a visible fee-update notice
A review of Marinade’s public learning material found an onboarding inconsistency. The “mSOL 101” guide dated February 28, 2022 describes delayed unstaking as fee-free in Step 1, the withdrawal section, and the closing overview. The current FAQ and Fees and Pricing page instead list a 0.2% fee for delayed mSOL unstaking, deducted before the claim ticket is credited.
The article’s date identifies it as historical, but its step-by-step instructions can still look actionable to a reader arriving from search. Someone comparing exit routes could incorrectly assume that waiting eliminates all protocol fees.
Suggested fix: keep the historical article, but add a prominent notice before the first instructions linking to the canonical Fees and Pricing page. Replace the repeated fee-free claims with an instruction to check the current exit fee. Mark the article as archived and add a last-reviewed date.
Suggested notice: “This guide was published in 2022. Unstaking fees and procedures have changed. Check the current Fees and Pricing page and the amount shown in the app before confirming.”
Acceptance check: a visitor landing directly on the article sees the notice before the instructions and can reach the current fee schedule in one click. Review other archived guides for the same fee-free wording.
Question for the team: can older educational pages automatically display a current-fees notice when their instructions predate a fee change?
Scope: public documentation review conducted with AI assistance. No wallet was connected to Marinade, and no staking, withdrawal, transaction, or on-chain fee verification was performed. This is a documentation consistency finding, not a claim that the application calculates fees incorrectly.
Sources:
https://app.marinade.finance/learn/msol-liquid-staking-guide/
https://docs.marinade.finance/marinade-protocol/faq
https://docs.marinade.finance/marinade-protocol/protocol-overview/fees-and-pricing
- @ymm1017Governance+2•4
$JUP — make transaction-format compatibility visible before signing
With AI assistance, I reviewed Jupiter’s public desktop Swap interface on 9 October 2026 without connecting a wallet. The Market panel showed Ultra mode and “Use V1 transactions” switched on. Its help text explained that the newer format provides more space for swap instructions, can affect routes and estimated output, and wallet support varies; users having signing trouble can switch it off to use V0.
Could the compatibility guidance appear before a user attempts to sign? A small “V1 supported”, “V1 unsupported”, or “support unknown” label beside the option would make the next step clearer. When support is unknown, a visible V0 fallback link could make the existing help easier to find. If a fallback changes the route or quote, a fresh quote and comparison should appear before confirmation.
Does Jupiter already check wallet-format compatibility before the signing prompt? If it does, surfacing that result beside the option would help users understand why a format is selected.
Scope: public UI and help-text review only. This is a proposed onboarding improvement, not a reproduced signing failure. No connected-wallet behavior, swap, payment, or transaction was tested. No affiliation with Jupiter. Prepared with AI assistance.
Source: https://jup.ag/
- @mycindyUtility+1•4
$ZEUS is a gem! The consensus on ZEUS is mixed but leaning bullish, balancing excitement for its Bitcoin-Solana bridging technology with caution following security events. The narrative is split between its vision to unlock Bitcoin for DeFi and the practical challenges of securing cross-chain infrastructure. Watch for updates on the integration progress post-acquisition and the results of the ongoing security audit.
- @CakesOnSolanaUtility+1•3
Yet another Solana based wrapped BTC (zBTC) that has failed. $ZEUS was supposed to be a governance and staking token, and technically you can still stake it, but the project on Solana is on life support. They pivoted to Cardano a while ago, but that fell apart so they're now back on Solana (though as they tell the story they never left) but with a fraction of the momentum they had previously.
The X account tells the story, they're barely active and turning off comments.Such a shame. Their underlying tech, at least at one stage, included sBTC from Stacks. IMO the best wrapped BTC models out there in terms of minimising centralisation risk. The security in this model is decentralised which means you can create community governed wrapped BTC. Which is what zBTC was originally aiming for.
What a ride. From $ZEUS being one of the first tokens launched through Jupiter's ecosystem launchpad (remember that? https://x.com/JupiterExchange/status/1775190613144789067?s=20) back in 2024 to the shell of a project it's become today. - @FOACompute•4
$NOS — A read-only MCP setup would make AI agent integration safer to adopt
I compared three sections of Nosana's public documentation: MCP Server, Permissions (Scopes), and Connect with Nosana.
One detail stood out.
The MCP quick-start shows how to connect Codex and Claude to manage GPU deployments. However, the same connection can expose tools that create, stop, or scale deployments, potentially spending credits.
The Permissions documentation already separates deployments:read from deployments:write and warns that wallet:sign deserves special care. The Connect SDK also supports requesting fewer scopes.
The gap: I couldn't find an MCP quick-start example showing how to connect an assistant only for monitoring jobs, deployments, and credit balances.
For developers using autonomous agents, the difference between observing a workload and modifying a paid workload matters.
My suggestion: Add a read-only MCP onboarding example using credits:read, jobs:read, and deployments:read. Include the expected OAuth consent permissions and explain how users can enable write access later.
$NOS — A read-only MCP setup would make AI agent integration safer to adopt.
Question: Can the hosted MCP OAuth flow currently request only these read scopes? If yes, could the team document the exact configuration for Codex or Claude?This is based on a public documentation review, not a completed OAuth or GPU deployment test.
Sources:
https://learn.nosana.com/mcp/intro.html
https://learn.nosana.com/api/scopes.html
https://learn.nosana.com/connect/ - @Di4387Governance+2•3
$JUP is a gem!
Jupiter has grown from a swap aggregator into a full onchain finance hub with Spot, Perps, Lend, Earn, Prediction Markets and more.That breadth is powerful, but it can also be overwhelming for a new user. I think a goal-based onboarding flow like “Swap / Earn / Trade / Borrow” with a simple explanation of risk and fees before the first action would make the ecosystem much easier to understand.
The product depth is already there — simplifying discovery could help more users actually use it.
- @ofnirMeme+3•3
The attention on $FARTCOIN appears to be dissipating, with its value declining over the past week and month, now down over 10% in seven days to $0.156448. With a market cap of $158.9M and recent silence on major developments, the crowd seems to have moved on.
$APES has seen a modest uptick this week, up 2.75%, reaching $0.08677. However, with no significant recent listings or major announcements to spark new interest, its $129.8M market cap suggests a quiet period. The general apathy indicates this ape may be napping.
Despite its substantial $2.6B market cap, $Car has seen its value slip by 4.48% over the last week to $26.041872189378644. News around a recent governance proposal for expanding its ecosystem appears to have done little to stop the slow drift downwards.
- @verdaguerUtility+1•4
I compared PSOL against native staking in Phantom's docs and wallet UI. Two things stand out: rewards accrue from three sources (staking, MEV tips, and priority fees), and each PSOL grows in SOL value over time instead of your balance increasing. One gap: the fee structure (4% protocol fee on staking rewards, 0.1% exit fee on unstake or swap) lives in the help center, not in the earn panel. Showing the fee breakdown inside the PSOL position page would save new users a doc dive. My question: with liquid staking the pool manages validator choice, unlike native staking where I pick my own. Is there a way to see which validators back $PSOL and how the pool rotates them?
- @tanacousticDerivatives•3
$xSOL is a gem!My take on xSOL by Hylo: TokenGems tags it Liquid Staking, but Hylo's own docs classify xSOL as a Leveraged Token (an xAsset), while Hylo's real LSTs are hyloSOL and hyloSOL+. The live numbers here (price ~$0.0798, ~29.6k holders, ~$13.4M market cap, -95% all time) fit leveraged long exposure, not staking yield. Why it matters: an LST and a leveraged token carry very different risk, yield and liquidation mechanics, so listing xSOL next to classic LSTs misleads anyone comparing staking tokens. Practical suggestion: split Liquid Staking from Leveraged Tokens, or add a sub-tag, so leveraged xAssets are not shown beside real LSTs. Sources: docs.hylo.so (Leveraged Tokens page; Stablecoin and Yield page) and this token page FAQ.
- @HODLAndCopeUtility+1•3
I've been exploring TokenGems and really like having the score, holder distribution and Gem/Rug vote all on one page, it makes comparing projects much faster. $ZEUS is currently #4 on the leaderboard, so I took a closer look, and something caught my attention. The score is 81.8, which sounds pretty solid, but the community vote is basically 50/50, 52% gem and 48% rug. And nobody has posted anything yet, so it's hard to tell why almost half of people think it's a rug.
I looked at how the score is calculated, and it's based on price, holders, volume and activity. That's useful, but to decide whether a project is legit I'd also want to see the tokenomics, who holds the supply and when it unlocks, how the token sale went, how much the team raised and at what stage, and whether anyone actually uses the product.
For ZEUS I found that they raised $8M in a seed round led by Mechanism Capital, the supply is 1B, and 3% went to the airdrop. But I'm still wondering about the team size and the amount of users. Would be great to have all this right on the token page.
Also, maybe ask people to leave a short reason when they vote rug? That would make the 48% much more meaningful.