Thomas

Fair enough about keeping the BNB and the potential non-blacklisted currencies. What about we add a `*` next to each blacklisted currency in the list, and a new line at...

I don't think it's making the output hard to read, but if it is, we could return this output only when using a special parameter, like `/balances noblacklist` or something...

I understand your points, and I agree that it will be hard to match all the corner cases. I guess I'll simply write my own external python script that will...

Actually I think I found the valid way to cover most -if not all- cases efficiently. To get the real value of the balance dedicated to trading, I only has...

I would love to have an SQL table that keep the open balance and close balance value for each day (in stake currency). That would allow the user to get...

I'm currently executing it at midnight UTC, as I want all the data to be "timezone-neutral". I've also made a security mechanism that keeps retrying to generate the performances of...

> well if you're interested in integrating this as base functionality (the `/daily` report is clearly lacking ..), i'd for sure not argue laughing Yeah, I might take this task...

Do we agree that if, for each day (let's say at 00:01 AM UTC), we store : - the equivalent of full output of the current `/balances` command - the...

Yes, of course we won't need exactly everything, but basically we will need to keep quite many information from `/status`, unless you want to query the existing data from the...

~Just to make sure I understand, you think we need to take any changes that has been applied on this repo since last time your forked it on gitlab, and...