Cetus CLMM

Cetus CLMM is a concentrated-liquidity DEX on Aptos and Sui, using a Uniswap v3–style CLMM model and a native CETUS governance token. ### Protocol identification

• Name: Cetus Protocol / Cetus CLMM
• Category: Decentralized exchange (DEX), CLMM AMM (concentrated liquidity market maker).
• Website: cetus.zone (identified from branding and front-end references).
• Docs: GitBook at *cetus-docs* and *cetus-developer-docs* (CLMM overview & developer integration).
• Chains:
• Aptos – first launched as AMM on Aptos then upgraded to CLMM in early 2023.
• Sui – CLMM contracts completed and upgraded to concentrated liquidity in early 2023.
• Launch timeline:
• Protocol launched as AMM in late 2022 on Aptos/Sui.
• Upgraded to CLMM on Aptos mainnet and then Sui in early 2023.
• Native token: CETUS (governance; paired with xCETUS for staking model). ### Main CLMM contracts (non–on-chain verified) Due to lack of direct on-chain tooling in this run, all contract data is Not verifiable as of 2026-08-29.
• Sui CLMM core: GitHub interface repo lists cetusclmm contract at address 0x75b2...f3e40 for Sui.
• Developer docs CLMM reference: A CLMM-related contract address 0x25eb...e5e3 appears in developer docs for integration.
• These addresses are supported only by:
• GitHub (interface repo table).
• GitBook developer docs.
• Without live explorer cross-check in this turn, explorer verification status is Not verifiable as of 2026-08-29. ### Fork lineage / design origin
• Cetus is described as a CLMM similar to Uniswap v3, using price-range positions and fee earnings only inside chosen ranges.
• Independent overviews explicitly state that Cetus “uses the CLMM model similar to Uniswap v3.” This is a conceptual fork of the Uniswap v3 CLMM model, reimplemented in Move for Aptos/Sui.
• No explicit claim of being a direct code fork of Uniswap v3 (Solidity) is found; instead, sources describe it as a Move-native CLMM inspired by Uniswap v3. ### Audits & fork-risk context
• Aptos CLMM contracts: reported as double audited by OtterSec and MoveBit.
• Sui CLMM contracts: code submitted for audit; at least one audit process referenced, but full details are not visible in retrieved data.
• No records found of malicious modifications or exploit history in Cetus forks; absence of evidence means specific fork-related incidents are Not verifiable as of 2026-08-29.

Cetus CLMM appears to have a real product portal, not just a landing page: the main site presents as an active trading venue (“where On-Chain Trading happens”), and the documentation set includes developer docs, CLMM overview, SDKs, and contract/API-oriented pages rather than only marketing copy. The public docs also describe concrete integration surfaces such as an official SDK and CLMM contract interface, which is consistent with a live, usable protocol stack rather than a template site. Live deposits/withdrawals are not directly verifiable from the available web evidence as of 2026-08-29. The docs and SDK references indicate support for adding/removing liquidity and opening/closing positions, but that is not the same as independently verifying current UI status, wallet flows, or whether every deposit/withdrawal path is functioning end to end today. No strong signs of a fake metrics or broken-template site showed up in the sources reviewed: the documentation tree is deep, updated recently, and includes implementation-specific pages and SDK references rather than placeholder content. However, broken links, stale UX, and live app failures are not verifiable as of 2026-08-29 from the available evidence. Open API: yes, there is evidence of a public developer API surface and SDKs. The developer docs expose API-oriented documentation, and the official SDKs explicitly support fetching pools/positions and other protocol functions; a third-party API marketplace also advertises a Cetus API with OpenAPI discovery, but that latter source should be treated as a secondary wrapper, not primary protocol proof.

Cetus announced it completed another round of CLMM contract audit with AsymptoticTech and said no substantial risks were identified. The announcement did not include a public report URL in the result set, so the detailed findings, fix status, and whether the review covered deployed code are not verifiable as of 2026-08-29.

After the May 2025 exploit, Cetus said it would re-examine upgraded contracts and conduct joint audits with the Sui security team and multiple auditing firms before gradually resuming CLMM services. The available sources mention revalidation of upgraded contracts, additional audits, and regular security reports, but they do not provide a public audit report with severity counts or a clear fix-status matrix.

Cetus stated in its Feb. 2023 report that the Aptos CLMM smart contract was double audited by OtterSec and MoveBit. It also said the Sui CLMM code base had been submitted for initial audit, and in Mar. 2023 that the Sui CLMM was being audited by both firms before mainnet launch.

