Your pool. Your fee policy.
Choose one adjustable LP fee, or different fees for the two swap directions. Set a permanent ceiling and build a controller that requires wallet and post-quantum approval for future fee changes.
Integration notes
Dynamic Fees deploys to public chains below · Directional Fees builds for local testing · not independently audited.
Build & exports
Downloads
What your build includes
A configured controller, its governed hook, manager, key registry and verifier, plus the complete 65-file Solidity source project and compiler input. Exports include the pinned helper bytecode and third-party notices.
The downloadable builds above target local chain 31337 and use the optional ML-DSA profile, whose one-time key setup takes about 40M gas and fits a single transaction only on Base and BNB Chain. To go live, use “Deploy to a public chain” below: Dynamic Fees then uses the hash-based post-quantum profile token launches use, whose key setup fits every supported chain. Building and downloading here does not connect a wallet, enroll a key, deploy contracts or move funds; deploying does each of those only after you approve it.
Integration notes
Supply verified infrastructure, ordered ERC20 addresses, a policy, a wallet owner and a newly enrolled public key at deployment. The actual controller address determines the hook’s CREATE2 permission salt. No test key or private key is included.
The base contracts have local integration tests. Compiling your settings does not run a new behavioral test. Fee changes—not each public swap or ordinary token transfer—require post-quantum approval. Deployment and connected fee-governance controls are separate workflows.
