Since the inception of the Hummingbot Foundation, we have paid out 282 bounties to 92 unique developer wallets. Bounties have been an unqualified success in leveraging the global developer community to maintain the Hummingbot codebase by fixing bugs and adding key components.
To continue on this path, we are excited to announce a new change to the Bounties process. Now, bounty recipients can choose whether to receive their payments in HBOT, our native governance token, or the USDC equivalent amount.
By allowing recipients to receive bounties in stablecoin if they wish, we aim to lower transaction fees while still enabling long-term supporters to accrue HBOT.
Launching a new process that connects skilled community developers with stakeholders seeking dev work
Last year, we introduced the Bounties process, which has successfully addressed numerous issues and funded vital technical improvements in the Hummingbot codebase. Bounties have been $HBOT-denominated rewards provided by the Foundation to developers for resolving bugs or adding enhancements (such as new connectors, strategies, etc.) to the Hummingbot codebase. Given its significant impact and cost-effectiveness, we believe it's time to expand the Bounties program to the broader Hummingbot ecosystem.
Here are the milestones that Bounties have achieved:
68 bounties paid, resulting in 53 bug fixes and 15 new features and exchange connectors, including Kucoin Perpetual, PancakeSwap, and SushiSwap.
Total funds spent: 13,337,000 \(HBOT (\)67,000 currently).
Now, we believe it's time to open up these bounties to the broader Hummingbot ecosystem, so we are recasting them as Community Bounties.
Community Bounties offer a platform for those seeking development work on exchange connectors, strategies, bug fixes, and more to connect with skilled developers capable of building these solutions. As with past bounties, Hummingbot Foundation will oversee the entire lifecycle of Community Bounties, including scoping, assignment, QA/engineering review, and code merge / payment.
Welcome back to the Hummingbot blog! Today, we're excited to share our recent experiment using the open source Hummingbot platform to build a crypto trading bot that applies an indicator-based directional strategy on the Binance Futures exchange using MACD and Bollinger Bands.
This experiment is the first in our new series of Strategy Experiments. Our goal is to create a collaborative environment where users can share their strategy experiments with the community, fostering growth and knowledge sharing among quant traders.
We encourage everyone to share their Strategy Experiments with the community, whether they're successful or not, as we can all learn from each other's experiences. By sharing our findings and discussing new ideas, we hope to create a thriving ecosystem where quant traders can continually improve and refine their trading strategies.
Now, let's discuss the details of our first experiment. Watch the video, or read the description below.
A new approach to solving one of the biggest problems that face issuers of digital tokens: liquidity.
For the first Liquidity Bounty, we have partnered with our friends at Harmony Protocol, a Layer 1 blockchain project with key innovations in sharding and network transport, founded by a highly technical team from Google, Apple, and Amazon.
Since Hummingbot is experimental, beta software that can be run in many different user configurations and markets, we are leveraging the power of our community to help us identify and properly handle all the edge cases which may arise.
As a small token of our appreciation for users who invest their time and effort to try out Hummingbot and report the issues they encounter, we are excited to announce a bounty program for reward users who help improve Hummingbot's stability and reliability!
We will pay bug reporters 0.1 ETH for any bug reported that meets the following criteria:
- It has a different root cause than any other bug reported by other users
- Reporter follows the submission guidelines below (see Submission)
- We decide to fix the bug