Skip to content
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

Forecast rewards collection on stake and extend #279

Closed
micahalcorn opened this issue Jul 26, 2022 · 2 comments
Closed

Forecast rewards collection on stake and extend #279

micahalcorn opened this issue Jul 26, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request P1 Large amount of significant user impact, a meaningful feature is broken ui/ux Workd that requires design and product overview
Milestone

Comments

@micahalcorn
Copy link
Member

To address #265 and #266, we're going to try informing the user that rewards will be collected when a new stake is created or an existing one is extended. If we continue to hear complaints from users after trying this approach, we will consider contract changes at that time.

There are a couple of different ways I'm thinking we could handle this.

  1. We could pop up a modal after the user clicks "Stake" or "Extend". The modal would explain that # OGV will be collected at the same time as the proposed transaction. We could also include an optional checkbox along the lines of "Got it, don't show me this again". My concern is that the modal would introduce an extra click and add friction to a high-value action. It's also likely that the user will check the box and then be just as confused as I was next time she comes back to stake/extend and doesn't see the modal.

  2. We could add an alert above the button explaining what will happen. The user isn't as likely to read this as she would an annoying modal, but it also wouldn't be as necessary to hide it for repeat uses and it wouldn't introduce an extra click.

Something like this 👇 (but prettier)

Screen Shot 2022-07-25 at 11 44 07 PM

@micahalcorn micahalcorn added enhancement New feature or request ui/ux Workd that requires design and product overview P1 Large amount of significant user impact, a meaningful feature is broken labels Jul 26, 2022
@micahalcorn micahalcorn added this to the Sprint 31 milestone Jul 26, 2022
@micahalcorn
Copy link
Member Author

micahalcorn commented Jul 26, 2022

I don't think we need to introduce something like this for the claim experience. It's possible that a user could claim veOGV from being an OUSD holder, then later claim and stake OGV from being an OGN holder. I believe that would cause some rewards to be collected, but this is probably an edge case. The same would be true of someone who buys OGV, stakes it, and then claims and stakes OGV.

@tomhirst tomhirst self-assigned this Jul 26, 2022
@tomhirst
Copy link
Contributor

For this use case, I think the info message above the button is both sufficient and the best option in terms of user experience.

If we want to guarantee that the message is read we could add a checkbox to proceed, though I'd prefer to avoid adding an additional click if we can.

I'll address this issue by adding the info message and we can further iterate based on additional user feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P1 Large amount of significant user impact, a meaningful feature is broken ui/ux Workd that requires design and product overview
Projects
Status: Done
Development

No branches or pull requests

2 participants