-
Notifications
You must be signed in to change notification settings - Fork 809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[arrow-vesting] Update Arrow-Vesting strategy to only count vested, unclaimed tokens #1388
Conversation
…elevant blocknumber
For your review too @thomasgarrison who is the project admin |
Tagging @BrassLion as he is the author of the strategy |
There are two active proposals that use this strategy, better to wait until they are closed, or even better if we can just create a new strategy https://snapshot.org/#/arrowair.eth/proposal/0xb8ec567d58521249365c2c6637ef6595c0ae4e6e9166e50d7dd07328f9777040 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I had a quick look at the new strategy and the logic makes sense to me.
Thanks guys, this all looks good to me. @ChaituVR We're all good to merge this whenever you're ready. Since it's a bug fix, we wouldn't mind doing it while the current proposals are live |
@thomasgarrison Does it change the voting power of existing voters? |
Yes. This is fixing a bug where voting power is being double counted if a voter has claimed $ARROW from a vesting contract. This is just now becoming an issue as cliffs have been reached. If that's problematic we can wait until the last proposal is done voting. I've asked everyone not to post any more proposals until this is merged in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see no open proposals now, so merging, Thanks for waiting ❤️
Previously this strategy counted all tokens sitting on a vesting contract, including claimed ones. This led to weird behaviors and double counting. The Arrow community tasked me with iterating this strategy to only count vested Arrow that can be claimed but is unclaimed. This way, used with the
balanceOf
ERC20 strategy in voting, the snapshots will allow members to vote their vested Arrow, even if unclaimed, and there won't be incorrect accounting regarding stake on votes.Shoutout to @daoio for the help.
Changes proposed in this pull request:
unclaimed
Arrow tokens in a vesting contract