Maverick Protocol: dynamic liquidity, pool-specific fees and V2 migration

Maverick’s exchange function is spot conversion through automated liquidity pools. Traders select the input and output token, review the resulting quote and approve a wallet transaction. Liquidity providers supply the assets that those trades consume. A position’s token composition can change as others trade; depositing two tokens is therefore exposure to a changing inventory, rather than a promise to receive the original quantities back.[8]

The V2 interface separates Swap, Add Liquidity, voting, voting-power management and Portfolio. Advanced tools let projects and market makers configure liquidity and incentives. These are different activities within the same ecosystem: swapping needs an executable quote, providing liquidity needs a chosen distribution, and incentive administration requires the relevant position and reward-contract settings.[18]

Movement uses the pool’s time-weighted price, which can differ from its current trading price. The contract performs native shifts without a separate movement transaction from each LP. That removes an operational step; it does not remove the economic effect of trading through the position.[5]

Mode Both carries a particular inventory risk. The permanent-loss guide explains how repeated price changes can cause the AMM to sell one asset after a fall and buy it back after a rise. Repositioning crystallises the difference. A later return to the starting market price need not restore the original assets, and fees would have to offset any such loss before the position produced a net gain.[6]

Creating a new pool involves choosing its fee, bin width and initial price, then supplying initial static liquidity so it can be discovered and traded. An incorrectly chosen starting ratio creates an arbitrage opportunity against the supplied assets. Pool creation is consequently a pricing and inventory decision, beyond simply adding another token pair to a menu.[9]

V2 exposes a fee for each swap direction. The rate is represented with 18 decimal places, so a stored value of 0.01 × 10^18 corresponds to 1%, not 0.01%. A hypothetical 1,000-unit trade at a 0.30% fee would incur 3 units before execution effects and network costs. That is an arithmetic illustration, not a quoted rate for any current pool.[11]

Raw incentives are distributed proportionately over a stated period, documented as between three and 30 days. Adding another incentive payment can change the remaining distribution schedule. A displayed incentive rate can therefore change as rewards, eligible liquidity and time remaining change. It is a description of the current programme, not a fixed deposit interest contract.[22]

The emissions guide distinguishes immediately claimable returns from the maximum boosted figure. Its grey APR includes fees and MAV available to claim now; the purple figure assumes the maximum lock-related boost and sufficient veMAV. Obtaining that figure can require locking MAV for four years. Matching emissions also require an eligible reward contract and qualifying incentives; the committee can admit additional incentive tokens with epoch-specific multipliers.[23]

Protocol administration can set the share of trading fees allocated to the protocol, the flash-loan fee rate and the receiving address. These parameters should be distinguished from the pool’s quoted total trading fee. A current pool quotation is more useful for execution than applying an old protocol-wide percentage from a launch article.[13]

The documented connection choices include MetaMask, Ledger, Coinbase Wallet, Trust Wallet and WalletConnect. The wallet must be on the network used by the selected deployment, and the interface can request a network change. Tokens on another chain are a separate balance: a matching ticker or the same wallet address does not itself move assets between networks.[17]

An ERC-20 allowance permits a specified contract to spend approved tokens. The approval guide describes choosing an amount and, when necessary, revoking an earlier approval before setting a replacement. Insufficient allowance can cause the subsequent action to fail. Disconnecting a browser session and revoking an onchain allowance are separate operations; a session ending does not undo an already authorised contract balance.[7]

The older position-management guide describes selecting bins for removal. Current V2 contract functions accept removal amounts and add a further condition for merged bins: their liquidity may first need migration through the merge stack. A legacy screen’s whole-bin workflow should not be treated as a universal limit on every V2 withdrawal.[11]

For MAV staking, the UI guide instructs users to preview the unlock date before signing and to track separate positions on the selected chain. Its one-, two-, three- and four-year menu choices are interface presets. The underlying voting-escrow explanation gives a minimum of one week and maximum of four years; a shorter contract capability is not evidence that every interface exposes that choice.[26][25]

A wallet signature initiates a contract action, while liquidity subsequently resides in pools or reward contracts. Some V2 pools are permissioned: the accessor can control who adds or removes liquidity and who swaps, and can change directional fee settings. Users must distinguish such a pool from a permissionless deployment before assuming that every action is freely available to every address.[12]

Pool administration includes functions restricted to the factory administrator, including protocol-fee collection and lending-fee settings. These are concrete control surfaces within the protocol. Describing the exchange as decentralised does not mean that every parameter is immutable or that every operational role has disappeared.[14]

Token behaviour can also change recoverability. Maverick’s rebasing-token guide says positive rebases accumulate as protocol fees rather than additional LP returns. A negative rebase can leave accounting claims larger than the assets available and prevent exits. A token whose units rebase is different from a wrapped token whose exchange value compounds; the token’s mechanism matters when assessing a pool.[15]

The security page lists separate review material for protocol generations, including OpenZeppelin, Hunter and Omniscia entries for V2 and earlier V1 reviews. This profile inspected that index, not every underlying report or deployed-bytecode match. No insured amount, named policyholder entitlement or exchange-wide loss reimbursement undertaking was verified from it.[16]

Published operational-wallet addresses identify particular incentive and delegation functions on different chains. They can help reconcile a documented programme’s transfers, but their balances are not a customer-liability statement. The page supplies no basis for treating those wallets as an audited reserve fund or as insurance for every liquidity provider.[20]

Maverick’s restriction notice excludes users acting from United States or sanctioned-country IP addresses from swaps, liquidity provision and other platform actions. It directs users who believe a block is erroneous to the official Discord. This is the published interface access rule; a wallet connection or the existence of an onchain deployment does not override it.[19]

