How to think about asset allocation, veBAL tokenomics, and AMMs when building custom liquidity pools

Okay, so check this out—creating a custom liquidity pool feels a lot like rearranging furniture in a new apartment. You can make it cozy, efficient, or weirdly fragile. My first time setting up a multi-token pool on Balancer I learned that asset choice, weights, and the tokenomics of the protocol you’re using matter way more than the flashy APY number. I’m biased, but I’ve seen nice pools fall apart because someone chased yield without thinking about composition. Somethin’ to keep in mind: fees, vol, and governance incentives all tug at your allocation in different directions.

Start with a simple intuition: you’re building a tiny market that other people will trade against. If trades are frequent and large relative to liquidity, you earn fees. If the assets diverge in price, you face impermanent loss. Those two forces — fee generation and divergence risk — are the twin levers for pool design. Initially I thought you could maximize fees by adding volatile pairs and low liquidity; nope. That approach gets you lots of trades, sure, but also scary IL and the kind of churn that burns LPs.

So how do you decide allocation? On one hand, you want exposure to expected volatility because volatility means opportunity for fees. On the other hand, too much divergence and your LP share evaporates when prices revert. A good pattern: blend assets with complementary characteristics. Use stable-stable pairs (or pools with higher amplification) for fee capture on stablecoin activity. Use diverse weighted pools for long-term holders who want exposure to a basket without frequent rebalancing. And place a small portion into higher-vol pools if you’re aiming to harvest swap fees.

Balancing weights, fees, and pool type

Weighted pools on Balancer let you design exposure directly: 50/50, 80/20, or more exotic splits. That flexibility is powerful. Set a heavier weight on the less volatile token to reduce IL, or do equal weights if you want natural rebalancing. Stable pools (with amplification) drastically reduce slippage between pegged assets, which makes them a go-to for stablecoin LPs that just want almost risk-free fee income. But they won’t capture the same fee magnitude as volatile pairs unless there’s tons of stablecoin trade volume.

Fees are another design lever. Higher fees deter arbitrageurs and casual swaps, but they increase per-swap revenue. Lower fees increase volume but can leave you undercompensated for IL. My instinct says split your treasury: some pools optimized for steady, low-risk income (low fees, stable assets), and some risk-on pools with higher fees and a smaller capital commitment. That way you don’t blow up on one wrong bet.

Also—practical note—when launching a new pool you control the initial price. That matters. If the initial price is off-market, arbitrage will suck out value until it’s fixed. So seed thoughtfully. Oh, and gas costs: creating and seeding pools isn’t free, so batch your moves when Ethereum is sane, or use a chain with cheaper gas if that’s an option.

veBAL tokenomics: aligning incentives and capturing value

veBAL (vote-escrowed BAL) is Balancer’s mechanism to convert BAL holders into longer-term stewards of the protocol. Lock BAL to get veBAL, and veBAL grants you voting power over gauge weights and a share of protocol fee distribution. That’s the core incentive loop: locking reduces liquid supply, aligns incentives toward liquidity that benefits the protocol, and gives locked holders influence over where emissions go. Initially I thought locking was just for governance flex—actually, the real benefit is economic for LPs because gauges direct emissions toward pools you care about.

Here’s the lean part—veBAL scarcity creates competition for emissions. If your pool attracts veBAL-weighted votes (or bribes), it will receive a bigger slice of BAL emissions. That boosts yields for LPs and can offset IL. But there’s a governance caveat: concentrated power among big lockers can skew emissions toward their preferred pools. On one hand you get efficient capital directed to productive pools; though actually, that can also lead to short-term gaming. Be mindful of the social layer—who holds the veBAL and why.

Practically, when designing pools, consider how attractive they are to vote-escrowed voters: stable pools with predictable fees vs. volatile pools with high APY but high risk. If you can capture some veBAL votes (or design a pool that naturally acquires them), you materially raise long-term returns. I won’t pretend it’s simple—veBAL dynamics change with governance proposals—but the principle stands: align pool incentives with veBAL flows.

Automated Market Makers (AMMs): routing, arbitrage, and utility

AMMs like Balancer are more than a matching engine. They’re programmable marketplaces. Balancer’s Vault and multi-token pools allow more granular routing and lower total capital needs for traders because you can route across many pools with a single swap. That smart order routing (SOR) reduces slippage for users, which in turn can increase volume for your pool if it sits on efficient routes.

Remember arbitrage is your friend and foe. Arbitrage keeps prices in sync with external markets but it also extracts value from LPs by realigning positions after price moves. Good pool design anticipates arbitrage and either prices in the expected cost or creates fee capture that exceeds it. For instance, if you design a pool that is often on a trader’s optimized route, you’ll get consistent fee income that helps cover IL.

One tactical tip: watch the exit and entry patterns. Pools with tokens that have concentrated off-chain liquidity (like listings on a centralized exchange) tend to see heavier arbitrage, so you may underperform naive APY calculators. Diversify pool types across your suite so no single failure mode kills your overall strategy.

Risk checklist before you deploy capital

I’ll be honest—this part bugs me because people gloss over it.

• Smart contract risk: Audits matter. Balancer’s core contracts are battle-tested but new pool contracts or integrations might not be.
• Impermanent loss: Model it. Use historical vol, not wishful thinking.
• Governance risk: veBAL centralization can shift emissions overnight.
• Liquidity fragmentation: Too many forks of the same pool dilute fees.
• Regulatory and fiat rails: Not technical but impactful over the long run.

One more: psychological risk. Pools that look great in a bull market can collapse in a fast unwind. Plan for stress scenarios.

Operational checklist for launching a Balancer pool

Quick practical steps—do these before clicking “create.”

• Pick tokens and weights based on correlation and desired exposure.
• Choose pool type: weighted, stable, or token-manager-driven (dynamic configs).
• Set fee tier mindful of target volume vs IL.
• Seed at market prices and in sufficient depth to attract natural routing.
• Consider incentives: gauge votes, bribes, or direct reward programs to bootstrap liquidity.
• Monitor and iterate—reweight if the market regime changes.

If you want to tinker directly or check out the pool types and docs, head over to balancer for the platform primitives and developer resources. The site is a handy place to see live pools, gauge weights, and how veBAL allocations shift over time.