CenturionDEX Support
Crypto basicsSecurityNetworksFAQs

Rebasing, reflection, and debasing tokens#

Rebasing, reflection, and debasing tokens can change a holder's balance or the amount delivered by a transfer without an ordinary buy or sell. These designs may behave unpredictably in AMM pools, so inspect the contract and test cautiously before swapping or providing liquidity.

How each design works#

  • Rebasing tokens adjust balances across holders according to a supply rule. A positive rebase increases token units; a negative rebase decreases them. Your share of supply may stay similar even though the displayed number changes.
  • Reflection tokens redistribute part of transfer activity to qualifying holders. Wallet balances may increase without a direct incoming transfer.
  • Debasing tokens reduce balances or supply according to contract rules. The term is used inconsistently, so verify the exact implementation rather than relying on the label.

Some tokens combine these mechanisms with transfer deductions, allowlists, blacklists, or administrator-controlled switches.

Why this matters for pools#

A pool is also a token holder. If its balance changes outside normal swap, mint, or burn operations, recorded accounting and actual balances can diverge. The effect depends on the contract and pool version.

In v2, reserve synchronization may change the quoted ratio or leave excess tokens that can be collected according to pool logic. In v3, concentrated-liquidity accounting assumes well-defined token transfers and can be incompatible with tokens that alter amounts unexpectedly. Deposits, swaps, fee collection, or withdrawals may revert or produce results that are difficult to predict.

CenturionDEX cannot disable or rewrite a token's contract behavior.

Step-by-step before interacting#

  1. Verify the token contract address on Centurion.
  2. Review verified source code and current official project documentation, if available.
  3. Look for balance-scaling functions, transfer deductions, exclusions, owner controls, and upgradeable proxy logic.
  4. Check whether CenturionDEX displays a warning or refuses a route.
  5. Test with an amount you can afford to lose and compare sent, received, and post-transaction balances.
  6. Avoid adding liquidity unless you understand how the pool handles balance changes and withdrawals.

Example#

Suppose you hold 1,000 units and a supply event changes your balance to 900 without a transfer. That does not by itself prove a 10% economic loss; every holder and pool may have been adjusted under the same rule. The market price and your share of total supply determine the economic effect.

If only certain addresses are excluded or transfers are treated differently, the outcome can be far less predictable.

Common issues#

  • A wallet balance changes while no transfer appears in history.
  • The CenturionDEX quote differs from the amount received.
  • Adding or removing liquidity reverts.
  • A token works for selected addresses but not others.
  • Contract behavior changes after an administrator action.

Stay safe#

Never sign a “balance sync” or “token migration” transaction from an unsolicited message. Verify every contract and wallet request. A legitimate token does not need your recovery phrase, private key, or password.

Related#