How Aurove works

Aurove is a liquid claim layer on Mezo Earn. Users deposit BTC, MEZO, or an existing veNFT. Aurove locks that value in a Mezo managed position owned by an Aurove manager, then mints fungible units the user can hold, wrap, swap, or redeem.

The protocol does not replace Mezo. Voting-escrow accounting, managed deposit and withdraw, distributors, voters, and concentrated-liquidity pools are Mezo / Tigris contracts. Aurove owns the Ledger, Vault, managers, sinks, ID20 wrappers, gauges, factory, and zap router.

Scope of the production deployment

• Two products only: managed BTC (avBTCm) and managed MEZO (avMEZOm).
• Ledger.depositErc20 and Ledger.depositVeNft still take an epochs argument, but the implementation ignores it and always mints the managed sentinel tranche. The dApp and zap still pass 4 (BTC) or 208 (MEZO). On the zap router, epochs == 0 means “leave this ERC-20 as a plain token,” which is a different flag from Ledger deposit.
• No duration-bucket products, no Aurove settlement window, no streaming reward contract.
• ID20 wrappers and Id20Gauges exist for those two tranches.
• Two CL pools exist: MUSD / avBTCm and avBTCm / avMEZOm.

Layers

• Core — Ledger (ERC-1155), Vault (custody), VeNftManager, RewardSink. Upgradeable.
• ID20 — factory, ERC-20 wrappers, Id20Gauges, zap router and adapters. Immutable.
• External — veBTC, veMEZO, BTC, MEZO, MUSD, CL factory/router/position manager, pool Voter.

Addresses: Deployment reference. Roles: Upgradeability and roles. Integrators: Architecture.