Skip to content

Proposals

All governance decisions in the Hummingbot ecosystem flow through Hummingbot Governance Proposals (HGP), a unified proposal type that covers all governance activities including:

  • Approving pull requests and new connectors
  • Allocating HBOT bounties for maintenance and improvements
  • Adding or removing connectors from the codebase
  • Electing the Board of Directors
  • Making changes to the governance system

Proposal Parameters

Parameter Value
Snapshot Space hbot.eth
Discussion Period 2 days minimum
Vote Duration 3 days
Minimum HBOT Balance 200,000
Quorum 5,000,000 HBOT
Approval Threshold >50%

Note

See the HBOT Tracker for the current Quorum Percentage, which is based on the HBOT circulating supply.

Proposal Process

1. Discussion Phase (2+ days)

Before creating a proposal on Snapshot, proposers should start a discussion thread in the #proposals channel on Discord. This allows the community to:

  • Provide feedback on the proposal
  • Suggest improvements or alternatives
  • Gauge community support before voting

The discussion phase should last at least 2 days to give the community adequate time to review and comment.

2. Snapshot Vote (3 days)

After the discussion phase, the proposer can create the formal proposal on the hbot.eth Snapshot space.

  • Any wallet with at least 200,000 HBOT can create a proposal
  • Voting is gas-less and uses your HBOT token balance at the snapshot block
  • 1 HBOT = 1 vote
  • Proposals must reach the 5,000,000 HBOT quorum and achieve >50% approval to pass

3. Implementation

If the proposal passes:

  • Pull requests: The Foundation will review and merge the code into the codebase
  • Bounties: The Foundation will create and manage the bounty assignment
  • Connector changes: The Foundation will implement the changes in the next release
  • Governance changes: The Foundation will update documentation and processes accordingly

If the proposal fails to meet the approval threshold or quorum, the proposer is free to revise and submit a new proposal.

Proposal Template

To be considered valid, an HGP should contain the following fields:

  • Title: Starts with HGP followed by a descriptive summary (e.g., HGP-100: Add XYZ Exchange Connector)
  • Description: Detailed explanation of the proposed initiative, including:
    • What is being proposed
    • Why it benefits the Hummingbot community
    • Any relevant context or background
  • Github Link (if applicable): Link to a Github pull request or issue
  • HBOT Allocation (if applicable): Proposed HBOT bounty amount and rationale

Common Proposal Types

Adding Connectors

For adding new exchange or blockchain connectors to the codebase:

  • Include a link to the pull request with the connector code
  • Explain why this connector benefits the Hummingbot community
  • The Foundation will conduct a technical code review and security audit before merging
  • New connectors should include unit test coverage

Removing Connectors

For removing existing connectors from the codebase:

  • Explain the rationale for removal (e.g., low usage, maintenance burden, security concerns, exchange shutdown)
  • The Foundation will remove the connector in the next release if approved

Proposing HBOT Bounties

For proposing development bounties funded with HBOT:

  • Describe the improvement or feature needed
  • Specify the proposed HBOT bounty amount
  • Optionally name a specific developer to assign the bounty to
  • If no developer is named, the Foundation will publicize the bounty to the community

Electing Board of Directors

The Foundation conducts annual Board of Directors elections via HGP. See Board of Directors for details on the election process.