Velocity - Liquidity Mining
Velocity is Surf’s AI execution engine for Concentrated Liquidity Market Maker (CLMM) pools on decentralised exchanges. It is designed to earn fees efficiently, adapt to changing market conditions, and protect capital through deterministic risk rules, all while staying non-custodial.
Velocity is the same execution class we use internally for professional liquidity operations. Over time, it becomes a primary distribution path for Surf across retail, DEX partnerships, and institutions.
What Velocity Does?
Velocity continuously manages a CLMM liquidity position by doing three things:
Defines the optimal liquidity placement based on real-time market conditions.
Adjusts liquidity dynamically when conditions change enough to justify a move.
Enforces protection by architecture through the Guardian Layer so unsafe actions never execute.
In practice, this means the agent is constantly deciding:
Where liquidity should be concentrated to maximise fee capture
How wide or narrow liquidity coverage should be to match the current regime
When to rebalance and when to stay put
How to maintain exposure limits and execution safety even during volatility spikes
This is not yield chasing. It is continuous liquidity optimisation inside hard constraints.
Strategy Inputs and Real-Time Signals
Every decision cycle uses a live view of the pool and the market, including:
Spot price behaviour and micro structure
Volatility regime and regime transitions
Trend strength and stability
Volume intensity and distribution over time
Liquidity depth and utilisation near the active price
Fee efficiency of the current liquidity placement
Execution cost estimates (slippage, price impact, gas)
Stress signals and anomaly detection
Cooldown logic to prevent over-trading
Each input has multiple possible states. When combined, the optimisation space becomes very large.
Velocity runs simulations across more than one million possible parameter combinations per evaluation window, then selects the best risk-adjusted outcome that satisfies the Guardian rules.
Multi-Band Liquidity Management
Velocity uses a multi-band liquidity structure that adapts to the market regime.
The concept is simple:
A portion of the capital is positioned for high fee capture near the statistically dominant price region.
Other portions of capital is positioned for protection and coverage when price expands, volatility rises, or regimes shift.
The agent continuously adjusts:
Placement
Coverage width
Capital distribution across bands
Rebalance timing
This is how Velocity balances fee generation with protection in real markets.
Simulation Before Execution
Before any change is executed, the AI planner simulates candidate configurations across multiple forward paths.
Each candidate is evaluated for:
Expected fee capture under different regimes
Impermanent loss sensitivity
Risk and drawdown behaviour
Execution feasibility at current liquidity depth
Exit and unwind safety under stress
Only candidates that pass deterministic constraints remain eligible. If nothing passes, the action is rejected and the position stays unchanged.
Guardian Layer Protection
Velocity is secured by Surf’s execution standard.
The AI can propose actions, but it cannot move capital freely. Every rebalance is filtered by the Guardian Layer, enforcing:
Allowlisted DEXs and pools
Exposure caps per asset and venue
Maximum reallocation limits
Slippage and price-impact bounds
Volatility and anomaly circuit breakers
Cooldown and rate limits
Emergency unwind paths
This architecture ensures Velocity behaves like a controlled execution system, not a discretionary bot.
Retail Deployment Model
Velocity will be offered to retail users through a simple vault experience:
Users deposit into their own non-custodial Smart Vault.
Funds flow from each user vault into a single shared CLMM vault for that market.
Surf’s AI manages the CLMM position inside the shared vault.
Fees and incentives are distributed back proportionally to users.
As the shared vault grows:
Liquidity depth improves
Fee capture scales
Execution efficiency increases
APY becomes more stable
This model is intentionally designed to build sticky TVL by turning liquidity provision into a savings-style experience.
Why Velocity Is a Moat for Surf
Velocity is a moat because it combines:
Real-time optimisation across a million-state parameter space
Simulation-driven decisioning rather than heuristics
Deterministic risk enforcement via the Guardian Layer
Full-stack ownership from signals to execution
Most CLMM vaults depend on static ranges, manual operators, or simple rule sets. Velocity is built as an execution system that can run continuously, safely, and at scale.
Primary Use Cases
Velocity is a distribution engine because it solves liquidity for multiple segments:
DEXs that need deep, sticky liquidity in core pools
Market makers that want automated, rule-constrained execution
Neo-banks integrating non-custodial yield and on-chain liquidity rails
Hedge funds and professional capital deploying large tickets with hard risk boundaries
Ecosystems and partners using Velocity as a native liquidity growth layer
Velocity is one of the clearest paths for Surf to serve institutions, because the volumes and fee potential scale directly with capital depth, and the risk standard is enforced by architecture.
Last updated