You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The list of proposals from a dao is filtered on the proposal details field and if isMinion exists. There also needs to be a way to tell which minion in the case where a DAO has multiple minions.
The text was updated successfully, but these errors were encountered:
In minion submitted proposal we have minion address as applicant so when we get list of proposals and see details field isMinion == true we can check for applicant address and based on that figure out which minion sent it. We can also use proposer field in proposal struct to check for it in case later on we want to specify applicant as actually user who created minion action from UI.
But that raises another question. Is there any specific reason behind keeping minion as applicant in proposals? it can cause issues later on when we want to automate grants proposal through a minion. If we keep minion as applicant then minion also needs to implement token transfer logic (pull pattern).
The list of proposals from a dao is filtered on the proposal details field and if isMinion exists. There also needs to be a way to tell which minion in the case where a DAO has multiple minions.
The text was updated successfully, but these errors were encountered: