@dino thank you for your response.
Fee: Compared to other exchanges, the fee-tier of users will change less often, but this is only because binance has such an unrealistic fee-tier system which is bound to BTC (with rsiing BTC price, it gets more and more difficult). Hopefully binance will change the required volumes in the future.
But even with the current fee tier system, I could easily be on a boundary. Eg. a month has 30 days and I trade 33.4 BTC every second day, and the other days nothing. After 1 month, I will have 30 day volume of 500 BTC and reached the better fee tier. But because I do not trade at the 31th day, the 30 day volume will go below 500. And the next day it will go over 500 again, so my fee-tier may change every single day in this extreme example. But even if my fee tier is getting worse only 1 day a month, I will only notice this after doing a REST call. And if I do this eg. only once per day, I may trade a whole day with wrong fees, resulting in losses. So I need to tighten the intervall when I do the REST call for fees. Even every 1 hour might be too less when you see my number of trades.
You say calculating the trading volume would solve this:
That might be a good idea, if I can calculate the trading volume 100% correct from websocket and I know the fee-tiers (which volume reaches which level). But how do I deal with different fee per pair? As you can see here, I don’t have the same fee for each pair: How to get promotional fee via API?
So even if this would work (I think the different fee per pair is currently not solvable), it is still very complicated, compared to the very minor work binance had to do, to simply add fee-tier-changes to any stream. It will only be send very rare, so no big traffic from this.
Trading pair status:
Since you offered no possible solution to this one, I guess you finally see my point and will implement something for this? Would be really important, especially combined with this topic: Rest API trading is not enabled - Any status call/stream? (implement a cancel_only status in API).
If you have working workarounds, eg. like the trading volume suggestion, I’m happy to hear them and to see, if they would really work. But if you don’t have workarounds, there is no other way than to implement it into API.
It is not like my feature requests are strange, many other exchanges do have what I request here. I want to hlep to make binance trading better. And at most I don’t want to make losses when my bot trades at binance.