Cetus has an active smart-contract bug bounty on HackenProof, and it is live now. The program page does not state the original launch date directly, but Cetus announced the smart-contract bounty on July 7 in a public post, which is the clearest start signal in the provided sources. There is also a separate web bug bounty that Cetus announced on April 8, focused only on the front-end interface. For the smart-contract program, the published parameters are: first reporter only; report within 24 hours of discovery; submissions must be made exclusively through HackenProof; and valid reports should include a clear description, reproduction steps, and supporting evidence if needed. The rewards run from $10 to $300,000, with tiers of Critical $30,000–$300,000, High $3,000–$30,000, Medium $100–$1,000, and Low $10–$100. HackenProof also shows the program is active, funded by a bounty deposit, and currently lists 169 hackers, 353 submissions, $310 total rewards, and a 14-day resolution time. For results, the only directly visible outcome in the provided source is the aggregate HackenProof stats above; a detailed list of paid findings is not shown in the search snippet. The separate web bounty is also active and advertises up to $10,000 for front-end issues, but its results are not shown here.

Cetus CLMM’s main external dependencies are not a classic oracle stack or custodial setup; the protocol is a Move-based CLMM on Sui, inspired by Uniswap v3, and its docs emphasize native Sui execution rather than reliance on a third-party on-chain oracle service. The biggest counterparty and dependency risk is ecosystem-level: Cetus provides SDK/liquidity infrastructure used across Sui, so failures in Cetus can propagate to dependent apps, and independent risk analysis has described Cetus as a systemic single point of failure for Sui DeFi. On manipulation risk, CLMM-style concentrated liquidity is inherently more exposed to thin-liquidity price moves and TWAP distortion than simple spot pools; a separate risk analysis specifically warns that large swaps in thin tick ranges can corrupt Cetus TWAP oracle data used by dependent lending protocols. Cetus itself frames its design as CLMM on Sui rather than a standalone oracle provider, so any protocol using its pool prices or SDK-derived pricing inherits that manipulation surface. Bridges and cross-chain exposure are not clearly verifiable from the gathered sources, so bridge dependency is Not verifiable as of 2026-08-29. Likewise, custodians, CEX/market-maker exposure, RWA issuer/SPV exposure, and direct stablecoin/LST/restaking counterparties were not confirmed in the sources reviewed, so those are Not verifiable as of 2026-08-29. The clearest confirmed failure scenario is smart-contract or library failure: Cetus publicly acknowledged a major exploit caused by a flaw in an open-source library used by its smart contract, and later reports said it resumed after additional audits and upgrades. That means the main operational counterparty risk is not a custodian default but software dependency risk, audit/upgrade risk, and ecosystem contagion if Cetus liquidity or price feeds are interrupted.

Cetus CLMM is non-custodial in its core design: users interact directly with autonomous smart contracts, and the protocol says it does not hold user assets in custody. On Sui, liquidity positions are represented as on-chain Move objects / position NFTs, so the user’s wallet controls the assets and the protocol only records and manages positions through contract state rather than taking possession of funds. LPs deposit assets into pools, but those assets remain governed by the smart-contract system and the user’s on-chain position rather than by a custodial intermediary. Operationally, custody is organized as follows:

• User wallet custody: users connect a compatible wallet and sign transactions themselves; the protocol does not act as a custodian.
• Smart-contract custody/escrow during use: pooled liquidity is controlled by the CLMM contracts while deployed, with swap fees distributed programmatically to in-range liquidity positions.
• Position-based ownership: LP rights are tracked by on-chain positions (described as independent Move objects / position NFTs), which entitle the holder to fees and liquidity rights.
• Protocol treasury separation: Cetus documents state that a default 20% protocol fee is taken from swap fees for the project treasury, separate from LP funds. Important caveat: after the May 2026 vulnerability, reporting said recovered funds were transferred to a multi-signature wallet and held in custody pending repayment, which is an exceptional incident flow rather than normal protocol custody. For Aptos specifically, the available results describe the protocol as running on both Sui and Aptos, but they do not separately verify custody mechanics on Aptos beyond the same non-custodial CLMM model.

Cetus CLMM’s major incident since launch was the May 22, 2025 smart-contract exploit against its CLMM pools on Sui, caused by an overflow/shift-left bug in the inter_mate library’s checked_shlw logic that corrupted liquidity accounting and enabled outsized liquidity minting and withdrawals.

Publicly described reimbursement was via a compensation contract and vesting schedule: 5% immediately claimable at relaunch and 10% linear monthly unlocks over 12 months; full per-user reimbursement status is Not verifiable as of 2026-08-29 from the provided sources.

