Raydium AMM

Raydium AMM appears to be a real, mature product rather than a pure landing page: the docs describe live swap flows on raydium.io/swap, pool/product references for AMM v4, CPMM, CLMM, and a developer API base at api-v3.raydium.io. The documentation also exposes operational integration endpoints for pool lists and quotes, which is consistent with a functioning live protocol surface rather than a static marketing site. I did not find verifiable evidence in the gathered sources of broken links, fake metrics, or obvious template/clone signs, but those checks are not fully verifiable as of 2026-08-29 from the available material alone. The strongest product-level signal is that Raydium publishes a documented REST API used by the UI and integrators, and the swap page is documented as a live transaction flow with amount entry and quote-based auto-population. Open API: yes. Raydium documents a public API at api-v3.raydium.io and separate devnet endpoints, with docs explicitly listing REST endpoints for pools, quotes, token metadata, and prices. Live deposits/withdrawals: Not verifiable as of 2026-08-29 from the gathered sources. The docs confirm live swapping and protocol/account references, but they do not independently prove deposit/withdrawal execution behavior or current UI status beyond that.

A 2026 review summarizes a HashEx audit from August 2024 with zero critical, high, medium, or low findings. This is a secondary-source claim in the search results, so the report details and bytecode-match coverage are not independently verifiable here.

Raydium docs list an Order-book AMM audit by Kudelski Security in Q2 2021. The provided search result includes the audit-history entry and report link, but not the finding counts or detailed fix status for this specific report. Bytecode-match coverage is not verifiable from the search results alone.

Raydium’s milestone page states that first-round audits on AMM v4 and Farm v3 were completed in November 2021 and that no critical findings remained, with minor code-quality recommendations addressed. The search results do not provide the underlying report link, exact severity counts beyond the no-critical statement, or a bytecode-match verification for deployed code.

Audit of the raydium-amm program on Solana. The report says the source code was delivered as github.com/raydium-io/raydium-amm and the audit was performed against commits d70a8fb with incremental reviews up to 8da289a. Findings: 0 critical, 1 high, 1 medium, 0 low, 4 informational. The high finding (OS-RAY-ADV-00) was marked Resolved; the medium finding (OS-RAY-ADV-01) was marked Resolved with patch 3dc6a26. The report also notes that code changes should be checked against the deployed program bytecode, and if the hash does not match, the deployed program is not the audited one.

Raydium’s milestone page states that Farm v6 was audited in May 2023 and that several medium findings were fixed in a v6.1 hotfix. The search results do not include the report itself or a bytecode-match confirmation for the deployed program.

Raydium’s milestone page states that CLMM audits in November 2022 found one critical issue and three high-severity issues, all fixed pre-deploy. It also says a later OtterSec re-audit covered Token-2022 support in April 2023. The search results do not include the full report links or confirm bytecode match against deployed code for those specific deployments.

Raydium does have an active bug bounty program for its Solana on-chain program code, and the public disclosure page says it has been live on Immunefi since 25 April 2023. The scope is limited to the on-chain program code (the Solana smart contracts at the listed program IDs); audits are separate and the bounty is intended to cover post-deploy issues, including economic attacks and some integration/SDK/off-chain bugs described by Raydium. The published payout parameters are:

• Critical: 10% of funds directly affected, with a floor of $50,000 and a cap of $505,000 for mainnet assets.
• High: $40,000.
• Medium: $5,000. Raydium’s own disclosure page says the public Immunefi listing reports about $3.4M total rewards paid and a median resolution time of about 1 day for the program-code bounty. The GitHub security policy mirrors the same severity schedule, which is a useful cross-check on the payout terms. I did not find a reliable, independently verified count of individual bounty submissions or an itemized public results ledger in the provided sources, so the only verifiable results are the aggregate figures Raydium cites from Immunefi.

Raydium is a Solana-native AMM and liquidity layer tightly coupled to Serum/CLMM infrastructure, Solana validators, and a set of stablecoins and external market makers. On-chain verification is not possible in this run: Not verifiable as of 2026-08-29. 1. External protocol & order-book dependencies

