Pool rules and risks
Review optional hooks, changing prices, and the limits of a successful simulation.
A hook is an external program attached to a pool. It can enforce rules at specific moments, such as before a trade or after a liquidity change. A pool without a hook is valid. Allowlists, trading windows, reward policies, and dynamic fees are optional examples, not restrictions on every grapl pool.
Read the rules before entering
Check which operations the hook controls, who can update its configuration or program, what proofs it needs, and its permitted fees. A policy that permits entry may place separate conditions on withdrawal. An application that does not understand the required hook should reject the action rather than omit it.
Rewards belong to the particular hook. A credit balance is not automatically transferable, redeemable, or part of your swap output.
Understand liquidity risk
Relative token prices change the assets held by your position. Compared with holding the original tokens, providing liquidity can leave you with less value; fee income may not offset the difference. Out-of-range positions stop earning new swap fees until the market returns. Full range still exposes you to token price changes.
Also consider token issuer powers, pool depth, hook and protocol bugs, upgrade authorities, and the interface or RPC you use. A test result or simulation does not establish an independent audit or production readiness.
Review what you sign
Verify the network, program, assets, recipients, spend limits, minimum received amounts, fee payer, and accounts being created or closed. Simulation checks one state snapshot. The state can change before inclusion, so your on-chain limits remain essential.
See Security for trust boundaries, limitations for unsupported features, and Hooks for technical details.