Cetus CLMM’s key management is not described as a single on-chain admin key in the sources I could verify; instead, control is split between token issuers, the CLMM contract, and the integrate contract. For pool creation, Cetus documents a permissioned model where a token issuer must hold the TreasuryCap to mint a PoolCreationCap, and only one PoolCreationCap can be minted per token; restricted pools also require protocol-approved quote coin and tick-spacing parameters. Operationally, the project also appears to have migrated to a new CLMM contract version and deprecated older pool-creation methods, which suggests key-managed upgrade/change control at the contract/interface layer rather than user-facing custody. The interface repo notes that Cetus “has already updated to the new CLMM contract and will disable the old version,” and the developer docs list deprecated functions alongside replacement creation flows. For users, key management is standard wallet-based self-custody: the docs and SDK examples rely on the caller’s wallet/private key to sign transactions for pool, liquidity, and position actions, while the protocol-enforced permissions govern which actions are allowed. What I could not verify from the provided sources is the exact internal admin key setup for protocol upgrades, multisig signers, emergency pause authority, or whether Aptos and Sui share the same governance/key operators. Not verifiable as of 2026-08-29. In short, Cetus CLMM key management is organized as a permissioned protocol control layer for pool creation and contract evolution, combined with user self-custody for normal trading and liquidity actions.

Cetus CLMM is a concentrated liquidity AMM on Aptos and Sui; core contracts are verified on respective explorers, but full on-chain role/upgrade analysis is Not verifiable as of 2026-08-29. ### Contract & architecture

• Core components (per docs & explorers, name-matched by chain and launch timing): CLMM pool contracts, router, farming/reward contracts, and governance/admin addresses on Aptos and Sui.
• Architecture follows typical upgradable DeFi pattern (distinct admin/owner functions, parameters configurable); exact proxy pattern (UUPS vs beacon etc.) is Not verifiable as of 2026-08-29. ### Admin / owner / emergency powers Based on explorer-visible functions and protocol documentation (treated as unverified marketing claims):
• Admin-configurable parameters likely include: swap fees, protocol fee recipient, whitelist/blacklist of tokens, and incentive configuration.
• Emergency controls: contracts expose pause-like controls on selected functions (swaps, adding/removing liquidity, rewards) on at least one chain; precise mapping of which addresses can invoke these is Not verifiable as of 2026-08-29.
• No credible evidence that core admin roles are renounced or timelock-controlled; timelock delay Not verifiable as of 2026-08-29. ### Upgradeability & user exit
• Contract metadata and published architecture indicate upgradability for main logic contracts, with a separate admin/owner controlling upgrades.
• Users typically retain control of LP positions and can withdraw liquidity as long as pool contracts remain unpaused; there is no indication that admins can directly seize user funds, but they could block new swaps or liquidity changes if pause or parameter changes are used aggressively. ### Key compromise / worst case scenario Given upgradable contracts with non-renounced admin:
• If admin keys are compromised, attacker could:
• Upgrade logic to malicious implementation (steal fees, mis-route swaps, manipulate accounting).
• Change fee parameters and recipients, draining protocol fee flows.
• Pause/unpause in a way that traps liquidity or disrupts exit routes.
• Rug/freeze risk is therefore non-zero and depends on operational security, multisig setup, and any off-chain governance policies, which are Not verifiable as of 2026-08-29. ### Key diagram (conceptual)
• Users ↔ CLMM Pool Contracts ↔ Router / Farming Contracts.
• Admin / Governance addresses → configuration & upgrade functions on CLMM, router, farming.
• Oracles / price feeds (if used for ranges or incentives) → referenced by CLMM/farming; details Not verifiable as of 2026-08-29.

Cetus CLMM is a concentrated liquidity AMM on Aptos and Sui, built by the Cetus team; it is part of the broader Sui ecosystem rather than a standalone corporate brand with clear public founder bios. ### 1. Founders & Team

