Live · Arc 5042Programmable markets · Uniswap v4
Build the hook.Launch the market.
Compose up to five visible swap rules, then open a Uniswap v4 pool instantly or use a bonding curve for price discovery first. Either way, the rules are fixed in place.
Hooks published last good read, through block 33971443.
Hooks published
- Five composable rulesEvery behavior is visible before launch.
- LP locked by constructionThe launchpad holds the position with no removal function.
- Fixed at launchPool rules cannot be rewritten after graduation.
The five blocks
What the hook actually does
Each block runs inside the swap, on the pool's own callbacks — there is no keeper, no off-chain trigger, and no oracle. Cuts apply to exact-input buys; sells pay the LP fee only. Every number below is a parameter you set before launch and nobody can set again afterwards.
Caps early buys and adds an LP fee in the first blocks.
~160K gas per swapFee scales with trade size.
~120K gas per swapBurns a share of actual buy output.
~140K gas per swapFee share streams to LPs.
~150K gas per swapA public counter pays every Nth buy.
~180K gas per swapThe hook builder
Pick the blocks.
Read the cost.
One block per behavior, five at most. As you tune the guard window, the pot cadence, or the burn share, the builder recomputes what a buy actually costs — the LP fee, the USDC-side cuts, and the output burn composed the way the contract composes them, not added up. Save the stack as a blueprint others can launch with, or launch it yourself.
- Five blocks, no Solidity
- Buy overhead recomputed as you tune, before you sign anything
- Creator fee split and LP distribution set per launch, not on the blueprint
- Every parameter public on the token page
The LP / pot USDC cut and Auto Burn apply to exact-input buys only. Auto Burn destroys its share of actual token output; it never accrues an USDC vault. Sells and exact-output buys pay the LP fee and nothing else.
The Nth-buy pot is deterministic: its public counter advances at most once per pool per block and the advertised Nth qualifying slot takes the pot. A funded pot remains claim-backed for the next scheduled winner; there is no permissionless flush. Qualifying buys must bind a canonical nonzero recipient, which the production router supplies automatically.
Read how it works →For Plunks
Publish a blueprint.
Take a cut.
Compose a stack, publish it as a blueprint, and earn a royalty on the eligible USDC hook fees whenever someone launches with it. Royalties are funded by the LP and pot USDC cuts; an Auto-Burn-only stack has no USDC share to fund one.
Compose a hook- 10x5a52…4aA223 launches · 0–5% royalty
- 20xA181…D60e7 launches · 1% royalty
- 30x8997…6C4F3 launches · 1–3% royalty
- 40x6FBA…7BAb1 launch · 5% royalty
- 50x0053…CFf91 launch · 1% royalty
Questions
Frequently asked
What is Plunk?
A token launchpad with a custom Uniswap v4 hook builder on Arc (chain id 5042). You stack up to five blocks into a hook, launch a fixed-supply token behind it, and every rule is readable on chain before anyone trades.
What are the five hook blocks?
Anti-Snipe caps and taxes buys for a set number of blocks after graduation. Surge Fees scales the LP fee with how much of the pool a trade consumes. Auto Burn sends a share of actual buy output to the dead address. LP Rewards donates an USDC-side share of buys to in-range LPs. The Nth-buy Pot fills a deterministic pot that pays the Nth qualifying buy.
Is the Nth-buy Pot random?
No, the pot is not random. A public counter advances at most once per pool per block, and the Nth qualifying slot wins — arithmetic anyone can check on chain. A minimum buy applies, and claimants can redirect their payout.
Where do Plunk tokens trade?
New launches sell through a bonding curve of ten tranches, each priced 70% above the one before it. When the last tranche sells out, the launch graduates into a Uniswap v4 pool in the same transaction, with its hook attached and immutable from then on.
Is Plunk adding leverage?
It is a published design, not something deployed. Leveraged Hooks would be credit extended by a hooked market itself rather than by a lending vault beside it: one pool, one liquidity base, spot and leverage on the same balance sheet. A trader posts equity, the market finances the rest and books what is owed back to it, and opening, closing and liquidating all execute through that same pool. How much credit a market may write is the minimum of its liquidity, the depth a liquidation could actually sell into, the $PLUNK bonded behind it and a protocol limit — so bonding more $PLUNK can raise that ceiling only up to what those other limits already allow, and never past them — behind a thin market it buys nothing. It would arrive through a bonded module marketplace rather than as a sixth built-in block. Providing liquidity to such a market means underwriting its credit: past the module's reserve, bad debt is the pool's. Leverage can lose you everything you post as equity. Not financial advice.
What is the official Plunk X (Twitter) account?
@useplunk_ — https://x.com/useplunk_. Verify links before connecting a wallet; an address plus its chain, not a ticker or a handle, is a token's identity.
What is the $PLUNK contract address?
$PLUNK has no contract address yet. It will be published here and in the CA button at the top of every page when the token launches; until then, treat any address claiming to be $PLUNK as fake.
Launch a token behind your own hook.
Four steps: name the token, pick the hook, choose an instant pool or a bonding curve, set the fee split, deploy. The hook is attached to the pool and cannot be changed.