Cube Exchange Credentials Not Being Accepted From Hummingbot Version 2.5.0

by ADMIN 75 views

Introduction

Hummingbot is a popular open-source trading bot that allows users to trade on various cryptocurrency exchanges. However, with the release of version 2.5.0, users have reported an issue with Cube Exchange credentials not being accepted. In this article, we will delve into the details of this issue, provide steps to reproduce it, and offer potential solutions.

Describe the Bug

When using the Dashboard after updating Hummingbot to version 2.5.0 and using Cube credentials that were used in version 2.4.0, an error is returned stating that the credentials are in the incorrect format. The error message is as follows:

pydantic_core._pydantic_core.ValidationError: 3 validation errors for cube
cube_api_key
  Value error, Invalid API key. API key should be a UUID string. [type=value_error, input_value='       ', input_type=str]
    For further information visit https://errors.pydantic.dev/2.11/v/value_error
cube_api_secret
  Value error, Invalid secret key. Secret key should be a 64-character alphanumeric string. [type=value_error, input_value='"
For further information visit https://errors.pydantic.dev/2.11/v/value_error
cube_subaccount_id
  Value error, is not in integer format.

Steps to Reproduce

To reproduce this issue, follow these steps:

  1. Install version 2.5.0: Install Hummingbot version 2.5.0 using the following command:
pip install hummingbot

  1. Try to add credentials to Cube using Dashboard: Open the Hummingbot Dashboard and try to add your Cube Exchange credentials. You should receive an error message stating that the credentials are in the incorrect format.

  2. OR open a standalone bot using the CLI interface: Open a terminal and run the following command to open a standalone bot using the CLI interface:

hummingbot --config-path /path/to/config.json

Enter your Cube Exchange credentials and exit the bot. The bot will not be able to be restarted.

Release Version

The release version that is affected by this issue is 2.5.0.

Type of Installation

The issue has been reported using Docker.

Attach Required Files

The error log file is available at errors.log.

Potential Solutions

Based on the error message, it appears that the issue is related to the format of the Cube Exchange credentials. Here are some potential solutions:

  • Check the format of the API key: Ensure that the API key is a UUID string. If it is not, try generating a new API key.
  • Check the format of the secret key: Ensure that the secret key is a 64-character alphanumeric string. If it is not, try generating a new secret key.
  • Check the format of the subaccount ID: Ensure that the subaccount ID is an integer. If it is not, try converting it to an integer.

If none of these solutions work, it may be worth out to the Hummingbot support team for further assistance.

Conclusion

Q: What is the issue with Cube Exchange credentials in Hummingbot version 2.5.0?

A: The issue is that the credentials are not being accepted due to a format error. The error message indicates that the API key is not a UUID string, the secret key is not a 64-character alphanumeric string, and the subaccount ID is not an integer.

Q: What are the specific error messages I can expect to see?

A: The error messages will be similar to the following:

pydantic_core._pydantic_core.ValidationError: 3 validation errors for cube
cube_api_key
  Value error, Invalid API key. API key should be a UUID string. [type=value_error, input_value='       ', input_type=str]
    For further information visit https://errors.pydantic.dev/2.11/v/value_error
cube_api_secret
  Value error, Invalid secret key. Secret key should be a 64-character alphanumeric string. [type=value_error, input_value='"
For further information visit https://errors.pydantic.dev/2.11/v/value_error
cube_subaccount_id
  Value error, is not in integer format.

Q: How can I reproduce the issue?

A: To reproduce the issue, follow these steps:

  1. Install Hummingbot version 2.5.0 using the following command:
pip install hummingbot

  1. Try to add your Cube Exchange credentials to the Hummingbot Dashboard. You should receive an error message stating that the credentials are in the incorrect format.

  2. Alternatively, open a standalone bot using the CLI interface and enter your Cube Exchange credentials. The bot will not be able to be restarted.

Q: What are the potential solutions to the issue?

A: Based on the error message, the potential solutions are:

  • Check the format of the API key to ensure it is a UUID string.
  • Check the format of the secret key to ensure it is a 64-character alphanumeric string.
  • Check the format of the subaccount ID to ensure it is an integer.

If none of these solutions work, it may be worth reaching out to the Hummingbot support team for further assistance.

Q: How can I prevent this issue in the future?

A: To prevent this issue in the future, make sure to:

  • Double-check the format of your API key, secret key, and subaccount ID before entering them into the Hummingbot Dashboard or CLI interface.
  • Use a UUID string for the API key.
  • Use a 64-character alphanumeric string for the secret key.
  • Ensure the subaccount ID is an integer.

Q: What if I am still experiencing issues after trying the potential solutions?

A: If you are still experiencing issues after trying the potential solutions, it may be worth reaching out to the Hummingbot support team for further assistance. They can help you troubleshoot the issue and provide additional guidance on how to resolve it.

Q: Is this issue specific to Hummingbot version 2.5.0?

A: Yes, this issue is specific to Hummingbot version 2.5.0. If you are using an earlier version of Hummingbot, you should not experience this issue.