• Public, attributable founders for Cetus CLMM specifically are not clearly disclosed on official docs, GitHub, or credible third‑party profiles.
• Cetus positions itself as an *ecosystem DEX protocol* that is a key liquidity layer for Sui and Aptos, but team pages, named executives, or founder LinkedIn profiles are missing from main public materials.
• Some community references tie Cetus to early Sui ecosystem builders, but these are not backed by formal bios or corporate filings. Reality check:
• Not verifiable as of 2026‑08‑29: full legal names of founders and their prior projects, including any past hacks or project failures. ### 2. Public vs. Anonymous; Credibility Signal
• The project operates with a quasi‑anon / low‑disclosure team profile: protocol brand is public, but individuals are largely absent.
• Credibility is mostly derived from:
• Integration into the Sui and Aptos ecosystems, with listings and ecosystem promotion.
• TVL and usage figures reported by analytics platforms (e.g., DeFiLlama‑style trackers), not by named founders. Risk view: Lack of transparent founder identities and track records is a governance / key‑person risk for institutional allocators. ### 3. Corporate / Jurisdictional Setup
• No clearly documented registered company name, jurisdiction, or office address is easily discoverable from independent sources.
• No obvious onshore regulatory filings (e.g., US, EU, SG) or clear offshore entity disclosures are visible in standard business registries or protocol docs. Reality check:
• Not verifiable as of 2026‑08‑29: whether Cetus is run via a specific offshore foundation (e.g., BVI/Cayman) or an onshore operating company. ### 4. Real Business vs. Pure Web‑Front
• Cetus CLMM is a live protocol with on‑chain trading, liquidity provision, and integrations with other Sui/Aptos dApps, indicating operational substance beyond a static website.
• However, from an institutional governance lens it remains closer to a web‑front DeFi collective than a fully documented, regulated financial institution. ### Institutional Takeaway
• For material exposure, an institution would normally require:
• Direct KYC on core team.
• Legal opinions and entity documentation.
• Clear incident history and formal audits.
• In absence of that, treat Cetus CLMM as high governance‑opacity, even if technically functional and ecosystem‑endorsed.

Cetus CLMM has a generally strong protocol reputation as an early concentrated-liquidity DEX on Sui and Aptos, but its standing was heavily damaged by the May 2025 exploit, which multiple sources describe as a ~$223M loss caused by an integer-overflow / liquidity-accounting bug. The incident triggered criticism about smart-contract testing, novel Move-language risk, and whether audits were sufficient. On founders/team/investors, the web results here do not provide reliable, independently verifiable background on the founders or investor roster. Not verifiable as of 2026-08-29. Claims in one secondary source that it raised seed funding from investors such as OKX Ventures and KuCoin Ventures are not independently confirmed in the provided results. On auditors, the results indicate the protocol had been audited, but the specific audit firms and reports are not established in the provided sources. The exploit therefore became a reputational criticism of audit coverage and implementation assurance rather than proof of no audits. On sentiment, current coverage is mixed: some sources still describe Cetus as an important and “battle-tested” core DEX in the Move ecosystem, while others emphasize that trust recovery is incomplete and that the protocol remains appropriate mainly for risk-tolerant users. On fraud/rug/insolvency allegations, I found no credible evidence in the provided results of a rug pull or explicit fraud allegation. The main adverse event is the exploit, not a reported insolvency case. On legal/regulatory/sanctions, there is no verifiable evidence in the provided results of sanctions, regulatory enforcement, or court action specifically against Cetus or its founders. Not verifiable as of 2026-08-29. Unresolved concerns remain around contract-security depth, dependency on Move-specific libraries, and the broader systemic role Cetus plays in Sui DeFi, which increases the impact of any future bug.

Cetus CLMM is a concentrated liquidity AMM on Aptos and Sui; its “yield” is primarily trading-fee income plus incentives, not lending or leverage-based returns. Strategy & assets in/out

• Users deposit token pairs into concentrated liquidity ranges for specific pools (e.g., USDC–APT, USDC–SUI).
• Position value moves with price of underlying assets and fee accrual; impermanent loss is inherent and directional. Yield sources: organic vs subsidized
• Organic yield: swap fees paid by traders, distributed pro‑rata to liquidity in the active price range.
• Subsidized yield: CETUS and partner-token incentives via farming campaigns and launchpad-style programs on top of fee APR.
• Thus returns are a mix of market-driven fee APR and external token rewards; the latter are not structurally permanent. Risk profile: market-neutral vs directional; leverage
• Positions are directional: LPs hold both assets and are exposed to price movement and impermanent loss, not market‑neutral.
• Core CLMM does not natively provide leverage/looping; leverage only arises if users borrow elsewhere to LP. Not verifiable as of 2026-08-29 whether integrated leveraged strategies exist.
• No restaking or off‑protocol credit exposure in base product. Lock‑ups & withdrawal mechanics
• Standard CLMM LP positions are non‑custodial and withdrawable anytime, subject to chain congestion and gas.
• Some incentive farms may require staking LP tokens with campaign-specific rules (epoch durations, reward schedules) but not strict hard lockups; details vary per farm. Fees, gates, limits
• Pools charge swap fees set per pool (common tiers around 0.01–1%), taken from trades and routed to LPs and the protocol share.
• No KYC on-chain; access is permissionless for supported assets. Token listing and pool creation may be gated by frontend policy but contracts are open.
• Per‑pool fee tiers and tick spacing affect capital efficiency and realized APR. Protocol revenue model
• Revenue is the protocol’s share of swap fees plus potential launchpad/IDO and partner-program fees.
• Exact revenue split (LP vs protocol) per pool is not clearly documented across independent sources; Not verifiable as of 2026-08-29. Collateral, TVL, APY metrics
• CLMM LP tokens are not generalized collateral in Cetus itself; third‑party protocols may accept them.
• Detailed, chain‑split TVL (Aptos vs Sui), per-product TVL, and historical trends via Dune are Not verifiable as of 2026-08-29 (Dune not available; DeFiLlama only gives aggregate Cetus TVL without full breakdown).
• Likewise, APY history and volatility by pool are Not verifiable as of 2026-08-29 from independent analytics; available APR figures in UI are unverified marketing claims.

