BitgesellOfficial / BitgesellOfficial/bitgesell

BGL (Bitgesell) Bounty/Improvement Program ($50000 budget)

Open
#81 73 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
29
Forks
75
PR merge metrics
No merged PRs in 30d

Description

Bitgesell (BGL) project is open for the contributions and participation.

BGL is BTC-derived cryptocurrency with own blockchain, transaction fee burning
mechanics and faster halving rate. A good source of the information would be the
first 2 posts in the bitcointalk forum thread: https://bitcointalk.org/index.php?topic=5238559.0

A $50000 budget formed by the BGL community to motivate developers make technical contributions.

Code improvements that would be paid include:
- fixes for unit and integration tests (this process is approximately 80% completed).
A good chunk of tests fixed (see example here https://github.com/BitgesellOfficial/bitgesell/pull/46
would be compensated around $1000);
- cleaning the codebase (this must require thorough understanding of what is required
and what is not), just fixing some comment links or introducing changes to readme files
could be useful (but bounty payment would be less);
- we are also looking for maintainers to review PRs, test the builds, test changes
manually and running test suites;
- Continuous Integration: there are CirrusCI configs written to build the
software for various platforms, there are minor issues present and fixes/updates to
those are also welcome;
- fixes to the UI are welcome, example: BGL has only segwit addresses support
(no legacy), so the feature of signing a message is not supported (BTC does not
support this too), removing this from UI in a graceful way would be considered as
useful contribution;
- infrastructural upgrades: if you want to bring up BGL testnet (which is not supported
at the moment as the fees in mainnet are very reasonable) this would be much welcome too;

This list is just an example, if you want to contribute in another way that you think
brings value to the project, feel free to ask prior (if the task is large) or make a
partial change/prototype. Honest contributions are welcome, the cheat/abuse contributions
like formal changes (formatting, a pair of comments added, etc.) would be rejected.
There are other repositories of the project (where you can propose updates too), notably:
- BGL-ERC20 Bridge (https://github.com/BitgesellOfficial/wbgl-bridge);
- BGL Web wallet (https://github.com/BitgesellOfficial/bitgesell-wallet);

We are strong believers in open-source and the approach that GitCoin is offering to the
worldwide developer community: freedom, transparency and direct cooperation.
Please respect everyone and don't spam messages that make no sense, any questions
could be asked in:
- the comment section in this github issue;
- the project forum thread (https://bitcointalk.org/index.php?topic=5238559.0);
- project Discord channels (https://discord.gg/Ubp359vZEF);

PRs would be paid in USDT upon approval, contributions in other areas (like infrastructure)
would be compensated after implementation. People that are interested are welcome to become regular
maintainers of the project (this is negotiable after some contribution is made);

Welcome to Bitgesell team and good luck!

3 maintainers would process new PRs: @madnadyka @janus @van-orton please keep incoming requests processed in good tempo (accept, reject, comment, etc.).

Contributor guide

Open the contributing guide

Research direction

Read the issue’s linked Bitcointalk posts and the example pull request #46 first, then identify one concrete contribution with the maintainers. Possible entry points named here include unit and integration tests, CirrusCI configuration, UI behavior, or testnet infrastructure. Done means the agreed change is implemented, tested or reviewed as appropriate, and approved by the maintainers.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
blockchain, ci-cd, infrastructure, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.