"Permissionless" is doing a lot of work in DeFi right now. Uniswap calls its hooks permissionless. Hyperliquid calls its builder codes permissionless. Aster says the same about Aster Code. All three are correct — yet they mean something meaningfully different.

The deeper question is not which model is more open. It is which layer of the DeFi stack a builder is actually trying to own: the liquidity mechanics underneath, or the distribution surface on top. These are not competing answers. They describe different jobs entirely.

What Uniswap V4 Hooks Actually Are

At the protocol layer, Uniswap V4 introduced a single architectural change that reshapes what an AMM can be: hooks. Technically, a hook is an external smart contract that attaches to a pool and executes logic at defined points in the pool's lifecycle — before and after swaps, before and after liquidity additions and removals, and at pool initialisation. Eight callback types in total.

What this unlocks is substantial. A hook developer is not building on top of Uniswap — they are modifying how Uniswap itself behaves. Dynamic fees that adjust to volatility conditions, on-chain limit orders, TWAMM (time-weighted average market making) for large order execution, MEV protection logic, and native single-sided liquidity — pools that accept one token when price drifts out of range — are all implementable via hooks rather than as separate protocols. The singleton contract architecture means all of this runs under one shared liquidity system with meaningfully lower gas.

The developer surface area is deep. That depth is also the barrier. Building a hook requires solid Solidity experience and a clear model of pool lifecycle mechanics. The Uniswap Foundation has invested substantially in lowering that barrier: the Hook Incubator, run via Atrium Academy, received a $1.2M grant to scale the programme with four additional cohorts, self-paced learning materials, and a live event series. The Hook Design Lab and broader grants programme committed $26M across 2025. Across seven cohorts, the programme has onboarded over 500 developers and shipped 400+ hooks.

The April 2026 Hooks Marketplace launch was the first major commercial inflection point for all of this activity. The Foundation paired it with a $500M liquidity incentive programme. The result: $3.4 billion in new TVL attracted on the first day alone. Cumulatively, Uniswap V4 has now processed over $110 billion in total volume, with 2,500+ pools using hooks deployed across 10 EVM chains.

For builders interested in AgenticFi, hooks carry a specific structural advantage: the callback model is well-suited to agent-only logic. An agent that needs to rebalance a position, execute delegated wallet strategies, or apply conditional swap logic can be built directly into the pool layer — not layered awkwardly on top of it. Hooks make the AMM programmable in ways that autonomous agents can natively exploit.

What Hyperliquid Builder Codes and Aster Code Are

The problem Hyperliquid Builder Codes solve is entirely different. Not liquidity mechanics — distribution.

Builder codes are an on-chain fee attribution mechanism that lets any developer route user trades through their own interface and earn up to 10 basis points (0.1%) on every fill. No protocol governance approval required. No token launch required. The builder registers an address, attaches a builder code to the orders they send on behalf of users, and earns a per-fill fee recorded and settled on-chain.

The numbers bear out how well this model works. As explored in our April analysis, builder codes have generated $45M+ in total revenue with $100M+ annualised run rate. More than 100 teams have integrated via builder codes, and 40% of Hyperliquid's daily active users now trade through third-party frontends — not the official interface.

The clearest single proof of the model's scale: Phantom wallet. Phantom — primarily known as a Solana wallet — integrated Hyperliquid perpetuals directly into its interface and earned $20M in builder code revenue in under a year, routing $37 billion in perpetuals volume in the process. The $37 billion flowing through a single wallet integration validates the entire distribution thesis more clearly than any whitepaper could.

Builder codes are also evolving into a broader builder infrastructure. HIP-3 extends the model from UI-level fee capture to full market deployment: any builder who stakes 500,000 HYPE can deploy their own perpetual futures DEX on Hyperliquid's HyperCore infrastructure, setting their own markets, oracles, and leverage parameters. HIP-3's open interest hit $1.43 billion within months of its October 2025 launch. HIP-4, which activated on mainnet May 2, 2026, adds a new primitive entirely: fully collateralised outcome contracts that function as prediction markets, composable with the same account that holds a trader's perps and spot positions.

As covered in our Aster Code analysis, Aster launched its own version of this model on March 27, 2026. Aster Code is a permissionless API that lets external developers build custom trading interfaces on top of Aster's liquidity pool, matching engine, and privacy stack — earning on-chain fees for every trade executed through their interface, with volume and earnings tracked via the Builder Center dashboard. Aster has also established the Aster Code Ecosystem Fund, providing grants, technical support, and distribution to builders entering its ecosystem.

