Maverickprotocol
Maverickprotocol LP positions can start with one token and change composition through trading
Maverickprotocol lets liquidity providers (LPs) fund some automated market maker (AMM) positions with one token, while trading can change their asset mix. Single-sided funding describes what enters the pool; ongoing exposure follows the position's distribution, price location, and liquidity mode. Directional strategies can keep a position mostly or entirely exposed to one pool asset under suitable price movements. A reversal can bring that liquidity into trades and convert it into the other asset. The practical requirement is compatibility between those possible holdings and the exposure that the provider accepts. Deposit composition, position ownership, and fee earnings each describe a different part of that choice.
Single-Token Funding and the Deposit Mix
Single-token funding is available when the chosen distribution requires only one pool asset at the prevailing price. Bins outside the active price range hold one side of the pair. The active bin generally contains both assets, so including it can require both tokens. The deposit preview computes amounts from the selected allocation; choosing a directional mode alone doesn't establish which tokens must fund it.
The wallet must hold the token balances required by that allocation on the pool's network. An allocation requiring both assets is incompatible with a wallet containing only one asset unless its funding changes.
Personal Claims Within Shared Pools
A personal position records an LP's allocation to specific liquidity bins. Other LPs may use different bins and modes inside the same pool. Pool-wide reserves can include other providers' holdings. The relevant quantities are the token balances attributable to the selected position. Its distribution identifies which price ranges can trade those assets, and its ownership record identifies who can withdraw them. The same token pair can support positions with materially different holdings.
Why Can a Single-Token Position Acquire the Other Asset?
A single-token LP position acquires the other asset when traders swap against its supplied liquidity. Providing liquidity permits the AMM to sell deposited tokens within the position's price ranges. Trades replace the outgoing asset with the incoming asset. A bin may therefore contain mixed inventory while price passes through it, then hold only the counterasset once trading fully crosses that range. The initial deposit remains relevant for measuring performance, while current balances describe present exposure.
Liquidity movement and token conversion are different mechanisms. A movement mode relocates liquidity under its rules; swaps exchange the assets. Automatic repositioning doesn't reserve the original token quantities.
Directional Exposure and Price Orientation
Directional mode names describe movements along a pool's price axis, expressed as a relative price between its assets. Mode Right follows increases in the base asset's price relative to the quote asset; Mode Left follows decreases. An LP can fund the bin below price with the quote asset while using Mode Right. The price being followed and the asset being held are therefore different concepts. Single-direction liquidity strategies can keep an LP mostly or entirely exposed to one asset in a pool. The supplied token, its bin location, and subsequent trades determine what that exposure consists of.
A Single-Token Budget Before and After Trading
In this hypothetical example, an LP holds only the quote asset in a selected pool, accepts possible conversion, and later encounters a falling pool price. The immediate constraint is funding: an allocation that includes the mixed active bin requires both assets. The single-token wallet can't fund that allocation as shown.
Before committing, the LP selects only the Mode Right bin immediately below the active bin and reviews the resulting token amounts. The one-token preview fits the available balance, so the LP funds that distribution. Suppose subsequent trades push price left through the entire funded bin. In this example, the pool's time-weighted average price also moves left, so Mode Right leaves the liquidity in place. Traders supply the base asset to the pool and receive quote tokens from the funded bin.
The position now holds the base asset even though the deposit used only the quote asset. That observation fits the hypothetical LP's willingness to accept conversion. A requirement to keep the quote asset continuously would instead favor holding it outside the pool. If the LP chooses to exit, removal releases the balances then owned by the position; it doesn't unwind the trades or restore the original deposit.
Trading Fees and Token Inventory
Trading fees accrue according to the LP's share of liquidity used in the active price range. Liquidity sitting away from that range earns no swap fees while it remains unused. A position can therefore be largely exposed to one token while spending time outside active trading. Concentration and turnover influence fee earnings through actual swaps.
Earned pool fees compound into liquidity reserves. V2 bin LP balances measure ownership units, and the assets represented by those units can change. A steady LP-unit balance doesn't imply steady token quantities. Fee accumulation and trading both affect the position's token inventory.
Pool Compatibility Before Allocation
Pool compatibility depends on the actual V2 pool's configuration, including its token contracts, network, bin spacing, and supported liquidity modes. V2 pools declare which modes they enable; protocol-wide support doesn't imply that every pool offers each mode. Different fee settings and bin widths can also identify distinct pools for the same pair. Movement modes use a time-weighted average price (TWAP), which can differ from the instantaneous pool price. Consequently, a chart's latest price alone doesn't establish where moving liquidity must already be located. The relevant configuration belongs to the pool that holds the position.
A pool's static liquidity also supports price discovery and arbitrage. When static liquidity is insufficient, price manipulation can distort the TWAP and expose movement-mode positions to unwanted repositioning. That can make their tokens available for trades at unfavorable prices.
Position Receipts and Control
V2 liquidity managed through a Maverick Position NFT belongs to the wallet that holds that non-fungible token. The ERC-721 record controls access to the associated liquidity, whose composition continues to follow the pool's trading and positioning rules.
Transferring or selling the NFT hands that liquidity control to the recipient. The assets needn't appear as ordinary token balances in the owner's wallet to form part of their holdings. A direct V2 pool position has different ownership behavior: it is nontransferable, and its recipient controls removal.
The V2
unSafeBurn
function burns the position NFT without removing its liquidity. After that burn, the linked liquidity can no longer be withdrawn.
Do Trading Fees Prove That an LP Position Beat Holding?
Trading fees don't prove that a position beat holding the original tokens outside the AMM. Impermanent loss measures the difference between an LP position's value and the value of retaining its original deposit. Both sides need the same valuation time and reference prices. A higher token count alone can't settle the comparison when the assets and exchange rates have changed. Network costs for adding or removing liquidity also affect an LP's net outcome.
Mode Both adds a distinct inventory risk because repositioning follows price in both directions. Repeated reversals can cause the position to buy high and sell low, depleting its reserves. Maverick AMM calls this permanent loss. Merely returning to an earlier market price doesn't automatically reconstruct reserves lost through those completed exchanges. Fees may offset some losses, yet their presence alone says nothing about whether the offset was sufficient.
Boosted Positions and Preset Exposure
Boosted Positions offer a preset liquidity configuration that other LPs can share. Their ERC-20 LP tokens represent a proportional claim on that position's underlying pool assets. The preset distribution and mode still govern which assets can trade and where liquidity sits on the price curve. An incentive token doesn't replace that underlying exposure. In V2, eligibility for a Boosted Position's incentive rewards requires staking its LP tokens in the relevant reward contract. Staking LP shares for incentives is a separate activity from MAV staking for governance.
Static Ranges and the Boundary of Conversion
Static liquidity can serve a different exposure goal: offering an asset for conversion within chosen price ranges. A single static bin can approximate a limit order because traders only access its inventory when price reaches that bin. Spreading the allocation across selected bins changes where conversion can take place.
A completed conversion doesn't close an LP position automatically. If the converted inventory stays available and price returns, trades can exchange it back. Removing liquidity ends that selected exposure to further pool swaps; it doesn't reverse earlier conversions.
A spot swap exchanges tokens at an obtainable execution price, subject to its output limits. LP-based conversion also entails the network costs of adding and removing liquidity, which belong alongside earned fees when comparing those paths.
Maverickprotocol questions, answered
Can a V2 Position NFT Hold Liquidity Across Multiple Pools?
A V2 position NFT can represent liquidity in multiple pools. Each pool retains its own pair and bin allocations, so the NFT doesn't turn those holdings into one common token balance. Exposure still has to be understood pool by pool.
How Can I Estimate the Tokens Required for a V2 Deposit?
MaverickV2Quoter's calculateAddLiquidity function estimates the token A and token B amounts for specified deposit parameters in a selected pool. It also returns an approximate gas estimate. The quoted token requirements describe that configuration at the evaluated pool state; they aren't a record of tokens already deposited.
Is Approving a Pool Token Enough to Create an LP Position?
Approving a token grants a spending permission; it doesn't deposit liquidity or create ownership of a funded position. The deposit transaction must also succeed. When that transaction requires allowances for both pool tokens, approving one token doesn't provide the separate allowance for the other.
Can I Remove Only a Fraction of a V2 Position?
The V2 position contract supports removing a fraction of the liquidity in a selected pool entry. Its getRemoveParams helper applies a requested proportion to that entry's recorded bin balances to prepare removal parameters. A dApp screen may expose only whole-bin selection even though the contract supports fractional amounts.
Why Might a V2 NFT's Pool Listing Omit Some Liquidity?
The V2 position NFT's stored pool-and-bin list is owner-maintained metadata and can be incomplete. The tokenIdPositionInformation view reports liquidity from the entries in that list, so it may omit additional holdings. An incomplete listing alone doesn't prove that the underlying pool balances disappeared.
Are Token A and Token B the Same Assets in Every V2 Pool?
Token A and token B are labels assigned within each V2 pool. The pool's tokenA and tokenB functions identify its token contracts, with token A assigned the smaller contract address. Their meaning remains tied to that pool when interpreting LP balances.
Where Do My Boosted Position Shares Sit After I Stake Them?
Staked Boosted Position shares sit in MaverickV2Reward's staking vault, while the reward contract records the stake under a transferable reward NFT. A wallet's unstaked LP-token balance therefore doesn't show all of that LP's exposure. Accounting for the staked shares requires including the position represented by the reward-contract stake.