Every pool has one fixed hook forever, normally. Hooknomics breaks that open: pick which hook behaviors apply to your swap from a live marketplace, pay only for the ones you select, and everyone else's swap runs completely unaffected by your choices.
Every swap that touches a Hooknomics pool runs through the same sequence.
Anyone can list a hook module in the marketplace: a fee curve, a protection scheme, a rebate rule. Each one names its own per-swap price.
Your choice gets encoded into the swap's own hookData, the same field Uniswap v4 already passes with every trade. Nothing about the pool itself changes.
On execution, the pool's hook decodes your selection and runs only those modules against your trade. Someone else's swap in the same block sees none of it.
A sample of what's listed. Prices are set by each module's author, not by Hooknomics.
A Hooknomics pool runs one hook, same as any Uniswap v4 pool. What's different is that the hook's behavior on any given swap depends entirely on what the trader selected beforehand, not on a single fixed configuration set at pool creation.
Uniswap v4 already lets every swap carry an arbitrary hookData payload
alongside it. Hooknomics uses that field for exactly what it's there for: a trader
encodes which module IDs they've paid for, and the hook reads that payload when the
swap executes.
Module fees are paid upfront into HooknomicsLedger as credits. When a
swap runs, the hook debits the credits for whatever was selected and splits the payment
between the module's author and the pool. Unused credits stay yours until you spend or
withdraw them.
Nothing here is deployed yet. A module is only as good as whoever published it, Hooknomics doesn't audit listings before they go live. Read a module's own source before paying for it.
Hooknomics would run on Robinhood, chain 4663.