Maverickprotocol
Maverickprotocol MAV staking gives holders veMAV voting power and access to conditional rewards
Maverickprotocol MAV staking locks MAV in a voting-escrow contract to provide veMAV voting power for governance and incentive allocation. That commitment can also affect eligible liquidity-provider rewards and participation in incentive batches. MAV remains unavailable for redemption until its individual lockup ends, and veMAV can't be transferred. Different uses have different prerequisites: a recorded stake establishes a lockup, an eligible balance supports voting, and a reward claim follows its contract or batch conditions. V1 stakes need synchronization before V2 veFlywheel voting. The amount committed, the chosen end date, and the applicable reward configuration determine which benefits a stake can support.
Topics on this page
Voting Rights and the Locked MAV Balance
A MAV lockup supplies voting weight while committing the underlying tokens until a recorded end date. veMAV means vote-escrowed MAV: it measures the rights associated with that commitment. The MAV amount records principal, whereas the veMAV amount records voting weight. They aren't interchangeable balances, and a larger veMAV figure doesn't mean that more MAV principal became redeemable.
Governance participation, directing liquidity incentives, and qualifying for certain rewards are separate applications of the same holding. Keeping MAV available in a wallet preserves liquidity when an immediate transfer is the priority. A direct stake suits a different goal: obtaining the voting rights and conditional benefits that require a lockup.
Governance Votes and Incentive Allocation
veMAV supports governance proposals and voting that directs the vote-matched portion of emissions toward eligible Boosted Positions. These positions concentrate an LP allocation within a pool. Matching emissions require a reward contract configured for MAV and veMAV, qualifying external incentives in that epoch, and an available matching budget. Matching eligibility can include MAV incentives and selected arbitrary incentive tokens under the applicable matching configuration. A position without qualifying incentives doesn't become eligible simply because it attracts votes.
A vote directs emissions to a Boosted Position's liquidity providers; it doesn't automatically pay the voter. Each provider of matching funds can veto a position's allocation from that provider's contribution. After the veto period, a distribution call sends any matched emissions to the position's reward contract for its participating LPs. Governance proposal voting also has a separate purpose from choosing where liquidity rewards flow, even though both use veMAV voting power.
Stake Readiness and V2 Lockup Parameters
A proposed V2 MAV stake needs enough token allowance for its voting-escrow contract on the selected chain to collect MAV. A wallet balance alone doesn't satisfy that prerequisite. Maverick V2's VotingEscrow implementation sets the minimum new-stake duration at four weeks.
| Parameter | Documented Value | Control or Redemption Consequence |
|---|---|---|
| V2 minimum new-stake duration | 4 weeks | A shorter duration falls outside this V2 implementation's bounds. |
| V2 maximum new-stake duration | 1,460 days, or 4 × 365 days | The recorded end date governs access to the locked MAV. |
| veMAV transferability | Non-transferable | Delegation preserves the owner's underlying MAV redemption rights. |
| V1-to-V2 synchronization threshold | At least 365 days remaining | A shorter legacy lockup needs a later end date before synchronization. |
With adequate allowance, the contract can collect the selected MAV for a valid stake. Keeping the amount and duration unchanged, insufficient allowance blocks that collection. Approving the intended contract repairs the missing permission, but doesn't create the lockup. An invalid duration remains invalid after approval; changing permission can't repair a duration outside the contract's bounds.
A completed staking call creates the lockup record, including its MAV amount, end timestamp, and voting weight. A successful transaction receipt and matching contract state establish that result. A confirmation prompt or submitted transaction hash alone doesn't establish a completed stake.
End Dates and Relative Voting Influence
The voting multiplier grows by a factor of 1.5 for each additional year in the chosen staking end date. Its curve uses the end time relative to the contract's starting timestamp. Consequently, the MAV amount and end date determine voting weight together. It doesn't specify interest on the MAV principal.
Time passing doesn't automatically extend a stake's end date. New commitments can receive greater weight through later end dates, diluting older stakes' relative influence. A recorded veMAV amount and its percentage of aggregate voting weight therefore describe different things. The relevant voting snapshot can also differ from an account's present balance. An extension affects the commitment's terms; it doesn't rewrite the balance recorded at an earlier snapshot.
Why Is a V1 Stake Missing From V2 Voting?
A V1 MAV stake must be synchronized with V2 before its veMAV contributes to V2 veFlywheel voting. The combined stake list can display a legacy position without establishing its voting eligibility. The synchronization contract requires the legacy end time to be at least 365 days beyond the synchronization time. A legacy stake below that threshold needs an extension before it can qualify.
The 365-day condition applies to legacy synchronization. It isn't the minimum duration for creating an ordinary V2 stake.
Synchronization status belongs to the account and legacy lockup index in the relevant deployment. The V2 voting snapshot must also include the synchronization before that weight becomes usable in its epoch. Delegation can explain another mismatch between a visible holding and voting power assigned to an address. V2 staking handles delegation automatically; legacy voting power may require delegation to the intended address.
LP Reward Boosts and Position Requirements
A veMAV balance can boost eligible MAV emissions when the holder's Boosted Position shares are staked in a reward contract configured for MAV and veMAV. The underlying LP allocation and the MAV voting-escrow stake remain separate holdings. A V2 reward contract can associate a reward token with a veToken; that association determines whether the relevant voting-escrow balance contributes to its boost.
Holding veMAV alone doesn't create LP shares or establish participation in a particular Boosted Position's rewards.
The V2 reward design allows up to approximately a 1.33x holding boost on eligible MAV emissions. It uses the veMAV balance associated with the wallet that provided liquidity. Reaching the ceiling depends on that wallet's share of the chain's veMAV supply relative to its share of the Boosted Position. This factor applies to emissions, without multiplying the original MAV principal. Liquidity modes govern how the LP position's liquidity moves, while its trading exposure remains part of liquidity provision. Locking MAV doesn't remove that position's loss risk. When the task is governance participation alone, taking on an LP position adds a separate asset allocation that the vote itself doesn't require.
Liquid Emissions and Locked Reward Claims
An eligible LP can receive liquid MAV emissions or stake those emissions for a duration-dependent boost. Choosing the locked route creates a MAV commitment with its own redemption terms. The V2 four-year emissions-staking option provides a 5x duration boost to eligible MAV emissions. The veMAV holding factor is separate, and depends on the LP's balance relative to the chain's total. The V2 interface's maximum boosted APR assumes a four-year emissions stake and sufficient veMAV.
The staking duration for reward disbursement and the duration of an existing MAV lockup are distinct inputs. Some V2 reward methods create a new voting-escrow lockup. When a reward claim stakes MAV into an existing lockup, the reward contract needs extender approval for that lockup. That route can extend its end date, delaying access to the MAV already committed there.
Incentive Batches and Historical Entitlement
V2 incentive batches allocate rewards pro rata from holders' veMAV balances at the batch's specified timepoint. A batch becomes claimable after that timepoint has passed. A larger present balance doesn't retroactively increase its historical share. Each batch also identifies its incentive token and any staking duration required when claiming.
For MAV-denominated batches, zero staking duration permits a liquid claim, while a nonzero duration requires a MAV lockup within the contract's permitted range.
Residual veFlywheel emissions provide one application: the residual-emissions design allocates unclaimed LP boosts to veMAV holders as four-year MAV stakes. That condition belongs to this distribution, while other funded batches can set different permitted claim terms. Claiming rewards and redeeming an existing principal lockup remain separate operations.
Delegated Votes and Retained Redemption Rights
Delegation lets another address exercise veMAV voting power while the holder retains ownership and the right to redeem the underlying MAV. Re-delegation can return voting power to the holder or assign it elsewhere. Delegation doesn't itself establish a payment arrangement with the delegate. The veFlywheel uses the balances and delegations captured at its voting snapshot. A later delegation change doesn't update that epoch's captured allocation. An LP can retain the veMAV holding boost on eligible MAV emissions after delegating voting power.
Adding MAV and Extending the Commitment
A V2 stake can accept additional MAV without changing its existing end date, while an extension moves redemption farther into the future. Adding MAV increases the amount committed under that stake's terms. Extending the end date changes the voting multiplier and the period during which the MAV remains unavailable. The management interface distinguishes Add from Extend.
The Add function is available for V2 stakes, and V1 stakes don't support that addition. A separate new stake preserves its own amount and availability date. Combining every intended use into a later-ending lockup can change access to MAV that previously had an earlier redemption date.
Redemption and the End of a Stake's Rights
A MAV stake becomes eligible for redemption on or after its recorded expiry, and unstaking returns the underlying MAV. Redemption also burns the veMAV associated with that stake. Reaching the end date establishes eligibility; it doesn't establish that a transfer back to the wallet has already completed. A previously extended stake follows its revised end date. Delegating voting power doesn't shorten that commitment or grant the delegate a separate withdrawal right. When continued access to liquid MAV is essential, a new lockup cannot supply that access before expiry.
Good to know
Why Do Different Chains Show a MAV Stake Numbered 0?
Stake numbering starts at 0 for each wallet on each chain, so identical stake numbers can refer to different lockups. An identifier becomes meaningful alongside the account, chain, and applicable staking contract. The number alone doesn't establish that two displayed entries represent the same MAV commitment.
Can I Change My veMAV Incentive Vote Again Within the Same Epoch?
Each address with eligible veMAV voting power can cast an incentive vote once per epoch on the relevant chain. The allocation can cover multiple eligible Boosted Positions. An address's vote on one chain doesn't establish the status of a vote in another chain's deployment.
Which MAV Balance Funds a V2 Stake Created for Another Address?
The V2 stake function collects MAV from its caller and credits the lockup to the specified recipient address. Its token allowance must authorize that collection. The recipient field identifies the account receiving the commitment and voting balance, so funding a stake doesn't by itself preserve the caller's redemption rights.
How Does an Extender Approval Differ From veMAV Delegation?
An extender approval authorizes a designated contract or address to extend a specific MAV lockup. Voting delegation assigns voting power while preserving the holder's redemption rights. V2 also supports revoking an extender approval. These permissions control different actions, even when the same account grants both.
Is a Previously Claimed veMAV Incentive Batch Claimable Again?
An account can claim a particular incentive batch only once. Claim information tracks whether that account has already claimed the batch, and the contract rejects a duplicate claim. Increasing a later veMAV balance doesn't reopen the completed claim or change its historical allocation.
Where Can I Read All of My V2 MAV Lockups?
MaverickV2VotingEscrowLens provides a paginated getLockups function for an account in a specified voting-escrow contract. Its index range allows multiple reads when needed. These results describe that contract's lockups; covering holdings across deployments requires keeping the account and network context attached to each result.