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

[Feature] Provide a way to show burned BSQ in a specific timeframe #3303

Closed
erciccione opened this issue Sep 20, 2019 · 5 comments
Closed

[Feature] Provide a way to show burned BSQ in a specific timeframe #3303

erciccione opened this issue Sep 20, 2019 · 5 comments

Comments

@erciccione
Copy link
Contributor

At the moment is not possible to know how many BSQ are burned in a determined time, but only the total burnt (which can be seen in "Fact & figures" -> "BSQ supply"). Would be nice to be able to check the amount for a specific timeframe, for example a month or a week, without having to dig the code.

@ripcurlx's suggestion on Slack:

Maybe we could add some time span setting (days, weeks, months) to the chart. But for detailed analysis an extension of the API would be the best thing to have.

@chimp1984
Copy link
Contributor

Agree. Some time selection (day, week, month, year) like in the trade statistics would be ok. Or a more sophisticated time selection with a range slider...

@niyid
Copy link
Contributor

niyid commented Sep 27, 2019

Hi @erciccione

Do you mean to replace the chart shown in the screenshot below with one that the time frame can be adjusted/selected?

Screenshot from 2019-09-27 02-36-00

@erciccione
Copy link
Contributor Author

@niyid That could be nice yes, but what i think would best is to implement @ripcurlx's suggestion about the API. But whatever will give us the possibility to check the burnt bisq in a given time frame will be appreciated.

@niyid
Copy link
Contributor

niyid commented Oct 3, 2019

Are these related?

#3292

@ghost
Copy link

ghost commented Feb 14, 2022

Seems like it was fixed in pr#5156 - @ripcurlx you could probably close this issue.

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

Successfully merging a pull request may close this issue.

5 participants