Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BGL PR bounty hunt ($10000 overall budget) #39

Open
wu-emma opened this issue Jul 19, 2021 · 24 comments
Open

BGL PR bounty hunt ($10000 overall budget) #39

wu-emma opened this issue Jul 19, 2021 · 24 comments

Comments

@wu-emma
Copy link
Collaborator

wu-emma commented Jul 19, 2021

To get more people involved and provide motivation, we are announcing Bitgesell Pull Request bounty hunt!

The rules are simple:

  • You can create any reasonable pull request that may contain any modifications, including, but not limited to:
    • Refactoring and simplification;
    • Test fixes (1 test group/file fixed by single PR counts!);
    • Cleanup of features that are no longer used (e.g. non-segwit transactions);
    • Documentation and comments (but if no code changes then some reasonable amount of changes should be done to count);
    • Bug fixes;
  • Every PR would be paid $500 in USDT upon approval, larger PRs could receive bigger payouts (PRs of lesser significance like comments editing or one-line changes could receive lesser payout).
  • Interested people are welcome to become maintainers of the project;
@ayushkumar63123
Copy link

Please tell whether my pr refactoring extract_strings.py would be rewarded or not?

@ayushkumar63123
Copy link

I am not getting any reply from one week or more. Please reply

@ayushkumar63123
Copy link

0x6957d999Bbea7771C22beA4Dea4d7c0E39E8Aa1F
Please note my wallet here too (I also sent it on mail).

@ayushkumar63123
Copy link

I made a new pr please check it out

@berbagi12
Copy link

if it is considered not in use the feature can be deleted and needs cleaning.
something that has no function can be deleted.

@ayushkumar63123
Copy link

ayushkumar63123 commented Jul 20, 2021 via email

@ayushkumar63123
Copy link

Is this pr eligible for reward?

@ayushkumar63123
Copy link

Please reply whether this is eligible or not then I will continue resolving other issues too

@ayushkumar63123
Copy link

By eligible I mean for bug bounty of 500 usdt

@ayushkumar63123
Copy link

Please review my pull request.

@Developer-piyush
Copy link
Contributor

To get more people involved and provide motivation, we are announcing Bitgesell Pull Request bounty hunt!

The rules are simple:

  • You can create any reasonable pull request that may contain any modifications, including, but not limited to:

    • Refactoring and simplification;
    • Test fixes (1 test group/file fixed by single PR counts!);
    • Cleanup of features that are no longer used (e.g. non-segwit transactions);
    • Documentation and comments (but if no code changes then some reasonable amount of changes should be done to count);
    • Bug fixes;

  • Every PR would be paid $500 in USDT upon approval, larger PRs could receive bigger payouts (PRs of lesser significance like comments editing or one-line changes could receive lesser payout).

  • Interested people are welcome to become maintainers of the project;

I request you to please have a look at my PR🙏🙏

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 500.0 USDT (500.00 USD @ $1.0/USDT) has been submitted by:

  1. @setiaj700
  2. @ayushkumar63123
  3. @berbagi12
  4. @antonyip
  5. @developer-piyush
  6. @soptq

@wu-emma please take a look at the submitted work:

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 265 years, 3 months from now.
Please review their action plans below:

1) ranjiths10 has started work.

Submit valuable and easy-to-understand bugs.
Earn and show respect.
Get more comfortable with the basics.
Write small, vulnerable programs and challenge others to find the hidden vulnerabilities.
2) ayushkumar63123 has started work.

I removed support for p2pk transaction in wallet.py and also the ability to sign for p2pk since its a non-segwit transaction type.
3) tafadzwachikuvire has started work.

i will make it work by coding .look i am a boy aged 14 and i was born on 2 may 2007 so i will be doing this task .it may take long but start to expect this done is 4 months thank you
4) gconnect has started work.

I would like to create a contribution guide for this project.
5) antonyip has started work.

Update and fix p2p_* tests......
6) developer-piyush has started work.

I have updated readme because first impression is last impression for users/funders/developers and visitors!
7) soptq has started work.

I can set up a build test to improve the general quality of later PR.
8) slowriot has started work.

Miscellaneous code quality and documentation improvements

Learn more on the Gitcoin Issue Details page.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 500.0 USDT (500.00 USD @ $1.0/USDT) attached to this issue has been approved & issued to @slowriot.

1 similar comment
@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 500.0 USDT (500.00 USD @ $1.0/USDT) attached to this issue has been approved & issued to @slowriot.

@slowriot
Copy link
Contributor

slowriot commented Nov 8, 2021

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Please note I still have the following merge requests open at present, all of which have been open for several months:

Additionally, I have a PR to join some of the above changes into Janus branch, where development appears to be ahead of master:

I have further contributions already committed locally, and am eager to submit them, but have not yet done so pending resolution of the discussion at #52 (comment)

Considering the amount of time that has passed, and the low review effort from maintainers, I have little faith that this project is serious about paying its contributors. I would caution other developers to consider carefully before contributing for the bounty.

@ayushkumar63123
Copy link

Someone please check my bounty

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 500.0 USDT (500.00 USD @ $1.0/USDT) attached to this issue has been approved & issued to @slowriot.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 500.0 USDT (500.00 USD @ $1.0/USDT) attached to this issue has been approved & issued to @slowriot.

1 similar comment
@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 500.0 USDT (500.00 USD @ $1.0/USDT) attached to this issue has been approved & issued to @slowriot.

@slowriot
Copy link
Contributor

Contrary to the above three notifications, I have not received any further payment. PRs remain open.

Contributors beware.

@wu-emma
Copy link
Collaborator Author

wu-emma commented Jun 28, 2022

@madnadyka @janus @van-orton
Please take care of this. @slowriot thanks for your patience and understanding. We would sort this out.

@slowriot
Copy link
Contributor

@madnadyka @janus @van-orton Please take care of this. @slowriot thanks for your patience and understanding. We would sort this out.

I see that after almost a year, the following two pull requests have finally been merged:

I'm glad to see my contributions are being used. However, I have not yet received payment. I would appreciate it if you could process payment to the addresses given in the PRs as agreed under this bounty.

Contributors:

For the benefit of other developers considering contributing, and wondering about the legitimacy of this project - I will update this message if payment has been received.

@wu-emma
Copy link
Collaborator Author

wu-emma commented Jul 11, 2022

@madnadyka @janus @van-orton Please take care of this. @slowriot thanks for your patience and understanding. We would sort this out.

I see that after almost a year, the following two pull requests have finally been merged:

* [URL fixes, documentation improvements #52](https://github.com/BitgesellOfficial/bitgesell/pull/52)

* [Base58 fixes #53](https://github.com/BitgesellOfficial/bitgesell/pull/53)

I'm glad to see my contributions are being used. However, I have not yet received payment. I would appreciate it if you could process payment to the addresses given in the PRs as agreed under this bounty.

Contributors:

For the benefit of other developers considering contributing, and wondering about the legitimacy of this project - I will update this message if payment has been received.

We appreciate the effort done and thanks for participation. However, having considered the PRs opened, after reviewing and extracting what could be merged into main branch, a decision was made to provide compensation in the amount of $300. Sorry for delayed reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@slowriot @gitcoinbot @berbagi12 @wu-emma @Developer-piyush @ayushkumar63123