CoinYQ Dossier

From Kitchen Emissions to a 400M Promise

CAKE financed liquidity with a contract that MasterChef can mint, then tried to make fee burns outrun emissions. The central question is whether a governance cap and direct voting can constrain a multichain system whose core proposals, emergency veto and product contracts remain team-administered.

MasterChef owned the oven before voters set the recipe

The CAKE contract submitted in September 2020 is simple: an owner may mint and there is no embedded cap. On mainnet the owner is the original MasterChef, whose pool weights and emission rate determine farm rewards. This made CAKE an operating subsidy for liquidity rather than a passive receipt for AMM fees.

A live 2026-09-04 call still resolved CakeToken owner to MasterChef. That does not mean the old chef alone controls every modern farm; later MasterChef versions and chain-specific systems distribute incentives. It does mean the headline cap must be read as policy above an uncapped base token.

Because the minting permission sits in this contract chain, a supply promise must be checked against both governance decisions and the live Chef configuration. A vote can set policy without rewriting the original CakeToken bytecode.

The gauge ballot was retired, not silently preserved

veCAKE once converted locks of one week to four years into voting power. Holders voted on gauges for later 14-day epochs, but Kitchen-selected core gauges, boosts and caps constrained allocation. The documentation now places veCAKE in a sunset archive.

Tokenomics 3.0 replaced that mechanism on May 15, 2025 with wallet snapshots: one CAKE, one vote, no delegation. Yet Core proposals remain team-only and team-implemented, community proposals are non-binding, no minimum quorum applies, and an emergency team veto remains. Direct voting is real but bounded.

One CAKE crossed chains through many control surfaces

Official developer material lists CAKE addresses across BSC, Ethereum, Arbitrum, Base, Linea, opBNB, zkSync, Aptos, Solana and Monad using LayerZero OFT infrastructure. The bridge interface can also select third-party providers. A 1:1 bridge promise does not make bridge messages, chain finality and local contracts one risk.

PancakeSwap's products differ by network as well. AMM versions, routers and farms are deployed separately, while perpetual V1 uses order-book engines and V2 uses chain-specific ALP liquidity. CAKE governance does not automatically upgrade, pause or compensate every component.

Burns turned a faucet into a balance-sheet argument

The project now calls 400M a hard cap after a January 2026 vote cut 450M to 400M. It targets roughly 4% annual deflation and a 20% reduction by 2030, using shares of spot fees, perpetual profits, CAKE.PAD, Prediction and Lottery for burns while continuing selected emissions.

The raw token totalSupply is not the same number. CakeToken transfers sent to a burn address remain counted in ERC-20 totalSupply, so PancakeSwap instructs readers to subtract burned balances. Burns can make effective supply fall, but they do not pay CAKE holders cash, grant LP claims or guarantee price appreciation.

How the project changed

  1. 2020-09-22
    CakeToken source is verified

    The BNB Chain token launches with owner-only minting and no embedded cap.

  2. 2023-11
    veCAKE and gauges formalize locked voting

    Locks direct a bounded share of later farm emissions.

  3. 2025-05-15
    Tokenomics 3.0 changes the ballot

    Wallet CAKE replaces veCAKE voting; delegation ends.

  4. 2026-01-16
    The 400M policy cap is proposed

    A successful vote reduces the stated cap from 450M.

Evidence and primary sources

Last evidence review: 2026-09-04

What is PancakeSwap?

PancakeSwap is a family of AMMs, routers, liquidity pools, farms and derivatives deployed across multiple chains. V2 pools use fungible LP tokens; V3 and Infinity use concentrated or configurable liquidity positions. Perpetual engines and bridge providers add distinct counterparties and contracts.

CAKE began on BNB Chain at 0x0e09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82. Official address documentation lists bridged or OFT representations on Ethereum, Arbitrum, Base, Linea, opBNB, zkSync, Aptos, Solana and Monad. These addresses represent one cross-chain token system, while each DEX deployment has its own pool, router and administrator surface.

What problem does PancakeSwap solve?

An AMM needs liquidity before trading can be useful. PancakeSwap used CAKE emissions through MasterChef to reward selected farms, then built fee-funded burns to offset those emissions. The tension is structural: emissions can buy liquidity today while diluting supply, and burns depend on future product activity.

Multichain expansion multiplies that tradeoff. A familiar interface may call different AMM versions, bridges or perpetual engines on different networks. CAKE voting can guide policy, but it cannot remove bridge, chain, hook, oracle, admin or liquidity-position risk.

How does PancakeSwap work?

The original CAKE contract is an 18-decimal BEP-20 with owner-only minting and no cap in its bytecode; its owner is the legacy MasterChef, which mints farm rewards. A 2026-09-04 BNB RPC call still returned MasterChef 0x73fe...9E24 as owner. The documented 400M hard cap is therefore enforced through governance and emission configuration, not a require statement in CakeToken.

Tokenomics 3.0 targets at least about 4% annual deflation and about 20% supply reduction by 2030. Burns use 15-23% of spot fees, 20% of perpetual profits, all CAKE.PAD fees, 3% of prediction rounds and 20% of CAKE played in Lottery; emissions remain for multichain farms, Lottery and ecosystem growth. These are project targets and policies, not guaranteed outcomes.

Governance changed in May 2025 from veCAKE to wallet-snapshot CAKE voting: 1 CAKE equals 1 vote, delegation is unavailable, Core proposals originate only from the team, community proposals are non-binding, and the team reserves emergency veto rights. The older lock-and-gauge system is archived; its historical votes directed non-core farm emissions but Kitchen rules, caps and boosts bounded the result.

Key facts

  • CAKE's BNB Chain contract is 0x0e09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82 with 18 decimals.
  • CakeToken has owner-only minting and no code-level maximum; its owner is the legacy MasterChef.
  • The official 400M cap followed a January 16, 2026 proposal reducing the policy cap from 450M.
  • BscScan raw totalSupply includes tokens sent to burn addresses; PancakeSwap subtracts burned balances to derive effective supply.
  • Since May 15, 2025, wallet CAKE at the proposal snapshot gives direct voting power; veCAKE is archived.
  • Core proposals are team-only and implemented by the team; community proposals are non-binding and the team keeps emergency veto power.
  • Cross-chain CAKE uses separate addresses and bridge infrastructure; one ticker does not make every deployment the same contract.

Official links

Categories

Related coins

Frequently asked questions

Is CAKE capped by the token contract?

No. The verified CakeToken code has owner-only minting but no maximum-supply check. The documented 400M cap is a governance and emissions policy.

Why can BscScan raw supply exceed 400M?

Transfers to burn addresses do not reduce CakeToken totalSupply. PancakeSwap's method subtracts irretrievable burn balances from the raw figure.

Is veCAKE still the voting token?

No. The page is archived. Since Tokenomics 3.0, wallet CAKE at a proposal snapshot supplies voting power.

Can CAKE voters execute every decision?

No. Core proposals are submitted and implemented by the team, community proposals are advisory, and the team reserves emergency veto rights.

Does CAKE give protocol revenue or LP ownership?

No direct dividend, redemption or pool-asset right is documented. Fees may fund burns; LP ownership comes from a separate LP position.

Is CAKE identical on every chain?

It is intended as one bridged token system, but each address, bridge path and product deployment has distinct contract and chain risks.

External trackers

Choose a tracking site for PancakeSwap: