[Possible Feature] 24h Volume

[brianleect]

Hi @brianleect, Could you add the USDT volume that Binance always shows and which is independent of the candles? I think it is the volume for the last 24 hours.

But not the percentage change in volume, I mean just the amount of USDT being traded at the moment.

For example:

"DUMP: TCTUSDT / Change: -1.16 % / Price: 0.023277 / Volume (USDT): 14.16M / Interval: 5m"

"PUMP: BTCUSDT / Change: 3.25 % / Price: 38536 / Volume (USDT): 20.14B / Interval: 30m"

Originally posted by @Juanjacinto123 in #10 (comment)

[brianleect]

Link: https://binance-docs.github.io/apidocs/spot/en/#24hr-ticker-price-change-statistics

@Juanjacinto123

If I'm not mistaken, this would be the endpoint to get the 24h volume info. However, the currently used endpoint is different due to different requirements for extraction frequency and concerns regarding the rate limit.

TEST_VOL version previously added uses the same endpoint though, and I could try to see if I could add it in.

[velajos]

Hi @brianleect, any update on this? Thanks

[brianleect]

Hi @brianleect, any update on this? Thanks

I have an idea of how this could still be implemented on the current program structure. I could have an option to use the alternate endpoint with 24h volume information in the config file. However, you would be unable to use the '1s' extract interval. Minimum extract would have to be > 3s or preferably 5s to have this 24h information to be sent along.

May I know why you would find this 24h volume information to be useful? Based on my current knowledge this information does not seem especially relevant considering we do not have a point of reference on whether this 24h volume number we have is supposed to large/small or if its a decrease or increase respective to previous timeframes.

[velajos]

Hi @brianleect, any update on this? Thanks

I have an idea of how this could still be implemented on the current program structure. I could have an option to use the alternate endpoint with 24h volume information in the config file. However, you would be unable to use the '1s' extract interval. Minimum extract would have to be > 3s or preferably 5s to have this 24h information to be sent along.

May I know why you would find this 24h volume information to be useful? Based on my current knowledge this information does not seem especially relevant considering we do not have a point of reference on whether this 24h volume number we have is supposed to large/small or if its a decrease or increase respective to previous timeframes.

Well, my strategy is Scalping and looks for abrupt price changes during time periods between 15 and 60 minutes. I particularly use that Volume as a speed indicator of the trade. For Volume >= 100M, I look for changes of 5% and for Volume<= 100M I require changes of at least 10%. This is why it is very useful to be able to see that Volume.

Perhaps it is not necessary to call the Api for every request, since it is Volume for the last 24 hours, it could be called every 2 or 4 hours and use that value for the next 2 or 4 hours.

However, if it is too complicated to incorporate, then there is no problem.

[brianleect]

Hi @brianleect, any update on this? Thanks

I have an idea of how this could still be implemented on the current program structure. I could have an option to use the alternate endpoint with 24h volume information in the config file. However, you would be unable to use the '1s' extract interval. Minimum extract would have to be > 3s or preferably 5s to have this 24h information to be sent along.
May I know why you would find this 24h volume information to be useful? Based on my current knowledge this information does not seem especially relevant considering we do not have a point of reference on whether this 24h volume number we have is supposed to large/small or if its a decrease or increase respective to previous timeframes.

Well, my strategy is Scalping and looks for abrupt price changes during time periods between 15 and 60 minutes. I particularly use that Volume as a speed indicator of the trade. For Volume >= 100M, I look for changes of 5% and for Volume<= 100M I require changes of at least 10%. This is why it is very useful to be able to see that Volume.

Perhaps it is not necessary to call the Api for every request, since it is Volume for the last 24 hours, it could be called every 2 or 4 hours and use that value for the next 2 or 4 hours.

However, if it is too complicated to incorporate, then there is no problem.

It should be not too difficult to incorporate. However, current codebase is being refactored which will likely take awhile before additional features are added in. My current schedule is rather packed as well. I'll try to see if we could add it in within 1-2 weeks if possible.

Thanks for your input as always Juan

[patbaumgartner]

Hi @Juanjacinto123, are you willing to contribute your idea? I think if this feature is also interesting for others we can likely implement it. Hope to see here more comments by others.