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
DAO DAO voting for natively staked coins can be more powerful, if we make an SDK module that just listens for all delegate, undelegate, and redelegate hooks. Then on each of these hooks, calls a sudo message to a pre-configured contract.
This would let us have a more powerful wrapper for governance! They could now compute the current semantic of "Voting power = stake at end of voting period", with no iteration at end time for instance. (The only iteration needed, would be to reclaim state, but we can have a separate process for that. Espec. if we make a gas token like dynamic)
Or we could switch semantics to "voting power = stake at beginning of voting period", or my favorite "voting duration = k days. Voting power = sum of stake_at_time_i * voting decision_at_time_i for times in the final day of voting" (to protect against last second vote attacks)
If we make an SDK module for communicating stake change events during the voting period, then we can unlock all of these capabilities for DAO DAO voting.
The text was updated successfully, but these errors were encountered:
DAO DAO voting for natively staked coins can be more powerful, if we make an SDK module that just listens for all delegate, undelegate, and redelegate hooks. Then on each of these hooks, calls a sudo message to a pre-configured contract.
Woah. This would be amazing. I think it would be useful for many other things as well!
DAO DAO voting for natively staked coins can be more powerful, if we make an SDK module that just listens for all delegate, undelegate, and redelegate hooks. Then on each of these hooks, calls a sudo message to a pre-configured contract.
This would let us have a more powerful wrapper for governance! They could now compute the current semantic of "Voting power = stake at end of voting period", with no iteration at end time for instance. (The only iteration needed, would be to reclaim state, but we can have a separate process for that. Espec. if we make a gas token like dynamic)
Or we could switch semantics to "voting power = stake at beginning of voting period", or my favorite "voting duration = k days.
Voting power = sum of stake_at_time_i * voting decision_at_time_i
for times in the final day of voting" (to protect against last second vote attacks)If we make an SDK module for communicating stake change events during the voting period, then we can unlock all of these capabilities for DAO DAO voting.
The text was updated successfully, but these errors were encountered: