CenturionDEX Support
Crypto basicsSecurityNetworksFAQs

How does the Centurion Protocol work?#

The Centurion Protocol matches swaps against token reserves held in AMM pools. Your wallet authorizes the transaction, the CVM executes the relevant pool logic, and the final balances are recorded on Centurion without a central operator taking custody.

How a swap works#

A typical swap follows this sequence:

  1. CenturionDEX reads available v2 and v3 pools for the verified token pair.
  2. The interface estimates output from current reserves, active ticks, fee tiers, and your amount.
  3. If the input is a CRC-20 token, you grant the selected protocol contract an allowance unless a sufficient allowance already exists.
  4. You review the route, estimated price impact, minimum received, and CTN network cost.
  5. Your wallet signs and broadcasts the transaction to Centurion.
  6. Protocol contracts transfer the input, apply pool math and fees, and send the output to the specified recipient.
  7. If an execution condition fails, state changes revert, although consumed Newtons can still cost CTN.

Smart-account wallets may combine approval and swap actions into one batch. A batch can simplify the interface, but you should still inspect each permission and call.

v2 execution#

In v2, a pool holds two reserves and maintains x · y = k. As the input reserve rises and the output reserve falls, the marginal price moves against a large swap. Every v2 swap pays the pool's 0.30% fee.

Liquidity providers deposit both assets at the current reserve ratio and receive CRC-20 LP tokens. Burning those tokens withdraws the provider's proportional share at the pool's current ratio.

v3 execution#

In v3, liquidity is assigned to price intervals bounded by ticks. A swap uses active liquidity at the current tick and can cross into additional ranges. Each fee tier is a separate pool.

Providers choose a range and receive a CRC-721 position NFT. While price is inside the range, the position can earn fees and change composition. Outside the range, it becomes inactive and holds one side of the pair until price returns or the owner adjusts it.

CTN and WCTN#

Native CTN pays network costs. Inside pools, CTN is represented by WCTN. The interface can perform wrapping or unwrapping as part of a supported transaction, but you must keep some native CTN available for Newtons.

Common issues#

  • Allowance is insufficient: approve the intended token amount for the correct spender.
  • Minimum output is not met: refresh the quote or review slippage tolerance.
  • The route changes: another transaction may have changed pool state.
  • No liquidity is active: a v3 pool may exist without depth near the current tick.
  • Simulation fails: token transfer logic or an invalid network can prevent execution.

Stay safe#

Verify the CenturionDEX interface, network, token contracts, spender, and recipient. Never share a recovery phrase or private key, and cancel any transaction whose calls or outcomes you do not understand.

Related#