Dev Overview

The developer documents listed here are for Sui network only.

Token Address:

CETUS Token CoinType

0x6864a6f921804860930db6ddbe2e16acdf8504495ea7481637a1c8b9a8fe54b::cetus::CETUS

xCETUS token coin_type

0x9e69acc50ca03bc943c4f7c5304c2a6002d507b51c11913b247159c60422c606::xcetus::XCETUS

SDKs & Contract Endpoints:

There are two apporaches for integrating with Cetus Protocol. The first involves utilizing the Typescript SDK, which grants you the ablilty to perform a wide range of actions. This encompasses queries, liquidity operations, and displaying data on the frontend. The alternative method entails a direct integration with Cetus CLMM contract. You can choose your integration method according to your actual demand.

Typescript SDK:

npm: @cetusprotocol/cetus-sui-clmm-sdknpm

GitHub - CetusProtocol/cetus-clmm-sui-sdk: The clmm sdk on Sui.GitHub

Smart Contract Endpoints:

GitHub - CetusProtocol/cetus-clmm-interfaceGitHub

Latest contract address:

Here is a list of primary contract addresses. We will update this form in real time. Please stay tuned for the updates here to ensure that your configuration is up to date.

• clmmpool is the core LP contract for Cetus. It's used by both SDK and contract endpoints method.

• integrate is the integration contract used by the SDK method.

• cetus_config is the config contract used by the SDK method.

Mainnet

Contract	Type	Mainnet Address
clmm_pool	package-id	0x1eabed72c53feb3805120a081dc15963c204dc8d091542592abaf7a35689b2fb
clmm_pool	published-at	0x157468379cfe5616c063ae39a889dd184ad48350d3e08f8d9b4ade22b8e3fb61
integrate	package-id	0x996c4d9480708fb8b92aa7acf819fb0497b5ec8e65ba06601cae2fb6db3312c3
integrate	published-at	0x15c0555d7601d98ca2659a8387d377a81b1e285ee0808484e101f96d05806187
cetus_config	package-id	0x95b8d278b876cae22206131fb9724f701c9444515813042f54f0a426c9a3bc2f
cetus_config	published-at	0x95b8d278b876cae22206131fb9724f701c9444515813042f54f0a426c9a3bc2f

Testnet

Contract	Type	Mainnet Address
clmm_pool	package-id	0x0c7ae833c220aa73a3643a0d508afa4ac5d50d97312ea4584e35f9eb21b9df12
clmm_pool	published-at	0xf3f49b91b82441ad017addff46d6d9a5867a755a86fb2374067fec19d6cc82c2
integrate	package-id	0x2918cf39850de6d5d94d8196dc878c8c722cd79db659318e00bff57fbb4e2ede
integrate	published-at	0x2918cf39850de6d5d94d8196dc878c8c722cd79db659318e00bff57fbb4e2ede
cetus_config	package-id	0xf5ff7d5ba73b581bca6b4b9fa0049cd320360abd154b809f8700a8fd3cfaf7ca
cetus_config	published-at	0xf5ff7d5ba73b581bca6b4b9fa0049cd320360abd154b809f8700a8fd3cfaf7ca

Latest NPM package version

npm package latest version: 5.1.10

Latest endpoint contract version

Mainnet

CetusClmm = { git = "https://github.com/CetusProtocol/cetus-clmm-interface.git", subdir = "sui/cetus_clmm", rev = "mainnet-v1.25.0" }

Testnet

CetusClmm = { git = "https://github.com/CetusProtocol/cetus-clmm-interface.git", subdir = "sui/cetus_clmm", rev = "testnet-v1.25.0" }

Now, you can select one approach to integrate with the service of Cetus Protocol:

via SDK

via Contract