CenturionDEX Support
Crypto basicsSecurityNetworksFAQs

I accidentally sent funds to the wrong address#

A confirmed Centurion transfer cannot be reversed by CenturionDEX or support. Recovery depends on who controls the destination address, which network you used, and whether the recipient is a wallet, service, or smart contract with a recovery function.

Step-by-step#

  1. Stop sending additional funds or paying anyone who claims they can reverse the transaction.
  2. Confirm the transaction status in a current official Centurion explorer.
  3. Record the transaction hash, sender, recipient, asset, amount, network, and time.
  4. Verify whether you sent native CTN, WCTN, or another CRC-20 token.
  5. Determine who controls the destination address.
  6. Contact that controller through a verified channel and provide the transaction details.
  7. Preserve all communication and report impersonators or recovery scams.

If the transaction is still pending#

A wallet may support replacing or cancelling a pending transaction by submitting another transaction with the same nonce and a more competitive fee. This is not guaranteed: the original can be included first, and a transaction that is already confirmed cannot be cancelled.

Check for earlier pending nonces before taking action. Avoid broadcasting repeated replacements you do not understand.

If you control the destination#

If the destination is another address derived from a wallet you control, switch that wallet to Centurion and select the correct account. Add the verified token contract for display if necessary.

If you sent on the wrong EVM-compatible network to an address whose private key you control, the same key may control that address on the source network. Access it only with trusted wallet software and verified network configuration. This does not move the asset to Centurion; it only lets you manage it where it was sent.

If a service controls the destination#

For an exchange, custodian, bridge, or payment service, contact its official support. Provide the transaction hash and exact network. The service may be unable or unwilling to recover unsupported deposits, and CenturionDEX cannot compel it to act.

Never trust a person who contacts you privately after you post the transaction publicly.

If the destination is a smart contract#

A contract can use assets only according to its code. If it lacks a withdrawal or recovery function available to an authorized party, the funds may be permanently inaccessible. Sending tokens to the token's own contract or an unrelated protocol contract is especially risky.

Do not sign an additional “rescue” transaction unless the function and operator are verified through official sources.

Common issues#

  • The recipient sees the same address on another chain but not the Centurion balance.
  • WCTN was sent when native CTN was expected.
  • A copied address was replaced by clipboard malware.
  • A service does not support the deposited CRC-20 token.
  • The destination has no known private key or recovery logic.

Stay safe#

Never share a recovery phrase, private key, password, or remote access with a recovery service. No one can guarantee reversal of a confirmed transfer. Verify every address on the wallet screen and use a small test transfer for new recipients.

Related#