User Avatar
7rYhG8…PeTV@Raidr
Rank
Gems earned
267
  • User Avatar
    @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?

  • User Avatar
    @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.

  • User Avatar
    @blackbitswan•3

    $BBSPre-launch is a gem!

  • User Avatar
    @blackbitswan•3

    $BBSPre-launch is a gem! Technical analysis operates on a critical hidden assumption: that market data follows a standard distribution and history repeats cleanly.

    During black swan events, that assumption collapses.

    Here is why classical technical indicators fail when extreme volatility strikes—and what actually drives price before order books break:

    1. Indicators are inherently lagging
    Moving averages, RSI, and MACD rely on past price action. When liquidity evaporates in seconds, lagging indicators do not forecast the turn; they merely record the damage after execution has already failed.

    2. Risk does not follow a bell curve
    Standard financial models assume tail risks are rare anomalies. In reality, market shocks follow fat-tailed, power-law distributions. When panic cascades, correlations converge to 1, rendering traditional support and resistance zones meaningless.

    3. Crowd psychology precedes price prints
    Price does not move until liquidity shifts, and liquidity shifts only when crowd conviction breaks. By tracking sentiment velocity and narrative divergence across global real-time sources, Emotional AI catches systemic stress before it reflects on the candlestick chart.

    Stop relying solely on backward-looking candles to protect against structural tail risks.
    #ArtificialIntelligence #PredictiveAnalytics #FinTech #CryptoTrading #MarketSentiment #DataScience #Web3 #EmotionalAI #StockMarket #BlackBitSwan

  • User Avatar
    @xiaoliangLiquid Staking•2

    $bSOL — BlazeStake’s withdrawal docs give conflicting fee guidance.

    I checked the live app and official docs today. The Fees page lists both Instant Withdrawal and Delayed Withdrawal at 0.1%, and the app also shows 0.1% on both paths.

    But the main BlazeStake intro still says instant unstake has a higher fee while delayed unstaking has a much lower fee. That can push users toward delayed unstaking for the wrong reason.

    Suggestion: update the intro and show the trade-off clearly:

    • Instant: 0.1%, immediate SOL when liquidity is available.

    • Delayed: 0.1%, receive a stake account and wait through Solana cooldown.

    Sources:

    https://stake-docs.solblaze.org/

    https://stake-docs.solblaze.org/features/fees

    https://stake.solblaze.org/app/

    AI-assisted review; no staking transaction was made.

  • User Avatar
    @Noviq01DEX+1•2

    $MET T — Detailed UX & UI Audit: DLMM Pool View, Limit Orders & Global Settings

    I spent time testing Meteora's web app (app.meteora.ag) across liquidity management, order placement, settings, and campaigns. Here are the core issues causing real UX friction, along with direct fixes.

    Priority Issues:

    1. High Default Priority Fees

    Under Settings > Transaction Broadcasting, 'Ultra' defaults to a 0.008 SOL cap (~$0.93 USD). The app doesn't show standard live fee estimates per tier, so smaller LPs and casual traders end up unknowingly paying massive tip fees on small transactions.

    • Fix: Show estimated SOL fee ranges right under Fast / Turbo / Ultra options.

    2. Inconsistent Default Slippage

    Slippage settings don't sync across tools. Swaps default to 0.5%, DLMM uses Dynamic Slippage, and Zap Out defaults to 0.4%. Moving between swaps and LP actions without noticing these differences leads to failed transactions during fast market moves.

    • Fix: Show an active slippage status on order cards and allow a global sync toggle.

    Usability & Visual Improvements:

    3. Cluttered Price Axes, Range Risk & Missing Chart Keys

    On volatile meme pools like CLAUDIA-SOL, tiny token decimal notation (like 0.0s448) stacks right on top of High, Low, and Bin markers, making the price axis unreadable. The Liquidity Distribution graph doesn't clearly label token colors, and the UI lacks a clear indicator for how close a position is to leaving the active bin range or an estimated "Fees Earned vs. Holding Raw Assets" breakdown.

    • Fix: Add a visual color key (e.g., SOL = Blue, Token = Turquoise), auto-collapse stacked price labels, and display a prominent active-range proximity indicator alongside net PnL estimates.

    4. Full Screen Chart Disconnect

    When expanding the price chart to Full Screen, all order and LP controls vanish. LPs analyzing live chart levels have to exit full screen completely just to adjust a range or drop a limit order.

    • Fix: Add a minimal overlay card for quick order execution inside the expanded view.

    5. Native Swap vs. Jupiter Routing

    The Swap tab displays a warning banner stating single-pool routing might deliver worse pricing than Jupiter, which forces users to drop what they're doing and head to Jupiter manually.

    • Fix: Place a 'Route via Jupiter' trigger directly inside the swap panel.

    6. Campaign Tab Navigation

    Campaign cards (like LP Stimulus Season 2) highlight dates and rewards, but don't link straight to the pools that qualify.

    • Fix: Add a direct 'View Qualifying Pools' link on each campaign card that filters the pool table automatically.

    Reviewed links:

    https://app.meteora.ag/dlmm/DfHEafDf9vk6tJzo7UEUQKsHmWnikzFvwW55WsxDyJuU

    https://app.meteora.ag/campaigns

    https://docs.meteora.ag/core-products/dlmm

  • User Avatar
    @starwishGovernance+1•3

    $ORCA

    Orca simulator: make the assumptions visible

    In an AI-assisted, wallet-free test of the SOL/USDC 0.04% pool, a roughly ±2% range and 7 days of Time In-Range showed approximately 6.13% Estimated Yield Earned. The numbers changed with live pool data.

    The tooltip explains the historical 24-hour yield basis. The documentation clarifies that Time In-Range is active time within the range, not total elapsed time, and excludes slippage and priority fees. These conditions are easy to miss.

    Could the result panel show “168 hours in range · historical 24H activity · excludes slippage and priority fees”? A 50%-fee-rate stress-test preset would also help users understand uncertainty. Does the estimate assume unchanged competing liquidity and reward rates?

    No wallet connection, deposit, or transaction was performed during this review.

  • User Avatar
    @King_davidMeme+1•4

    $PUMP is a gem!

  • User Avatar
    @caiyeliangMeme+1•5

    $PUMP P — Pump has the largest holder base on your top-10 board — 311,239 holders — but the lowest holder-distribution score of the group (0.31). That's a lot of wallets with comparatively concentrated supply. For a launchpad token it raises a practical question: how much of that concentration sits in bonding-curve / liquidity contracts rather than individual wallets? Splitting the distribution score into "contract" vs "EOA" buckets would make it far more actionable for launchpad tokens.

  • User Avatar
    @linnormGovernance+2•3

    $SNX has seen its price dip over the last week and day, -6.0% and -7.0% respectively, despite a 7.2% gain over the past month. A recent governance proposal, SCCP-2092, aims to enable Perps V3 on Arbitrum, potentially drawing new liquidity and expanding the protocol's reach. The nearly $138M market cap suggests a strong base, but watch closely where this new liquidity flows.

    $UNI is down 6.6% in the last day and 9.8% over the week, a notable retraction from its impressive 150.5% three-month surge. While the Uniswap Foundation recently discussed fee switch implementation, progress seems slow. The token needs new, significant liquidity inflows to support its recent gains, or it risks further consolidation as profit-takers exit.

    $AERO has seen a minor pullback of 1.0% in the last day, but its one-month performance is a strong 29.2% gain, indicating sustained interest. Aerodrome Finance recently activated a fee switch, directing protocol fees to veAERO holders, which should incentivize long-term staking and deepen liquidity on Base. This move generates real yield for holders.

  • User Avatar
    @Arslan4617Wireless•3

    $HNT — docs: the halving table shows more HNT than the max supply stated one paragraph above it

    Page: docs.helium.com/tokens/hnt-token, section "Max Supply".

    The paragraph says the halving schedule gave an initial maximum of 240,000,000 HNT, that year 1 issued ~17,000,000 HNT less than targeted, and that max supply therefore decreased to ~223,000,000 HNT.

    The table right under it does not apply that shortfall. Its "HNT at Year Start" column reads 225,000,000 for August 1st, 2027 and 228,750,000 for August 1st, 2028. Both are above the ~223,000,000 maximum the page has just stated. I recomputed the column: it is the plain running sum of "Target HNT Emission" (60 + 60 + 30 + 30 + 15 + 15 + 7.5 + 7.5 = 225 million), so it is the pre-shortfall schedule. With the 17 million removed the two rows would be about 208.0 and 211.75 million.

    Two smaller things on the same page:

    1. The Year column runs 1 to 8 and then repeats 7 and 8 for 2027 and 2028. Those rows should be 9 and 10.

    2. The text gives the HIP-20 cap as 34.24 HNT per 30-minute epoch and the current daily cap as 1,643.83561643 HNT. 34.24 x 48 = 1,643.52. The daily figure equals 1% of 60,000,000 / 365, so 34.24 looks like a truncated 34.2466.

    What checks out: the Net Emissions example. (400 x 6/7) + (9,500 x 1/7) = 1,700, capped at 1,643.83561643, leaving 7,856.16438357 HNT burned.

    Suggestions:

    1. Rename the column to "Target cumulative HNT (schedule)" or add a column with the ~17M shortfall applied, so the table agrees with the stated maximum.

    2. Fix the Year numbers in the last two rows.

    3. Add a link to the live on-chain supply next to the table. Burns and Net Emissions mean real supply differs from the schedule, and a new reader cannot tell which number is which.

    Question for the team: after the year-1 shortfall, is ~223M the cap the on-chain program enforces, or does emission still follow the 240M schedule row by row?

    Source (reviewed 7 Oct 2026): https://docs.helium.com/tokens/hnt-token

    AI-assisted review. The arithmetic was recomputed; nothing was checked on-chain. No affiliation with Helium.

  • User Avatar
    @Arslan4617Governance+2•3

    $JUP — the Metis /quote docs sample crashes before it returns a quote, and never sends the API key

    Page: developers.jup.ag/docs/swap/v1/get-quote. In the first JavaScript example the options object with 'x-api-key' sits after the closing parenthesis of fetch(...), not inside it. Shortened, the code is: await ( await fetch(url), { headers: {...} } ).json()

    That is a comma expression. I ran the block exactly as written on Node 22 with a stub fetch that logs its arguments. Result: fetch is called with 1 argument, so no headers and no key are sent. Then it throws "TypeError: (...).json is not a function", because .json() is called on the plain options object, not on the Response.

    So a developer who copies the sample gets a crash on the first run, and the request that does go out is keyless. The rate-limits page lists Keyless at 0.5 RPS and Free at 1 RPS, so the difference matters.

    The Swap V2 page (order-and-execute) has it right: fetch(url, { headers: { "x-api-key": API_KEY } }).

    Suggestions:

    1. Move the options object inside fetch( ) in the v1 sample. It is a one-line fix.

    2. The page says Metis is "no longer actively maintained". Put the link to the Metis-to-Router migration guide next to that notice, so readers land on a working sample.

    3. Run doc samples in CI against a stub fetch. This class of error would be caught automatically.

    Question for the team: is there a sunset date for /swap/v1, and will keyless calls to it keep working until then?

    Sources (reviewed 7 Oct 2026):

    https://developers.jup.ag/docs/swap/v1/get-quote

    https://developers.jup.ag/docs/swap/order-and-execute

    https://developers.jup.ag/docs/portal/rate-limits

    AI-assisted review. The sample was executed locally against a stub; no API key used, no swap performed. No affiliation with Jupiter.

  • User Avatar
    @oujiMeme+1•2

    $PUMP bounty board (go.pump.fun) this week: 79 live bounties and roughly $14K unclaimed, but most open bounties are attention-buying (hold $5 and callout, follow me to win). Original-artifact bounties sit at only $5-9 with single-digit submissions, while the bigger $100+ content bounties I found had already expired with 34-49 entries and no winner. Has the team considered a higher funding floor for escrow-backed artifact bounties? The current economics select for token purchases over creative work, which likely drives the high expiry rate.

  • User Avatar
    @Arslan4617Oracle•4

    $PYTH — OIS docs: the Reward Examples page still shows 10% yields while rewards are paused

    The Oracle Integrity Staking overview says the reward rate was set to 0 on 22 April 2026 (OP-PIP-103) and that no rewards are currently distributed. The Mathematical Representation page repeats it: y = 0, "stake is still at risk of slashing".

    The Reward Examples page, one click away, carries no such notice. All six examples assume "Annual Rate of Rewards r = 10%" (Example 4: publisher 10.3% APY, delegators 9.8%), and the built-in calculator returns positive rewards. Example 5 shows the other side: a 5% maximum slashing rate, 300 -> 285 and 200 -> 190.

    Read together, a delegator's position today is: reward 0, downside up to the 5% maximum slash. A reader who lands on the examples page from search sees the opposite picture.

    Suggestions:

    1. Put the same "rewards paused" notice on Reward Examples, and default the calculator to y = 0, keeping 10% as a labelled historical scenario.

    2. Add an example for the current state: stake 500, y = 0, one 5% slash = -25. That makes today's risk/reward explicit.

    3. OP-PIP-103 cites the Pythnet sunset planned for Q3 2026 but gives no path for resuming rewards. A line on that in the overview would help.

    Question for the team: with rewards at 0 and withdrawals open, what is expected to keep delegated stake in publisher pools, and will OIS restart after the Pythnet sunset or be replaced?

    Sources (reviewed 7 Oct 2026):

    https://docs.pyth.network/oracle-integrity-staking

    https://docs.pyth.network/oracle-integrity-staking/mathematical-representation

    https://docs.pyth.network/oracle-integrity-staking/reward-examples

    https://forum.pyth.network/t/passed-op-pip-103-pausing-ois-rewards/2471

    AI-assisted documentation review; no staking transaction performed.

  • User Avatar
    @bibek_solGovernance+2•2

    $JUP I checked Jupiter's home page on 6 October 2026 without connecting a wallet.

    I noticed that the swap screen — the first thing a new user sees — sits directly next to 250x leverage perpetuals, a Gacha pack opening feature (up to 32x), and prediction markets. All of these are high-risk, and none of them carry a visible risk warning on the home page.

    This matters because Jupiter is Solana's front door. A first-time user from a country where a failed transaction is real money will not know that 250x leverage can wipe an account in seconds, or that Gacha packs are gambling-style products, not investments.

    Suggestion: add a one-line risk label to the Perps, Gacha, and Prediction Market tiles on the home page — something like "High risk — can lose your full deposit." It's a small change that protects new users without changing the product.

    Question: is there a first-time-user mode that hides leverage and Gacha until the user has completed at least one swap?

  • User Avatar
    @grafvitnirUtility+4•4

    $LINK, with its $10.4B market cap, saw a 72.5% price increase over three months, yet a 5.3% drop this week. Recent announcements include the Chainlink Cross-Chain Interoperability Protocol (CCIP) expanding to Arbitrum and Base, providing secure cross-chain data and token transfers. While CCIP expands utility, the mechanism for fee value capture by the $LINK token remains indirect through staking rewards, not direct protocol revenue.

    $RUNE is up 50.1% over three months but down 0.5% in one day. THORChain has been subject to various exploits in the past, including a major one in 2021. While the platform maintains its decentralized exchange function for native cross-chain swaps, the long-term security posture remains critical for a protocol handling $255.2M in market cap.

    $INJ has surged 50.8% over three months and 42.0% in the last month, despite a 1.8% daily dip. The Injective Volan upgrade, focusing on performance enhancements for institutional adoption and new dApps, has recently been implemented. This upgrade strengthens the underlying execution layer, and a new token burn mechanism, where 60% of fees from dApps on Injective are burned, directly strengthens $INJ token value.

  • User Avatar
    @Harvey500Stock•3

    $NVDAX is a gem!

    Heads-up for anyone landing here from search: TokenGems currently lists more than one "NVDAx" entry. The other one (contract B15STJ…U4nM) has only 3 holders, a price of $0.00000945 — nowhere near NVDA's actual share price — and its "Visit website" link points to penguinonsol.com, a penguin meme coin site with nothing to do with xStocks. TokenGems itself flags it: "We couldn't verify recent pricing for this token, so its market figures are unreliable."

    This page (contract Xsc9qvGR…9qEh) lines up with what a tokenized NVIDIA stock should look like.

    Why it matters: the whole point of xStocks is regulatory-compliant exposure to real equities. If the first thing a newcomer meets is a lookalike entry with 3 holders, the trust proposition breaks before it starts — same name-confusion problem @Nuancee flagged for $SI, but with real money at stake.

    Suggestion for TokenGems: add a verified/official badge on the canonical contract for tokenized equities, and surface a warning on suspected duplicates. For xStocks specifically, cross-checking the issuer's official contract list would kill most of these at the source.

  • User Avatar
    @Harvey500Meme+1•3

    $SI is a gem!

    One data point worth flagging: this page's sentiment poll shows 55% voted "Rug" versus 45% "Gem" — yet $SI has 57,303 holders and a $26M market cap. Plenty of holders, but more than half of onlookers suspect a rug. That gap is itself a signal: a meme coin lives or dies on community trust, and a 55% rug vote is a warning sign hanging on the page that scares off new money.

    Three low-cost suggestions for the builders (no product changes needed):

    Put the liquidity lock proof (contract link) in the "About" section — right now a new visitor finds nothing but price and votes, zero trust-building info;

    Publish the team multisig wallet address so holders can verify treasury movements;

    Fix this together with the same-name token confusion @Nuancee raised: make the official site link and contract address a permanent part of the project's identity everywhere. These are two sides of the same trust problem.

    None of this requires changing the product, but it directly answers that 55% distrust vote.

  • User Avatar
    @hoanguyen3021DEX+1•3

    $MET Meteora Discover (2H view): the TVL change column contradicts other columns in the same row.

    Checked 6 Oct 2026 (~03:30 UTC) on app.meteora.ag, Discover → Top Performers, 2H, no wallet connected.

    STONK-SOL (DLMM, bin step 20):

    - TVL $2.58M, +101%; Active TVL $2.51M, +99.13%

    - Net Deposit -$214.87K, pool price +4.91%

    - Fees -24.55%, while Fees/Active TVL +76.11%

    Two things don't add up. TVL can't double in two hours while LPs withdraw $215K and the price moves 5%. And if fees fell 24.55% while Fees/Active TVL rose 76.11%, Active TVL must have fallen about 57%, not risen 99%.

    Same pattern on ZCAT-SOL (bin step 80): Net Deposit -$137.9K, price -9.84%, yet TVL +78.92%; Fees -65.88% vs Fees/Active TVL +37.11% implies Active TVL about -75%, shown as +91.96%. ALLINU-SOL shows it too, and most rows on the page show TVL around +80-100% for the window.

    LPs use these columns to pick pools, so a wrong TVL trend makes a pool look like it is attracting liquidity while it is losing it.

    Suggestion: check the baseline used for the TVL / Active TVL change (it looks like the comparison value is far too low, or the direction is flipped), and add a tooltip saying what each % is compared against.

    Question: is the 2H TVL change computed against the value at the start of the window, or against something else, like an average over the previous window?

    (Researched with AI assistance; numbers taken from the page on 6 Oct 2026.)

  • User Avatar
    @arashilanOracle•4

    $PYTH documentation feedback (AI-assisted research): Pyth's 'Why Update Prices' guide describes paying a small protocol fee for every update, while 'Current Fees' says the Core update fee is now zero across mainnet EVM chains as part of the Core sunset.

    Could the explainer link that step to Current Fees and distinguish protocol fees from network gas and any data-service charges? Keeping getUpdateFee in the example makes sense; a note that it currently returns zero would clarify the migration without implying every Pyth product is free.

    This is a public-documentation review, not a deployed integration or security finding. No affiliation with Pyth. Prepared for the TokenGems feedback contest.

    Sources:

    https://docs.pyth.network/price-feeds/core/why-update-prices

    https://docs.pyth.network/price-feeds/core/current-fees

  • User Avatar
    @hoanguyen3021Lending•3

    $KMNO Kamino Earn: the RockawayX EUROP vault page shows history the vault doesn't have yet.

    On https://kamino.com/earn/lend/rockawayx-europ/vault-overview (checked 6 Oct 2026, no wallet connected):

    - Deployment Date: 7 September 2026, about 29 days ago.

    - Yet the page shows "Supply APY (90D Avg) 0.25%" and a "180D Growth" figure.

    - Total Supplied $4.49M, Total Borrowed about $352, Utilization 0.01%, current Supply APY 0.00%.

    - Interest Generated across all users: +$0.04.

    0.25% a year on $4.49M would be roughly $890 over 29 days, so the 90D average doesn't describe what depositors in this vault actually earned. Kamino's docs say quoted APYs are trailing averages, but don't say what is shown when a vault is younger than the window.

    Smaller point: the vault is labelled "Balanced" while its own strategy text calls it "conservative", and I couldn't find where Conservative / Balanced / Aggressive are defined in the docs.

    Suggestion: for vaults younger than a window, show "since launch (29 days)" instead of 90D/180D, and add a note when utilization is near zero ("little borrow demand yet; second market coming").

    Question: is the 90D figure taken from the Schuman EUROP Prime Market's history before this vault existed?

    (Researched with AI assistance; numbers re-checked on 6 Oct 2026.)

  • User Avatar
    @oldleeGovernance+1•3

    $SANC / Sanctum: the INF unstaking help contradicts the interface.

    On https://app.sanctum.so/unstake/INF, selecting INF makes Instant the active option and disables Delayed. The FAQ also says INF must be converted through instant unstaking. However, opening "How to choose?" describes delayed unstaking and assigns it "0.3% for INF". That presents a fee for an option the interface does not offer.

    This makes the exit-method comparison confusing: a newcomer could expect a delayed INF route, then wonder why it cannot be selected.

    Suggestion: make the help dialog follow the selected asset. For INF, explicitly state that only Instant is supported and remove INF from the delayed-fee sentence. For eligible LSTs, show the applicable delayed fee and the wallet claim step.

    Is that 0.3% reference left over from a previous flow, or is there a supported INF redemption route the interface does not expose? Either way, aligning the help text, FAQ, and available actions would resolve the ambiguity.

    Evidence: public interface checked on 6 October 2026, without connecting a wallet or submitting a transaction.

  • User Avatar
    @xbfomeUtility+1•2

    The charts on $STREAMflow's recipient dashboard are kind of a pain to read when a project has like a big token unlock setup. Right now, when a contract has a massive initial unlock day and then switches to like a smooth daily drip, the graph just shows one basic line. It completely hides how steep the inflation rate actually jumps on day one compared to the slow daily release after it. This makes it way too hard for people to visually check the actual dump schedule at a glance. On top of that, the bulk stream wizard has a sneaky problem. If you copy-paste like fifty wallets into a mass payout and just one of those accounts is completely new or has 0 SOL in it, the platform doesn't warn you at all before you hit sign. The whole transaction just partially fails or drops if the network is busy, which is a problem when you're just tryna pay out a community.

    Imo they just need to build a quick check into the setup screen to flag empty addresses right before you sign.

    Also can the devs look into adding that kind of address check, and maybe toss like a simple visual indicator on the charts too? Separating the initial big token dump from the regular stream rate on the graph would make tracking things a whole lot cleaner for everyone.

  • User Avatar
    @mycindyGovernance+1•2

    $UNI is a gem! The consensus on UNI is bullish, driven by a powerful confluence of institutional adoption, regulatory clarity, and real-world utility expansion. The narrative has shifted from pure DeFi speculation to Uniswap's role as critical infrastructure for the tokenization of global assets. Watch the $10.30–$10.96 resistance zone; a sustained breakout could validate the current optimism and open the path toward higher price targets.

  • User Avatar
    @solportbondGovernance+2•3

    $RAY LaunchLab's creator-fee docs need a version check. The 'LaunchLab creator fees' page says the default post-migration split gives the creator a 10% Fee Key NFT. But 'How creator fees work' says migrations after the 2026-08-17 upgrade combine creatorScale with platformScale into a platform-owned locked-LP share. The migration instruction docs describe the same change.

    That's a meaningful difference for someone estimating what they can earn from a launch. LP-fee rights and CPMM creator fees aren't the same thing.

    Could you mark the older explanation as pre-upgrade and link it to the current flow? A before/after table showing the fee type, recipient, claim method and applicable migration date would help. It should also explain when platform_cp_creator replaces the launch creator as the CPMM fee recipient.

    https://docs.raydium.io/products/launchlab/creator-fees

    https://docs.raydium.io/user-flows/how-creator-fees-work

    https://docs.raydium.io/products/launchlab/instructions