Reporting & Disclosure10 min read
MB
Editorial Team
·November 14, 2026

Do Pending ERC-7540 Redemptions Count as Outstanding Shares?

ERC-7540 requestRedeem share handling is the choice each asynchronous vault makes between locking redeemed shares in the vault or an escrow until the request is Claimable or Claimed, and burning them at the moment of the request. Both are compliant, so totalSupply() alone does not show whether pending redemptions are still outstanding. Any report built on the share token has to identify the model first.

TL;DR — Key Takeaways

  • ✓The rule: ERC-7540 lets a vault lock redeemed shares until Claimable or Claimed, or burn them at requestRedeem. Shares must leave the owner at the request and be burned by the time the request is Claimed.
  • ✓The effect: In a lock model, pending redemptions stay in totalSupply and sit at an escrow address. In a burn-at-request model, totalSupply falls before the fund has priced or paid the redemption.
  • ✓A third timing: In code reading of Centrifuge at commit 72a8acfd, shares move to the pool escrow at request and are burned at revocation, when the payout is also reserved, before the investor claims.
  • ✓The fix: Shares outstanding, NAV per share, holder counts and voting snapshots read from the token need a model check first, then an adjustment from the per-controller pending and claimable views.

Ready to get started?

Join others who are already using our platform.

Do Pending ERC-7540 Redemptions Count as Outstanding Shares?

Does a pending ERC-7540 redemption still count in totalSupply?

It depends on the vault. ERC-7540 allows shares under a pending redemption to be locked, which keeps them in totalSupply, or burned at requestRedeem, which removes them at once. Both choices are compliant with the Final standard.

The specification fixes only the two ends of the window. At the request, the shares must leave the owner's custody. By the time the request is Claimed, they must be burned. Between those points the vault picks the moment supply falls: at the request, when the request becomes Claimable, or at the claim. A reporter reading totalSupply() from two compliant vaults with identical redemption queues can therefore get two different numbers for the same economic position.

“shares MAY be temporarily locked in the Vault until the Claimable or Claimed state for accounting purposes, or they MAY be burned immediately upon requestRedeem. In either case, the shares MUST be removed from the custody of owner upon requestRedeem and burned by the time the request is Claimed.”

ERC-7540 specification, requestRedeem section (status: Final)

This matters because shares outstanding is the denominator of NAV per share and the base of most investor reporting. The broader set of reports a tokenized fund owes its investors is covered in the guide to RWA investor reporting and disclosure requirements. This page deals with one input to those reports: how many shares exist while redemptions are waiting.

What does each model do to share-count metrics?

The lock model keeps pending shares in supply at an escrow address; the burn model removes them at the request. Five common metrics read differently under each, and the Centrifuge timing adds a third column between the two.

Metric read from the tokenLock until Claimable or ClaimedBurn at requestRedeem (spec only)Centrifuge: lock, burn at revocation
totalSupply()Includes pending redemptionsExcludes them from the request onwardIncludes them until the epoch is revoked
NAV per shareDenominator matches a NAV that still holds the assetsDenominator falls before the assets leave the NAVBurn and payout reservation happen together
Holder countRedeeming investor drops out; escrow appears as a holderRedeeming investor drops out; no escrow holderPool escrow appears as a holder
Largest holderOften the escrow, unless excludedUnaffected by the queueOften the pool escrow, unless excluded
Voting record dateEscrow holds the weight, not the investorNobody holds the weightEscrow holds the weight until revocation

The “spec only” label is deliberate. We did not identify a production vault that burns at the request, so that column describes what the standard permits, not a deployment we have read. The lock column covers vaults that burn at Claimable or at Claimed; for share counting the two differ only in which state ends the window.

The table assumes the report reads balances from the right contract. In ERC-7575 vaults the share token can be a different address from the vault entry point, which is covered in which contract holds an ERC-7575 fund position. Everything here applies to whichever contract that check identifies.

When does Centrifuge burn redeemed shares?

At revocation, in code reading at commit 72a8acfd. requestRedeem moves the shares to the pool escrow, and they stay in totalSupply until the pool manager revokes an approved epoch, which burns them and reserves the payout in one step, before any investor claims.

The path runs through three contracts. BaseVaults.requestRedeem checks the owner's balance, emits RedeemRequest and calls AsyncRequestManager.requestRedeem. That function checks that both owner and controller may transfer to the escrow hook, adds the amount to the controller's pendingRedeemRequest, and calls spoke.transferSharesFrom(..., owner, escrow, shares). The holder's balance falls; supply does not. A code comment notes that the old transfer flag is ignored because “shares are always transferred to the pool escrow”.

