Availability
The yield’s metadata does not set a KYC requirement for either vault.
Entering
The enter argument isamount, in the vault’s input token; an optional receiverAddress sends the share token to an address other than the signer. The yield’s status.enter is false while the vault has minting paused.
Exiting
Exiting does not return funds directly. The exit argument isamount (or useMaxAmount for the full position) and an optional receiverAddress; submitting it creates an on-chain redeem order rather than a withdrawal. The yield’s status.exit is false while the vault has redeem-order creation paused.
The order sits in an operator fill window (cooldownPeriod) of 3 days for both vaults. Once the operator fills it, the position exposes a CLAIM_UNSTAKED pending action; running it is the transaction that finally returns the input token to your address.
Position and balances
While subscribed, your address holds the vault’s share token and its price per share reflects accrued yield; reward claiming for that accrual is automatic. A redeem order in flight and a filled, unclaimed order both report as separate balances until you runCLAIM_UNSTAKED. The public balance types you see across this lifecycle are active (held shares), exiting (order pending fill), and withdrawable (filled, awaiting claim).
Yuzu is documented under RWAs because it is a tokenized-RWA yield engine, even though its yields carry
type vault. It is not duplicated under DeFi Vaults.Next steps
Discover yields
Filter and page through the yields enabled for your project.
Action lifecycle
Request, sign, and submit enter and exit actions, and run pending actions like
CLAIM_UNSTAKED.