Eligibility also depends on the selected pool. Permissioned-pool code restricts core actions to its configured accessor. This can affect adding assets, unwinding a position and trading, independently of geographic frontend restrictions. The relevant pool’s configuration therefore forms part of the practical access assessment, rather than only the protocol name appearing in a wallet.[12]

The swap guide presents confirmation in both the interface and the wallet, with price impact, minimum received, slippage tolerance and deadline settings visible before execution. A failed or expired transaction should be distinguished from a completed swap before another instruction is sent. The documented controls bound an attempted transaction; they do not promise a fill when available liquidity or execution conditions change.[3]

Portfolio is the documented place to locate and manage liquidity positions. Troubleshooting needs the selected network, position and transaction context, especially when assets were deposited into a reward contract rather than left as ordinary LP holdings. The public guide does not provide a telephone dealing alternative, a guaranteed recovery time or an emergency order-cancellation service.[10]

The security documentation links to interface terms, but the destination returned 404 when checked on 20 October 2026. An exact current contracting company and a financial-services permission for that company were therefore not established. The technical documentation identifies protocol components without resolving the interface’s legal counterparty.[33]

V2’s factory and pool administrative roles are software permissions. The existence of a fee receiver, owner role or pool accessor explains who can perform particular contract actions; none of those roles is evidence of a regulator’s authorisation to provide investment or exchange services in a jurisdiction.[13]

The current deployment register lists V2 mainnet contracts for Arbitrum, Base, BNB Smart Chain, Ethereum, Scroll and zkSync Era. It also separates pre-Epoch 3 incentive and reward contracts from later deployments. Matching the chain, generation and contract is essential when locating a balance; the same product label can span several separately deployed contracts.[2]

The official application remained discoverable at review, including an indexed voting page referring to a September 2026 epoch. That supports the profile’s current operational scope, but it supplies no independently measured active-user count or present trading volume. Historical adoption claims have not been converted into a current size ranking.[31]

The V1-to-V2 guide describes a user-led transition: remove liquidity in the old application and add it to a chosen V2 position. It gives separate application links and does not describe an automatic transfer of every position. This review found no final universal withdrawal deadline in that guide.[4]

Legacy veMAV uses a different transition. The syncing guide requires at least one year remaining on a V1 lock for the described V2 voting route; an insufficient remaining term needs extension to qualify. Syncing voting power is not redemption of the underlying locked MAV and does not turn the old position into immediately available cash.[27]

The tokenomics page sets a maximum supply of two billion MAV and provides a vesting schedule extending into later years. Its dated unlock table and its older circulating-supply statement describe different things. Scheduled releases are not a measured current free float, and neither figure counts traders using the exchange.[28]

Operator

Maverick Protocol; an exact legal counterparty for the public interface was not established.

Exchange model

Decentralised

Service scope

Multi-chain spot AMM, configurable LP positions, incentive contracts and MAV voting escrow. Individual pools and protocol generations have distinct parameters.

Client types

Retail clients; Professional clients

Pricing publication

Public pricing

Other names

Maverick V1; Maverick V2; Maverick AMM

Funding scope

Crypto enters from a compatible wallet on the selected chain. Position removal, reward unstaking and MAV redemption are different operations; no native bank-deposit route was verified.

Custody and asset handling

Users sign through their wallets; contributed liquidity and locked MAV are held in the relevant contracts. Pool and reward balances need separate tracking.

Client eligibility

The interface excludes actions from United States and sanctioned-country IP addresses. Technical contract access and financial-services permission are separate questions.

Support

Official documentation and the linked Discord provide assistance. The restriction guide directs mistaken geoblocking reports there; no emergency dealing service or complaint deadline was verified.

Authorisation and registration scope

No exact licensed interface entity or exchange-specific financial permission was independently verified. The published terms destination was unavailable at review.

Exchange metadata checked 20 Oct 2026Source 1Source 4Source 11Source 17Source 18Source 19Source 25Source 30Source 31Source 33

Boosted Positions package a chosen liquidity configuration into shared LP tokens. To receive the corresponding incentives, holders stake those tokens in the relevant reward contract. V2 can associate more than one reward contract with a position, so holding its shares does not automatically confer every advertised programme’s rewards. The position and the incentive account both matter.[21]

Voting-escrow MAV is a non-transferable governance balance linked to locked MAV. Delegating voting power retains ownership and redemption rights over the underlying stake, and delegation can be reassigned. This is governance staking rather than proof-of-stake network validation. The voting multiplier concerns governance weight, not an advertised interest rate on the principal.[25]

Emission voting uses an epoch snapshot taken seven days after the epoch begins. Stakes or delegations added after that point do not create eligibility for that same snapshot. Legacy voting power must also be synced in time. A transaction can succeed onchain yet still miss the timing condition for the current voting period.[24]

The LP-balance reference distinguishes ordinary positions, Boosted Position shares held in a wallet and shares staked in reward contracts. Historical reconciliation needs all relevant contracts and chains, plus deposits, removals, swaps and reward claims. Looking only at the connected wallet’s token list can omit invested assets. A tax-complete downloadable statement service was not verified.[30]

The V2 market-data API requires a chain identifier and reports fields such as token addresses, last price and rolling 24-hour base and target volumes. Those volumes are in their respective token units; the liquidity field uses dollars. Combining raw figures across tokens without conversion would produce a misleading total. A public ticker endpoint supplies information, not spending authority over a wallet.[29]

The current website uses AI-oriented positioning. Native liquidity movement follows the selected contract mode. Any external agent submitting transactions needs separately authorised wallet or contract permissions; the website label does not define that authority.[32]