• Historically, Raydium’s central limit order book routing depended on Serum’s markets; after the FTX/Alameda collapse and Serum compromise, Raydium migrated to OpenBook and its own CLMM pools. This adds protocol risk from OpenBook’s continuity (liquidity, governance, potential bugs).
• Concentrated liquidity pools and “liquidity layer” design mean Raydium is deeply integrated with other Solana DEXs (e.g., Jupiter as a router). Failure or exploit of major routers can impact routing quality and slippage, but usually not Raydium pool solvency. 2. Oracle & price manipulation risk
• Raydium AMM pricing is largely pool-reserve based (constant-product / CLMM math), not oracle-driven; direct oracle failures (e.g., Pyth, Switchboard) mainly impact protocols that use Raydium LP prices as inputs for lending/liquidations, rather than Raydium itself.
• However, thin-liquidity pools are vulnerable to price manipulation via aggressive trades, affecting any integrated routers or downstream protocols referencing Raydium prices. 3. Bridges & cross-chain exposure
• Raydium is Solana-only; it does not operate its own bridge. Cross-chain assets (USDC via Wormhole, wBTC, etc.) introduce bridge and custodian risk: a bridge exploit or custodian insolvency can render wrapped assets worthless or unredeemable while still tradable in Raydium pools. 4. Stablecoin, LST & RWA exposure
• Major pools use USDC, USDT and other stables; depeg or issuer insolvency (Circle, Tether) directly impacts LPs by rebalancing pools toward the depegged asset and permanent loss vs. solvent assets.
• Exposure to SOL staking derivatives (LSTs) such as mSOL, stSOL, jitoSOL adds validator-set and staking-program risks: slashing, governance failure, or depeg relative to SOL leads to asymmetric losses for LPs.
• Any RWA-backed stablecoins or tokens in pools import their issuer/SPV credit and legal risk; these are off-chain and not transparent on-chain. 5. CEX / MM counterparty risk
• Liquidity in Raydium pools is heavily influenced by external market makers and arbitrageurs, many active on centralized exchanges (Binance, Coinbase, etc.). CEX outages or regulatory actions can reduce arbitrage efficiency, increasing spreads and making AMM prices easier to manipulate. Overall, Raydium’s main counterparty risk channels are: Solana L1 reliability, stablecoin/LST and bridge issuers, external order-book/routers (OpenBook/Jupiter), and professional market makers with CEX dependencies.

Raydium AMM is organized as non-custodial, self-custody: users connect a Solana wallet and interact with permissionless smart contracts rather than depositing assets into a Raydium-controlled account. In practical terms, the user keeps control of the wallet keys, and swaps or liquidity actions are executed on-chain through the AMM program. For liquidity providers, assets are deposited into pool smart contracts and LP tokens represent the provider’s position; the protocol documentation and third-party reviews describe this as funds being locked in liquidity pool contracts, not held by Raydium as a custodian. Raydium’s older AMM v4 was originally hybrid and posted liquidity to OpenBook, but Raydium says that OpenBook dependency has been removed from the program; today AMM v4 is a pure constant-product AMM. So the custody model is: user wallet custody at the front end, on-chain program custody for pooled liquidity, and no centralized Raydium custody of user funds.

A prior incident is widely reported on December 16, 2022: an attacker allegedly compromised an admin private key (some reports suspect a trojan on a team VM) and drained about $4.4 million from eight constant-product pools. Reported response included a patched program, a community-approved compensation plan funded by team-held RAY, and migration of authority to a Squads multisig with hardware wallet and timelock protections.

Raydium AMM’s known major incident since launch is the June 10, 2026 exploit of five deprecated AMM V3 liquidity pools on Solana, where attackers drained about $1.34 million in RAY, SOL, and USDC using a forged/fake LP token mint validation flaw in retired code. The affected pools were legacy pairs including Sollet USDT-RAY, Sollet ETH-RAY, SRM-RAY, USDC-RAY, and RAY-SOL; multiple reports say current users and active pools were not affected because the vulnerable program had been phased out in 2021. Raydium said it would fully reimburse losses from treasury and began a security review / retirement of legacy AMM V3 program calls.

