[RFC-01] Adopt a Balancer AutoRange Pool as Neverland’s Core USDC/DUST Liquidity Venue

[RFC-01] Adopt a Balancer AutoRange Pool as Neverland’s Core USDC/DUST Liquidity Venue



Summary

This proposal recommends migrating Neverland’s incentivised USDC/DUST liquidity from the existing Uniswap V2 pool to a newly deployed Balancer V3 AutoRange pool on Monad. Today, the Uniswap V2 pool creates headline liquidity, but much of that capital is not useful at the prices where DUST actually trades. The AutoRange pool is a fungible concentrated liquidity AMM that automatically recenters its price range over time without any user action, giving Neverland the capital efficiency of concentrated liquidity without the operational and game-theoretic problems that have undermined previous concentrated liquidity attempts.

The expected outcome is meaningfully deeper effective liquidity at the trading price, materially lower slippage on routine trades, more productive LP incentives and fees per dollar spent, and a more resilient DUST price chart through the recurring epoch sell pressure cycle.

The migration will be done as a hard cutover and nUSDC LP incentives which are currently distributed via Merkl on V2 LP positions will be redirected to holders of the AutoRange pool’s BPT. Neverland’s existing protocol-owned liquidity, currently held in a Uniswap V3 position, will be withdrawn and redeployed as a passive Uniswap V2 backstop position alongside the new AutoRange venue. The proposed initial parameters, suggested by the Balancer team, are a price ratio of 4.0, a centeredness margin of 5%, and a price shift exponent of 2%.

Problem Statement

Neverland currently incentivises liquidity in a Uniswap V2 USDC/DUST pool that holds approximately $835k worth of DUST and USDC. V2 spreads this capital uniformly along the entire constant-product price curve, which means that the overwhelming majority of it sits at prices far from where DUST actually trades. The effective depth at the spot price is a small fraction of the headline TVL, which means Neverland is currently incentivising a large amount of liquidity that is not meaningfully active where DUST actually trades. Traders therefore experience much worse slippage than $835k of liquidity should imply. The migration fixes this by making the same incentive budget support liquidity that is actually useful at the trading price, instead of spread passively across the entire V2 curve.

This is a particular problem given Neverland’s flow profile. Locked DUST positions mature on a 7-day epoch cadence, and a meaningful concentration of sell pressure occurs in the roughly ±1 day window around each epoch end. On a V2 pool that prices this flow inefficiently, the recurring imbalance translates directly into a recurring price dump on the chart. Each epoch produces a visible downward move that is larger than the underlying selling actually warrants, simply because the available depth at the trading price is relatively thin. This is bad for DUST holders, bad for sentiment, and creates an attractive setup for predatory positioning ahead of each epoch end.

Previous attempts to fix this with concentrated liquidity have failed for a different reason. Some LPers converged on ultra-narrow ranges to maximise fee and incentive capture, and were then forced to rebalance constantly as the price moved, producing rebalancing cascades that fragmented liquidity and pushed most passive LPers out of range. The incentive program ended up subsidising a small group of active managers who could withstand this churn, rather than building the durable, broadly-held depth that Neverland actually needs. The structure punished exactly the kind of LP the protocol most wants to attract: passive, durable liquidity providers who want exposure to USDC/DUST without competing in a range-management game against active LPs.

The Balancer AutoRange pool resolves both sides of this problem. It delivers the capital efficiency of concentrated liquidity, which improves the price chart by absorbing epoch sell pressure with much less price impact, while encoding the range management as a deterministic on-chain mechanism with parameters fixed at deployment. All LPs share a single range and hold a single fungible BPT, and the pool itself handles range adjustment automatically. There is no manual range to set, no manual rebalancing, and no game to win against other LPs. Volatility no longer forces individual LP action.

Low Level Details

Capital Efficiency and Impact on DUST Price Stability

The most important consequence of this migration is on the DUST price itself. With the same amount of liquidity concentrated into a ±4x range around the trading price rather than spread along the entire price curve, the effective depth that any given trade actually sees is multiples larger than it is today. Concretely, this means three things:

First, routine swaps move the price less. The same $10k buy or sell that produces a visible candle on the V2 chart today will produce a much smaller move on the AutoRange pool. The DUST price chart should become quieter and more orderly through normal trading activity.

