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

Revenue Breakdown - Staking and Dapp history #12

Open
Gabriel-x42 opened this issue Jun 11, 2020 · 1 comment
Open

Revenue Breakdown - Staking and Dapp history #12

Gabriel-x42 opened this issue Jun 11, 2020 · 1 comment
Labels
bounty Issues with this designation will provide an x42 bounty to anyone who solves them. enhancement New feature or function requests

Comments

@Gabriel-x42
Copy link
Member

Describe the solution you would like:
A clear and concise reveneue tab added to the side of Server or expanded transaction history in a manner the user can break down how much he made with staking, specific dapps and other types of revenue that might come about. The system we have right now is somewhat simplistic and doesn't show the whole picture in detail.
In this manner users would be able to determine at a glance if a dapp is worth hosting after a certain period of time.

image

image

This change would also solve the sizing issue for the unlocked xServer UI.

@Gabriel-x42 Gabriel-x42 added the enhancement New feature or function requests label Jun 11, 2020
@Gabriel-x42
Copy link
Member Author

A bounty of 5000 x42 has been added to anyone who delivers the code for this function.
The pull request MUST be approved and merged before the bounty is paid.

@Gabriel-x42 Gabriel-x42 added the bounty Issues with this designation will provide an x42 bounty to anyone who solves them. label Jan 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty Issues with this designation will provide an x42 bounty to anyone who solves them. enhancement New feature or function requests
Projects
None yet
Development

No branches or pull requests

1 participant