Raydium AMM key management is organized around privileged on-chain authorities rather than user-held keys. According to Raydium’s docs, each program has at least one privileged role, and admin actions like program upgrades, fee changes, pool status toggles, and config creation are gated behind multisigs instead of single keys. For the legacy AMM v4 program (raydium-amm), the upgrade authority is the 3-of-4 Squads multisig with a 24-hour timelock, while pool/admin actions are handled by a separate Treasury multisig (3-of-5). Raydium also states that the four upgrade signers are independent, air-gapped cold-device signers held by core team members, which reduces single-point-of-failure risk. The architecture docs further say there is no on-chain token-voting governance for admin control; instead, multisigs handle these privileged paths. For the AMM v4 program specifically, the on-chain accounts include an authority PDA that controls the token vaults, so users do not hold vault authority themselves. In practice, the key-management model is: user keys sign swaps and LP actions; program authorities control protocol-level changes through multisig-governed upgrade and admin paths. One limitation: I could confirm the documented admin model and program-address mapping, but not the current live multisig signer set or any recent rotation events from the provided sources. Not verifiable as of 2026-08-29.

Raydium is a Solana-native AMM and DEX launched in February 2021, built and still largely run by a pseudonymous, globally distributed team rather than a conventional, onshore corporate setup. ### Founders & Core Team

• The protocol was co-founded by pseudonymous members “AlphaRay”, “XRay” and “GammaRay”, with additional figures such as StingRay and RayZor mentioned in several profiles.
• AlphaRay: leads overall strategy, operations, product direction and business development; background in algorithmic commodities trading and later crypto market-making starting in 2017.
• XRay: Chief of Technology, leading the dev team; ~8 years’ experience in trading systems and low‑latency architectures in TradFi and crypto.
• GammaRay: heads marketing and communications and contributes to strategy.
• Later ecosystem/BD roles include named contributors such as Timon Peng (co‑founder/BD) and mst (business development) in project databases, plus 0xINFRA as a core contributor leading protocol development and investor relations via Reactor Labs.
• In 2025, Ben Ungvari publicly joined as Chief Marketing Officer, indicating some transition toward doxxed, professional leadership in outward‑facing roles. ### Anonymity vs Public Presence
• Multiple independent sources describe Raydium’s founding team as anonymous/pseudonymous, with all key founders using “Ray” handles and no widely confirmed real‑world identities.
• Claims that external figures like Joe McCann are “founders” appear in secondary commentary but conflict with the broader record that attributes founding to the pseudonymous Raydium team; those references likely conflate Serum’s ecosystem role with Raydium’s origin. ### Track Record, Offices, Jurisdiction
• The team is portrayed as ex‑Wall Street quant traders and blockchain developers, but this is based on narrative profiles and interviews, not on-chain or corporate filings.
• There is no verifiable, widely cited physical office location or clear corporate domicile for the core Raydium protocol entity; typical coverage treats it as a globally distributed DeFi project rather than a regulated, onshore business. → Not verifiable as of 2026‑08‑29 whether there is a formal operating company, registered jurisdiction, or real-world office behind the core protocol. ### Reality Check & Incidents
• In December 2022, Raydium suffered a $4.4m exploit via compromise of an admin address controlling multiple liquidity pools; the team acknowledged the issue, published a post‑mortem, and offered a 10% bounty to the attacker. This is a notable key‑management and operational‑security failure for a pseudonymous team.
• Overall, Raydium operates as a real, high‑usage DeFi protocol with significant historical revenue and ecosystem importance on Solana, but governance, ownership, and legal structure remain largely opaque and centered on pseudonymous founders.

Raydium AMM has a generally strong reputation in Solana DeFi as a long-running, high-liquidity protocol, but it has a real security blemish and some recurring user complaints. The GitHub repository describes it as an on-chain, permissionless constant-product AMM on Solana, and third-party reviews still describe it as one of Solana’s main liquidity hubs. Key positives:

