ERC-8113 Series accounting for vault performance fees (Series Accounting for Incentivized Vaults)
Draft · Vaults & DeFi · created 2025-12-25
A series accounting method in which ERC-7540/ERC-4626 type vaults track separate assets, shares, and high-water marks for each deposit batch, enabling fair collection of performance fees on returns without free-riding.
Why it is needed
Vaults typically collect performance fees based on a single, vault-wide highwater mark (the highest price-per-share recorded so far). But if a user's deposit is claimed at a price-per-share below this highwater mark, that user pays no fee on the entire gain accrued from their entry price up to the new highwater mark once the vault later sets a new one. This is the free-rider problem, and it erodes the returns existing users receive relative to the fees they paid. The problem is especially pronounced in vaults that source returns from real-world assets (RWA), where price-per-share swings sharply at each rebalancing or settlement cycle, yet DeFi had no formal implementation of series accounting, the standard technique used in traditional funds.
In depth
State variables separated per series
Conventional vaults keep only a single totalAssets and totalShares for the whole vault. Under this standard, each series MUST independently maintain its own total assets, total shares, shares of users, list of users, and highwater mark. A vault that rebalances periodically, as in the ERC-4626 model, treats all deposits received within one rebalancing period and settled at the same price as a single batch, while ERC-7540 type asynchronous vaults settle deposit requests cleared at an oracle-provided price under the same series id.
Key terms
A series is a kind of sub-vault holding a batch of deposit requests settled together. The price-per-share is the ratio of a series' total assets to its total shares, and the highwater mark is the highest price-per-share that series has recorded. The oracle is the entity that sets the price-per-share, and settle is the act of rebalancing or clearing deposit requests according to the logic the oracle determines. The lead series is the default series into which the initial deposit requests are settled; outstanding series are any series other than the lead series in which user shares remain; and consolidation is the process of moving all user shares from outstanding series into the lead series.
Deposit branching logic
When the oracle provides a new price-per-share, if the lead series' current highwater mark is greater than that price, the vault MUST create a new, unique series id and settle all pending deposit requests into that new series. Conversely, if the highwater mark is not greater than the price, the vault MUST settle pending deposit requests into the lead series, and if any outstanding series exist, it MUST consolidate all of them into the lead series.
redeem requests denominated in assets instead of shares
Vaults conforming to this standard MUST allow users to redeem, or request redemption, in terms of an asset amount rather than a share amount. The vault is RECOMMENDED to store the proportion of total assets that the user's requested amount represents. At settlement, the vault MAY follow a FIFO approach, redeeming from the lead series first and, if insufficient, filling in order from the outstanding series with the lowest series id. A fragment of a single request processed across multiple series is called a Redeem Slice.
Why assets are used instead of shares
Because user shares are non-fungible across series, a user holding assets across multiple series cannot be represented by a single shares value. Taking requests denominated in shares per series would force a user to submit multiple requests when redeeming more than they hold in a given series, and consolidation would require separately preserving historical price-per-share information while redeeming from the lead series, adding implementation complexity and security risk. Taking requests denominated in assets solves this, since the implementation only needs to compute the user's asset proportion across all series.
Why outstanding series are consolidated
During a sustained period of poor vault performance, a new series can be created for every new batch, causing the number of outstanding series to grow rapidly. Too many series can push the implementation that processes them past the block gas limit, leaving the vault unable to operate, and it also clutters the NAV/AUM sheets a traditional fund manager pulls for accounting reports across multiple series. Once the lead series reaches a new highwater mark, every outstanding series has, by that point, also reached that new highwater mark, meaning each user has already paid their rightful performance fee; consolidating at this point resolves both the gas limit problem and the reporting problem at once.
Backward incompatibility with ERC-4626 and ERC-7540
ERC-8113 is not backward compatible with ERC-4626 or ERC-7540. On the ERC-4626 side, totalAssets, convertToShares, and convertToAssets all additionally require a seriesId input, and redeem must change its input from shares to assets. On the ERC-7540 side, requestRedeem's input must change from shares to assets.
A proposal that has not yet been finalized
This document is a Draft-status proposal created on 2025-12-25. Discussion on Ethereum Magicians is still ongoing, and the specification may change or be discontinued.
Things to watch out for
- Risk of errors from complex fee calculations: Yield-bearing vaults can have multiple layers of fixed and variable costs applied before the performance fee, which can cause a mismatch between the expected fee and the fee actually collected.
- Thorough verification and documentation required: Protocols must carefully analyze whether the accounting results from their implementation match expectations, and must clearly document every fee calculation method.