• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
HummingbotHummingbotby0x9FA3156B802eA7ECFe55173Eafc296f509a28777fengtality.eth

[HGP-26] Allocate budget for developer bounties

Voting ended over 3 years agoSucceeded

Hummingbot Foundation proposes to establish the following budgets for developer bounties:

1. Establish budget for CEX Connector Revamp program

This is a re-issuance of HGP-25

As discussed in the forum thread below, Hummingbot Foundation proposes to allocate HBOT tokens to pay community developers for upgrading connectors for certified exchanges to the latest v2.1 standard. This HGP proposes to establish the following bounties:

  • Add FTX Perpetual v2.1 connector: 750,000 HBOT
  • Add Gate.io Perpetual v2.1 connector: 750,000 HBOT
  • Upgrade Binance Perpetual connector to v2.1: 750,000 HBOT
  • Upgrade HTC spot connector to v2.1: 500,000 HBOT
  • Upgrade ByBit spot connector to v2.1: 500,000 HBOT
  • Upgrade Huobi spot connector to v2.1: 500,000 HBOT
  • Upgrade AscendEx spot connector to v2.1: 500,000 HBOT

Total HBOT requested: 5,000,000

2. Establish budget for General Fixes & Enhancements

Since we started paying community devs to fix bugs in August, we have paid out 20 bounties to 8 different developers. So far, these bounties have drawn upon the 1M Bug Hunt budget, and there are currently 360K HBOT remaining.

We propose to formalize this budget under the umbrella title "General Fixes & Enhancements" to create an HBOT allocation that can be used to fund bug bounties, as well as other enhancements that community members may propose via HIP.

There remains 1.5M HBOT allocated for External Integrations currently. Since there have been only 2 submissions that have successfully drawn upon this budget since it was established in March, we propose to shift the remaining 1.5M into the General Fixes & Enhancements budget, so that the total budget is 1.86M.

Total HBOT requested: 1,860,000

Bounties Process

  • All bounties are posted on Bounties Board
  • Developers should apply for assignment by commenting on Github issue for each bounty
  • Foundation assigns bounty by replying on Github issue
  • Developer submits pull request with the code that fixes the bounty on Github
  • Developer creates PRP referencing pull request and this HGP
  • After PRP is approved and pull request is merged, bounty will be paid to developer's ETH address

The Hummingbot community can see the status of HBOT allocations and distributions in the HBOT Tracker public Google Sheet.

Off-Chain Vote

For
6.59M HBOT100%
Against
0 HBOT0%
Abstain
0 HBOT0%
Quorum:104%
Download mobile app to vote

Discussion

Hummingbot[HGP-26] Allocate budget for developer bounties

Timeline

Oct 21, 2022Proposal created
Oct 21, 2022Proposal vote started
Oct 28, 2022Proposal vote ended
Jan 30, 2026Proposal updated