Hummingbot spot connector bot-api integration changes

[HalukG]

Integration Checklist for Hummingbot Connector with Bot API

Overview

This checklist details the changes made and further actions required to integrate the Hummingbot connector with our internal Bot API.

Bot-api schema referenced here: https://github.com/geniusyield/dex-contracts-api/blob/main/web/swagger/api.yaml

Changes Made

1. genius_yield_exchange.py

• Updated Endpoint URLs: Adjusted REST API URLs to match the internal DEX API schema.
• Order Placement: Ensured _place_order method aligns with the provided API structure.
• Order Cancellation: Updated _place_cancel method to use correct endpoint and parameters.
• Trading Rules: Adjusted _format_trading_rules method to parse and validate trading pair information correctly.

2. genius_yield_auth.py

• Authentication Method: Updated rest_authenticate to use header-based authentication as per our schema.
• Signature Generation: Adjusted _generate_signature method to match the internal API’s requirements for request signing.

3. genius_yield_constants.py

• Updated Constants: Modified URLs and paths to align with our internal DEX API endpoints.
• Rate Limits: Adjusted rate limits to reflect the internal API’s constraints.

4. genius_yield_api_order_book_data_source.py

• Order Book Snapshot: Updated _request_order_book_snapshot method to fetch order book data from the correct endpoint.
• Order Book Message Parsing: Adjusted snapshot_message_from_exchange and diff_message_from_exchange methods to align with the schema’s structure for bids, asks, and update IDs.

5. genius_yield_order_book.py

• Message Structure: Updated snapshot_message_from_exchange, diff_message_from_exchange, and trade_message_from_exchange methods to correctly parse and structure order book messages based on the provided schema.
• Removed Unused Fields: Removed references to fields not present in the schema, ensuring data consistency.

6. genius_yield_utils.py

• Validation Logic: Updated is_exchange_information_valid to ensure trading pairs are enabled based on status and permission sets.
• Config Map: Ensured GeniusYieldConfigMap includes fields for API key and secret with appropriate prompts.

7. genius_yield_api_user_stream_data_source.py

• Removed User Streams: Acknowledged the absence of user stream support and adjusted the implementation to log this and avoid unnecessary processing.

[HalukG]

Need to verify wheter we can map symbol to market_id

[HalukG]

Needs to be double checked wheter trading_pair is appropriate here. Might be correct to use asset_ticker instead

[HalukG]

Need to check wheter we can use tx id as means of an orders id. Contact api does not have a seperate order id field it seems.

[HalukG]

Again might be more appropriate to use ticker here