Second, the recurring epoch sell pressure becomes substantially more absorbable. The ±1 day surge of post-epoch selling currently functions as a predictable downward catalyst because the pool’s response to that flow is steep. In a concentrated environment, that same flow lands into far more depth at the trading price and produces a correspondingly smaller move. Over time, this should compress the magnitude of the recurring epoch dip, make the post-epoch reversion cleaner, and reduce the incentive for actors to position predatorily ahead of each epoch end.

Third, the asymmetry of the benefit is favourable. Because Neverland’s flow is biased toward predictable downside pressure, the dampening effect of concentrated liquidity is focused on exactly the moves we most want to dampen. Consequently, buy pressure also moves the price less, which is a real cost in directional rallies, but the trade against a more stable baseline price chart and a more resilient response to known sell catalysts is the right one for Neverland’s current stage, while we build out more revenue streams and meaningful utility to drive organic demand for the DUST token.

LP Economics and Fee Flexibility

The migration also improves the fee and incentive surface for LPs. The current V2 pool is locked into a flat fee model, regardless of DUST’s volatility, flow profile, or liquidity needs. A Balancer AutoRange pool gives Neverland more flexibility to align LP compensation with the actual market structure of DUST.

Fees, depth, and incentives become better aligned. LP capital sits closer to the trading price, routed flow interacts with more useful liquidity and the incentive program rewards positions that actually improve execution instead of rewarding idle liquidity across unused parts of the curve.

AutoRange Pool Architecture

A Balancer AutoRange pool concentrates liquidity inside a defined price range and uses the same in-range swap math as a UniV3 position. The novelty is that the pool maintains its own range and shifts it over time in response to where the market is actually trading. When the pool is near the middle of its range, it behaves as a static concentrated position. When trading flow pushes the pool’s balances meaningfully out of balance, the pool begins migrating its range over time to follow the market. LPs hold a single fungible BPT and do not manage individual positions. Adds and removes are proportional. No external operator, ALM, or rebalancing actor is involved.

Initial Pool Parameters

The Balancer team has suggested an initial price ratio of 4.0, a centeredness margin of 5%, and a daily price shift exponent of 2%. These settings prioritise pool stability over rapid range adaptation, which is the appropriate posture for a pool that must absorb a recurring, mean-reverting flow cycle every 7 days.

The ±4x range gives the pool meaningful headroom to absorb normal price movement without needing to chase it. The low centeredness margin means the pool sits still through ordinary epoch wobble rather than reflexively moving its quoted range every time a few large trades come through; the epoch-end imbalance is mean-reverting in character (subsequent buy interest, two-way flow across the following days), so allowing the pool to absorb it within the existing range is preferable to shifting the range itself in response to flow that does not represent a sustained directional move. The conservative shift exponent ensures that when the pool does need to track a sustained directional move, it does so gently rather than in jumps.

The centeredness margin and the price shift exponent are admin-mutable post-deployment and can be tuned in the future as we observe real behaviour. The price range bounds are fixed at deployment.

Post-Migration Liquidity Structure

The Balancer AutoRange pool becomes the core incentivised liquidity venue. Aggregator routing should naturally prefer it on size because of the concentrated depth advantage.

The Uniswap V2 pool remains live as a passive backstop. Neverland’s existing protocol-owned liquidity, currently held in a Uniswap V3 position, will be withdrawn and redeployed into this V2 backstop. The V2 pool is not incentivised after migration. It exists as a non-Balancer fallback that ensures DUST remains routable through V2-only paths and provides redundancy in the unlikely event of an issue with the AutoRange venue.

Incentive Program Migration

The nUSDC incentive program continues with the same budget and the same Merkl distribution infrastructure. The key change is the target: rewards accrue to holders of the AutoRange pool’s BPT rather than to LPs of the V2 pool. The V2 Merkl campaign will be ended in the same coordinated action that begins the new AutoRange campaign. We do not propose dual incentivisation, because splitting an already modest TVL across two simultaneously incentivised venues would dilute the signal to LPers about where Neverland wants liquidity to sit.

The exact incentive budget is out of scope for this proposal and will be adjusted at the discretion of the team once the pool is live and baseline TVL response can be observed.

Security Assessment

The AutoRange pool has been the subject of two independent security reviews for which formal reports are available and linked in the references. Balancer has additionally communicated that the pool has been subjected to further AI-driven security analysis through FailSafe, Octane, and another provider, although formal reports from these additional reviews were not made available for this RFC.

