When I deploy the dao with the
DaoFactory, my second plugin relies on the address of the first plugin... What do you recommend?
Should I deploy the second plugin separately after or is there a way to precompute the address of the first plugin and pass it for the setup of the second plugin in the
createDAO plugin settings?
The token is itself an index that represent the vault, buy the DAO token-> buy proportially the dao vault tokens.
mint function in this case interacts directly with the DAO as it mints new tokens, buys the underlying DAO tokens and stores them in the DAO. The user can than redeem/burn the token and get back/sell the underlying tokens face value.
The DAO becomes itself an index, like an ETF or a decentralised fund.
The token is itself strictly related to the DAO and should be core part of its infrastructure and security.
I am not sure if it is a good idea to separate the logic, since the token itself is core part of the voting plugin to take decision on how to manage the DAO index composition.
The above all implies that the token itself stores the dao index asset composition and weights and it is also responsible to edit the latter(swap asset and update assets struts) when those kind of proposals are passed.