> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/onyx-protocol/general-flows/suggested-subscription-rounds.md).

# Suggested Subscription Rounds

There are no built-in rounds/epochs or other procedural requirements for handling deposits, redemptions, and fees, but there is a general procedure that should be followed:

1. Investors submit deposit requests and redeem requests ([flow](/onyx-protocol/general-flows/async-deposit-and-redeem.md))
2. Admin calculates requests to fulfill and triggers share value update
   1. update all asset rates via `ValuationHandler`
   2. update share value via `ValuationHandler` ([flow](/onyx-protocol/general-flows/share-value-update.md))
   3. transfer redeem (and fee) assets shortfall to `Shares`
3. execute deposit requests ([flow](/onyx-protocol/general-flows/async-deposit-and-redeem.md#fulfillment))
4. execute redeem requests (flow: see deposit requests)
5. (optional) distribute fees ([flow](/onyx-protocol/general-flows/fee-settlement.md#distribution))
6. withdraw assets surplus from `Shares` for asset management


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enzyme.finance/onyx-protocol/general-flows/suggested-subscription-rounds.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.