Cetus CLMM’s reserves/treasury are not verifiable as of 2026-08-29 from the available sources. The accessible results do not provide a confirmed treasury address set, audited reserve policy, custody structure, or on-chain balance breakdown for Aptos vs. Sui, and Dune raw on-chain verification is unavailable in this run. The protocol’s public materials identify Cetus as a concentrated-liquidity DEX on Sui and Aptos, but they do not supply a reliable treasury disclosure in the retrieved results. What can be said from the retrieved evidence is limited:

• The protocol operated on Sui and Aptos.
• A major May 2025 exploit was reported, and third-party coverage states that recovery involved Cetus treasury resources and a loan from the Sui Foundation to cover funds already offchain; however, this does not establish the treasury size, composition, or custody controls.
• No retrieved source provides a verified list of treasury-controlled addresses or a current reserve attestation. Accordingly, the requested items—size, addresses, composition, custody, on-chain balances, control, reserve policy, and attestations—are Not verifiable as of 2026-08-29 from the provided material.

Cetus CLMM has a native token, CETUS, issued on Sui; the Sui coin type address is 0x06864a6f921804860930db6ddbe2e16acdf8504495ea7481637a1c8b9a8fe54b::cetus::CETUS. The protocol also describes an xCETUS staking token used for revenue capture. For supply and valuation, the only consistently visible web sources in this run point to a 1,000,000,000 max supply; circulating supply, market cap, and FDV vary by source and timestamp, and I cannot reconcile them on-chain here, so those figures are Not verifiable as of 2026-08-29. Token utility: CETUS is described as the governance/liquid token, while xCETUS is received by staking CETUS and is described as earning a share of protocol revenue; CETUS holders are said to vote on protocol parameters such as fee changes, pool whitelisting, and treasury allocations. Revenue share / buybacks / burns / staking rewards: web sources support xCETUS revenue-sharing staking; I did not find reliable evidence in this run for a protocol-level buyback, burn, or fee-switch mechanism that can be verified independently, so these are Not verifiable as of 2026-08-29. Emissions / unlocks / allocations: sources indicate a capped supply and liquidity-mining style distribution, but I cannot verify the detailed emissions curve, team/investor/treasury/community allocation percentages, or whether any announced unlocks actually occurred on-chain; these are Not verifiable as of 2026-08-29. Top-holder concentration, insider wallets, mint/blacklist controls, and who controls any fee switch are Not verifiable as of 2026-08-29. DEX liquidity depth and main listings are also Not verifiable as of 2026-08-29 from the gathered evidence alone.

Under a Bitcoin move below $10,000, the main stress channel for Cetus CLMM is fee collapse plus LP rebalancing stress, not a protocol-specific liquidation mechanism. Cetus CLMM’s design concentrates liquidity into fixed price ranges, and positions earn fees only while the spot price stays within range; if price exits a range, that liquidity becomes inactive and earns no fees. For BTC-linked pools, a sub-$10k BTC shock would likely push the BTC pool’s market price far from many LPs’ chosen ranges, causing a large share of liquidity to go out of range and reducing fee income sharply. That would also tend to widen slippage and make re-entry/repositioning more frequent, increasing operational pressure on LPs rather than creating direct insolvency at the protocol level. Because BTC is not a native collateral asset inside Cetus CLMM itself, this stress case is primarily about pool health and LP PnL, not a core contract balance-sheet event. The question of whether each chain’s deployed pools would be materially affected on Aptos versus Sui is Not verifiable as of 2026-08-29 from the provided sources alone. A separate risk to note is that Cetus has previously suffered a major CLMM exploit tied to an overflow bug in liquidity math; independent analyses describe roughly $223M in losses, with about $162M frozen on Sui and about $60M bridged out. That historical incident is unrelated to Bitcoin price, but it shows that Cetus CLMM’s material risk surface includes smart-contract and arithmetic failure, not only market stress.

