Kyber (KNC) Price

KNC is the ERC-20 utility and governance token of the KyberSwap ecosystem, short for Kyber Network Crystal. It is not the native token used to pay Ethereum gas; its main protocol role is to let holders stake, vote through KyberDAO, or delegate their voting power to participate in governance related to ecosystem incentives and token arrangements. KNC's uses therefore depend on KyberDAO and KyberSwap rules, rather than merely on holding the token code itself. Governance can determine certain token-related parameters and arrangements. Before using it, distinguish current KNC from KNCL, which has been upgraded to the legacy version.

After holders stake KNC in KyberDAO, they can obtain voting power corresponding to their staked position and vote on proposals that enter the governance process. They may also delegate their voting power to another participant to vote on their behalf. Delegation changes who exercises the voting power; it does not transfer ownership of the tokens to the delegate. This participation method connects the token to governance: proposals may concern incentives, ecosystem development, and token-related arrangements, and voting outcomes are then implemented under the DAO's governance procedures. Simply holding KNC without completing staking or delegation under the rules in effect does not mean that a holder has participated in voting.

KNC stakers may receive voting rewards because KyberDAO's reward funding comes from a portion of fees collected from KyberSwap trading activity and is distributed in KNC to participants who meet the applicable rules. It is not fixed yield that accrues automatically just because tokens are held in a wallet. Receiving rewards requires satisfying eligibility requirements such as staking and voting during the relevant Epoch: first establish a staked position usable for governance, then vote on applicable proposals, and finally claim or settle rewards according to that period's rules. Reward size is affected both by the fees entering the reward pool and by governance-set distribution rules, so it cannot be inferred directly from the number of tokens held at a single point in time.

KNC's supply has involved issuance, burns, and authorization for additional minting rather than a rule that has remained fixed since inception. Official tokenomics materials state that 226 million tokens were initially minted in 2017, after which some unclaimed tokens were burned; after additional minting was authorized for an ecosystem growth fund in 2021, maximum supply increased to 252,301,550 tokens. These figures describe the supply history and maximum-supply arrangement and should not be confused with real-time circulating supply. Whether further minting, burning, or token upgrades occur must be decided through KyberDAO governance. To understand KNC supply, distinguish tokens that have been created, tokens that have been burned, the maximum-supply arrangement, and the amount actually circulating.

KNCL is the legacy name for the previous version of KNC. After the 2021 upgrade, the new token retained the KNC ticker, while the old token was renamed KNCL. Their names are similar, but they represent different versions, and KNCL should not be treated as the same asset that can directly use current KNC governance and functionality. The official upgrade path migrates KNCL to current KNC at 1:1: the migration changes the token version, not the exchange ratio. When holding the legacy version, the key considerations are whether the asset has been migrated and whether the wallet, platform, or contract in use supports the current version.

No. KNC is not a token with a permanently fixed supply commitment: KyberDAO can make governance decisions on arrangements such as token upgrades, minting, and burning, so supply rules may change through valid governance resolutions. This does not mean that any party can change supply freely outside the rules. Actions affecting supply should first enter the DAO governance path; issuance, burns, or migrations that have already occurred each affect maximum supply, the number of tokens in existence, or the usable token version differently. To assess a supply change, review the specific proposal or official implementation notice rather than relying on the token name alone.