> 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/contract-implementations/issuance.md).

# Issuance

## ERC7540LikeDepositQueue

Ordered queue for handling async deposits of a specific asset for shares. Partially compatible with ERC-7540.

Config:

* `asset` : the ERC20 token deposited in exchange for shares
* `minRequestDuration` : minimum time before a request is cancellable
* `depositRestriction` : deposit request restriction
  * `None` : no restrictions
  * `ControllerAllowlist` : in-contract allowlist for depositors

Usage:

* depositors create requests for specific amounts of `asset`
* `asset` amounts for pending requests are escrowed in the queue contract
* admins selectively execute requests; shares are minted to depositors, `asset` amounts of executed requests are moved to `Shares`

Notes:

* Charges entrance fee, if set on `FeeHandler`
* Request execution order and timing is at the discretion of admins
* Whether or not to execute specific requests is at the discretion of admins

## ERC7540LikeRedeemQueue

Ordered queue for handling async redemptions of shares for a specific asset. Partially compatible with ERC-7540.

Config:

* `asset` : the ERC20 token withdrawn in exchange for shares
* `minRequestDuration` : minimum time before a request is cancellable

Usage:

* redeemers create requests for specific amounts of shares
* shares amounts for pending requests are escrowed in the queue contract
* admins selectively execute requests; shares are burned from escrow, `asset` amounts are distributed to redeemers

Notes:

* Charges exit fee, if set on `FeeHandler`
* Request execution order and timing is at the discretion of admins
* Whether or not to execute specific requests is at the discretion of admins

## SyncDepositHandler

Immediate deposit of one asset for shares. One transaction, no request and no admin execution.

Config:

* `asset`: the ERC20 accepted for deposits. Set in `init` and not changeable. A different asset is a new handler.
* `depositorAllowlist`: an `IAddressList`. `address(0)` allows any depositor. A depositor who is not on the list reverts `DepositorNotAllowed`.
* `maxSharePriceStaleness`: `uint24` seconds since the last share-price update. `0` accepts only a price from the current timestamp. `type(uint24).max` disables the check (`MAX_SHARE_PRICE_STALENESS_DISABLED`). Any other value reverts `SharePriceStale` once the price is older than that.
* `postDepositHook`: called at the end of the deposit. `address(0)` disables it. A revert rolls back the whole deposit.

Usage:

* The caller submits `deposit(assetAmount)`, or `depositReferred(assetAmount, referrer)`.
* The handler checks the allowlist and the share-price age, prices the gross shares, then settles the entrance fee on `FeeHandler` when one is set.
* It mints the shares left after the fee to `msg.sender` and pulls the full asset amount from `msg.sender` into `Shares`.

Notes:

* Charges the entrance fee, if set on `FeeHandler`. A zero fee mints the full share amount.
* The handler must be a registered deposit handler so it can settle the entrance fee and mint shares.
* May not support irregular asset behavior, such as fee-on-transfer tokens.
* `setDepositorAllowlist`, `setMaxSharePriceStaleness`, and `setPostDepositHook` are `onlyAdminOrOwner`.

## SyncRedeemHandler

Immediate redemption of shares for one asset. One transaction, no request and no admin execution.

Config:

* `asset`: the ERC20 paid out. Set in `init` and not changeable. A different asset is a new handler.
* `maxSharePriceStaleness`: `uint24` seconds since the last share-price update. `0` accepts only a price from the current timestamp. `type(uint24).max` disables the check (`MAX_SHARE_PRICE_STALENESS_DISABLED`). Any other value reverts `SharePriceStale` once the price is older than that.
* `postRedeemHook`: called at the end of `redeem`. `address(0)` disables it. A revert rolls back the whole redemption.

Usage:

* The caller submits `redeem(sharesAmount)`.
* The handler checks the share-price age, then settles the exit fee on `FeeHandler` when one is set.
* It burns the gross shares from `msg.sender` and pays `msg.sender` the asset value of the shares left after the fee.
* The handler must be a registered redeem handler so it can settle the exit fee and burn shares.

Notes:

* Charges the exit fee, if set on `FeeHandler`. A zero fee pays the full amount.
* The payout asset must already be held by `Shares`.
* `setMaxSharePriceStaleness` and `setPostRedeemHook` are `onlyAdminOrOwner`.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.enzyme.finance/onyx-protocol/contract-implementations/issuance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
