PancakeSwap Infinity hooks are separate smart contracts that add custom behavior to individual liquidity pools. A hook can adjust swap fees, apply trader discounts, create an onchain limit-order mechanism or introduce another rule before or after a pool action. These features can improve execution or capital efficiency, but they also add logic that users should identify before swapping or providing liquidity.

Last reviewed: September 1, 2026. PancakeSwap can add or change hooks, eligible pools, fee rules and supported networks. Confirm every live pool feature and contract address in the official interface. This independent article is educational and is not financial advice.

What is PancakeSwap Infinity?

PancakeSwap Infinity is a modular version of the PancakeSwap decentralized exchange. It introduced a shared Pool Manager, extensible hooks and two main automated market maker designs: CLAMM and LBAMM. These tools let pools use different liquidity and fee strategies without requiring a new version of the entire protocol for every feature.

CLAMM, or Concentrated Liquidity AMM, allows liquidity providers to place capital within selected price ranges. Concentrating liquidity can improve capital efficiency near the active price, but a position outside its range stops serving swaps and generally stops earning trading fees.

LBAMM, or Liquidity Book AMM, distributes liquidity across price bins. Trades within a bin can occur without moving its price, while different liquidity shapes can place more or less capital near the current market. The risk and management requirements depend on the selected pool, bin distribution and token pair.

A hook is not a third pool type. It is additional logic attached to an Infinity pool. A CLAMM or LBAMM pool can operate without a hook or with a compatible hook that changes specific actions.

What are PancakeSwap Infinity hooks?

A hook is an externally deployed smart contract called at defined points in a pool’s workflow. Depending on its permissions and design, it may run before or after a swap, liquidity change or another supported action. It can calculate a dynamic fee, verify eligibility for a discount, manage an order strategy or coordinate liquidity.

This modular design separates the core AMM from optional features. It also means that two Infinity pools for similar assets can behave differently. One might use a fixed fee, another a dynamic fee, and another additional order or discount logic.

PancakeSwap states that any developer, protocol or community member can build and deploy a custom hook. Therefore, the words “Infinity pool” do not prove that every attached hook was created by PancakeSwap or carries the same risk. Users should evaluate the exact pool and hook rather than relying only on the platform name.

Do hooks affect an ordinary token swap?

They can. PancakeSwap’s Universal Router searches liquidity across V2, V3 and Infinity. If a hook-enabled Infinity pool contributes to the selected route, its rules can affect the fee or execution even when the user did not manually open that pool first.

This does not mean every PancakeSwap swap uses a hook. The chosen path depends on tokens, networks, liquidity, trade size and the routes available at that moment. Before signing, review the route, final output, price impact and fee details shown by the application.

A route that advertises a discount is not automatically the cheapest overall. Compare the amount expected after every fee and price effect. Deep liquidity without a discount can produce a better result than a discounted pool with weaker execution.

Dynamic Fee Hook

The official PancakeSwap Dynamic Fee Hook replaces one permanently fixed swap fee with a fee calculated from market behavior. PancakeSwap describes the model as charging proportionally higher fees on larger arbitrage trades while leaving enough incentive for arbitrageurs to keep pool prices aligned.

For traders, the important point is that the fee can change. A previous swap, a screenshot or a static article does not determine the fee for the next transaction. The quote shown immediately before confirmation is more relevant.

For liquidity providers, higher fees during adverse or volatile conditions may offset part of the loss created when arbitrage moves assets out of a pool at changing prices. It does not remove impermanent loss, token-price risk or the possibility that fee income is smaller than the decline in position value.

Before using a dynamic-fee pool, check:

  • the current quoted fee and expected output;
  • whether the trade routes through one or several pools;
  • price impact for the intended amount;
  • the hook address and creator;
  • how the fee can change under volatile conditions.

VIP Discount Hook

The VIP Discount Hook, described by PancakeSwap as powered by Brevis, can reduce fees for eligible high-volume traders on supported pools. Eligibility is based on relevant onchain activity over defined periods. The mechanism uses zero-knowledge proof technology to verify conditions without requiring a conventional registration flow for each swap.

A wallet with substantial total volume is not necessarily eligible everywhere. The selected pool, measurement window, networks and program rules matter. Verify that the pool displays the applicable feature and that the final quote reflects the reduction.

Do not increase trading volume solely to reach a fee tier without calculating spread, price impact, network costs and market risk. A future discount may be worth less than the cost of unnecessary transactions.

CAKE holding fee discounts

The Token Holding Fee Discount Hook can apply lower fees to qualifying CAKE holders in supported pools. PancakeSwap says eligibility can depend on an average balance over a time window rather than only the balance at the instant of a swap.

Consequently, buying CAKE immediately before a transaction may not produce a discount. Holding CAKE also creates token-price exposure that can be much larger than the fee saved. Evaluate the asset independently instead of treating a discount as guaranteed profit.

Check the current tiers, eligible pairs, observation period and displayed quote. Program conditions and participating pools can change after this article is published.

Fee-Earning Limit Order Hook

PancakeSwap’s native onchain limit orders use an Infinity hook and a concentrated liquidity position at a chosen price. When market activity trades through that position, the deposited asset can convert into the desired token. Because the order acts as liquidity, the maker can earn a trading fee on the filled amount.

PancakeSwap’s April 2026 overview described a 0.1% fee option and a newer 0.01% tier intended to improve execution priority. The available pairs, network and fee choices can change, so verify them in the current limit-order interface.

Important limitations include:

  • reaching the target price does not guarantee a complete fill;
  • an order can fill partially and leave the remainder active;
  • execution depends on trading activity through the relevant liquidity;
  • the deposited token remains exposed to market movement while waiting;
  • withdrawing an unfilled remainder requires an onchain action and may cost gas;
  • earned fees may be small relative to price movement.

