All discussion about PancakeSwap v4 will happen in this Category, including Requests for Proposals (RFPs), grant initiatives, and more.
Dear ChefMaroon,
I’ve developed a Private Market Maker (PMM) hook for PancakeSwap Infinity, currently deployed on BSC at:
0x2157b252fbc7153837d3be8cd5129a414b64b47a
This is the 14th deployed version, and I’m actively preparing further improvements for the coming days.
The hook overrides the native AMM via beforeSwapReturnsDelta, prices swaps from external oracles (V2/V3/V4 compatible), applies dynamic fees across 6 volatility tiers, enforces directional balance guards, and manages segregated per-pool reserves as VaultTokens (ERC-6909). Full CLBaseHook implementation with afterInitialize, beforeAddLiquidity, beforeSwap, and afterSwap callbacks.
It is multichain by design — the same contract can be deployed across any chain supported by PancakeSwap Infinity, with oracle addresses and pool parameters configurable per-chain via the companion app. One hook, multiple networks.
The problem: pools created with this hook receive zero swaps — the router does not route to them. I understand hooks need to be whitelisted, but I cannot find any public application form or documented process.
I’d appreciate guidance on the following:
- What are the requirements for a hook to be whitelisted for routing?
- Are there restrictions on hook type — must it be AMM-based, or is PMM (beforeSwapReturnsDelta) acceptable?
- Must the hook be open to public LPs, or can it serve a single market maker?
- Is there a formal application process? The CAKE Emission Program blog mentions a form, but the link appears unavailable.
- Does the hook require an audit before consideration?
I’ve been iterating on this for months across 14 versions and I’m committed to continued development. I’d rather align with PCS requirements now before deploying the next version than keep building without direction.
Happy to share source code, documentation, or any additional information you need.
Thank you.