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

[1.5][happyconcepts] More intuitive vesting BTS stats #294

Closed
robrigo opened this issue Aug 19, 2017 · 18 comments
Closed

[1.5][happyconcepts] More intuitive vesting BTS stats #294

robrigo opened this issue Aug 19, 2017 · 18 comments
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design
Milestone

Comments

@robrigo
Copy link

robrigo commented Aug 19, 2017

The stats shown under the "Membership" tab are confusing to me. I would expect "Pending vested fees" to match the amount of BTS I have vesting from my referee's use of the system; instead it is 0.

screen shot 2017-08-19 at 10 21 01 am

On the "Vesting balances" page, there are more accurate stats. Should the stats be removed from "Membership" entirely? Can we improve the intuition of these stats and unify them under one place? Perhaps there should be two tabs, one for worker pay stats and another for referral pay stats?

screen shot 2017-08-19 at 10 21 27 am

@wmbutler wmbutler added this to the 170914 milestone Aug 21, 2017
@wmbutler
Copy link
Contributor

wmbutler commented Aug 21, 2017

Setting this as a question until we have a bit more clarification from @svk31. Is Pending vested fees supposed to be equal to Available to Claim?

If so, we should make these labels the same, if not, we need some tool tips to help users understand the difference.

@wmbutler
Copy link
Contributor

@svk31 Need help understanding this so I can offer a solution.

@wmbutler wmbutler changed the title More intuitive vesting BTS stats [1] More intuitive vesting BTS stats Aug 31, 2017
@happyconcepts
Copy link
Contributor

Unless this is for @svk31 ...

I would be happy to scope this for clarification as I dive into graphene this weekend.

Looks like cashback_vb, or pending_fees, or pending_vested_fees I will dive deeper ....

@wmbutler
Copy link
Contributor

wmbutler commented Sep 4, 2017

You've got it.

@wmbutler wmbutler changed the title [1] More intuitive vesting BTS stats [1][happyconcepts] More intuitive vesting BTS stats Sep 4, 2017
@wmbutler
Copy link
Contributor

@happyconcepts we are about to close out this Sprint. Will you have this complete today or tomorrow?

@calvinfroedge
Copy link
Contributor

@happyconcepts @wmbutler I think this issue needs more clarification, i.e. reproduction steps, and may some input from @svk31 on where the numbers come from

@wmbutler
Copy link
Contributor

Moving to @calvinfroedge since Sprint is being released tomorrow and no communication from @happyconcepts

@wmbutler wmbutler added [3] Bug Classification indicating the existing implementation does not match the intention of the design and removed question labels Sep 13, 2017
@wmbutler wmbutler changed the title [1][happyconcepts] More intuitive vesting BTS stats [1] More intuitive vesting BTS stats Sep 13, 2017
@calvinfroedge calvinfroedge removed their assignment Sep 13, 2017
@wmbutler wmbutler modified the milestones: 170914, 171001 Sep 13, 2017
@wmbutler wmbutler changed the title [1] More intuitive vesting BTS stats [1.5] More intuitive vesting BTS stats Sep 13, 2017
@happyconcepts
Copy link
Contributor

@wmbutler @calvinfroedge Can I stay with this one? The testnet was bugging on me so I couldn't check the worker vesting yet ... but I got it up yesterday and there is a reset tomorrow on testnet.

@happyconcepts
Copy link
Contributor

happyconcepts commented Sep 14, 2017

I now have a few referral test accounts and I am digging into it today to see if graphene::wallet::vesting_balance_object_with_info is picking up witness and worker balances too.

Different data sources for Pending vested fees and Available to Claim seems appropriate as far as the user experience is concerned. Also this reference client may have been showing two cases, pulling a single vesting balance (for referrals and fees) and pulling an array of multiple balances in the cases where a user has worker pay vesting as well as fee cashbacks vesting, they can have two different vesting balances and schedule