• Protocol standing: widely recognized as a major Solana DEX/AMM with deep liquidity and active product development.
• Founders/team visibility: the project is public and maintained as open-source code on GitHub, but the search results here do not reliably verify specific founders or investor backing.
• Audits/security posture: independent reviews mention audits and later hardening after a 2022 incident, but the results provided do not include primary audit reports, so specific audit quality is Not verifiable as of 2026-08-29. Main criticisms and concerns:
• Security incident: multiple third-party reviews state Raydium suffered a December 2022 exploit/private-key compromise with about $4.4M drained; these sources also say the issue was tied to key compromise rather than an underlying AMM logic flaw.
• User sentiment: Trustpilot and Reddit snippets are notably negative, including scam accusations and strong complaints from users, though these are anecdotal and not proof of protocol fraud.
• Fraud/rug allegations: the search results contain user-level scam accusations, but no credible source here substantiates a rug pull or insolvency event.
• Legal/regulatory/sanctions: no reliable evidence in the provided results of sanctions, regulatory enforcement, or insolvency proceedings. Not verifiable as of 2026-08-29. Overall, the reputational picture is: strong market relevance, mixed retail sentiment, one significant past security incident, and no confirmed fraud/rug or regulatory case in the supplied sources.

Raydium is a Solana-native AMM and order-book DEX whose yield comes primarily from trading fees and incentives on liquidity pools; there is no protocol-level leverage or restaking built into core LP products. ### Strategy & Assets In/Out

• Users deposit token pairs into AMM liquidity pools (e.g., SOL–USDC), receiving LP tokens; traders swap against these pools.
• Raydium also routes to/with Serum-style central limit order books, so LPs effectively provide liquidity both to the AMM and order-book.
• Assets out: swap proceeds, LP share of trading fees, plus RAY or partner-token incentives in some pools. ### Yield Source: Organic vs Subsidized
• Organic yield: swap trading fees (commonly 0.25–0.30% per trade, split between LPs and protocol/treasury, depending on pool type).
• Subsidized yield: additional RAY emissions and external project rewards for “farms” and “acceleraytor” pools; these depend on token incentives and can be volatile.
• Overall, Raydium yields are a mix of organic fee APR + volatile incentive APR. ### Market Exposure & Leverage
• Core LP positions are directional and expose users to impermanent loss; they are not market-neutral.
• No native leverage, looping or restaking in the base AMM. Any leveraged LP exposure arises via external protocols integrating Raydium LP tokens (e.g., margin lending on Solana), which is outside Raydium’s own design. ### Lock-ups & Withdrawal Mechanics
• Standard pools: no lock-up, LPs can withdraw at any time subject to Solana network conditions.
• Incentive programs or IDO/launchpad allocations may have vesting/lock-up, but these are product-specific and not universal to LPing. ### Fees, Limits & Protocol Revenue
• Swap fee structure (example ranges, pool-dependent):
• Portion to LPs (majority share).
• Portion to Raydium treasury / RAY stakers (protocol revenue).
• Protocol revenue is thus fee-based, plus any treasury holdings and RAY emissions management; exact revenue split per pool type is documented in Raydium docs but not fully cross-validated by independent analytics.
• Gating: standard DeFi token access; no KYC, but subject to jurisdictional restrictions via front-end; contract-level access is open. ### TVL & APY (Data Limits)
• On-chain verified TVL, per-product and per-chain, is Not verifiable as of 2026-08-29 (Dune MCP unavailable).
• DeFiLlama reports Raydium as one of the larger Solana DEXs with hundreds of millions in TVL over 2024–2025 with cyclical drawdowns, but this is aggregator data, not on-chain verified.
• Historical APYs show high volatility, especially on incentivized pools; sustainability is higher for blue-chip, fee-only pools and lower for incentive-heavy, long-tail token pools. ### Collateral
• LP tokens function as collateral only when accepted by external Solana protocols (money markets, structured products); this usage is external to Raydium and varies by protocol.

