Fund Manager
Create Index
The Fund Manager calls the API endpoint to create a new index, with the following parameters:
Fee setting
FM wallet address (here they´ll recieve the fees)
The token which will be used as credential for the FM in order to change the asset weights and claim fees. (NFT)
List of tokens that will make up the index
Initial number of MTK minted
Token price.
The contract backend builds the "Create Index" transaction with the parameters mentioned above. This transaction creates a portfolio with the initial tokens deposit, the minimum LVC necessary to hold these different assets, and the NFT that identifies this portfolio. The initial MTK mint is paid to the FM.
The contract backend returns the unsigned transaction cbor to be signed by the Fund Manager.
Collect Fee
The Fund Manager calls the API endpoint to collect fees from Index, with the portfolio NFT policyId as parameter.
The contract backend builds the "Collect fees" transaction with the portfolio NFT policyId as parameter. This transaction creates an order that, when processed, will pay the accumulated fees to the FM.
The contract backend returns the unsigned transaction cbor to be signed by the Fund Manager.
Update the weights of the underlying assets in a Index.
The Fund Manager calls the API endpoint to update weights of the Index, with parameters: portfolio NFT policyId, and new token weights distribution.
The contract backend builds the "Update weights" transaction, with the parameters mentioned above. This transaction creates an order that, when processed, will update the weights information held in the portfolio.
The contract backend returns the unsigned transaction cbor to be signed by the Portfolio Manager.
*Disclaimer: On V1, rebalancing is done is this way, there´s is not way to add or remove the initial underlying assets of the Indexes. If FM wants to "remove" an asset, they´ll need to send it to 0%.
Following versions will allow adding and removing of the underlying assets.
Last updated