Vault Flush Implementation

Having the option of running DHW in an asynchronous manner, executing it separately for each of the Strategies, leads to users receiving their receipt tokens gradually.

To ensure deterministic outcomes, all deposits are pooled at the Vault level, pending a Vault Flush, before being sent to DHW for processing.

Simply put, a Vault Flush is a synchronization point and can be executed by any user, at which point the funds aggregated within a specific “Vault Flush” period are made available to DHW. Only once an existing Vault Flush has been synced can a new Vault Flush be requested, preventing a situation where two Vault Flushes have overlapping DHW indexes.

Last updated