Any ideas on "Intuitive" from a UX perspective please? Of the two types of vesting schedules (coin/days and linear/cliff) it appears that only advanced users are going to experience linear vesting in action (for balances due to witness and worker amounts).

Perhaps having a "basic" display and an "advanced" display is appropriate to keep the UX easier on the casual user?

@robrigo what would you expect to see, for example?

@robrigo
Copy link
Author

robrigo commented Sep 14, 2017

I think one helpful improvement from the current situation would be adding a hover-over tooltip that explains what each field means. i.e. what are pending fees vs. pending vested fees vs. vesting balance amounts.

The discoverability of these two pages is rather low IMO, and I believe it would be better overall if all of the stats were combined into one view, instead of showing "confusing" stats on the membership view. This is all my own opinion, of course. :)

@wmbutler
Copy link
Contributor

I think this issue just wants to display the same values if they represent the same thing. Let's keep it simple.

@happyconcepts
Copy link
Contributor

@wmbutler makes sense to me; let me fix this bug so it is consistent in both screens of the UI and get you a PR later today, probably missed Sigve's auto build for 9-14 though.

@robrigo I like the thought; the merrier it is in the lifetime member screen, the more lifetime members there will be imo. Perhaps the Tables rework or a "feature" issue in the near future - thanks for your feedback.

@wmbutler
Copy link
Contributor

You did miss the 9/14 build. We will add this into 10/01

@wmbutler wmbutler changed the title [1.5] More intuitive vesting BTS stats [1.5][happyconcepts] More intuitive vesting BTS stats Sep 14, 2017
@happyconcepts
Copy link
Contributor

thank you @wmbutler and good morning

@happyconcepts
Copy link
Contributor

I suggest that for clarity we should change the name of "Pending vested fees" to something else, primarily because these are actually instantly available cashback "fees" that are not subjected to the vesting calculations at all. Yes they are available fees, which is like vested fees, but they are not vested fees.

According to the relevant graphene documentation about Pending vested fees the "Pending vested fees" on the Member screen is not supposed to be equal to Available to Claim on the Vesting screen.

How about "Pending Cashback Fees" or something similar? If I understand it, this data is max TTL of 2 minutes i.e. the maintenance interval so most of the time it will always show as 0.

happyconcepts added a commit to happyconcepts/bitshares-ui that referenced this issue Oct 1, 2017
@wmbutler
Copy link
Contributor

wmbutler commented Oct 1, 2017

@svk31 did this get included in 171001?

@svk31
Copy link
Contributor

svk31 commented Oct 2, 2017

No, cause the PR doesn't really make things any clearer imo.

@svk31 svk31 modified the milestones: 171001, 171015 Oct 2, 2017
@happyconcepts
Copy link
Contributor

  1. This "Pending Vested Fees' showing in the Membership UI is different; the value is independent of the vested balance/claimable value on the Vesting UI. These fees are pending, and they will be available once processed upon the next maintenance interval. But they are not vested.

From the documentation: graphene::chain::account_statistics_object::pending_vested_fees

these fees will be paid out as pre-vested cash-back (immediately available for withdrawal) rather than requiring the normal vesting period
So to call them "vested" in the UI is causing confusion.

  1. What is the next step? I guess what I did was only to intentionally fix it quickly so that you could focus on more important bugs.

svk31 added a commit that referenced this issue Oct 13, 2017
* Update README.md

* Issue 315 - Add Chart Clamp To Settings Dropdown (#373)

* Add Chart Clamp To Settings Dropdown

* Removed Unused Variable

Merging as is and then we'll see about handling the redraw bug in the next sprint.

* More intuitive vesting stats in UI - issue #294

* pending_vested_fees->pending_immediate_fees

* Fees terminology

I took a stab at this.

* Remove fees_pending and fees_vested text, update fee texts #294
@svk31 svk31 closed this as completed Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design
Projects
None yet
Development

No branches or pull requests

5 participants