The audited commit contained no critical, high, or medium severity findings across the two reviews for which reports are available. All low-severity findings identified by Cantina were fixed by Balancer. The remaining residual risks are real but specific, and the proposed parameter choices and operational posture (in particular the conservative price shift exponent, and the intention to make minimal use of admin-side price ratio updates) address them directly.

Residual Risk Considerations

The AutoRange pool is a relatively new pool type. Although well audited and in production use across Balancer V3 deployments, it has less production track record than V2-style or static concentrated designs. The conservative parameter selection and the V2 backstop are the mitigations for this.

A sustained directional price move in DUST would draw the pool out of range and trigger gradual repricing. At a 2% shift exponent, the pool’s catch-up is intentionally slow, which is good for stability but means that during a strong sustained trend the pool may continue quoting prices that lag the market-clearing level for an extended period. The relevant mitigations are the built-in gradual shift mechanism, the parallel V2 backstop pool which will exhibit different price dynamics under the same flow and create some arbitrage rebalancing, the ability of organic buy-side flow to enter at depressed prices, and the ability to tune the shift exponent or centeredness margin in genuinely extraordinary conditions.

Several admin-side controls (the centeredness margin, the daily price shift exponent, and the price ratio) carry MEV implications when used, particularly the price ratio update. We do not anticipate routine use of these controls, and the operational policy around them should be specified before deployment.

Alternatives Considered

Status quo (continue incentivising the V2 pool). Rejected. Capital inefficiency at the trading price is the single largest problem with the current setup, and it translates directly into a worse DUST price chart through the recurring epoch sell cycle. The status quo also makes both incentive and user capital inefficient. Neverland pays for headline liquidity, but only a small portion of that liquidity improves execution at the current DUST price. Users commit capital to the pool, but much of that capital does not translate proportionally into better execution, stronger fee productivity, or more efficient incentive spent..

Plain Uniswap V3 or V4 concentrated pool with Merkl incentives. Rejected based on direct prior experience. DUST volatility caused LPs to gravitate to ultra-narrow ranges and rebalance constantly, producing rebalancing cascades and pushing most passive LPs out of range. The result was incentive capture by a small group of active managers rather than durable broad-based depth.

Balancer Weighted Pool or Stable Pool. Considered. Both are determined as the wrong shape for the asset. DUST is not pegged, so a Stable Pool is inappropriate. A Weighted Pool is fundamentally V2-style math with adjustable weights and does not solve the capital efficiency problem.

Gyro 2-CLP. Considered. Gyro pools share the virtual-balance mechanism that underlies the AutoRange pool but lack the automatic range-shifting behaviour.

Open Questions

  1. Migration communications.
    How long should the notice period be given to existing V2 LPers?

  2. Monitoring and reporting cadence.
    What metrics are reported back to governance after migration (effective depth, realised slippage per epoch, centeredness over time, LP retention), on what cadence, and what would trigger a parameter tuning proposal?

  3. Overlooked areas.
    Are there any areas within the RFC that are overlooked, not mentioned, or require further clarification?

Closing Statement

The case for this migration is primarily a case about the DUST price chart. The current V2 pool absorbs Neverland’s recurring epoch sell pressure inefficiently, producing predictable downward moves that are larger than the underlying flow warrants and that create a self-reinforcing setup for predatory positioning. Concentrated liquidity fixes this at the structural level by stacking more depth at the trading price. The Balancer AutoRange pool delivers that benefit in a form that does not collapse under DUST’s volatility the way previous concentrated liquidity attempts did, because it removes the need for LPs to defend their own range while it benefits Neverland’s existing incentives structure for better and more useful liquidity and stronger LP economics without turning LP participation into an active range-management competition.

The proposed parameters are conservative and well aligned with Neverland’s flow profile. The migration plan is a clean cutover with a V2 backstop preserved for redundancy. The pool type has been independently audited with no critical, high, or medium severity findings.

We invite community feedback on the topic, before this proposal progresses toward a Neverland Governance Vote.



References

This is a wall to read, Hyper, but my initial thought was: as long as the team thinks it is secure enough, go for it!
Never liked V2 too much to begin with, and I remember it was always billed as a temp solution until CLAMM or something better comes around. Let’s go!

7 Likes

I absolutely love this idea! That’s a pretty cool feature of their newer pools!

7 Likes

Yeah reCLAMM has been renamed to AutoRange Pool.

6 Likes

I’ve reviewed the audits around this pool and I’m confident this is both a safe transition and a big improvement for Neverland overall. It addresses a lot if not all of the current inefficiencies around DUST liquidity and technically the Balancer’s tech on this one checks out.

So I do support this RFC from both a technical and incentive-design perspective.

Right now the V2 pool gives us what I see as fake liquidity depth as only a fraction of that liquidity is actually useful where trading activity happens. Moving core incentives toward a Balancer AutoRange BPT allows the same incentive budget to create materially deeper effective liquidity around spot pricing, better execution quality for traders, and less unnecessary price impact during normal trading activity, epoch rotations, and reward-related flows. Also DUST doesn’t have to trade at low trading fee ranges, more fees for Mermaids is also a very nice and positive plus.

Directionally I strongly believe this is the right move.

10 Likes

As someone who holds a large LP position, I am 100% for this.

Regarding “How long should the notice period be given to existing V2 LPers”, I would say the sooner the better. I would assume most LPers check merkl on a daily basis so a few days (at most a full epoch) seems more than enough.

7 Likes

I don’t get all technical stuff, vit it sounds clever to me

4 Likes

im agree with the deal

3 Likes

The execution can be simple. At the next epoch, when this proposal gets finalized, we can simply split 75% of the rewards to the Balancer pool right away. Naturally, most people will migrate, so for this week, within a couple of days, the pools will be equalized on their APR value, while people not moving fast will have a full week with rewards to read the news and migrate.

Frontend execution will be similar, to make sure that there is enough notice, banners etc.

5 Likes

V2 pools are passive by nature, so I imagine despite best efforts there will still be some people who will find out a month later. Yet, I think the benefits are too great to just sit and wait. 1 epoch transition time should be fine.

4 Likes

Seems to make sense if security checks out. Solid

4 Likes

Speaking on behalf of the Balancer team, it is genuinely an honor to see the migration to an AutoRange pool framed as Neverland’s first RFC.

We are and will keep actively monitoring pool behavior post-deployment, in close contact with the Neverland core team. If observed behavior suggests parameters should be tuned, that conversation will happen openly.

Separately, we are also very glad that Balancer currently holds the largest DEX pool on Monad, with 100% of that liquidity routed into Neverland’s lending market. The depth of the existing integration is part of why this migration is a natural next step for both sides.

Looking forward on all that is yet to come!

7 Likes

Let’s do this already. DUST is central to everything we do so I support this change. When to vote?

4 Likes

Fully support this proposal and the team behind it. Moving from V2 to the Balancer AutoRange pool feels like the right move to improve real liquidity depth, reduce epoch-related volatility, and make incentives far more efficient for both traders and LPs. The design also solves many of the issues traditional concentrated liquidity created for passive LPs.

3 Likes

Thank you for the time to write here. I think everyone is convinced the AutoRange pool is more efficient and the only real concern is safety. Cata seems to think the code is secure enough (and we have come to know him as a stickler for secutiry), but what is your personal take on this?

4 Likes

I would like to have the benefits of having concentrated liquidity levels automatically adjusting to price levels.

However at this time security is more pressing that almost all other things, even though passing 2 independent security reviews. I fully remember other who were hacked despite having 3rd party security audits. I hope there is an inhouse effort to check further, and cost could be mitigated by utilizing trained AI wholly managed by the team.

2 Likes

Can the Balancer team disclose their approach to private key security, multi-sig processes, use of dedicated signing devices, and timelocks? Uniswap is tried and true. Its never been hacked or exploited. Moving significant funds to Balancer is a giant leap of faith. Some LP’ers will be willing to take that leap. Some will not unless there are strong security assurances.

2 Likes

As big LP position holder.

The question about admin key security is the right one, but it should be directed at Neverland rather than Balancer, Balancer provides the infrastructure, but who holds admin rights to this specific pool is a Neverland governance question. More concretely: the RFC itself notes that “the operational policy around [admin-side controls] should be specified before deployment” but leaves it open. Before this moves to a vote, it would be good to see that policy actually written down: multisig threshold, signing setup, and critically, under what conditions the team would consider using the price ratio update (which the docs flag as carrying MEV implications). “We don’t plan to use it routinely” is not the same as a committed policy.

3 Likes

I am generally in favour of migrating the USDC/DUST LP to Balancer.
As several people have expressed concern, provided Balancer’s security is adequate, I believe this is a sound strategic move.
I would just like to clarify one point: I believe we previously migrated the USDC/DUST LP position from Uniswap to Balancer and then immediately moved it back to Uniswap; is it correct to assume that the issues that arose on that occasion have now been resolved?

