AVUSD in the Avant stack: stable receipt, not a yield token
Avant’s AVUSD is engineered to be the “cash leg” of the protocol, not the yield product. The official docs describe avUSD as a stable token fully backed 1:1 by USDC, minted by depositing USDC, and redeemable back to USDC. It receives no yield.
That design choice matters. If you are holding AVUSD, you are holding a claim on USDC that Avant custody and strategy plumbing sits behind. From a TradFi lens, AVUSD reads like a demand liability issued by a manager that runs a strategy book. You are not buying “protocol equity.” You are extending balance sheet capacity and taking operational and redemption-path risk in exchange for stability and composability.
For comparison, our Frax USD tokenomics review covers a different approach to stablecoin design tradeoffs.
Yield lives elsewhere in the same stack. Users can stake AVUSD into savUSD (Senior Tranche) or boost into avUSDx (Junior Tranche). Both are yield-bearing via an increasing exchange rate versus AVUSD. The protocol frames this as a capital structure with explicit loss absorption ordering, where Junior absorbs losses before Senior.
So AVUSD’s “tokenomics” are less about emissions and more about (1) mint/redeem governance, (2) fee take-rates, (3) how yield is routed, and (4) what happens under stress when everyone tries to exit at once.
In token economy design terms, that shifts attention from emissions to control surfaces, cashflows, and exit rails.
Supply mechanics: elastic mint/burn, bridged supply, and why “max supply ∞” is real
AVUSD does not have a fixed supply schedule. Supply expands when users mint by depositing USDC and contracts mint AVUSD 1:1. It contracts when AVUSD is redeemed back into USDC.
CoinGecko reflects that elastic design in the way it reports supply. As of March 4, 2026, CoinGecko shows AVUSD circulating supply of 110,536,298, total supply of 111,885,940, and max supply as ∞.
Cross-chain availability is a second-order tokenomics problem because it changes the failure modes. Avant’s docs state AVUSD can be bridged across supported networks using Chainlink CCIP, and the bridging guide explicitly anchors bridging to Chainlink CCIP.
Onchain, the project publishes distinct contracts for native AVUSD and bridged representations, plus CCIP pool contracts. In practice that means AVUSD’s “supply integrity” is not just the mint/redeem contract on its native chain. It is also the bridge security model and whatever operational controls sit behind bridge administration.
Cashflows: where yield goes, who gets paid, and how the protocol captures revenue
Avant is explicit that it generates yield via a multi-strategy framework across market-neutral or risk-contained DeFi strategies, including basis trades, lending rate arbitrage, yield trading (for example via Pendle-style markets), lending markets, LP, and other opportunistic approaches.
The key tokenomics question is not “does the strategy yield.” It is “who receives the yield after fees and buffers.” Avant’s docs describe yield distribution to the holders of yield-bearing tokens (like savUSD and avUSDx), with different timing mechanics: Senior accrues daily, Junior updates weekly on Thursdays at epoch boundaries.
AVUSD itself does not receive yield. That creates an implicit internal transfer: AVUSD holders who do not stake are not compensated for the strategy yield generated by the USDC backing their AVUSD. The Reserve Fund documentation makes this more concrete. It states that the capital backing unstaked avAssets (like avUSD) is still deployed in underlying strategies and that a portion of the yield generated by this capital is redirected to capitalize the Reserve Fund.
From a TradFi realist view, this is the cleanest way to understand AVUSD’s economic role: AVUSD is “non-interest-bearing funding” that supports the protocol’s risk budget and internal insurance. That can be a good trade if you value composable stable liquidity more than yield. It is not free. The yield is being allocated away from you by design.
Junior tranche economics are also spelled out in a way most protocols avoid. The docs state Junior (avAssetX like avUSDx) gets a structurally higher yield sourced from (1) baseline yield, (2) a 10% structural yield redistribution equal to 10% of total yield generated by all capital committed to the main strategy, redistributed exclusively among Junior capital, plus (3) extra yield from separate DeFi strategies, plus (4) occasional treasury contributions.
Protocol revenue capture is mostly via performance fees and redemption fees. Avant states it takes a 10% performance fee on net profits generated by strategies, and that there is also a variable performance fee allocated to expert trading partners. Separately, “a fee is applied when assets are redeemed,” described as a liquidity management tool and displayed on the frontend at time of transaction.
Two observations that follow mechanically.
First, if you are modeling “sustainability,” Avant has an actual revenue claim. It is not a governance-token-only hope. The protocol can fund operations from strategy PnL via a 10% take-rate.
Second, AVUSD itself is not the revenue-capture instrument. The value of AVUSD is supposed to be stability and redeemability. Fee extraction hits users through lower distributed yield (for savUSD/avUSDx holders) and through explicit redemption fees on exit paths.
Redemption and duration risk: cooldowns, fees, and the MAX “min-price” rule
Stablecoins live or die on their exit rails. Avant’s rails have three different “durations,” depending on where you sit in the stack.
1) AVUSD → USDC (base redemption). Avant documents that avAsset redemptions are often completed within a few hours, but can take up to 7 days depending on market liquidity and other conditions. Importantly, base redemption requests can be canceled or adjusted before finalization by submitting a new request.
That waiting period is not just “UX friction.” It is an explicit liquidity gate. In stress, gating is what prevents a bad day from becoming a bank run that forces fire-sales across the strategy book. It also means AVUSD is not structurally equivalent to USDC in a liquidity crunch, even if it is designed to be backed 1:1.
2) savUSD → AVUSD (unstaking Senior). Unstaking savAssets has a 24 hour cooldown for savUSD → avUSD, during which funds are locked and earn no yield.
3) avUSDx → AVUSD (redeeming Junior / MAX). Redemption for boosted tokens is fixed at 7 days, and there is no yield accrual during that waiting period.
The most important clause is the final redemption price rule for avAssetX. Avant documents that the final redemption price for avAssetX tokens is calculated as the lower of (i) the price at request time and (ii) the price at the end of the cooldown period.
Mechanically, this is an anti-gaming feature that shifts tail risk onto Junior holders during the redemption window. It reduces the incentive to “race out” of avUSDx right before a negative repricing because you cannot lock in a stale high exchange rate and coast through the cooldown. You eat the worse print. That is a real, finance-native design choice. It makes Senior safer at the expense of Junior optionality.
On dates: the docs describe the “min-of-two-prices” rule as current behavior, but the documentation does not clearly timestamp when this went live. A public event listing tracked a “MAX Redemption Mechanism Update” effective December 3, 2025. Treat that as secondary confirmation, not canonical protocol specification.
Finally, Avant’s stated fee model includes a redemption fee applied when assets are redeemed, with the specific fee shown on the frontend. A variable redemption fee is, economically, a “liquidity spread” controlled by the protocol. In TradFi terms, it is the protocol pricing its own balance sheet capacity during outflows.
Control surface: admins, permissioned minting, and the unfinished governance story
If you only read the product pages, you might walk away thinking AVUSD is fully automated mint/redeem against USDC. The protocol’s public smart contract materials paint a more centralized operational picture.
In the official avUSD-Contracts repository README, Avant describes AVUSD.sol as an ERC-20 with an owner-controlled minter address. The owner can set the minter, and the minter is the only address that can mint AVUSD, with the ability to mint an unlimited amount.
The same README describes the minting contract path: mint() and redeem() are callable only by addresses granted permission by Avant. Users sign EIP-712 orders offchain, and Avant’s backend submits those signed orders onchain after checks.
This centralization is not hidden in third-party commentary. Dedaub’s published security assessment flags “Crucial protocol actions are centralized,” explicitly naming minting and redeeming of AVUSD and management of backing collateral as centralized. That centralization issue is listed as open in their report.
The protocol’s own security documentation is consistent with that operational model. Avant describes institutional-style custody and control layers such as MPC wallets and transaction policy enforcement with address whitelisting and role-based access control. It also describes integrations like Fireblocks as a mechanism to restrict strategist actions to whitelisted protocols and approved transaction types.
On audits, Avant lists multiple smart contract audits (including Omniscia and Dedaub) and ongoing OPSEC work with Trail of Bits, with a public list of reports and dates in their docs. Dedaub also states the audited AVUSD contracts were at commit e41cf318…, matching the repository commit references shown in other Avant audit materials.
Governance is the part that is structurally “not there yet.” Avant’s docs mention an AVANT governance token in the future and a “Governance Backstop (Future)” layer that would sit between the Reserve Fund and the Junior tranche in the loss waterfall. The same docs page that describes the token set calls AVANT the governance token, phrased as “will be.”
That is not a criticism. It is a modeling constraint. Until governance is live, AVUSD is effectively an admin-managed instrument with published controls and audits. If you are underwriting AVUSD as a cash equivalent, the relevant question is not “is there governance.” It is “how strong are the operational guardrails, how transparent are the addresses, and what is the observed behavior under stress.” Avant does publish strategy-related addresses and contract addresses, which helps verifiability.
Risk analysis (ranked)
AVUSD’s core promise is stability and exit to USDC. Almost every meaningful risk is a risk to that promise. Avant’s own risk disclosures group risks into smart contract, strategy and market risk, custody and operational risk, liquidity and redemption risk, and counterparty risk.
Dominant risk: centralized control of mint/redeem and the backing collateral.
This is the dominant risk because it is upstream of everything else. If minting and redeeming are permissioned and routed through a backend submission flow, then AVUSD’s “convertibility” becomes partly a policy decision, not just a contract property.
From a financial-instrument perspective, that means AVUSD is best underwritten as “stablecoin issued by an operator running a strategy and custody stack,” not as a purely autonomous overcollateralized stablecoin. This doesn’t make it bad. It makes it different. The upside is that an operator can act quickly in incidents, rotate keys, yank capital from external protocols, and run a coherent treasury policy. Avant’s security stack is clearly built in that direction, including MPC custody, transaction policy engines, whitelisting, and real-time monitoring partners.
The cost is that you are taking a hybrid risk profile: onchain contract risk plus offchain operator risk. That is the same “single point of failure” shape TradFi tries to diversify across custodians, administrators, and trustees. Avant partially addresses this with institutional tooling, but the structural reality is still there.
One more reason this is dominant: the AVUSD token itself has an owner-controlled minter according to Avant’s published repository README. If that control plane is compromised, an attacker does not need to “break the peg” via slow market forces. They can attack supply integrity directly.
CoinGecko even surfaces a third-party warning (via GoPlus) that the contract creator can make changes such as disabling sells, changing fees, minting, and transferring tokens, and advises caution. I would not treat GoPlus UI warnings as gospel. I would treat them as a prompt to verify admin powers and upgradeability onchain.
Given that public docs explicitly describe a future governance token and future governance backstop, the most conservative read is that AVUSD is still in the “progressive decentralization” phase. That can work. It just lowers confidence in parameter stability.
Top 3 risks
-
Centralized mint/redeem and admin-key compromise. Trigger: compromise of owner/minter/admin credentials, or policy-driven restriction of mint/redeem flow. Mechanism: AVUSD’s minter can mint unlimited supply and mint/redeem flow is described as permissioned and backend-submitted, so control-plane failure can directly impair supply integrity or convertibility. Who bears it: AVUSD holders first (peg and redemption), then savUSD/avUSDx holders via broader protocol stress. Measurable indicators: changes in privileged roles or minter address, unusual mint volumes, redemption queue growth, and any public disclosure of operational incidents or emergency controls.
-
Strategy loss that overwhelms protection layers. Trigger: adverse basis funding regimes, external protocol exploit, or market dislocation that produces losses in the deployed strategy set. Mechanism: losses are meant to be absorbed in order by Reserve Fund, then a future Governance Backstop, then Junior tranche, before Senior is hit. If losses exceed buffers, the system can face impaired redemptions or a soft depeg due to confidence and liquidity stress. Who bears it: Junior tranche first, then potentially Senior and AVUSD holders through delayed redemptions and secondary-market discounting. Measurable indicators: reserve fund adequacy relative to deployed capital, reported strategy underperformance, and widening AVUSD price deviations on DEX venues.
-
Redemption-path duration and fee risk under stress. Trigger: large, synchronized exits or thin liquidity that forces redemptions into the longer end of stated waiting windows. Mechanism: AVUSD redemptions can take up to 7 days, savUSD has a 24-hour cooldown, and avUSDx has a fixed 7-day window with no yield plus a worst-of-two-price rule. Redemption fees can further increase the effective exit spread. Who bears it: users needing immediate liquidity, and Junior holders most acutely during avUSDx cooldown windows. Measurable indicators: growth in active redemption requests, rising redemption fees, and persistent AVUSD discounts vs $1 on liquid DEX pairs.
If you want more frameworks for evaluating crypto balance-sheet risk, browse our crypto research.
If you’re structuring incentives, disclosures, or stress tests around designs like this, it’s worth treating the system as a balance-sheet product and modeling it accordingly. That is where token economy design gets real, and where careful tokenomics consulting earns its keep.
This article is part of our Tokenomics Deep Dive series.








