Mentioned in This Article
1. What is the PancakeSwap CAKE emissions proposal?
The core team behind PancakeSwap, the decentralized exchange, published a plan on October 14 that would reduce daily CAKE emissions by about 69% while allowing liquidity providers on newer pools to keep 88% of the swap fees they generate. The proposal, called The Flip, remains in forum discussion, and several early replies from token holders are critical.
In plain terms, the team wants the exchange to pay for growth out of trading revenue rather than newly created tokens. Providers who supply the assets that traders swap against would earn a bigger slice of fees, and the protocol would mint far fewer CAKE each day to attract them.
The proposal arrives at a moment when many decentralized exchanges are reconsidering how they reward participants. Handing out freshly created tokens can draw liquidity quickly, but it also creates selling pressure whenever recipients convert rewards into other assets. PancakeSwap's team is effectively arguing that the exchange is mature enough to rely on real trading income instead.
Because the plan touches both the income of liquidity providers and the supply schedule of CAKE, it affects two groups with partly opposing interests, which helps explain why the first reactions have been mixed.
2. How would swap fees be divided under The Flip?
The team, which posts on the community forum under the name The Kitchen, would apply the new split to v3 and Infinity pools across all 11 blockchains on which PancakeSwap operates. Those include BNB Chain, Ethereum, Base and Solana. On most such pools today, liquidity providers retain between 66% and 68% of swap fees. Under the plan, they would receive 88%, and the remaining 12% would go to the PancakeSwap Treasury.
The team calculated what the change would have meant in practice. Had the new split applied to 2025 trading volume, liquidity providers on v3 and Infinity pools would have collected about $62 million more in fees. Trader fee tiers, meaning what people pay to swap, would stay the same, so the shift moves money between the protocol and the people who fund its pools rather than adding any cost for traders.
Older v2 pools work differently. Their fees are fixed in the contract code and cannot be altered, so they would be left as they are. They would also continue to direct 23% of swap fees into the CAKE burn, the mechanism that permanently removes tokens from circulation.
Understanding the split requires a quick look at how an automated exchange earns money. Each time a user swaps one token for another, a small fee is charged on the trade. That fee is divided between the people who deposited the tokens that make the swap possible, known as liquidity providers, and the protocol itself. A higher provider share makes depositing assets more attractive, which in turn deepens liquidity and tends to lower costs for traders through smaller price impact.
The 12% retained by the PancakeSwap Treasury would be the protocol's cut on those newer pools. Compared with the current arrangement, in which providers keep roughly two-thirds of fees, the share kept by the protocol would be smaller in relative terms, which is the central trade-off of the plan.
3. Why does the plan cut CAKE issuance so sharply?
Daily CAKE emissions would drop from 22,500 tokens to 7,000. That is 15,500 fewer tokens each day, which adds up to roughly 5.7 million fewer CAKE every year. The team described the goal in a short line: growth should be paid for by activity on the platform rather than by minting more CAKE.
The tokens that would still be issued, 7,000 a day, would not go to the usual pools. They would fill a new ecosystem pool named the Pantry. According to the team, the money there would be spent on marketing, partnerships and seeding liquidity in new pools, giving it a job similar to a growth budget.
Token emissions are a standard way for decentralized exchanges to attract liquidity. The drawback is dilution: when a protocol creates new tokens and hands them out as rewards, the supply grows unless burns offset it. By lowering emissions and paying providers with a larger fee share, the proposal tries to swap one incentive for another.
The numbers give a sense of scale. Moving from 22,500 to 7,000 tokens per day means the protocol would create less than a third of the CAKE it issues now. Over a year, the difference of roughly 5.7 million tokens is the amount that would no longer enter circulation, assuming the plan is adopted as written and current conditions persist.
4. What happens to existing Infinity pools?
Pools already running on the Infinity design face a technical wrinkle. Their liquidity-provider fees were locked in when each pool was created. Since those cannot be changed, the lower protocol cut would shrink the total fee charged on swaps rather than raising the providers' portion.
As an example, a pool charging 1% would end up charging about 0.76%. The change would make those pools cheaper for traders but would also reduce the total amount of fees collected per swap, which is a trade-off the community may weigh when it considers the plan.
The distinction between older and newer designs is a reminder that decentralized protocols often carry several generations of contracts at once. Pools built on earlier versions can be hard to modify because their rules are embedded in code, so proposals like this one usually apply fully only to the newest products and leave older ones as they are.
5. Does CAKE remain deflationary?
The team argues that it does. Its position is that v2 pools alone keep the token net deflationary, because the burn from those pools outweighs the remaining new issuance. It points to an average net supply decline of about 190,000 CAKE per week across the past 10 weeks.
That pace, the team says, keeps CAKE on course for a supply reduction of roughly 20% by 2030. The target comes from Tokenomics 3.0, a framework the community approved in April 2025. Supply has already shrunk by 11.5% since that framework took effect.
The supply ceiling has also been lowered more than once. In December 2023, token holders voted to reduce the maximum supply from 750 million CAKE to 450 million. A second vote, which closed on January 19, 2026, cut the cap again, to 400 million. The new proposal would continue that direction by reducing issuance rather than raising it.
A net deflationary token is one whose circulating supply shrinks over time because more tokens are burned than created. Projects with this feature often promote it as a way of rewarding long-term holders, since a smaller supply can, all else equal, increase the value of each remaining token. The team's argument is that the 69% emissions cut does not endanger this property, since the v2 burn alone keeps supply falling.
Critics counter that the burn, not the net figure, is what matters to many holders, because v3 and Infinity pools would no longer contribute to it. The two views rest on different readings of the same data, and the forum discussion will likely revolve around which one the community finds more convincing.
6. Why are some holders pushing back?
Most of the early forum replies have been negative, and several participants said the burn would get smaller. One user, Juapia, wrote that v3 and Infinity stop burning CAKE and asked why the team did not state that more plainly. The user suggested sending part of the 12% treasury share toward burns as a compromise.
Another commenter, matrdolfo, who said they have held CAKE since 2021, said they were fundamentally opposed to the final outcome. A third, PancakesLover, said they would personally vote against the change.
Their concern is an old one in token design. Holders often value burns because they reduce supply and can support the price, while liquidity providers value higher fee revenue. The Flip gives more to the second group, and the first is asking what it loses. At the time of the proposal, CAKE traded at $2.20 on October 15, a drop of about 6.8% over 24 hours, according to CoinGecko.
These objections are only an early sample of opinion. Forum threads tend to attract the most engaged and often the most skeptical participants, and the result of a formal Snapshot vote can differ from the mood of a discussion thread. Still, the team has said it will weigh the feedback, so the comments carry some influence over the final wording.
7. What is the timeline, and when might a vote take place?
If the plan is approved, the proposal says rollout would start in November and be completed by the end of January 2027. It has not yet moved to a Snapshot vote, the off-chain voting tool that PancakeSwap token holders use to decide protocol changes, and no date has been set for one.
The team said it will review all feedback before publishing a final proposal for voting. That signals that the details, including how much of the 12% treasury share is sent toward burns, could still be revised in response to what holders say in the forum.
For now, the main signals to watch are the tone of the forum discussion and whether the team amends the plan before a vote is called. The outcome will show how much weight PancakeSwap's community gives to liquidity providers' returns compared with the token's burn, an argument that many decentralized exchanges face as they try to move away from heavy reliance on token incentives.
A detailed rollout over roughly three months, from November through the end of January 2027, suggests the team expects to roll the change out gradually across its 11 supported chains rather than in a single step. Any revisions made after the discussion could change both the schedule and the specific percentages, so the figures reported here describe the proposal as published on October 14, not a final design.