4 Likes

Neverland has no privileged role on it. We can’t move the range, can’t pause it, can’t touch a cent of LP funds. On fund and key control we’re in the same position as any other LP. The parameter controls (centeredness margin, shift exponent, price ratio) sit behind Balancer’s permission layer, the same one governing every other Balancer V3 pool. We can request adjustments through coordination with Balancer, but we don’t hold the keys to execute them ourselves.

And yeah, how Balancer operationally handles those keys is a fair thing for this thread to dig into.

These are valid concerns, and I’m glad we’re hashing this out in the open here. This is what makes Governance great.

We’ll make sure to redirect the operational security questions directly to the Balancer team so they can provide accurate answers regarding their signer setup, multisig operational procedures, timelocks, and key management policies rather than us speculating on their behalf.

That said, I’ll give my personal view on the broader security discussion.

The existence of past incidents alone is not a meaningful security model, neither to condemn a protocol nor blindly trust another. If the standard is “a protocol had an exploit before therefore it should never be trusted again”, then most major DeFi infrastructure would immediately become unusable, including protocols people currently trust with billions of dollars today.

Uniswap itself has had vulnerabilities, ecosystem exploits, frontend compromises around integrations, and critical edge cases discovered over the years. The same is true for Curve, Balancer, bridges, lending protocols, and practically every battle-tested protocol category in DeFi.

Even our own lending instance of choice, “the most secure lending framework in DeFi”, has had vulnerabilities we’ve caught and handled. That does not suddenly mean Aave is insecure or that every protocol built on top of it should be abandoned overnight.

The reason Neverland is secure today is because we are paranoid. The moment we see something that could plausibly have been a true positive and exploitable vulnerability, we freeze immediately and ask questions later, even though “this is Aave engine, the greatest of all”.

I’ve seen the same type of paranoia recently from the Balancer team with reCLAMM. They halted pools proactively and treated uncertainty itself as a reason to slow down and investigate rather than gambling on optimism. In my view, that mindset is one of the healthiest starting points a protocol can have in DeFi if it wants good odds of surviving multiple cycles without catastrophic incidents.

I’m not being naive, everything can happen at any point in time. Balancer can get rekt, Aave can get rekt, everybody can get rekt. Some incidents can be louder than others and have a much bigger impact. We’ve seen that recently in DeFi. I’m just saying that security is not binary and it’s not determined by whether a protocol has ever experienced an incident in its lifetime, everybody daring to stick around has. Protocols without incidents are protocols which didn’t pivot enough in the space yet to have a few war medals and wounds. The true question is:

  • “What failed?”
  • “Was it architectural, operational, frontend, governance, dependency-related or integration-related?”
  • “How was it mitigated afterwards?”
  • “What operational posture exists today?”
  • “What are the tradeoffs versus the alternatives?”

Yeah, answers on these topics would be highly beneficial during our decision-making leading to a vote.

From my POV, the current Uniswap V2 setup has real structural inefficiencies that directly affect DUST market behavior. This is not “The price is bad because we’re in this bad inefficient pool”. The market ultimately dictates everything no matter what you’re calling a home for your liquidity, but it’s not mutually exclusive to the fact that the high inefficiencies of Uniswap V2 are having us die on every hill every single time somebody simply offloads a $5K position on an almost $1M pool, and that shouldn’t be the case for a protocol that is dedicating projected more than $1M dollars a year in incentives to build their governance token liquidity.

Audits alone also do not magically create safety, this is true. An audit is a snapshot review which can be wrong at any time production drifts enough and almost never reflects operational risk. Going to Balancer’s pool doesn’t delete or help with risk, it takes today’s inefficiencies out of the picture, the ones bleeding us out on every trade, inefficiencies that we can’t and have no business carrying ourselves with an in-house solution. We don’t have the expertise to manage liquidity pools at this level and that would be the real experiment here, AI-supported or not.

I’ll be blunt. Nothing can ever be absolutely safe, not DeFi, not TradFi, nobody. Every big giant alive today has had incidents to some degree. Some were louder than others, some managed to get back up and keep moving forward.

A respectable Italian philosopher once said “It’s about how hard you can get hit and keep moving forward. How much you can take and keep moving forward. That’s how winning is done!” :sweat_smile: and that is why, after all that, I’m open to keep working alongside Balancer. We share the same paranoia, they’ve been to war, got wounded, and came back alive with more experience this time.

8 Likes