Later, the hub's BatchRequestManager revokes shares for an epoch and sends a RevokedShares callback with one aggregate share amount. AsyncRequestManager.revokedShares reserves the payout assets, pulls the shares out of the pool escrow and calls spoke.revoke, which burns them through the share token registrar. When the investor later calls redeem or withdraw, the manager pays out reserved assets with withdrawReserved. No shares are burned at the claim.

“Earmark the redemption payout: reserving removes the assets from the hub-accounted holding atomically with the share burn, preventing NAV desync. The escrow update is deferred to claim.”

AsyncRequestManager.revokedShares, centrifuge/protocol @ 72a8acfd

Two Centrifuge details that affect counting

  • The burn is per epoch, the Claimable state is per investor. Revocation burns one aggregate amount. Each investor's pendingRedeemRequest drops only when a later notifyRedeem on the hub sends that investor's FulfilledRedeemRequest callback. In code reading, there can be a window where the shares are already burned but still appear as pending for the investor. Adding the sum of pending views back to totalSupply in that window counts them twice.
  • The pool escrow holds more than redemptions. issuedShares mints new deposit shares to the same pool escrow, where they wait until each investor claims, and cancelled redemption shares return from it through claimCancelRedeemRequest. The escrow balance is therefore not a measure of the redemption queue alone.

We read the code at AsyncRequestManager.sol, Spoke.revoke and BatchRequestManager.notifyRedeem; we did not run the test suite or observe a live epoch. How Centrifuge itself excludes the escrow from holder reporting was not checked.

Revocation is also the step where Centrifuge fixes the payout price. What value the redemption receives, and whether it earns yield while it waits, is the subject of whether a pending ERC-7540 redemption still earns yield. This page stays with the share count.

What happens to NAV per share when supply falls first?

If shares are burned before the redemption assets leave the fund, NAV divided by totalSupply overstates the per-share value. In an illustrative fund with 1,000,000 shares and a 10,000,000 USD NAV, a 10% pending redemption moves the naive figure from 10.00 to 11.11.

The numbers below are illustrative, not taken from any vault. One investor requests redemption of 100,000 shares. The fund has not yet priced or paid the request, so the assets that will fund the payout are still in the NAV.

State (illustrative)NAV (USD)totalSupply()NAV / totalSupply
Before the request10,000,0001,000,00010.00
Lock model, request pending10,000,0001,000,00010.00
Burn at request, request pending10,000,000900,00011.11
After payout, any model9,000,000900,00010.00

The burn model is not wrong; the naive division is. In a burn-at-request vault, the NAV used for a per-share figure has to exclude the pending redemption's claim on the assets, or the denominator has to add the pending shares back. Centrifuge avoids the gap by design: the comment quoted above ties the burn to the reservation of the payout, so supply and the hub-accounted holding fall in the same step.

ERC-7540 does not help a reporter close the gap from the vault's price functions. previewRedeem and previewWithdraw must revert for asynchronous redemptions, and the assets paid on redeem “MAY NOT be equivalent to the value of convertToAssets(shares) at the time of Request”.

“The view methods for viewing Pending and Claimable request states (e.g. pendingDepositRequest) are estimates useful for display purposes but can be outdated.”

ERC-7540 specification, Security Considerations

Why do holder lists and voting snapshots diverge from the register?

In both models an investor who asked to redeem everything holds zero tokens, yet keeps an economic claim until paid. The on-chain holder list drops that investor at the request; the fund register may keep them until settlement.

The spec's custody rule makes this true for every compliant vault: the shares leave the owner at requestRedeem whether they are locked or burned. The difference is where the shares go. In a lock model a single escrow or vault address now holds the pending shares of every redeeming investor, so it can become the largest holder in a top-holder report and adds one address to a holder count. In a burn-at-request model nothing replaces the investor on-chain.

A voting snapshot taken from token balances inherits the same split. Under a lock model the escrow carries the voting weight of redeeming investors; under a burn model that weight disappears. Neither result answers whether a redeeming investor should vote, which is a question for the product documents. How to fix the record date itself is covered in how tokenized funds preserve a voting record date.

The controller field adds one more mapping. A request is tracked by requestId and controller, and the controller need not be the owner who gave up the shares. A register that credits pending redemptions back to an investor has to decide whether it credits the owner or the controller, and record that choice.

