Cetus Protocol

Cetus Protocol: How Its Sui-Based Liquidity System Works

Cetus combines concentrated-liquidity pools, dynamic-liquidity tools, and swap aggregation on Sui. CETUS is tied to staking and the project’s planned xCETUS governance system, but users remain exposed to smart-contract, liquidity-management, and ecosystem risks.

A liquidity protocol built on Sui

Cetus is a DeFi protocol deployed on Sui that provides several market functions rather than a single exchange contract. Its public materials describe a swap aggregator, a concentrated-liquidity market maker known as CLMM, and a dynamic-liquidity market maker known as DLMM. The project also presents vaults, liquidity incentives, intent-based trading features, and asset-launch tools as parts of its wider product set. The aggregator is designed to route trades across liquidity sources, while CLMM and DLMM are the underlying liquidity systems for different market-making approaches.

This creates an important distinction for users. A trader may interact with Cetus as a routing interface without relying on one pool, while a liquidity provider supplies capital to a specific Cetus market-making system. The project’s developer repository describes the aggregator as routing across 28 DEX providers, whereas CLMM uses continuous tick ranges and DLMM uses discrete bins with dynamic fees. Those components can depend on different contracts, SDKs, pool configurations, and external liquidity sources.

How concentrated liquidity works

Cetus CLMM lets liquidity providers select a price range instead of spreading capital across the entire possible price curve. A position is active when the pool price is inside its selected range and becomes inactive when the price moves outside it. The design can improve capital efficiency and fee concentration, but it also makes liquidity management more specialized than in a basic constant-product pool.

The official Move interface shows that a CLMM position is represented by an on-chain position object containing the pool, paired asset types, lower and upper tick indexes, and liquidity amount. The interface includes functions for opening positions, adding and removing liquidity, collecting fees and rewards, closing positions, and taking or repaying flash loans. This structure is useful for integrations, but it also means that position ownership, tick selection, fee accounting, and contract versioning all matter in practice.

DLMM, aggregation, and developer access

Cetus’s newer DLMM model organizes liquidity into discrete bins rather than continuous tick ranges. The project’s developer materials describe Spot, Curve, and BidAsk strategies for DLMM positions, with dynamic fees intended to respond to market conditions. In practical terms, CLMM is presented as a continuous-range liquidity model, while DLMM is aimed at more structured market-making around selected bins and strategies.

Developers can access the system through public Move interfaces, TypeScript SDKs, and an aggregator API. The official CLMM SDK supports mainnet and testnet configuration, while the Move interface recommends the Sui Move Registry for package versions. The repository also warns that Git tags may not always reflect the latest published package versions. Integrators therefore need to track package addresses, published versions, SDK compatibility, and the exact pool or route being called rather than assuming that all Cetus interfaces are interchangeable.

What CETUS and xCETUS do

CETUS is used in the project’s staking and governance design through xCETUS, described by the documentation as a non-transferable escrowed token. Users can convert CETUS to xCETUS at a one-to-one ratio, while converting back requires a vesting period. The documented redemption terms range from a 15-day period at a 0.5-to-1 conversion ratio to a 180-day period at a one-to-one ratio. Shorter redemptions can forfeit the unclaimed portion to the protocol’s ecosystem treasury.

The documentation says xCETUS is intended to provide staking rewards funded from protocol-fee net profit and to represent governance voting power. It also says governance functionality is planned to begin after circulating supply reaches at least 90% of total supply. That is a project-defined condition, not independent evidence that governance is already active or broadly decentralized. The same documentation limits the stated voting rights to Cetus protocol features and parameters rather than ownership of a company or its assets.

Security history and control questions

Cetus suffered a major exploit on May 22, 2025, according to an independent account from OCC Research citing Chainflow. The report describes an arithmetic-overflow vulnerability in CLMM tick calculations that enabled an attacker to manipulate price calculations and drain approximately $223 million from multiple pools. It also reports that validators representing more than 90% of Sui stake coordinated to freeze assets associated with the attacker, followed by a recovery vote.

The incident is relevant to both Cetus and Sui users because it exposed two separate control layers: application smart-contract risk and chain-level crisis coordination. The response helped limit further movement of funds, but the same report raised questions about rushed voting, the role of the Sui Foundation, and the precedent for validator intervention. Past recovery action does not establish that future exploits will be prevented, fully recoverable, or handled under the same process.

Who the system is for

Cetus is designed for traders seeking routed swaps, liquidity providers willing to manage concentrated or bin-based positions, market makers using defined strategies, and developers building Sui applications around swap or liquidity functions. The system may be useful to users who need Sui-native liquidity infrastructure, but its complexity is higher than a simple exchange interface suggests. Pool selection, price ranges, fee tiers, token contracts, route construction, package versions, and wallet transaction permissions can all affect the result of an interaction.

Key takeaways

• Cetus is a multi-part Sui DeFi system combining swap aggregation, CLMM pools, and DLMM markets.
• CLMM positions use selected price ranges, which can improve capital efficiency but require active risk and range management.
• CETUS is connected to xCETUS staking and the project’s planned governance framework; the documented activation condition should not be treated as proof that governance is already active.
• Developers must track contract versions, SDK compatibility, package addresses, and the exact route or pool used.
• The May 22, 2025 exploit remains a material part of Cetus’s security record and of the wider Sui governance discussion.

Risks and open questions

• Smart-contract risk remains material after the 2025 CLMM exploit, and public documentation alone cannot establish that all current deployments are secure.
• Concentrated and bin-based liquidity can become inactive or lose value when prices move outside selected ranges; fee income is not guaranteed.
• The aggregator depends on external liquidity providers, pool quality, route logic, and supported Sui assets.
• The documented xCETUS governance design includes a 90% circulating-supply condition, but the current operational status and breadth of governance participation require separate verification.
• Validator coordination during the 2025 incident raises unresolved questions about emergency intervention, censorship resistance, and the division of control between application developers and the Sui validator set.