Aster's position in this comparison is worth noting directly: the exchange holds second place in the perpetuals market by open interest, behind Hyperliquid, with $1.26 trillion in cumulative volume. It is not a minor project pursuing Hyperliquid's playbook — it is the nearest credible challenger deploying the same distribution model from its own infrastructure.

The model in both cases is straightforward: builders create the front end, users trade through it, and the builder earns a commission on every executed trade that flows through that interface. The protocol retains its liquidity and matching engine; the builder owns the UX layer on top.

A Direct Comparison

Model	Layer	Focus	Monetisation	Customisation	Agentic Fit
Uniswap V4 Hooks	On-chain (pool level)	Innovate liquidity mechanics	Hook subscriptions, grants, or indirect value	Very high — modify pool behaviour directly	High — agent-specific callbacks, wallet delegation, automated strategies
Hyperliquid Builder Codes	Off-chain (UI/routing)	Order flow & UX ownership	Up to 10bp per fill, direct on-chain settlement	Moderate — frontend/UX, some market params	Medium — agents can use UI layer
Aster Code	Off-chain (UI/routing)	Order flow & UX ownership	On-chain fee per fill, Builder Center tracking	Moderate — interface and market access	Medium — agents can use API layer

The table makes the structural difference visible. Uniswap V4 Hooks operate at the pool level — the customisation is deep and the monetisation is indirect (ecosystem value, grants, downstream protocol revenue). Hyperliquid and Aster operate at the distribution layer — the customisation is frontend-oriented and the monetisation is direct, per-fill, and settled on-chain from day one.

Neither model is inherently superior. The right choice depends entirely on what problem a builder is actually solving.

The table makes the structural difference concrete. These two models sit on entirely different layers of the stack, so they attract different kinds of builders.

Which Model Fits Which Builder

The framing of "Hooks vs Builder Codes" implies a competition that does not really exist. These models sit on different layers of the same stack. A hook developer and a builder code developer are not competing for the same user or solving the same problem.

The strategic question for any builder is: are you trying to innovate liquidity mechanics, or are you trying to own a distribution surface?

Uniswap V4 Hooks fit builders who:

Are modifying how liquidity pools themselves behave — custom fee structures, novel AMM curves, on-chain order types
Have existing Solidity expertise and are comfortable at the smart contract layer
Are building for institutional LP customisation, quant or algo strategies that need on-chain logic
Are working on yield innovations — rehypothecation hooks, dynamic rebalancing, JIT liquidity strategies
Are building agentic systems that need to operate at the pool level rather than the UI level

Hyperliquid Builder Codes and Aster Code fit builders who:

Are building wallets, copy-trade platforms, analytics tools, trading terminals, or social trading apps
Have frontend and product expertise and want a path to direct, sustainable revenue without launching a token
Are competing on user experience and distribution as the core product — the infrastructure is someone else's problem
Are integrating perpetuals trading as a feature rather than building a trading protocol from scratch

Astarter.app is focused on the frontend builder model — a clean trading interface designed to leverage permissionless distribution rather than on-chain liquidity primitives.

The simplest filter: if the differentiation lives inside the pool contract, hooks are the tool. If the differentiation lives in the UX, the distribution channel, or the product layer on top of shared infrastructure, builder codes are the path.

There is one area of genuine overlap worth flagging: agentic applications. An AI agent operating at the pool level — rebalancing LP positions, executing conditional logic, managing delegated wallets — needs hooks. An agent acting as a trading interface — routing orders, applying strategy logic at the order level, earning fees on execution — is better served by the builder code model. The layer where the agent operates determines the model that fits.

Both architectures reflect a broader trend in DeFi's maturation: protocols increasingly function as infrastructure layers, and value accrues to the builders who own the surfaces users actually touch. The choice between them is not philosophical — it is a function of where a builder's actual expertise and product differentiation lives.

CoAgentic Dev researched and drafted this analysis. Reviewed and approved by OrionJVale. Corrections and verifiable additions via the CoAgentic contact page.

Uniswap V4 Hooks vs Hyperliquid Builder Codes: Two Philosophies of Permissionless Building