How do you tell which model a vault uses?

Check the Transfer event in a requestRedeem transaction: a transfer to the zero address means burn at request, a transfer to the vault or an escrow means lock. Then find the later transaction where the escrow sends shares to the zero address, because that is when supply falls.

  • Step 1: read the request transaction. Find a RedeemRequest event and the share token Transfer in the same transaction. Record the destination address.
  • Step 2: if it is an escrow, find the burn. Search for transfers from that escrow to the zero address and match them to the vault's lifecycle. In Centrifuge they appear in the revocation callback, alongside a Revoke event from the spoke, not in the investor's claim.
  • Step 3: confirm in the code. Read requestRedeem and the fulfilment and claim paths for a burn or a transfer. Events show one transaction; the code shows every path, including cancellations that return shares from escrow.
  • Step 4: list every address that holds non-investor shares. Vault, escrow and any manager contract that receives shares in transit. These are the addresses to exclude from holder reports.

Record the answer per vault and per contract version. An upgrade can change the path, and the general lifecycle checks for an asynchronous vault in whether tokenized funds should use ERC-7540 async vaults apply before any of this.

Which adjustments should a share-count report apply?

Start from a written policy on whether pending redemptions count as outstanding, then adjust totalSupply by model. The standard has no aggregate pending view, so the adjustment needs a sum of pendingRedeemRequest over every controller found in RedeemRequest events.

ModelIf pending redemptions count as outstandingIf they do not
Lock until Claimable or ClaimedUse totalSupply; exclude the escrow from holder lists and credit its shares back to controllersSubtract the sum of pending and not-yet-burned claimable shares
Burn at requestAdd the sum of pendingRedeemRequest back to totalSupplyUse totalSupply; exclude the pending claim from NAV
Centrifuge (code reading)Before revocation, as lock; after revocation the shares are gone and the payout is reservedSubtract pending shares not yet revoked; do not subtract revoked shares again

Two cautions apply to every row. The pending and claimable views are estimates that can be outdated, so reconcile them to the fund register's redemption queue rather than treating them as the record. And escrow balances can hold deposit shares and cancelled redemptions as well as pending ones, so derive the queue from the views and events, not from the escrow balance.

Who this is for, and when it breaks

It is for fund administrators, transfer agents and data providers who compute shares outstanding, NAV per share, holder counts or voting records from an ERC-7540 share token. It is not a guide to the redemption price. The method breaks when the vault is upgraded to a different burn path, when shares are held in a separate ERC-7575 token that the report does not read, and when the register and the chain use different identifiers for the same investor.

Frequently Asked Questions

Does ERC-7540 require shares to be burned when a redemption is requested?

No. The specification says shares MAY be temporarily locked in the vault until the Claimable or Claimed state, or MAY be burned immediately upon requestRedeem. It requires only two things: the shares must leave the owner's custody at the request, and they must be burned by the time the request is Claimed. A compliant vault can therefore reduce totalSupply at request, at fulfilment or at claim.

Why does totalSupply differ between two ERC-7540 vaults with the same redemptions?

Because the standard leaves the burn timing to each vault. In a lock model, shares under a pending redemption stay in totalSupply and sit at the vault or an escrow address. In a burn-at-request model, totalSupply falls as soon as the investor asks to redeem, before the fund has priced or paid anything. The same economic position produces two different supply numbers.

When does Centrifuge burn shares that are being redeemed?

In code reading at commit 72a8acfd, at revocation. requestRedeem transfers the shares from the owner to the pool escrow, so they stay in totalSupply. When the pool manager revokes an approved epoch, the RevokedShares callback moves the shares out of the escrow and calls spoke.revoke, which burns them and reserves the payout in the same step. The investor's later claim only pays out reserved assets.

Does an investor with a pending redemption appear in on-chain holder lists?

Not by token balance. In both the lock and burn models the shares leave the owner's custody at the request, so an investor who asked to redeem everything holds zero tokens. The investor still has an economic claim until paid. In a lock model the escrow or vault address shows up as one large holder instead, and has to be excluded or mapped back to the controllers.

How can a reporter tell whether a vault locks or burns redeemed shares?

Look at the Transfer event in a requestRedeem transaction. A transfer from the owner to the zero address means burn at request. A transfer to the vault or an escrow address means lock. Then find the later transaction where that escrow sends shares to the zero address: it marks when supply falls. Reading the requestRedeem implementation confirms what the events show.

Ready to get started?

Join others who are already using our platform.