Curve Finance Accuses PancakeSwap of Copying StableSwap Code, Seeks Licensing

Curve Finance has publicly accused PancakeSwap of incorporating parts of its StableSwap implementation into PancakeSwap Infinity without complying with the open-source licensing and attribution requirements. Curve pointed to specific file attributions and code segments that it says derive from its StableSwap AMM formula, warning that improper reuse or modification can create technical risks and legal violations. Curve cited prior stableswap-related exploits (Saddle 2022, Balancer 2025) to stress that deep expertise is required to safely integrate stablecoin AMMs. PancakeSwap responded it will contact Curve to discuss the matter; both parties signalled a preference for cooperation and potential licensing rather than litigation. PancakeSwap Infinity — launched across Arbitrum, BNB Chain and later Base — introduced cross-chain swaps, smart-contract “hooks” for custom pool parameters, dynamic fees, on-chain limit orders and reduced pool-creation costs, and included an “Infinity StableSwap” upgrade intended to lower slippage. For traders, immediate effects are primarily reputational risk and potential short-term volatility in governance tokens (notably CRV and CAKE) if the dispute escalates or forces contract changes or rollbacks. Monitor announcements from Curve and PancakeSwap, possible licensing outcomes, and any emergency contract updates — these could trigger short-term liquidity shifts and token price moves.
Neutral
The immediate market impact is likely neutral. The dispute is primarily legal and reputational: both projects signalled willingness to negotiate and prefer licensing over litigation, reducing the chance of abrupt technical disruptions. For traders, the most direct price exposure is to governance tokens (CRV and CAKE). Short-term volatility is possible if the disagreement escalates, a licence demand forces PancakeSwap to modify or rollback code, or if security concerns prompt emergency audits or pool withdrawals. Historically, code-reuse disputes and exploit precedents can trigger sharp but often short-lived moves as uncertainty resolves. Over the longer term, resolution via licensing or joint audits would limit ongoing downside; prolonged litigation or a forced rollback could harm PancakeSwap’s product rollout and liquidity, creating sustained negative pressure on CAKE. Conversely, a clean licensing deal and coordinated security fixes could stabilise markets. Traders should watch official statements, on-chain activity (liquidity and volume in affected pools), governance forums, and any code patches or audit notices to time risk management actions.