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

Displaying pool.near farm APY is confusing for end users and incorrect #2951

Open
3 tasks
AngelBlock opened this issue Oct 12, 2022 · 2 comments
Open
3 tasks

Comments

@AngelBlock
Copy link

Story

This is our feedback from chatting with a few users, after we launched the new pool.near validator with farm a week ago, details here: https://link.medium.com/4NeqSjs0Otb

A user goes to Staking in Wallet, select validator and view the details:
Screenshot 2022-10-12 at 10 10 10

User sees 10.57% APY or other and assumes its the network APY, effectively users thinks its NEAR rewards APY,

If APY is 0%, as shown below, which is, for all the pool.near pools with no farming, user thinks they won't make any rewards and refrain from staking to that validator:

Screenshot 2022-10-12 at 10 17 20

Since the goal is to eventually move all the validators to new poolv2, or at least encourage new validators to use v2 pools as oppose to v1, I think the UX of how we show rewards needs to be redesigned.

Also, this message is not exactly right, validator DOES grant rewards in NEAR (5% fee)
Screenshot 2022-10-12 at 10 18 24

Suggestions:

Redesign the page:

  • add NEAR rewards APY, calculated based on validator fee
  • add separate farming sections, with clear explanation (or link to) about farms, and show calculation of farm APY
  • remove message saying validator grants staking rewards in other then near for pools <100% fee or change it.

User feedback example:

Screenshot 2022-10-12 at 10 26 34

Screenshot 2022-10-12 at 10 24 22

@paulmattei
Copy link

Is it possible to get an update on this?

@chefsale
Copy link
Contributor

Bumping this issue, as many people have asked us why the APY is zero since launching the pool. @MaximusHaximus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants