hummingbot
Bounty - Add new version of Telegram integration
Description
This bounty involves implementing a new version of Telegram integration for Hummingbot, enhancing communication between users and their running bots. The updated integration should improve usability, reliability, and security while ensuring seamless interaction with Telegram’s latest API.
Requirements:
-
Feature Enhancements:
- Upgrade to the latest Telegram Bot API
- Implement real-time notifications for important bot events (e.g., order execution, errors, balance updates).
- Add support for executing basic commands via Telegram, such as checking status, stopping the bot, or retrieving performance reports.
-
Integration Details:
- Use official Telegram Bot API documentation to ensure compliance with best practices.
- Implement secure authentication to prevent unauthorized access.
- Optimize the message format for better readability, including markdown or inline buttons where applicable.
- Ensure rate limits and message queues are properly managed to avoid spam or API blocking.
-
Testing & Documentation:
- Write unit tests to validate message delivery and command execution.
- Conduct integration tests to confirm the bot correctly receives and responds to Telegram commands.
- Provide clear documentation on setting up and configuring Telegram integration, including security best practices.
Deliverables:
- A fully upgraded Telegram Integration for Hummingbot.
- Comprehensive unit and integration tests.
- Updated documentation explaining new features, setup instructions, and usage guidelines.
Bounty Acceptance Criteria:
- The integration must function correctly with all core Hummingbot functionalities.
- Code must pass Hummingbot’s review process and adhere to coding standards.
- Tests and documentation must be complete, clear, and user-friendly.
Timeline:
- Developers have two weeks after assignment to complete the bounty or provide demonstrable progress.
Bounty
- Sponsor: Hummingbot Foundation
- Bounty amount: TBA
- Developer portion: TBA
Bounty Sponsor: Hummingbot Foundation Bounty amount: The bounty is valued at 300 USDC, payable in HBOT. The exact amount of HBOT will be calculated based on the average price of HBOT in USDC over the last month (30 days), ending at the time of payment. Developer portion: 300 USDC, payable in HBOT.
Assigned to @evseevnn , please be informed:
- Please keep us informed on your progress over the next few days
- Follow contribution guidelines (https://hummingbot.org/developers/contributions/)
- Review the checklist after PR submitted (https://hummingbot.org/developers/contributions/#checklist)
- Let us know if you don’t have time, and we will unassigned and keep it open for other devs
- Only one dev can be assigned to one bounty
Thanks for your contribution!
Hi @nikspz. I planned to publish PR today. I need finalize with tests first.
Also, want to inform that we cannot manage all started HB instances by one bot, because of Telegram API not let us to do it. So, each HB instance need use self Telegram bot.
@nikspz PR is ready. One small update will tomorrow, but current implementation worked and based architecture will not changed if not required from HB team.
https://github.com/hummingbot/hummingbot/pull/7550
Unassigned @evseevnn since no updates in this PR https://github.com/hummingbot/hummingbot/pull/7550
This bounty is onhold bc Backend API (Feat/backend api v2)+ Feat/add headless support changes https://github.com/hummingbot/hummingbot/pull/7673 + https://github.com/hummingbot/backend-api/pull/65
@nikspz can I work on this I guess the factor holding it back has been fixed ....I saw the issue has been closed already