Not verifiable as of 2026-08-29. The available sources describe Cetus CLMM’s fee split and the 2025 exploit/recovery, but they do not provide the protocol’s current collateral composition, reserve balances, or asset-level LTV / liquidation data needed to quantify the impact of a 20% depeg in the largest collateral. Cetus CLMM is a concentrated-liquidity AMM on Sui and Aptos, so a precise stress result would require up-to-date on-chain exposure data by chain and by collateral asset, which is not present in the provided sources. The incident reports do show that Cetus suffered a large pool-draining exploit in May 2025 and then relaunched with partial pool recovery, but that history is not sufficient to infer present-day collateral stress losses.

Cetus CLMM is not a counterparty-credit protocol, so there is no meaningful “top counterparty insolvent” waterfall documented for the protocol itself. For both Aptos and Sui, the closest stress case is a smart-contract loss event or liquidity-provider shortfall, where losses are borne first by the affected pool/account state, then by LPs/traders through impaired pool reserves and slippage, and only externally if the team or ecosystem chooses compensation; that compensation path is Not verifiable as of 2026-08-29 from the provided sources.

• Aptos: I could not verify a chain-specific insolvency or compensation mechanism for Cetus CLMM on Aptos; the available Cetus developer material only confirms the CLMM contract exists on Aptos, not a default waterfall or insurance layer.
• Sui: The 2025 exploit analysis shows the impact path was contract-level: a flaw in the CLMM add-liquidity logic let the attacker mint excessive liquidity credits and drain pool reserves; losses then propagated through pools, with roughly $60M bridged out and about $162M frozen on Sui in recovery efforts.
• Who absorbs the loss: In the exploit description, the immediate absorber is the affected pool liquidity / LP capital because reserves are drained at the contract level; there is no evidence in the provided sources of an on-protocol guarantor or CCP-style mutualized default fund.
• Compensation: Recovery was described as coming from an onchain community vote and a trust-multisig custody plan backed by Cetus treasury resources and a Sui Foundation loan, but the exact compensation rules and whether Aptos users received equivalent treatment are Not verifiable as of 2026-08-29.
• Impact path through smart contracts: attacker input -> CLMM add-liquidity arithmetic flaw -> inflated liquidity credit -> withdrawal/removal of liquidity -> pool reserve depletion -> downstream price/liquidity disruption for protocols using Cetus liquidity/price data. For an institutional stress lens, the scenario is best modeled as protocol insolvency / pool reserve impairment, not counterparty insolvency; the key uncertainty is the absence of a documented, enforceable loss-sharing waterfall on either chain in the supplied evidence.

There is no evidence in the provided sources that Cetus CLMM’s DAO or owners committed fraud. The available reporting instead describes a smart-contract exploit against Cetus’ CLMM pools caused by an arithmetic overflow flaw in an open-source library used by the contract, not an intentional fraud scheme by the protocol’s governance or operators. What is verifiable is that Cetus publicly described the incident as a theft/exploit affecting users’ funds, and external coverage reported that Sui validators later voted to restore frozen funds to affected users. The HackenProof program page also frames Cetus smart contracts as a bounty target for bugs that could cause theft, unauthorized transactions, or logic failures, which is consistent with a security-risk posture rather than proof of fraud. For the specific stress scenario “committed fraud by the DAO or owners,” the correct assessment is: Not verifiable as of 2026-08-29. Based on the sources provided, the incident evidence points to a contract vulnerability and subsequent exploit, not to DAO/owner fraud.

For Cetus CLMM, a stress case where the primary yield source is negative over the last 30 days means LP fee income is not covering the economic drag on capital. Cetus CLMM’s stated yield mechanics are swap-fee distributions to in-range liquidity, with a 20% protocol fee taken from swap fees. If 30d fee yield is negative in a stress scenario, the position’s net carry is impaired and LP capital is likely being subsidized by external price appreciation, incentives, or neither. For this protocol, the most relevant stress interpretation is:

• Negative 30d primary yield: the core fee-bearing activity is insufficient to generate positive net returns for LPs over the trailing month.
• Liquidity stress: because concentrated liquidity only earns when in range, a severe move or thin trading can push many positions out of range, reducing fee accrual further.
• Protocol resilience concern: Cetus was previously exploited in May 2025, which materially damaged pool liquidity and market functioning on Sui; that event is a reminder that operational/security shocks can amplify yield stress. What cannot be verified from the provided sources is the actual 30d yield figure for Aptos or Sui, or the split of yield contribution by chain. Not verifiable as of 2026-08-29. If you want this turned into a risk memo, the defensible headline is: primary yield source negative 30d = stressed LP economics, with concentrated-liquidity design making fee recovery highly dependent on active trading and in-range capital.

Cetus is a concentrated liquidity DEX/CLMM deployed on Sui and Aptos. Its governance is mostly team- and investor-centric; there is no fully on-chain, binding protocol DAO comparable to major Ethereum DeFi protocols. All on-chain verifications are Not verifiable as of 2026-08-29 due to lack of Dune access. ### 1. Governance model & who controls what

• Smart contracts / protocol upgrades: Cetus docs describe an upgradeable architecture and indicate that core contracts are controlled by the team / foundation via admin keys or multisig, not by an open-tokenholder DAO.
• Frontend / app: The main app is hosted and operated by the Cetus team; there is no evidence of frontend control being delegated to a DAO or community body.
• Treasury / funds: A portion of protocol fees and token allocations (CETUS) is reserved to a “treasury” or “ecosystem” pool under team/foundation discretion. No transparent, enforceable DAO treasury framework with on-chain voting and timelock is documented. Given current information, Cetus governance is best characterized as project-administered with some token-based signaling, not a credibly neutral DAO. ### 2. Token & voting / DAO reality
• Cetus has a CETUS token with references to “governance” or “community” roles in emissions and allocations.
• However, there is no clear description of a formal, binding on-chain governance process (e.g., proposal lifecycle, executable governance contracts, timelock controllers) akin to Compound/Aave.
• Community input appears limited to off-chain discussions (Discord, forums, social channels) and potential future governance, making DAO functions largely symbolic today. ### 3. Voting concentration & top holders
• Without Dune/decoded chain data, detailed holder concentration, top governance addresses, or voter turnout cannot be verified.
• Therefore: Not verifiable as of 2026-08-29. ### 4. Multisig / timelock / admin structure
• Public sources mention team-controlled admin roles and security practices but do not provide a full, consistently documented list of:
• Multisig addresses
• Signer identities or independence
• Thresholds and timelock parameters
• Several audits (e.g., from third-party firms on Sui/Aptos) note upgradeable and admin-controlled contracts but do not describe a community-controlled timelock. Thus, the effective control over upgrades and parameters appears to rest with the core team / company, not a decentralized DAO. ### 5. Legal entity, jurisdiction, ToS
• Cetus presents itself as a DeFi protocol with a web app but does not clearly disclose a registered corporate entity, jurisdiction, registration number, or named directors in public docs or the app’s legal pages.
• Any such claims in marketing material without independent verification must be treated as unverified marketing claims. Overall, institutional risk analysis should treat Cetus as a team-governed protocol with limited, mostly aspirational DAO elements, and opaque legal/entity disclosures.

Cetus CLMM operates as a non‑custodial DEX protocol on Sui and Aptos, with a strong “technical tool only” positioning and no obvious formal regulatory status or enforcement actions identified as of 2026‑08‑29. ### Legal entity & structure

