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
ref #8462 (comment)#8462 (comment)
While implementing VoteAuthorization as part of #8312, we needed access to the state to verify ProposalType against authorized ProposalTypes. For now there's no clean way to access the state (read-only should suffice) and validate certain authorization constraints. This will limit the granular authorizations and forces everyone to use just GenericAuthorization without any Msg specific limitations.
Allowing a way to read the state from authorization (inside Accept) would enable more freedom for users to make granular authorizations.
The text was updated successfully, but these errors were encountered:
after discussions with the security team we have opted to create an authorization account type via accounts. Users can extend the account whichever way they would like without needing to fork as well. No need to modify authz further
ref #8462 (comment) #8462 (comment)
While implementing
VoteAuthorization
as part of #8312, we needed access to the state to verifyProposalType
against authorizedProposalTypes
. For now there's no clean way to access the state (read-only should suffice) and validate certain authorization constraints. This will limit the granular authorizations and forces everyone to use justGenericAuthorization
without anyMsg
specific limitations.Allowing a way to read the state from authorization (inside
Accept
) would enable more freedom for users to make granular authorizations.The text was updated successfully, but these errors were encountered: