Aave Founder Stani: Considering Token Burn Mechanism
Stani Kulechov, founder of Aave, stated that he is considering adding a token burn mechanism in Aavenomics 3.0. The specific ratio, source of funds, and execution path have not yet been disclosed.
Aavenomics 3.0 was previously positioned to continuously repurchase AAVE with protocol revenue and to automate the repurchase process, moving it from temporary committee decisions to a standardized on-chain mechanism. In June, it was publicly explained that under the Aave Will Win framework, 100% of Aave protocol and GHO revenue would belong to AAVE tokens, covering product lines such as App, Pro, and exchange; 3.0 aims to make repurchase the default setting, which can only be stopped by a governance vote. The existing Aavenomics Part One allows the finance committee to repurchase approximately $1 million weekly in the secondary market, which is a revocable and adjustable authorization, rather than a built-in logic of the protocol.
Public governance data indicates that since April 2025, over 205,000 AAVE tokens have been repurchased, accounting for about 1.28% of the maximum supply of 16 million tokens. Estimates suggest that with the revised revenue allocation, the repurchase scale could reach approximately 292 tokens daily, fluctuating with fees. The protocol has accumulated fees exceeding $2.2 billion, with an annualized fee window previously seen at around $400 million; Kulechov previously provided an annualized revenue estimate for the DAO of about $134 million. The destination of repurchased tokens has always been a design variable: treasury, Safety Module, or burn address.
If the burn mechanism is implemented, it would mean that repurchases would no longer just transfer circulating tokens to the treasury or insurance module, but would directly reduce supply. This is different from locking tokens in the Safety Module for security incentives: the former compresses the circulating supply, while the latter turns tokens into a buffer for protocol payouts. The core conflict that 3.0 aims to resolve is the revenue ownership dispute triggered by Aave Labs separating exchange fees from the DAO treasury at the end of 2025; in April 2026, Aave Will Win was passed with a high vote, consolidating brand product revenue into the DAO and allocating $25 million in stablecoins plus 5,000 AAVE to Labs. The burn would advance the "revenue belongs to tokens" from an accounting perspective to a supply perspective.
Details of the mechanism remain unclear. The burn could occur immediately after repurchase, proportionally based on revenue, or governance could set a cap. Until disclosed, the market can only interpret it as an enhancement to automated repurchases, rather than an already approved proposal. The next steps still require quarterly calls or ARFC to provide contract paths, triggering conditions, and whether it can be reversed.
From a market mechanism perspective, this is an event-driven repricing of token supply and demand, not a sudden change in borrowing demand. Buyers are secondary holders and market makers betting on a deflationary narrative; sellers are addresses waiting for details, interpreting repurchases as treasury accumulation rather than destruction. The flow of funds is the protocol fees buying AAVE, and if burned, it would leave circulation, reducing reserves in the Safety Module and treasury. The beneficiaries are those expecting a contraction in circulating supply, while the pressure is on the thickness of the insurance module and the future spending flexibility of the DAO. Before voting, price reactions mainly stem from expectation differences rather than actual on-chain destruction.
Source: Public Information
ABAB AI Insight
Aave's tokenomics has gone through three phases: the early Safety Module locked AAVE as bad debt insurance; in 2025, Part One converted fees into weekly repurchases by the committee; in 2026, Aave Will Win consolidated Labs product revenue into tokens. Kulechov repeatedly emphasizes "one asset, one model," addressing the months when Labs and the DAO competed for fees. The burn mechanism pushes the same logic to its conclusion: fees not only buy tokens but also make them disappear.
The capital path is the protocol interest and stablecoin GHO minting tax flowing to the secondary market. The scale of repurchases is tied to borrowing utilization rates, liquidation penalties, and front-end product fees, not inflationary subsidies. Burning the purchased tokens means giving up the opportunity to use the same batch of tokens for incentives, insurance, or allocations to Labs. Maker uses stable fees to buy and burn MKR, and Ethereum burns priority fees, both representing the same type of choice: exchanging traffic for scarcity, and narrative for treasury flexibility.
In a similar position, Aave was the first in lending protocols to write "all fees belong to tokens" into governance constitution, while Uniswap and Compound still largely remain at fee switches and treasury accumulation. The industry phase is shifting from subsidy growth to controlling circulating supply. If the burn becomes reversible, the market will treat it as marketing; only when written into an irreversible contract does it approach the structural deflation of Ethereum EIP-1559.
Structural judgment belongs to the transfer of pricing power. In the past, pricing power in lending protocols was based on interest rate models and liquidation penalties; now it must shift to how fees become token supply and demand. The burn transforms the protocol from "a treasury with income" to "a pipeline with burning," where token holders no longer only have residual claims on the treasury but also on future fee supply contraction. Mechanically, this is because governance wars have proven that if income is not bound to irreversible token outcomes, the lab layer can cut off traffic at any time.
ABAB News · Cognitive Law
Repurchases into the treasury are savings; burning after repurchase is contraction.
Revenue belongs to tokens; if it can still be redirected, it is not ownership.
Insurance requires thickness, deflation requires disappearance; both cannot be fulfilled with the same token simultaneously.