Raydium AMM’s *treasury / reserves* are only partially verifiable from the web results provided. The clearest public figure is that Raydium’s fee split sends 4% of trading fees to the protocol treasury, while 12% is used for RAY open-market buybacks and 84% goes to LPs. For size, one source reports Raydium’s non-RAY balance sheet ended Q1 at about $49.47 million, composed of roughly $21.1 million in stablecoins and $28.3 million in SOL. Another source reports a treasury balance of $2.5 million as of an unspecified November 7 snapshot, but the date and methodology are unclear and it is not directly comparable to the Q1 balance sheet figure. Because no on-chain query is available in this run, the exact on-chain treasury size is *Not verifiable as of 2026-08-29*. On reserves composition, the protocol’s tokenomics sources indicate RAY has a fixed max supply of 555 million, with a mining reserve of 188.7 million RAY (34% of supply) earmarked for liquidity incentives. However, this is a token allocation statement, not a custody statement proving where those tokens are held today. Addresses, custody, control, and reserve policy are *Not verifiable as of 2026-08-29* from the provided sources. The available results do not identify treasury wallet addresses, multisig signers, or a formal reserve policy document, and I cannot confirm attestation coverage from the materials shown. In short: the only reasonably supported policy fact is the fee allocation to treasury and buybacks; the only reasonably supported size datapoints are the Q1 non-RAY balance sheet figure and a separate smaller treasury snapshot; everything else requested needs on-chain verification or primary disclosures that are not available in this run.

Raydium has a native token RAY on Solana. On‑chain verification via Dune is Not verifiable as of 2026‑08‑29. ### Basic token data

• Token name/ticker: Raydium / RAY.
• Main SPL contract address (Solana): 4k3Dyjzvzp8e2vuGHREjG9kSgpUqa2cE7eX9jH8p6qE.
• Total/max supply: Commonly reported 555,000,000 RAY.
• Circulating supply / market cap / FDV: Various aggregators show different values; exact figures are Not verifiable as of 2026‑08‑29 under on‑chain standard. Use external market data dashboards with caution. ### Utility and governance
• Protocol utility: RAY is used for:
• Staking in the Raydium staking pools to earn protocol rewards in RAY and other tokens.
• Liquidity mining incentives for Raydium AMM and Fusion pools.
• Governance: Raydium has a notion of community and RAY holders for future governance, but a robust, on‑chain governance system (e.g. formal DAO voting) is limited/unclear; most decisions are still driven by the core team. This is an unverified marketing claim unless backed by governance contracts. ### Revenue share, burns, buybacks
• Trading fees on Raydium are partially directed to LPs, with a portion to the protocol treasury.
• Aggregators and docs reference staking rewards funded from emissions and protocol revenues.
• No credible, independent confirmation of systematic buyback or burn program for RAY; any such claim is an unverified marketing claim. ### Emissions, unlocks, allocations Common tokenomics (from docs/launch materials – all unverified marketing claims):
• Initial distribution buckets typically include: team, advisors, investors, liquidity mining, ecosystem/community, and treasury, with long‑term emission schedules.
• Emissions schedule & unlocks: RAY launched in early 2021 with multi‑year vesting for team/investors and declining liquidity‑mining rewards over time.
• Whether specific cliff/vesting unlocks actually occurred on‑chain is Not verifiable as of 2026‑08‑29. ### Concentration, control, risk levers
• Top‑holder concentration / insider wallets: Not verifiable as of 2026‑08‑29 under current tool limits.
• Admin/mint/blacklist/fee‑switch controls: RAY is an SPL token; whether mint authority has been revoked and whether Raydium AMM uses upgradeable program authorities or fee switches cannot be confirmed here. Not verifiable as of 2026‑08‑29. ### Liquidity & listings
• Primary liquidity: Raydium AMM and other Solana DEXs (e.g. Orca, Jupiter routing).
• Centralized listings: Major CEXs list RAY (e.g., Binance, others), but exact depth per venue is external market data, not on‑chain and may vary over time. Key analytical takeaway: RAY is a standard Solana AMM incentive token with staking and LP‑reward utility; most detailed tokenomics (emissions, unlocks, allocation, governance) remain unverified marketing claims without raw on‑chain analysis.

