You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A zero-asset redemption from a delisted holder stays stuck and keeps its epoch open #445
A redemption that prices to zero assets settles by returning its shares at claim. If the holder is delisted, or the compliance rules refuse the transfer, before they claim, claim_redeem reverts with HolderNotEligible, because returning the shares needs an eligible holder. cancel_redeem reverts with AlreadyPriced. The shares stay in the vault's escrow until the holder is listed again or the vault winds down. Meanwhile the epoch keeps one open redemption and never reconciles, so its share dust stays pending and its cash dust stays counted as owed. The fix planned for #434 releases cash dust once every request in the epoch has settled, which never happens here.
Steps to reproduce
A holder requests to redeem shares worth less than one unit of the deposit asset.
The epoch is priced, and the request rounds down to 0 assets.
Compliance delists the holder.
The holder calls claim_redeem: it reverts with HolderNotEligible.
The holder calls cancel_redeem: it reverts with AlreadyPriced.
Expected vs actual behavior
Expected: the request settles, and its epoch reconciles. Actual: both calls revert, the shares stay escrowed, and the epoch keeps one open redemption.
Priority
Medium — rated Low on its own, but it has to ship with the fix for #434
Additional context
Found by the automated security sweep of tag tranche2 (commit db90b95), finding P0A. The path: redeem::claim → return_shares → deliver → guards::eligible_to_receive. A possible fix, untested: when the payout is zero and the holder cannot receive shares, burn the escrowed shares, as a wind-down claim already does.
Activity