FAQ

The LP fee: the pool’s static fee, from 0 to 10% and set when the pool was created, or, in a pool with a Dynamic fee module, the fee that module returns for this swap, capped at 50%. Part of the LP fee, at most 25% and set in the global config, goes to the protocol treasury; the rest stays in the pool for its LPs.

On top of that you pay Solana’s network fee and a priority fee. The app shows the fee before you sign.

The patch is part of a pool’s address. SOL/USDC with no modules, SOL/USDC with a dynamic fee and SOL/USDC with a limit order book are three pools, each with its own liquidity. The app quotes them all and routes to the best output.

LPs and traders accept a pool’s rules when they deposit or trade. If a patch could change, someone could add a hostile module after the deposits arrive. So the patch is fixed forever, and new rules mean a new pool.

Only in a pool with a Lockup, or another module with Before remove. A Lockup has one unlock time for the whole pool, shown on the pool’s page. Adding liquidity and swapping are never locked.

SPL Token and Token-2022 mints. Token-2022 mints with transfer fees, transfer hooks, a permanent delegate or other extensions that change how transfers behave are refused. SOL trades as wrapped SOL; the app wraps and unwraps it for you.

Not in v1. Swaps are exact input with a minimum output.

Any wallet that supports Wallet Standard. Phantom, Solflare and Backpack are detected automatically.

A module can make a transaction fail, raise the fee to 50% for a swap, refuse withdrawals if it has Before remove, or trade next to the user if it has Returns delta. It cannot touch the vaults, use your signature or get around your minimum output.

Patchbay v1 is new software and has no published audit yet. Read Security before you put in more than you can afford to lose.

You do, before you use a pool: its page lists every module in its patch. The registry is curated by the Patchbay admin and decides which modules the app shows by name. It is not an audit and gates nothing on-chain: any module with valid flags can be used in a pool.

Yes. Any program that implements the hook interface can be plugged into a new pool. See Write a module.

No. The AMM accepts any module whose address carries valid flags. A listing only puts its name in the app’s registry.

Hooks are cross-program calls inside one transaction. On Solana those calls are cheap and fast, every account a module touches is declared up front so the AMM decides exactly what a module receives and what can sign, and re-entrancy is impossible by design. Mining a module address is a PDA search anyone can run in a browser.

$PATCH is launching soon. Its contract address is published on this site, on the plate below and on the home page. While the plate says “launching soon” there is no official token. Always compare the full address.

There is no on-chain token governance in v1. One admin key manages the global config (the treasury and the protocol’s share of the LP fee, at most 25%) and the module registry.

The admin role can be handed to a multisig or a DAO later, in two steps: propose, then accept. No admin can change an existing pool.