Burnable
Any holder can call burn() to destroy their own CKT, permanently lowering total supply.
CK TOKEN is a fixed-supply, burnable BEP20 token. The full supply was minted once at launch, there is no mint function and no admin key — so the supply can only move in one direction: down.
CKT is a plain OpenZeppelin ERC20 with one extension: holders may burn their own tokens. Everything else that usually makes tokens risky was left out on purpose.
Any holder can call burn() to destroy their own CKT, permanently lowering total supply.
2,000,000,000 CKT were minted once in the constructor. No code path can ever create more.
Every transfer moves the exact amount sent. No hidden fees, no honeypot logic.
No address can be frozen or censored. Your tokens stay under your control.
Nobody can halt transfers or trading. The token always works.
No Ownable, no admin roles. There are no privileged functions to call.
The deployed bytecode is final. It cannot be upgraded or swapped out — by anyone.
Built on OpenZeppelin's audited ERC20. Source code is verified and readable on BscScan.
Burning sends tokens to nowhere: they are subtracted from your balance and from totalSupply()
in the same transaction. There is no way to bring them back.
burn(value)Enter the amount in wei — CKT has 18 decimals, so 1 CKT is 1000000000000000000.contract CKToken is ERC20, ERC20Burnable { uint256 public constant INITIAL_SUPPLY = 2_000_000_000 * 10 ** 18; constructor() ERC20("CK TOKEN", "CKT") { _mint(msg.sender, INITIAL_SUPPLY); } } // Inherited from ERC20Burnable: // burn(value) burn your own tokens // burnFrom(acct, value) burn with allowance
Everything below can be checked independently on BscScan.
The full supply sits in the deployer treasury at launch. Allocations for liquidity, community and reserves will be published here and executed transparently on-chain.
Always compare the full address before you trade or add the token. Anything else is not CKT.
0xb7BF195c97DC68173fe771e7c2b73131Cb9d200F