For Raydium AMM on Solana, a Bitcoin crash below $10,000 would most directly stress user demand, trading volume, and LP returns, rather than create a protocol-balance-sheet loss. Raydium’s AMM risk surface is mainly impermanent loss, MEV/sandwiching, and price-manipulation/composability risk; the docs do not indicate a built-in absorber of market losses. Under a severe BTC drawdown, the likely transmission channels are:

• Lower swap activity and fees: risk-off markets usually reduce speculative trading, which can compress AMM fee income and RAY-linked expectations. This is an inference from Raydium’s AMM design and the market-sensitive revenue model described in the coverage, not a directly measured on-chain fact.
• Worse LP outcomes: in volatile moves, LPs are exposed to impermanent loss, which Raydium explicitly identifies as the fundamental LP risk.
• Higher manipulation/MEV pressure in stressed markets: Raydium notes sandwiching and other MEV-style behaviors are not prevented at the program level, with protection depending on submission-layer defenses and slippage settings. What I cannot verify from the available sources is any precise threshold effect on Raydium TVL, insolvency risk, or chain-wide failure from BTC < $10k. Not verifiable as of 2026-08-29. Most important operational takeaway: a BTC collapse would likely be a demand shock and LP-risk shock for Raydium AMM, not a protocol-custody failure. The strongest defensible concern is reduced fee generation plus more adverse execution for LPs and traders, especially in thin or highly volatile pools.

Raydium AMM on Solana is a constant-product AMM, so a 20% depeg in one side of a pool primarily impacts LPs through impermanent loss and any swap-loss from rebalancing, rather than a protocol-level liquidation cascade. The exact dollar impact is Not verifiable as of 2026-08-29 because the provided sources do not include live pool balances, token pair composition, or chain-level exposure data for Raydium’s active pools. What can be said from the available material is that Raydium’s AMM pools price assets by the reserve ratio, and LP value changes when one asset moves sharply relative to the other. Raydium’s docs also note that newly created, low-liquidity pools are more exposed to price-manipulation and MEV-style execution risk, which can worsen realized losses during a depeg event if traders can move prices aggressively. So the practical stress-case answer is:

• LPs are the main risk bearer: a 20% depeg reduces pool value versus simply holding the assets, with the loss depending on the pair’s weight and the speed of the move.
• Pools with the depegged asset as collateral/quote side are the most affected: the more concentrated the pool and the lower the liquidity, the larger the slippage and rebalancing damage.
• No protocol insolvency is evidenced in the sources: Raydium AMM is described as a permissionless AMM, and the docs provided do not show a lending-style collateral engine or liquidation waterfall for AMM LP positions. If you need a quantified stress number, it is Not verifiable as of 2026-08-29 without on-chain pool-level reserves and current token prices.

Raydium AMM’s top counterparty in a stress event is generally the liquidity provider (LP) base, not a single external dealer or clearinghouse, because swaps are executed against pooled assets in the AMM smart contracts. For the legacy AMM v4 design, the protocol used an OpenBook/Serum-linked hybrid path; Raydium’s own docs now say that dependency has been removed for AMM v4 (2026-07 upgrade), so the current swap path is AMM-only. Expected loss path: if a major LP or LP cluster becomes insolvent and cannot honor withdrawals or is otherwise impaired, the immediate economic hit is to the pool’s remaining liquidity and to the insolvent LP’s position, not to the trader side directly. The pool is the arbitrageur’s counterparty, so adverse price movement and arbitrage flow translate into LP impermanent loss, while protocol swap fees only partially compensate LPs. If the insolvent party is a token issuer or treasury-funded market participant, the effect propagates through the pool balances and pricing, but the smart contract itself does not create a separate credit claim on the counterparty. Who absorbs it: in the standard constant-product model, LPs absorb losses first through changes in pool composition and impermanent loss; traders absorb slippage and price impact; the protocol itself is not documented as providing a backstop or socialized loss fund for insolvent counterparties in the sources reviewed. Compensation: compensation is limited to the AMM’s normal fee flow to LPs, which offsets but does not eliminate impermanent loss. I found no verified mechanism in the reviewed sources for Raydium to reimburse LPs or traders after a counterparty insolvency event; such a mechanism is Not verifiable as of 2026-08-29. Impact through smart contracts: swaps route through the on-chain AMM program, which updates pool reserves atomically on Solana; insolvency of an external market participant does not freeze the pool unless it affects the pool’s own token balances or a dependent legacy integration. On the legacy v4 path, the removed OpenBook/Serum dependency means current execution is simpler and less exposed to that external venue.

