-
Notifications
You must be signed in to change notification settings - Fork 47
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 Request: Lending Rate History #42
Comments
@godfrey22, can you please detail a bit moire? Should the best lending rate for a given period be displayed only? Or are you suggesting it should be used in a certain way (and if yes how should it be used?) |
For instance, I can set the interval for 1 min. So that, in every minute (12:00, 12:01...) the best lending rate could be recorded in a csv maybe. If I set it to 1 hour, every hour(12:00, 13:00...) the best lending rate could be recorded. |
@godfrey22, ok thanks, it's still not very clear if you want to just display the best lending rate or you want to include this data for the bot to "adjust the lending rate much more efficient.". Do you have a proposal/suggestion on how you would like to have it done? The lending server already keeps track of the best return rates during the last 48 hours and uses this data in conjunction with the average loan holding time to calculate the best return rate. The average loan holding time is normally between 1-12 hours. As such, looking at data from several weeks/days back, has not much relevance. Surly you will be less efficient if you keep waiting for a better loan which may come in several days time. |
@dutu It will be great if it can display the best lending rate over time as a chart on the web interface. But I really hope it can display the rate in a wide range of time. |
@godfrey22, this would be out of scope of a lending bot, but certainly a nice feature to have and I will consider it for a next release. |
Hi, is it possible to record the best lending rate by a given interval, which can be set in the config?
The text was updated successfully, but these errors were encountered: