• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
Pull Request ProposalsPull Request Proposalsby0x78afCe8414fb4DfcB01c35Db53547e71283779E70x78af…79E7

Tick Size Configurable

Voting ended over 3 years agoSucceeded

Summary


All the major components of Hummingbot are Time Iterators like the connectors and the strategies. The Clock notifies all the components involved in the strategy by calling the method c_tick() of the time iterators every tick_size .

The idea under this PR is to let the user modify the tick size by using a config variable because currently the tick size is not configurable and by default is 1 second.

Details


Adding a tick size config variable to the conf_client.yml will let the user change it by modifying the yml, using the command config tick_size in the client or with the extra argument in the start that will be —tick-size.

In the PR are implemented the two options, but I created a poll in Discord to see if the community wants the two solutions or just one of them. If the result is that they only want just one, I will delete the other one. Link: https://discord.com/channels/530578568154054663/557343500908363786/1014877021203091487

Rules:

  • If the argument —tick-size is not used in the start command, the default tick_size of the conf_client.yml will be used
  • By defaul the tick_size will be 1 second.

The changes in the code include:

  • Fix the issue The conf_client.yml is not created when Hummingbot starts #5648 .
  • Add the tick_size as a variable in the ClientConfigMap, this means that you will be able to change the value of the tick size in the conf_client.yml or by running config tick_size.
  • Add an argument in the start command that let you override the tick size.
  • Add parameter to the config command and the test related.

PR: https://github.com/hummingbot/hummingbot/actions/runs/2972981795

Off-Chain Vote

For
508.88K HBOT100%
Against
0 HBOT0%
Abstain
0 HBOT0%
Quorum:1037%
Download mobile app to vote

Timeline

Sep 01, 2022Proposal created
Sep 01, 2022Proposal vote started
Sep 08, 2022Proposal vote ended
Oct 26, 2023Proposal updated