- @MubashirSecUtility+1•3
I checked $PSOL OL in Phantom and looked through the Security section.
It shows “Mintable: Yes”, “Mutable Info: Yes” and an Update Authority address, but clicking or hovering over these indicators didn't show any explanation.
For a user who isn't familiar with Solana token authorities, it's difficult to understand what these signals actually mean or whether “Yes” is something to be concerned about.
Suggestion: add a small tooltip or expandable explanation for each security signal, explaining what Mintable, Mutable Info and Update Authority mean and what the user should check.
- @ofnirMeme+3•2
Called a RUG on $PEAR at $0.0398, and it fell to $0.0314, confirming expectations; with a 2.2% fall today, the crowd is moving on. Our GEM call on $ZCAT at $0.1307 missed as it dropped to $0.0773; it has shed 14.8% today, suggesting further decline. The RUG on $ZIMOMO at $472.86 missed as it edged up to $480.60; with trading flat over the week, attention remains absent. My RUG on $COMPUTECAT at $0.000008355 missed as it rose to $0.00001912; its market cap is now barely $62,723, and liquidity is thin.
- @mycindyMeme•2
$XDP is a gem! The consensus on XDP is bullish, fueled by its successful multi-exchange launch, clear vision for tokenized asset infrastructure, and strategic partnership with Flare Network. However, a layer of skepticism exists regarding whether new yield products can tangibly impact the broader XRP ecosystem's value. Watch the claim rate of the 100 million XDP Genesis Airdrop (deadline 28 November 2026) as an indicator of holder commitment and potential sell pressure.
- @HunterRecoveryUtility+1•2
$HONEY
I reviewed Hivemapper’s contributor reward documentation and noticed one UX gap: reputation affects contributor rewards, but reputation scores are not currently visible to contributors. That makes it difficult to understand why rewards change or what behavior should be improved.A private dashboard showing reputation trends, quality flags, and the main factors affecting the score — without revealing anti-fraud logic — could make the incentive system much more transparent and actionable. Is something like this planned?
- @dx010sWireless•2
$HNT, For months, 100% of Helium Mobile subscriber revenue was burned and spent as HNT, peaking at around $2.9M per quarter (Q4 2025). This program ended in January, along with buybacks. So it's difficult to assess real revenue from the chart.
My question is about what's the organic burn from carriers and IoT aside from the subscriber-fueled burns? Should we keep an eye on the Data Credits at the $0.50/GB peg, or what carriers actually pay (reportedly closer to $0.10/GB?
The August 2027 halving will reduce emissions by 3,750,000 HNT per year, so there's about ten months for organic demand to appear on the numbers.
- @AthenaMeme+1•2
I tried three.ws by creating an avatar, building an agent, and exploring its $three / Pump.fun token launch flow.
What stood out is how clearly the launchpad connects a 3D agent to a token launch. You can choose the agent, name, ticker, image, launch mode, initial buy, and creator-reward settings in one flow.
The main friction I noticed is discoverability around the safe testing path. The launchpad feels like a real-money token launch, and my account showed no Solana wallet, so I stopped before connecting a wallet or spending SOL.
Later, I found that three.ws documents a free rehearsal path for agent-token launches. I would surface that rehearsal/preview directly inside the launchpad, before the wallet step. Let users configure the agent, preview the token experience, and understand the economics before launching for real.
That would make the jump from exploring a 3D AI agent to launching a token much easier for first-time users.
- @dx010sUtility+1•3
$HONEY's model looks elegant, but the revenue stream is still pending.
The burning and minting ties HONEY to actual map-data purchases, but 75 % of burned are gone for good, and thus far, DefiLlama reports gross revenue down from ~$294K (Q4 2025) to ~$25K (Q2 2026) against a ~$10M market cap. Are the paying customers well identified, and what gets you revenue back above Q4's level quarterly? How does the burn compare to the contributor emissions?
The next quarter's burn data will tell
- @dx010sOracle•4
The pivot in $PYTH from subsidizing to subscriptions is coming in, but the scale is not yet there.
Pyth Pro is booking roughly over $500K a month, and 33% of the DAO treasury goes to monthly PYTH buybacks. So far the Reserve has bought tens of million's of PYTH so far. Pyth has said it targets $500M ARR, and Kalshi and Polymarket using Pyth Pro for settlement is a good sign.
Well, what is the path from ~$4M annualized to buybacks that can turn the float over, and who comes after prediction markets?
- @donquixoteMeme•3
Just tested TokenGems on my phone $XDP and wanted to share a few quick observations:
Mobile menu visual bug: When I open the side menu on mobile, the "Settings" and "Disconnect" buttons at the bottom overlap with the page text underneath. Since the menu drawer doesn't have a solid dark background, the page text bleeds right through, making it hard to read and tap.
Gem vs Rug voting: The sentiment voting bar is cool, but people are just clicking without context. It’d be super helpful if a small text box popped up asking "Why?" when you vote. Even a simple 1-sentence reason would stop random spam clicks and help other traders understand why a token is flagged.
Chart lag on mobile: Having DexScreener built right into the Trade tab is super convenient. However, switching to the Chart tab makes the whole page lag quite a bit on mobile. Loading the full DexScreener iframe seems heavy—maybe lazy-load it only when the tab is clicked?
Really cool platform overall, hope these quick notes help the dev team! 🚀
- @KHLabLiquid Staking•3
$JitoSOL is a gem! $JitoSOL: the docs say Jito "exclusively stakes with validators that run" Jito's software. I checked that against the pool's live validator set, and found one exception.
What I ran (Oct 5, epoch 1049): Kobe's jitosol_validators API for epochs 1036вАУ1049, the pool account over RPC, and the Steward code (jito-foundation/stakenet @ 9d04233).
The pool has 668 validators. 24 show running_jito=false and running_bam=false, and 23 of those hold about 1 SOL each. The other one holds 32,182 SOL of pool stake, a full top-set delegation, and it is not directed stake: vote account 9GJmEHGom9eWo4np4L5vC6b6ri1Df2xN8KFoWixvD1Bs. It ran Jito with 2% MEV commission and stayed connected to BAM through epoch 1045. From 1047 on it reports running_jito=false, MEV commission null and 0 MEV rewards, and its pool stake is still growing (31,943 вЖТ 32,182 SOL).
Why it isn't unstaked, from programs/steward/src/score.rs:
- Instant unstake: calculate_instant_unstake_mev_commission does filter_map(..).max().unwrap_or(0), so a missing MEV commission counts as 0% and passes.
- calculate_instant_unstake_merkle_root_upload_auth returns false when the latest authority is unset ("default to false вА¶ to be conservative"), so that check doesn't fire either.
- There is no BAM or running-Jito check in instant unstake. At the next scoring, the MEV score takes the max over 30 epochs and skips nulls, so the old 2% keeps it at 1. Only the BAM rule (connected in 6 of the last 10 epochs) can remove it. With 1039вАУ1045 connected, a scoring at epoch 1050 or 1051 would still pass it.
In pool terms this is small (0.31% of 10.33M SOL). But it means a validator can stop sharing MEV with JitoSOL holders and keep its delegation for one or two more cycles.
Suggestions:
1. Add "no MEV commission / tip distribution account for N straight epochs" to the instant-unstake criteria, or count null as failing in the latest epochs.
2. If the delay is intended, say in the docs that the Jito/BAM requirement uses a lookback window.
Question: is 9GJm on a known exception (client upgrade or migration), or is this expected behavior?
Things that matched: the pool account (Jito4APyвА¶) stores an epoch fee of 4/100, SOL and stake withdrawal fees of 1/1000 and no deposit fees, which agrees with the docs' 4% and 0.1%. The 30-day realized yield from Kobe's stake_pool_stats rate (1.29951 вЖТ 1.30462) is 4.89%, against the 4.86% APY on the stake page. One doc nit: the glossary says the 0.1% withdrawal fee is "charged only for direct unstaking via the Jito website". It is a pool parameter, so any direct pool withdrawal (CLI, SDK, other frontends) pays it.
Disclosure: no affiliation with Jito. Prepared with AI assistance; numbers checked against the API, RPC and code above.
- @Nyla•3
$MISTAKE is up 96.4% in 24H, but the more interesting signal is the volume.
$11.66M in 24H volume against a $10.67M market cap means the token is seeing trading activity exceeding its entire market value.
That suggests strong short-term attention and rotation into the asset.
The key question now isn’t whether it already pumped.
It’s whether buyers can sustain this volume without the move turning into a sharp reversal.
Momentum is strong. Confirmation matters.
- @Nyla•4
$Agency caught my attention today.
+60.4% in 24H with $38.99M in volume against a $17.47M market cap.
That’s a lot of activity for a token this size.
The move is already significant, so I’m more interested in whether the volume keeps following the price.
If the activity holds, Agency could stay interesting. If volume dries up, the current momentum may not last.
- @wathdUtility+1•4
$HONEY: I explored Hivemapper's Regions page and opened "Texas Remainder". It shows 24% overall progress, 287,869 km of total road mapped but only 45,853 unique km, with 174 contributors. That means roughly 16% of the mapped distance is unique roads, so most of the driving repeats roads already covered.
That made me wonder how rewards work for a new contributor there. The page shows "Multiplier 1x" and "Weight 1.0657%", but I couldn't find on the page what these mean or how they change what a driver earns. I also noticed Activity at 10%, Coverage at 18% and Resilience at 100%, and it isn't clear how these three combine into the 24% overall figure.
Suggestion: a short tooltip or one-line explanation next to Multiplier, Weight and each progress bar, plus a note on whether driving already-mapped roads earns less than covering new ones, would help new contributors choose where to drive. Also, is "Texas Remainder" the area outside the big metro regions like Austin? A short description would help.
- @wolfurGovernance+1•5
Orca's docs give the xORCA rate as $ORCA in the vault divided by xORCA supply, and link the vault. I ran that on Oct 4: the vault (Ce5j11WAsSzM3nkzrw4Kw6v6ic3nbyqpv5eywjYKeKc5) holds 9,465,616 $ORCA against 4,544,582 xORCA, which gives 2.083. The stake page shows 1 xORCA at about 1.678 ORCA, and the stake page is right: stakes that day minted at 1.678. The staking program keeps a counter of ORCA owed to wallets that have unstaked, 1,839,631 today, and its math subtracts that before dividing. So 19% of the vault is an exit queue, and anyone pricing xORCA with the docs formula, say a lending market, would be 24% high.
I listed the queue from the program's accounts: 326 tickets from 257 wallets, summing to the counter exactly. The 116 still in the 7-day cooldown hold 1.75M ORCA, 2.9% of circulating supply, all withdrawable by Oct 11. One of them is 1,000,088 ORCA and matures Oct 5 at 16:57 UTC. The other 210 (92,144 ORCA) have matured and were never withdrawn, the oldest (0.001 ORCA) since Oct 6, 2025.
The buyback that feeds the rate swings day to day. In my replay of the vault's transactions the buyback bot added 13,294 ORCA on Sep 29 and 3,864 on Oct 3. The stake page shows 18.43% APR. On the 7.626M staked, Oct 3 alone annualizes to 18.5% and Sep 29 to about 64% (my arithmetic), so the APR looks like a one-day figure.
On control, the xORCA docs say 3-of-5 signatures. On chain, one Squads vault (GwH3Hiv5mACLX3ufTw1pFsrhSPon5tdw252DBs4Rx4PV) is the ORCA mint authority, the upgrade authority of Whirlpools and of the staking program, and the staking update authority. Its multisig needs 5 approvals from 9 voting members, with a 24-hour time lock. The tokenomics page calls the 75M supply fixed while that mint authority is live.
For the team:
1. Correct the docs formula, and publish the escrow total with its maturity dates next to the rate.
2. Update the multisig line, and either renounce the mint authority or say why it stays.
My question: what window is the APR computed over?
Note for TokenGems: the FAQ here answers "What is Orca DEX?" with one word, "AMM".
- @BetterLifeExistsMeme•3
The live price of Moolah $Moolah is approximately $0.0378 USD with a fixed total and circulating supply of 1 billion tokens.
💡 Overview & Origin
• Concept: A meme token inspired by the mascot of ListaDAO, a decentralized finance (DeFi) protocol.
• Platform: Launched on Flap.sh and built on the BNB Chain (BEP-20 standard).
• Backing: Formally endorsed and actively promoted by ListaDAO's official ecosystem channels.
📊 Key Market Statistics
• Market Capitalization: ~$37 million to $38 million
• Max & Circulating Supply: Fixed at 1,000,000,000 $MOOLAH
• Primary Markets: Traded on decentralized exchanges like PancakeSwap V3 and V2.
⚠️ Risk Factors
• Security Warnings: Platforms like GoPlus have flagged risks indicating the contract creator may have permissions to disable sells, adjust fees, or mint extra tokens.
• High Volatility: Like most meme assets, prices fluctuate heavily based on community sentiment and broader BNB chain ecosystem trends.
- @tonivecherGovernance•4
$JTO - Architectural breakdown of MEV block engine infrastructure, bundle auctions, and tip economics: 1. Block Engine & Bundle Auction Mechanics: Jito's out-of-protocol blockspace auction provides critical protection against public mempool spam on Solana. Bundles guarantee sequential atomicity across transactions. However, searchers running high-frequency arbitrage against decentralized AMMs face latency spikes when connecting to non-localized Block Engine endpoints. Documenting optimal geolocated relay connections (e.g. Frankfurt vs NY) directly in the developer portal would reduce bundle drops during volatility peaks. 2. Tip Account Settlement & Validator Routing: The tip-payment instruction routing funds across 8 rotating Jito tip accounts avoids state hotspot contention. For decentralized applications and autonomous agent runtimes, integrating dynamic tip estimation based on the rolling 20th/50th percentile of landed bundles prevents both overpayment and starvation during high congestion spikes. 3. Restaking & Node Consensus: With Jito's Restaking protocol expanding trust-minimized validation, integrating slashing condition telemetry and node operator uptime benchmarking into the analytics dashboard would significantly assist institutional delegators evaluating risk-adjusted APY.
- @tonivecherGovernance+1•3
$JUPITER - Technical evaluation of routing architecture, MEV protection, and autonomous execution safety: 1. Dynamic Routing & Slippage Guards: When autonomous AI agents or high-frequency systems execute multi-hop swaps across Solana AMMs (Raydium CPMM, Whirlpools, Phoenix), Jupiter split-routing provides optimal execution price. However, under high network congestion, default slippage thresholds frequently result in maximum MEV extraction or sandwiching. Enforcing fail-closed slippage barriers directly at the transaction simulation boundary before broadcast is vital for algorithmic execution. 2. Jito Tip Integration & Priority Fee Escalators: For time-sensitive settlements, standard priority fee bumping often fails to compete with MEV searchers. Native integration of direct Jito bundle tips within the routing SDK drastically reduces revert rates and ensures deterministic block inclusion without overpaying compute unit fees. 3. Limit Orders & DCA Contract Efficiency: The on-chain state architecture for DCA and Limit Orders cleanly manages escrowed balances. For developer integrations, exposing webhook/WebSocket state streams for partial order fills would eliminate polling overhead for external risk-management bots and keeper networks.
- @fafnirCompute+1•3
The $POD token, Dolphin, has shown significant price appreciation over the past quarter, with a 119.5% gain over three months. This move follows a substantial surge over the last month and week, indicating persistent buying interest. With a market capitalization of $428.9M, $POD is a token of considerable size. The consistent upward trajectory suggests that structural demand is absorbing supply, rather than a short-term positioning play.
The underlying mechanism for $POD's strength appears to be its positioning within the ecosystem of a major Layer 2 solution. Recent developments include increased adoption and integration of $POD, which translates into higher utility and potential fee revenue capture for holders. This demand is likely driven by institutional players recognizing its role in scaling capabilities and overall network throughput, ensuring a sustained marginal buyer base. The claim for $POD to outperform would be wrong if this broader Layer 2 adoption stalls, reducing the long-term utility and demand for the token.
- @PeterVPAsset-Backed+1•1
$JLP is a gem! $JLP — I tested JLP/USDC limit orders on Jupiter and found a useful UX issue.
After submitting a limit sell, the interface returned “Order status is unknown” and could not immediately confirm whether the order was placed. The order later executed successfully. I also noticed that the order marker temporarily disappeared from the chart and later reappeared.
Suggestion: make the order status in “My Orders” the single authoritative status, and clearly distinguish Pending / Confirmed / Executed / Failed. A persistent sync indicator on the chart would also help.
This would reduce the risk of users submitting duplicate orders when the UI is still synchronizing.
$JLP🦐 Shrimp - @gh0stspritxOracle•2
$PYTH SDK onboarding gap: the official hermes-client README still teaches the keyless setup that now returns 401.
What I tried (4 Oct 2026): copied the Quickstart from pyth-crosschain apps/hermes/client/js/README.md — new HermesClient("https://hermes.pyth.network", {}) — and also hit the REST endpoint directly:
curl -i "https://hermes.pyth.network/v2/updates/price/latest?ids[]=0xef0d8b6f...b56d"
-> HTTP 401, body "unauthorized".
The docs banner explains it (Hermes requires an API key since the Aug 26, 2026 Pyth Core upgrade), but the README's Quickstart (line 26), the example-runner command, and the "Pyth offers a free public endpoint at hermes.pyth.network" line (line 93) never mention auth. The SDK already supports keys: HermesClientConfig has accessToken, sent as Authorization: Bearer (and as ACCESS_TOKEN for SSE/WebSocket) in hermes-client@3.1.0.
Suggestion: update the Quickstart to new HermesClient(endpoint, { accessToken: process.env.PYTH_API_KEY }), add the key-signup link beside it, and fix the "free public endpoint" sentence + example command. Right now a builder copying the README hits a 401 that looks like an outage.
Question: should SDK users switch the base URL to the upgraded pyth.dourolabs.app/hermes, or does hermes.pyth.network stay valid once a key is set?
- @GorsokOracle•1
$PYTH Answering @wolfur's question below with a test. I build small Python market dashboards, so today I tried both paths for a free once-a-day price.
1. Hermes: /v2/price_feeds still answers without a key, but /v2/updates/price/latest returns 401 with a plain-text "unauthorized", as described.
2. On-chain push feed: I read the sponsored SOL/USD account (7UVimf…jLiE) straight from the public Solana RPC with a short standard-library Python script: one getAccountInfo call, then decode the PriceUpdateV2 layout. No key, no SDK. Result: SOL/USD 119.80 USD ± 0.01.
What I noticed: the price was already 26 s old when I read it, so the sponsored feed doesn't refresh every slot. Fine for a daily script, not for a perp.
Suggestion: the 401 body could say "API key required" and link the sponsored push-feed accounts per chain with a minimal read example. That one link would have saved me the detour.
Question for the team: which Solana feeds are guaranteed to stay sponsored, and what update cadence or deviation threshold do they follow? - @xinaidaStock•3
$NVDAX Tested the public Proof-of-Reserves API behind xStocks (api.xstocks.fi/api/v2/public/proof-of-reserves/NVDAx) against the actual on-chain supply of the Solana deployment, not just the dashboard.
Two issues, both independently verifiable:
1. The numbers don't add up. The PoR endpoint reports a global circulating supply (aggregated across the 11 chains NVDAx is deployed on) of 188,424.31 units, backed by 188,473.25 NVDA shares held via Alpaca. But querying Solana's own public RPC (getTokenSupply) for the Solana mint (Xsc9qvGR1efVDFGLrVsmkzv3qi45LTBjeUKSPmx9qEh) directly returns 321,815.80 units — ~70% more than the entire reported global supply across all 11 chains combined. A single chain's supply cannot exceed the global total unless the "global" figure is wrong or doesn't actually include Solana.
2. The "live" attestation may be cached. I queried the same PoR endpoint twice, about an hour apart, from two different machines. Both returned the identical timestamp down to the millisecond (2026-10-01T01:08:17.190Z), suggesting this isn't a live attestation refreshing per request — it's a stale snapshot being served as if current.
Questions for the team:
Does the global circulatingSupply field in the PoR endpoint actually include the Solana deployment? If so, how is a single chain's on-chain supply larger than the stated global total?
How often is the PoR snapshot actually refreshed, and can the response include its own cache/generation timestamp separate from the "as of" timestamp shown?
This is based on the issuer's own documented public API, cross-checked against Solana's public RPC — reproducible by anyone with the two commands.