Centurion Protocol security#

Using the Centurion Protocol involves several independent security layers: protocol contracts, token contracts, the Centurion network, your wallet, and the interface you choose. No audit, simulation, or past performance can eliminate every risk.

Protocol contract risk#

AMM contracts hold assets and execute deterministic rules. A defect in swap, liquidity, accounting, access-control, or upgrade logic can put funds at risk. Before relying on a security claim, confirm that any audit report, deployment reference, or disclosure process is current and linked through official Centurion channels.

An audit is a review of a particular code version and scope. It is not insurance, a guarantee, or proof that every integration and token behaves safely.

Because exact deployment and administration details can change, verify the current contracts and their control model rather than relying on an address copied from an old article or message.

Token and market risk#

The protocol is permissionless. A pool can contain a malicious, upgradeable, restricted, rebasing, or counterfeit token. A token may allow buying but block selling, change transfer behavior, or grant broad administrator authority.

Market risks include:

Thin or concentrated liquidity and severe price impact.
Impermanent loss for liquidity providers.
Manipulated or short-lived pool prices.
Out-of-range v3 positions.
Losses from volatile or unbacked assets.

A pool's existence and a visible token logo are not security approvals.

Wallet and signature risk#

A valid wallet signature can authorize exactly what a malicious contract needs. Review:

CRC-20 spender and allowance amount.
CRC-721 or CRC-1155 operator approvals.
Batched smart-account actions and delegated permissions.
Recipient addresses, token contracts, and value transfers.
Network identity and chain ID.

Disconnecting a site does not revoke onchain permissions. Remove unused approvals through a trusted Centurion-compatible tool.

Interface and infrastructure risk#

A cloned site can generate malicious transactions while looking identical to CenturionDEX. RPC services, indexers, browsers, extensions, and devices can also fail or be compromised.

Reach CenturionDEX through a verified official source, keep wallet software updated, and compare important transaction details on the signing device. Hardware signing reduces key exposure but cannot protect you if you approve a malicious transaction.

What to do when something looks wrong#

Stop signing and record the site, transaction hash, token contracts, and wallet prompts.
Disconnect the site, then separately review approvals and smart-account permissions.
If a key or recovery phrase was exposed, move remaining assets to a newly created wallet from a clean device.
Report the incident through current official Centurion channels and appropriate local authorities.
Do not pay a stranger who promises guaranteed recovery.