PancakeSwap's veCAKE Purge Sparks Mystery-Wallet Governance Scandal

A governance dispute is unfolding at PancakeSwap after leadership proposed scrapping veCAKE, the vote-escrow mechanism that had given long-term token holders outsized influence over the protocol, just as on-chain records show an unidentified wallet quietly amassing enough locked CAKE to swing any resulting vote.

01A proposal that removes the thing it claims to protect

PancakeSwap's team put forward "Tokenomics Proposal 3.0," marketed under the banner of "True Ownership, Simplified Governance and Sustainable Growth." Its central change: retiring veCAKE and the Gauges Voting System entirely, along with unlocking all staked CAKE without penalty.

Under the plan, daily emissions would fall from roughly 40,000 CAKE to about 22,250 CAKE, and the PancakeSwap team itself would take over emissions management using "real-time data" rather than token-holder votes. Future IFO and TGE participation would also no longer require CAKE staking, removing one of the main incentives that had driven long-term locking in the first place.

Community members were quick to note the imbalance in the pitch. Forum user AtuIA observed that "95% of the content focuses on removing the old tokenomics model," while the replacement was described only vaguely as "easier and more efficient" — comparing it to demolishing a house with no blueprint for what comes next.

02Suspicious timing, and a wallet trail leading back to PancakeSwap itself

Before the proposal was even published, a wallet began locking CAKE in volumes approaching half of the entire supply, spread across multiple newly created addresses — a pattern that would let it dominate any veCAKE-based vote while, unlike genuine long-term stakers, being free to unlock the moment the proposal passed.

On-chain investigator Juapia, a longtime PancakeSwap ambassador, traced the funding history of one of the addresses involved: 0xd183f2bbf8b28d9fec8367cb06fe72b88778c86b. Its first transaction originated from 0x655E2488E1f116bE4020DC37AEbf9895e074c33E, recorded in this transaction. That funding address, in turn, traced back to an old PancakeSwap treasury wallet, 0x7122C91049511b58A14Ce2CE10f1aCF318cc51d0, via this earlier funding transaction. The treasury address itself is confirmed by a historical PancakeSwap post. "It is not a simple whale!" Juapia wrote while publishing the receipts.

Should the proposal pass, this wallet's locked tokens would be freed immediately, while other participants would be left to deal with the aftermath.

03Cakepie and other integrators caught in the middle

Among the protocols most exposed is Cakepie, which has spent over a year as PancakeSwap's largest veCAKE holder, having locked roughly 13 million CAKE for four-year terms. Cakepie's model mirrors Convex's relationship with Curve: users deposit CAKE and receive a liquid token (mCAKE), while Cakepie's own CKP governance token directs the resulting voting power — giving depositors liquidity and yield while Cakepie gains scale and influence.

"We were blindsided," Cakepie said after learning of the proposal alongside the rest of the community, adding that the move "feels deeply misaligned with the mutual trust we've worked hard to establish." A Cakepie representative, Dondon, was blunter still: "They built a protocol based on freedom to create - and now they're pulling the rug on the very builders they empowered. Is this DeFi? No. This is betrayal."

Stake DAO, which holds a position through its sdCAKE locker worth more than $500,000, echoed the concern, calling the proposal a move that "goes in the opposite direction from PancakeSwap's development over the past year" and asking that the team either abandon the change or introduce fair compensation for affected holders.

Curve Finance's Michael Egorov, who designed the original ve-tokenomics model that veCAKE was based on, weighed in as well: "ve-tokenomics reason to exist is to prevent governance attacks, making decision makers take long-term responsibility over their actions… Upgradability is a bug. Don't make your veGovernance upgradable, especially the lock part." Shortly afterward, Egorov re-locked his own veCRV positions for a full four years, in what looked like a pointed show of commitment to the model PancakeSwap was abandoning.

04A real problem, but a disputed remedy

The proposal does address a genuine criticism: prior to the mystery lock-up, Cakepie had reportedly accumulated close to 50% of total veCAKE voting power, directing emissions toward lower-volume pools. PancakeSwap's Head Chef Philip pointed out that "some pools extract value from $CAKE holders without adding much value."

But critics argued the response was disproportionate. Community member Hubert countered that "the solution is not to deprecate the very good veCAKE model... Just stop giving 25% of emissions to Magpie," while another user, Kuwada, questioned whether future projects would still choose to build on PancakeSwap given competing options like Uniswap. Alternative fixes proposed on the forum — caps on outsized pools, better incentives for high-volume activity, and penalized early exits — went unadopted in favor of full centralization of emissions control.

05PancakeSwap's response leaves the core question unanswered

Facing growing criticism, PancakeSwap published a blog post addressing nine selected community questions, but did not directly address the suspicious CAKE lock-up. On Twitter/X, the team's Head Chef acknowledged only that "there has been some discussion around the newly locked CAKE, and while we understand it's a significant amount, we're happy to see CAKE community members actively participating in the ecosystem."

Separately, user Marco Polo pressed PancakeSwap on decentralization claims given that many users face geo-restrictions on TGE participation; the team's response framed the TGE as a Binance Wallet partnership and pointed to broader IFO access for CAKE holders. Asked whether veCAKE would remain active through the vote itself, PancakeSwap confirmed it would — leaving the newly locked wallets' voting power intact for the decision. On the sustainability of its proposed 4% annual burn rate, the team acknowledged the figure is not guaranteed, being "based on data from the past two years" and dependent on trading volumes holding up.

06Community sentiment and unresolved tension over supply

Cakepie's Grimmace suggested a middle path: "Kitchen's goal is for CAKE deflation and improved reward efficiency. Cakepie is definitely glad to help, and I believe this could be done through different mechanisms rather than just killing veCAKE directly." Critics also noted the apparent contradiction between the stated deflationary goal and the plan's effect of releasing roughly 79 million additional CAKE into circulation upon unlock. Forum user Bethoveen warned this would "trigger a sharp drop in price," adding that "burns alone cannot keep up with this influx—not in the short term nor over several years."

An informal poll cited by Marco Polo found that roughly three-quarters of unique respondents opposed the proposal, against less than one-fifth in favor. Marco Polo asked whether the team would proceed regardless: "Was this community discussion meant to listen, or just a box to tick off while a quiet 25M vote block waits in the shadows to force approval?"

As of publication, Tokenomics Proposal 3.0 remains unvoted and could still be revised. The episode has nonetheless become a broader test case for governance-attack dynamics in DeFi: whether a protocol's own emission and treasury history can be used to trace potential vote manipulation, and whether veTokenomics systems can survive when the entity that created the rules also controls whether they can be rewritten.