Define your pool’s boundaries.
Choose the price range your pool will accept. Swaps must finish within the band; changing it requires both wallet and post-quantum approval.
Integration notes
local builds · not independently audited.
Build & exports
Downloads
What your build includes
Your configured controller, governed hook, manager, key registry and verifier, plus the complete 64-file Solidity source project and compiler input. Exports include helper bytecode and third-party notices.
This builder targets local chain 31337. It uses the optional ML-DSA profile, with expensive onchain key setup—not the cheaper hash-based profile. Its one-time key setup takes about 40M gas, which fits within a single transaction only on Base and BNB Chain; Ethereum, Arbitrum and Robinhood Chain cap transactions below that. Token launches use the hash-based profile and are not affected. Building here is free and does not connect a wallet, enroll keys, deploy contracts or move funds. Deploying to a public chain (below) instead uses the hash-based SLH-DSA key profile token launches use: about 1M gas for the shared verifier, once per chain, so it fits every supported chain.
Integration notes
Supply verified infrastructure, ordered ERC20 addresses, a policy, wallet owner and enrolled public key at deployment. Find the hook permission salt for the actual controller address and child initcode. No test keys or private keys are included.
Initialization is permissionless anywhere inside the initial band. Bounds are inclusive for swaps; ordinary liquidity callbacks are unaffected. A replacement band must include the current spot price. This is pool-local policy, not an oracle or a guarantee against manipulation or LP losses.
The base contracts have local integration tests. Compiling your settings does not run a new behavioral test. Connected band-governance and deployment are separate workflows.
