Architecture
Last updated
The vault sits between the party requesting redemption and the yield strategies that hold the bulk of the capital. An instant-settlement module maintains an immediately accessible reserve, and risk controls bound every settlement.

The holder or application that submits an atomic redemption request and receives the reference asset in the same transaction.
This is deliberately generic: it can be an end user redeeming directly, a payments integrator settling a transaction, or any contract that needs instant liquidity on demand.
The tokenized cash account. It holds the share-pricing logic, converts shares to reference assets against current NAV, and orchestrates the liquidity recall and payout atomically.
Curator-managed allocations that hold the majority of vault capital in capital-efficient positions. Capital is deployed automatically when idle and recalled automatically when a redemption needs it.
A liquidity layer that keeps reserves in highly liquid lending markets (Aave and Morpho) where they can be withdrawn synchronously within the settlement transaction. The module is drawn down to fund settlement and topped back up when surplus liquidity returns.
Price feeds and guardrails (oracle price guards, per-transaction rate limits, redemption fee caps, and spread bounds) that bound every settlement and protect the vault under high-velocity redemption flow.
Refer to this link for the on-chain implementation contract on Ethereum.
Last updated