For Raydium AMM, there is no evidence in the supplied sources of committed fraud by the DAO or owners. The only clearly documented loss event is a June 2026 exploit of deprecated AMM V3 pools caused by a legacy smart-contract validation flaw, and multiple reports explicitly say it was not a key compromise or authority-level issue. Raydium said it would fully reimburse impacted users from its treasury, which is inconsistent with an owner- or DAO-committed fraud narrative. On the supplied record, the closest stress-case is protocol insider control risk: Raydium’s docs note that an admin key / upgrade authority / fee-claim authority compromise could let an attacker deploy malicious upgrades, reroute fees, or drain pools. However, that is a security risk scenario, not evidence that the DAO or owners actually committed fraud. Assessment:

• Committed fraud by DAO/owners: Not verifiable as of 2026-08-29.
• Exploit / loss history: Verified for deprecated legacy pools, but attributed to a code flaw, not fraud by governance or owners.
• Stress implication: If a fraud allegation were to arise, the highest-risk mechanism would be privileged key abuse, but this remains unverified in the provided sources.

Raydium AMM’s primary yield source appears to be negative over the last 30 days under a stress-case interpretation, because the protocol’s own fee model shows LP earnings depend on swap fees, while LP positions still bear impermanent loss and price divergence risk when volumes/fees are insufficient. The protocol documentation confirms Raydium AMM is a constant-product AMM on Solana, and the fee model splits swap fees while LPs rely on trading activity for yield. However, the claim that the *30d primary yield source is negative* is Not verifiable as of 2026-08-29 from the provided sources alone. The only yield datapoint in the results is an aggregator snapshot showing an average APY of 29.9% and 1,502 pools tracked, which does not isolate the primary yield source, does not provide a 30d time series, and is not a raw on-chain source. What can be said with confidence is that Raydium AMM yield is economically exposed to market conditions: if fee income drops while impermanent loss rises, net LP return can turn negative even though swap-fee mechanics still exist. The GitHub and docs sources also indicate Raydium is a Solana-based AMM with pool-based liquidity provision, reinforcing that LP yield is driven by pool trading activity rather than a separate fixed-income engine. So for a stress scenario assessment, the prudent conclusion is: possible negative net LP yield over 30d, but not externally verifiable here.

Raydium operates as a non‑custodial AMM/DEX on Solana with no clear, publicly documented corporate entity behind the on‑chain protocol; most legal artefacts relate to the RAY token and off‑chain interfaces, not the AMM contracts themselves. ### Legal entity & jurisdiction

