There are two primary end users of the FNDZ Protocol: fund owners and retail users. The FNDZ Protocol is designed to have protections in place for both of these parties without being overly restrictive and rigid.
Fund owners are allowed to make asset exchanges via the IntegrationManager on behalf of the fund (e.g., a DAO fund owner can approve accounts to make exchanges on behalf of its funds)
A fund owner configures the rules of their fund: fees and policies, the denomination asset by which share price and performance are measured, the time-lock between shares actions (buying or redeeming shares) for a given user, etc. The fund owner exchanges assets in their fund for other assets via integration "adapters", e.g., KyberAdapter or CompoundAdapter . This is the primary way in which a fund owner can accrue value for their fund. A fund owner can also assign a couple other roles to help manage their fund:
- a migrator who can migrate the fund to the current release
- accounts that are allowed to make asset exchanges via the IntegrationManager on behalf of the fund (e.g., a DAO fund owner can approve accounts to make exchanges on behalf of its funds)
A fund can theoretically have unlimited depositors, who get exposure to a fund's performance by buying and redeeming fund shares. Shares are currently non-transferable between depositors (though they can be transferred within the protocol to pay fees).
Fund owners can opt in to use one or more policies and other configurable measures to protect their depositors where necessary. It is assumed that depositors will pay special attention to review the protective policies and protections in a particular fund before depositing. See "Known risks & mitigations" section.