CenturionDEX Support
Crypto basicsSecurityNetworksFAQs

How do I use testnets on CenturionDEX?#

Use a Centurion testnet only through a currently supported official test interface. Add Fornax or Centaurus from verified configuration, obtain tCTN through the official distribution method if available, and keep mainnet assets out of the testing account.

Before you begin#

Choose the testnet required by the application or development task:

  • Fornax uses chain ID 287 and tCTN.
  • Centaurus uses chain ID 288 and tCTN.

A testnet may not have the same Centurion Protocol contracts, tokens, pools, or features as mainnet. Confirm current deployment information through official Centurion channels before testing an integration.

Step-by-step#

  1. Create or select a wallet account intended for testing.
  2. Get the current Fornax or Centaurus network configuration from an official Centurion source.
  3. Add the network to your wallet and verify the chain ID.
  4. Open the official CenturionDEX test environment, if one is currently provided for that testnet.
  5. Obtain tCTN through the current official faucet or distribution process, if available. Do not pay real assets for it.
  6. Confirm that both wallet and interface show the same testnet.
  7. Add only verified test token contracts needed for the exercise.
  8. Start with a simple tCTN transfer or low-risk test transaction.
  9. For a swap, review the test pool version, fee tier, route, approval, and minimum received.
  10. Record transaction hashes and contract versions so the test can be reproduced.

What a useful test covers#

A good integration test checks more than a successful confirmation. Verify:

  • Correct chain detection and rejection of the wrong network.
  • CTN-to-WCTN wrapping behavior where applicable.
  • CRC-20 allowance handling and approval limits.
  • v2 and v3 quote handling for the deployed test contracts.
  • Slippage reverts, insufficient tCTN, and token-transfer failures.
  • Wallet simulations and smart-account batch presentation.
  • Clear separation between testnet and mainnet configuration.

Common issues#

  • The faucet is unavailable: use only alternatives announced through official channels; never trust paid offers in direct messages.
  • No route appears: the testnet may not have a funded pool.
  • The token contract differs from mainnet: this is expected because deployments are separate.
  • The test passes but mainnet fails: liquidity, contract versions, token behavior, and fee conditions can differ.
  • tCTN is visible on the wrong chain: verify the chain ID and remove duplicate custom-network entries.

Stay safe#

Testnet signatures can still authorize malicious contracts. Never reuse a high-value account when a separate test account will work, and never share a recovery phrase, private key, or password to receive tCTN or technical support.

Related#