This mechanism differs from PancakeSwap’s older ORBS-powered limit orders, which were deprecated for new orders in September 2025. Users managing an old order should identify its version rather than assuming the current Infinity instructions apply.

TWAMM Hook

A Time-Weighted Average Market Maker hook can divide a large trade into smaller executions over a selected period. The objective is to reduce the immediate price impact that one large swap might cause.

Spreading execution does not guarantee a better average price. The market can move against the trader during the schedule, liquidity can change and every strategy introduces contract and execution assumptions. Compare the time horizon, cancellation rules and complete costs before using a time-weighted order.

Shared Inventory Hook

Introduced in August 2026, PancakeSwap’s Shared Inventory Hook is designed to let one inventory support liquidity across multiple asset pairs. Capital is injected when a swap needs it rather than being permanently divided among separate pools.

This design targets capital efficiency for professional liquidity providers and asset issuers. Ordinary traders may encounter its liquidity through routing without managing the shared inventory themselves. As a newer mechanism, it should be evaluated using its current contracts, audits, ownership controls and live documentation rather than assumed to behave like a standard passive pool.

How to identify a hook-enabled Infinity pool

  1. Open the official PancakeSwap application. Use a verified bookmark instead of an advertisement or unsolicited link.
  2. Open Earn and the liquidity section. Interface names can change, but the pool directory contains the relevant details.
  3. Select the Infinity filter. This separates Infinity pools from V2, V3 and StableSwap listings.
  4. Choose the correct network. A similarly named pool on another chain has different contracts and liquidity.
  5. Read Pool Features. Tags can identify dynamic fees, discounts, order types or additional features.
  6. Open the complete feature list. A “+1” or similar indicator means more logic may be attached than the first visible label shows.
  7. Verify the hook address. Follow the block-explorer link and compare the address character by character.
  8. Identify the creator. Determine whether the hook was built by PancakeSwap, a named partner or an independent third party.
  9. Review available source code and documentation. Open source improves inspectability but does not guarantee the absence of vulnerabilities.

Are PancakeSwap Infinity hooks safe?

No smart contract can be described as completely safe. Infinity hooks can add valuable functionality, but they also increase the number of assumptions involved in a pool. The risk depends on the specific hook code, deployment, permissions, creator, external dependencies and token pair.

Relevant risks include:

  • Code risk: an error can produce incorrect fees, accounting or execution.
  • Permission risk: privileged roles may be able to change parameters or manage components.
  • Integration risk: a hook can depend on an oracle, proof system, vault or another contract.
  • Economic risk: correct code can still create unfavorable outcomes under extreme market conditions.
  • Token risk: malicious, fee-on-transfer or unusual tokens can behave unexpectedly.
  • Liquidity risk: a thin pool can produce large price impact or incomplete execution.
  • Approval risk: granting a contract permission can expose tokens if the spender is malicious or compromised.

A verified source-code badge or public GitHub repository is useful evidence, not a warranty. Audits can reduce uncertainty but cannot prove that a system will never fail.

Checklist before swapping through a hook-enabled pool

  • Confirm the official PancakeSwap domain and connected network.
  • Verify both token contract addresses.
  • Review every pool included in the route.
  • Check the current fee, expected output and price impact.
  • Open the Pool Features details when available.
  • Identify the hook creator and contract address.
  • Inspect the requested token allowance.
  • Use a small test for an unfamiliar pool or hook.
  • Reject any request for a seed phrase or private key.

Checklist before providing liquidity

  • Understand whether the pool is CLAMM or LBAMM.
  • Review the price range, bins or liquidity shape.
  • Identify every attached hook and external dependency.
  • Calculate returns after gas, price movement and impermanent loss.
  • Check whether rewards require the position to remain in range.
  • Understand withdrawal conditions and emergency controls.
  • Avoid treating displayed APR as a guaranteed future return.

Frequently asked questions

Do all PancakeSwap Infinity pools use hooks?

No. Hooks are optional and attached selectively. Some Infinity pools display no Pool Feature, while others can have one or more features implemented through a hook.

Are hooks used automatically when I swap?

They can be. The Universal Router may use a hook-enabled Infinity pool when it contributes to the selected route. Review the route and quote before signing.

Can I disable a hook on an existing pool?

A user generally chooses whether to use the pool or route; they do not remove its attached contract logic for one transaction. Select another available route or pool if the hook does not fit your requirements.

How do I get a PancakeSwap fee discount?

Eligibility depends on the specific supported pool and hook. Current examples include qualifying trading-volume and CAKE-balance conditions. Confirm the live feature rules and final quote.

Does the Dynamic Fee Hook always reduce fees?

No. Dynamic means the fee can adjust. Calm conditions may result in a lower fee, while certain volatile or arbitrage conditions can produce a higher one.

Does the Limit Order Hook guarantee execution?

No. Execution requires market activity through the position and can be partial. A target price being reached elsewhere does not guarantee that the entire order fills.

Are third-party PancakeSwap hooks audited?

Do not assume so. Check the exact creator, contract, repository, audit reports and permissions for the hook attached to the pool.

Final takeaway

PancakeSwap Infinity hooks make pools programmable. They can adjust fees, verify discounts, create fee-earning limit orders and coordinate new liquidity strategies. The same flexibility means users must look beyond the token pair and identify the contract logic attached to the pool.

For current details, consult PancakeSwap’s official Infinity Hooks 101 guide, Dynamic Fee Hook documentation and fee-earning limit-order instructions.

Open PancakeSwap ↗Official website