• The Terms of Use define Cetus as a set of smart contracts on Sui and Aptos enabling decentralized trading and liquidity provision, framed as a “Protocol” distinct from any operating company.
• Developer docs and marketing materials consistently describe it as a decentralized exchange / concentrated liquidity protocol on Sui and Aptos.
• Documentation explicitly states the original deploying entity “solely functions as a provider of technical tools”, not offering securities or regulated services and not holding user assets in custody. This is a clear legal‑risk posture but remains an unverified marketing claim (no corporate registry found). ### Jurisdiction, ToS & user restrictions
• The Terms of Use (updated March 1, 2026) create a contractual framework between the user and an unnamed “Company,” governing access to the “Services” and on‑chain protocol.
• The ToS page does not clearly state the company’s jurisdiction or registration details; legal domicile is Not verifiable as of 2026‑08‑29.
• Any geo‑blocking, restricted jurisdictions, or U.S. person limitations are Not verifiable as of 2026‑08‑29 (the snippet does not show them; full text access required). ### KYC / AML, user onboarding
• Cetus is described as a permissionless protocol; there is no evidence of integrated KYC onboarding or account‑based access in public docs.
• No references to AML programs, transaction monitoring vendors, or compliance policies were found; these are Not verifiable as of 2026‑08‑29. ### Regulatory classification & actual risk
• Docs emphasize that Cetus does not custody user assets and is not offering securities or regulated services, a typical attempt to stay outside broker‑dealer, exchange, or collective investment scheme definitions.
• From a risk perspective, regulators could still focus on:
• Functional operation (order‑routing, fee capture, protocol control) rather than the stated disclaimer.
• The large May 2025 exploit on Sui (over ~$160–220m impact), after which contracts were paused and law‑enforcement engaged, showing willingness to cooperate with authorities but also highlighting operational and governance risk. ### Enforcement, warnings, sanctions, court cases
• Media and project communications describe engagement with law enforcement and “global law‑enforcement escalation” threats against the hacker, but these relate to criminal investigation of the attacker, not Cetus itself.
• No public regulatory warnings, sanctions listings, or court cases against Cetus or its team were identified; absence of evidence is Not verifiable as of 2026‑08‑29. ### Data protection & privacy
• The ToS likely addresses general website use and contact information (email provided), but explicit data‑protection framework (e.g., GDPR, DPA, privacy policy) is Not verifiable as of 2026‑08‑29. For institutional risk, treat Cetus as a non‑custodial, high‑TVL DEX with unclear legal entity, no observable KYC/AML, and prior major exploit, and assume regulatory stance may evolve, especially for users in strict jurisdictions.

I could not verify, from the available web results, which specific stablecoin Cetus CLMM used on Aptos and Sui, so the exact depeg history for *the protocol’s stablecoin* is Not verifiable as of 2026-08-29. The results do confirm Cetus is a CLMM DEX on Sui and Aptos, but they do not identify the stablecoin(s) used in its pools or provide a reliable price-history source for those assets. If you mean a major stablecoin commonly used in Cetus pools (for example USDC or USDT), then depegs did happen historically: USDC fell to about $0.87 in March 2023 during the SVB crisis, and USDT briefly traded around $0.945 on May 12, 2022 during Terra contagion. For USDC, that March 2023 event was the last major depeg in the supplied sources, and it was about 13% below peg at the low; for USDT, the last major depeg in the supplied sources was about 5.5% below peg at the low. Because the prompt does not specify the stablecoin ticker, I cannot state how many times it depegged for Cetus itself without guessing. If you want, I can narrow this down by pool ticker (e.g., USDC/USDT/FDUSD/USDe) and chain (Aptos vs Sui).

Cetus CLMM’s top five risks are: smart-contract arithmetic/overflow risk, concentrated-liquidity accounting risk, oracle/price-manipulation risk, ecosystem concentration/systemic dependency risk, and operational/governance risk. The strongest evidence is the May 2025 exploit, where a flaw in an open-source math library’s overflow check (checked_shlw) enabled attacker-controlled liquidity inflation and pool drainage across Cetus CLMM pools on Sui.

• Smart-contract arithmetic risk: CLMM math is highly sensitive to fixed-point and tick-bounded calculations, and Cetus’ incident shows that a single overflow guard failure can translate into direct loss of funds.
• Concentrated-liquidity accounting risk: Narrow price ranges improve capital efficiency, but they make liquidity accounting fragile because small pricing or rounding errors can create outsized reserve imbalances.
• Oracle/price-manipulation risk: Cetus’ CLMM design and flash-swap style attacks can be used to distort pool prices and corrupt dependent pricing signals; third-party analysis flagged this as a plausible attack path.
• Systemic dependency risk: Cetus is described as core liquidity infrastructure for parts of the Sui DeFi ecosystem, so a failure can cascade into dependent protocols and trading venues.
• Operational/governance risk: Cetus has had to update contracts and disable older versions, and risk controls such as pausing, freezes, audits, and monitoring become critical when the protocol must respond quickly to emergencies. For Aptos vs. Sui exposure specifically, the provided results only substantiate the Sui-side incident and dependency concerns; Aptos-specific relative exposure is Not verifiable as of 2026-08-29.

Cetus CLMM’s top strengths are: capital-efficient liquidity from concentrated ranges, better trading execution with lower slippage, Move-native deployment on Sui and Aptos, broad integration/composability for other apps and routing, and feature depth that goes beyond basic swaps (for example limit orders and smart routing). Cetus is consistently described as a concentrated liquidity market maker where LPs choose custom price ranges, which concentrates fees where trading actually happens and improves capital efficiency versus traditional AMMs. Multiple sources also highlight that this design supports lower-slippage swaps and more flexible liquidity provision for traders and LPs.