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
Currently, we only check that the user's voting power is > 0 to allow voting on offchain spaces.
We should retrieve the minScore from the voteValidation property on offchain proposal, and set the minimum score for voting from it (onchain proposals will always have minScore = 0)
This score will be used in the votingPower composable/stores to determine whether a user can vote on a proposal, or create a space, and show the corresponding warning message
This feature will be based on #511 (extracted as the vote reason PR is heavy enough, and not restart the review process)
The text was updated successfully, but these errors were encountered:
wa0x6e
changed the title
feat: support custom minimum voting power score on offchain proposal voting
feat: support custom minimum voting power score when voting on offchain proposals
Aug 7, 2024
wa0x6e
changed the title
feat: support custom minimum voting power score when voting on offchain proposals
feat: support custom minimum voting power score when proposing/voting on offchain proposals
Aug 11, 2024
wa0x6e
changed the title
feat: support custom minimum voting power score when proposing/voting on offchain proposals
feat: support custom minimum voting power score when voting on offchain proposals
Aug 11, 2024
Currently, we only check that the user's voting power is > 0 to allow voting on offchain spaces.
We should retrieve the minScore from the
voteValidation
property on offchain proposal, and set the minimum score for voting from it (onchain proposals will always have minScore = 0)This score will be used in the votingPower composable/stores to determine whether a user can vote on a proposal, or create a space, and show the corresponding warning message
This feature will be based on #511 (extracted as the vote reason PR is heavy enough, and not restart the review process)
The text was updated successfully, but these errors were encountered: