— Why CDEX

Same protocol. Two names.

The site says Zerith. The token in your wallet says CipherDEX with the symbol CDEX. Both are correct. Here's why, in two minutes.


— Section 01

What you see in your wallet

When you claim test tokens or check your balance, your wallet shows the on-chain metadata of the token contract. The contract was originally deployed under the project's previous name, and was deployed with these constants:

name()The full name your wallet displays.
CipherDEX Token
symbol()The ticker, used in MetaMask and on Etherscan.
CDEX
decimals()6 decimals (USDC-style), not 18.
6

— Section 02

Why we can't just rename it.

ERC-20 token metadata — name, symbol, decimals — is set in the constructor and stored in immutable storage. There is no setName function on a standard ERC-20. That immutability is the property exchanges, wallets, and indexers rely on. Tokens that change their ticker on the fly are a phishing vector, not a feature.

We could deploy a fresh token with the symbol ZER and migrate balances — but that creates two tokens, two contract addresses, two markets, and forces every previous user to take a manual migration action. The cure is worse than the inconsistency. So we keep CDEX on-chain and use Zerith everywhere else.


— Section 03

What it means for you.

  • Nothing functional changes.

    Every encrypted bid, every auction, every payment, every claim works the same. The ticker is a label.

  • The same contract is the same contract.

    If you held CDEX before, you still hold it. No re-claim. No migration. No replay.

  • The pre-mainnet token will have a clean ticker.

    When we deploy production-grade contracts on Arbitrum mainnet, the settlement token will launch under a final ticker. CDEX is and will remain the testnet/Sepolia token.


— Still have questions

The /contact page has a 12-question FAQ and a direct line to a human.