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

Show commission earned #135

Closed
3 tasks
faboweb opened this issue Nov 28, 2017 · 8 comments · Fixed by #2049
Closed
3 tasks

Show commission earned #135

faboweb opened this issue Nov 28, 2017 · 8 comments · Fixed by #2049

Comments

@faboweb
Copy link
Collaborator

faboweb commented Nov 28, 2017

I as a user
Want to see the amount of commission I earned
So that I stay engaged in holding atoms.

AC:

  • a user should be able to see how many rewards they have been issued from each validator they have delegated to
  • a user should be able to see a sum of the total rewards he has in all validators
  • rewards should update in the UI as they update

See following event for updates on rewards (taken from https://github.com/cosmos/cosmos-sdk/blob/develop/docs/spec/distribution/state.md):

dependencies: #209

@faboweb faboweb added feature low priority has been discussed, will be addressed later labels Nov 28, 2017
@faboweb faboweb mentioned this issue Nov 28, 2017
13 tasks
@jbibla
Copy link
Collaborator

jbibla commented Nov 28, 2017

delegators don't earn commissions. technically, they are issued "fee shares" for staking their Atom's.

  • a user should be able to see how many fee shares they have been issued from each validator they have delegated to.
  • we should display the approximate value of these fee shares

since this takes place on the client we should store it locally. in the event that there is a bug or the data is erased or disappears for any reason it is possible to query for this information. but we should store it locally by default.

if we need to calculate this — the math can be found in the gaia repo spec.

yo @rigelrozanski how'd i do? ✌️

@rigelrozanski
Copy link

Yes - each delegator receives fees shares, and are encouraged to withdraw their fee reward with a reasonable frequency. When withdrawing fees all fee shares they have accumulated must be withdrawn at once (backend requirement). Note that this is totally different from withdrawing atom provisions which are by default bonded, meaning that to withdraw them they must be unbonded. @jolesbi you did well - next thing you need to do is dig up the math from the spec! hehe I can help with this if you get stuck, there is a lot in there.

@jbibla jbibla added this to the Launch v1 milestone Feb 5, 2018
@jbibla jbibla added blocked ✋ issues blocked by other implementations/issues and removed low priority has been discussed, will be addressed later labels Feb 5, 2018
@jbibla jbibla mentioned this issue Feb 5, 2018
11 tasks
@NodeGuy NodeGuy removed this from the Launch v1 milestone Aug 9, 2018
@fedekunze fedekunze added discuss and removed blocked ✋ issues blocked by other implementations/issues labels Aug 28, 2018
@NodeGuy NodeGuy added this to the Staking 1.0 milestone Aug 30, 2018
@NodeGuy
Copy link
Contributor

NodeGuy commented Sep 3, 2018

next thing you need to do is dig up the math from the spec! hehe I can help with this if you get stuck, there is a lot in there.

Holy cow there's a lot in there, @rigelrozanski! Thanks for your offer of help. I see the cosmos/gaia repository is now deprecated in favor of cosmos-sdk. Would you please point us to the relevant document within cosmos-sdk (I can't find it) and extract for us the formulas we need?

@rigelrozanski
Copy link

@NodeGuy - PR just being finalized now - you can look at everything in this dir. (https://github.com/cosmos/cosmos-sdk/tree/rigel/piggy-bank-fee-spec/docs/spec/distribution)

*note don't bother looking in the WIP folder - that's a more complicated mechanism which will not be implemented for a while

@NodeGuy
Copy link
Contributor

NodeGuy commented Sep 4, 2018

Thank you. We'll take a look when the PR is merged.

@NodeGuy NodeGuy added blocked ✋ issues blocked by other implementations/issues and removed discuss labels Sep 4, 2018
@faboweb faboweb added the discuss label Sep 4, 2018
@faboweb faboweb self-assigned this Sep 4, 2018
@faboweb faboweb changed the title Commission earned SPIKE Commission earned Sep 4, 2018
@faboweb faboweb removed their assignment Sep 4, 2018
@faboweb faboweb changed the title SPIKE Commission earned Commission earned Sep 4, 2018
@rigelrozanski
Copy link

@NodeGuy
Copy link
Contributor

NodeGuy commented Sep 4, 2018

Thank you. Blocked by #1285.

@NodeGuy NodeGuy removed the discuss label Sep 4, 2018
@faboweb faboweb added epic and removed epic labels Sep 20, 2018
@faboweb faboweb changed the title Commission earned Show commission earned Sep 20, 2018
@faboweb faboweb added staking2 and removed staking1 labels Oct 2, 2018
@NodeGuy NodeGuy removed this from the Staking 1.0 milestone Oct 5, 2018
@faboweb faboweb removed the feature label Oct 17, 2018
@faboweb faboweb added fees and removed blocked ✋ issues blocked by other implementations/issues staking-2 labels Feb 17, 2019
@fedekunze fedekunze added the blocked ✋ issues blocked by other implementations/issues label Feb 19, 2019
@fedekunze fedekunze mentioned this issue Feb 22, 2019
5 tasks
@faboweb faboweb removed the blocked ✋ issues blocked by other implementations/issues label Feb 22, 2019
@fedekunze
Copy link
Contributor

see comments on #2010

faboweb added a commit that referenced this issue Jun 2, 2020
* fixed a bug where a single proposal would not load (#125)

* trigger ci

* fixed missing terra data source (#128)

* Fabo/fix missing terra db query (#130)

* fixed missing terra data source

* fixed missing query

* Fabo/fix failing staking query for terra (#132)

* fixed missing terra data source

* fixed missing query

* fix bech32 prefix in selfStake resolver

* linted

* Fabo/hide proposals on terra (#134)

* fixed missing terra data source

* fixed missing query

* fix bech32 prefix in selfStake resolver

* linted

* don't show proposals on terra
faboweb added a commit that referenced this issue Jun 2, 2020
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

Successfully merging a pull request may close this issue.

5 participants