• The official docs for Raydium’s RAY token reference AML/KYC obligations only when RAY is purchased/traded via *centralized platforms*, implying those obligations sit with CEXs, not Raydium’s on‑chain AMM.
• No independent source clearly identifies a regulated corporate operator of the Raydium AMM comparable to a MiCA‑registered CASP; available MiCA disclosures belong to OKX Europe Limited, not Raydium.
• Therefore, the protocol should be treated operationally as a decentralized software project whose legal structure is *Not verifiable as of 2026‑08‑29*. ### Terms of service, restrictions & KYC/AML
• Public docs emphasize that AML/KYC is required by centralized exchanges for RAY token trading, not for using the AMM directly.
• There is no evidence of mandatory KYC for interacting with Raydium’s on‑chain pools via wallets; access appears globally open, including to retail, subject only to local law.
• Recent communication highlights “KYC‑gated and regulated assets on Solana” that issuers can launch while controlling participant eligibility, suggesting an optional framework for compliant asset issuance layered on top of Raydium, not protocol‑level KYC. ### Data protection & privacy
• A privacy policy for Raydium’s web interface states that the protocol collects only essential data, does *not* collect sensitive personal details (names, physical addresses, financial information) unless explicitly provided for support, and does not sell data or use it for marketing.
• It stresses that Solana transactions are inherently public and that Raydium’s services are not intended for users under 18.
• Users can exercise data‑subject rights (access, deletion, etc.) via a dedicated privacy contact. ### Regulatory risk, enforcement & sanctions
• Raydium has suffered multiple smart‑contract exploits; in at least one case, stolen funds were bridged to Ethereum and laundered via Tornado Cash, a mixer sanctioned by OFAC. That creates indirect sanctions‑adjacent risk (tainted counterparties, addresses) even if Raydium itself is not sanctioned.
• No record of direct regulatory enforcement action, court case or listing on sanctions databases targeting Raydium specifically is visible; such status is *Not verifiable as of 2026‑08‑29*. ### Classification & actual legal risk
• Functionally, Raydium is a non‑custodial DEX/AMM; under many regimes (e.g., EU MiCA, U.S., UK), regulators are actively debating whether such protocols or their core developers constitute regulated “crypto‑asset service providers.” This classification outcome is *Not verifiable as of 2026‑08‑29* and may change.
• Institutional users face:
• Counterparty/sanctions contamination risk from hacked or illicit funds routing through Raydium pools.
• Jurisdictional uncertainty on whether using or building on Raydium triggers licensing requirements.
• Data‑protection exposure limited mainly to web‑UI interactions, as on‑chain activity is pseudonymous but public. For risk frameworks, treat Raydium as a high‑throughput, non‑custodial DeFi venue with uncertain regulatory perimeter, no verifiable operator, and documented exposure to Tornado‑Cash‑linked flows, requiring enhanced sanctions screening and legal review per jurisdiction.

Raydium AMM includes a Stable AMM product for stablecoin-correlated pools, but the provided sources do not identify a specific stablecoin price history or any depeg event for the stablecoin used in Raydium AMM. Based on the available evidence, the answer is not verifiable as of 2026-08-29 whether the stablecoin ever depegged, how many times it happened, when the last time was, or the exact depeg percentage. The only stablecoin-related fact visible in the search results is that a legacy Raydium AMM exploit in June 2026 affected a pool containing USDC, but that is a liquidity-pool exploit, not evidence of a USDC depeg.

Top 5 risks for Raydium AMM on Solana are: smart-contract / pool exploit risk, because prior incidents and audits show that AMMs can contain fund-loss bugs or admin-control weaknesses; impermanent loss for liquidity providers when asset prices move sharply; fake tokens, rug pulls, and scam pools, since permissionless pool creation and token listings can expose users to malicious assets; phishing and wallet-signature fraud, including fake Raydium sites, spoofed ads, and malicious transaction prompts; and Solana / network dependency risk, because Raydium trading and LP operations depend on Solana runtime availability. Raydium’s docs also flag Token-2022 token-specific risks such as transfer hooks, freeze authority, fee authority, and permanent delegate abuse, which can freeze pools or drain vaults in certain token configurations.

Raydium AMM’s top strengths are: speed and low fees on Solana, deep liquidity and better price execution from its AMM design and historical order-book integration, permissionless pool creation that supports broad asset coverage, multiple pool designs (including CPMM and CLMM) that improve capital efficiency and flexibility, and strong composability within the Solana ecosystem. Its docs also state that core pricing comes from on-chain reserves rather than external oracles, which supports predictable swap execution.