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
Use case: A SubDAO manages a large portion of the treasury, how to they guarantee that they won't use those tokens to vote and take over the DAO?
Solution would be to have a DAO manage add limits on voting power (potentially setting it to zero in some cases). For example, a Development Foundation could have its voting power limited to give DAO members assurance that they won't use their tokens in governance again.
Need to do it mainly for the Token DAO voting contracts:
dao-voting-native-staked
dao-voting-token-factory-staked
dao-voting-cw721-staked
This is less relevant for membership DAOs IMO.
The text was updated successfully, but these errors were encountered:
Added 2 new macros for limitable voting modules
Added an error for LimitExceeded when attempting to stake more than allowed
Added test case for limits
Solution is optimistic hence the map instead of snapshotmap for limits, so reducing limit after a user has already staked will not be affected DA0-DA0#684
Also fixed some clippy errors
Use case: A SubDAO manages a large portion of the treasury, how to they guarantee that they won't use those tokens to vote and take over the DAO?
Solution would be to have a DAO manage add limits on voting power (potentially setting it to zero in some cases). For example, a Development Foundation could have its voting power limited to give DAO members assurance that they won't use their tokens in governance again.
Need to do it mainly for the Token DAO voting contracts:
dao-voting-native-staked
dao-voting-token-factory-staked
dao-voting-cw721-staked
This is less relevant for membership DAOs IMO.
The text was updated successfully, but these errors were encountered: