What is Centurion?#
Centurion is a decentralized, EVM-compatible Proof-of-Stake layer 1 smart-contract network. Its execution environment is the Centurion Virtual Machine, or CVM, and its native token is CTN. Its guiding tagline is “Build, Operate, Stake.”
How the network works#
Validators participate in Proof-of-Stake consensus to order transactions, produce blocks, and verify state changes. Smart contracts execute on the CVM, which is compatible with established EVM tooling and account formats.
Centurion addresses use 0x followed by 40 hexadecimal characters. Compatibility of address format does not merge Centurion with another network; Centurion has its own balances, contracts, validators, chain IDs, and transaction history.
Protocol changes and standards use Centurion-specific names:
- CRC-20: fungible tokens.
- CRC-721: unique NFT assets and CenturionDEX v3 positions.
- CRC-1155: multi-token contracts.
- CIP: numbered Centurion improvement proposals.
CTN, WCTN, and Newtons#
CTN is the native asset used to pay network costs and participate in the network's staking economy. Computation is measured in Newtons.
Centurion uses a CIP-1559-style fee market with a per-block base fee and a transaction priority fee. Your wallet estimates the CTN needed for the Newtons a transaction may consume.
WCTN is the wrapped CRC-20 form used by smart contracts and liquidity pools. Native CTN can be wrapped when it enters a pool, but only native CTN pays network costs.
Network identities#
- Centurion mainnet: chain ID
286, native token CTN. - Fornax testnet: chain ID
287, test token tCTN. - Centaurus testnet: chain ID
288, test token tCTN.
Always obtain current RPC and explorer configuration from official Centurion sources. Do not guess endpoints or copy them from unsolicited messages.
CenturionDEX on Centurion#
CenturionDEX is the decentralized exchange interface for the Centurion Protocol. It operates on Centurion rather than on a third-party blockchain. Its live AMM versions are v2 and v3.
A wallet must be connected to the correct Centurion network before it can see the relevant pools, balances, and contracts. The same address on another EVM-compatible chain has separate state.
Common issues#
- Wrong chain ID: balances and applications do not match the intended network.
- Only WCTN is available: unwrap or obtain native CTN for Newton costs.
- A token symbol is duplicated: verify the Centurion contract address.
- tCTN is mistaken for CTN: test tokens have no mainnet value.