-
Notifications
You must be signed in to change notification settings - Fork 187
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.
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
[CRITICAL] Bountysource is Insolvent, do not use! #1586
Comments
Please add my case to your list: This is a serious problem. I'm not exactly a rich man, and I'm going to have to find another way to help pay to feed myself. I wish the best for all others in my situation! |
Hi, please add these bounties to the list, they were collected but not cashedout (even though the request is pending all the way from march): |
ouch. maybe we should put up a bounty to bring them to justice and finance a law suit |
Make sure in your PayPal resolution centre, you view each dispute and escalate to PayPal, otherwise all the seller needs to do is ignore the dispute and the case is closed without resolution. https://www.paypal.com/disputes/ Here is the message I sent
|
The Newpipe team released an article earlier this october announcing a loss of around $6000 to Bountysource. |
Just to report another case, Bountysource did not pay out $3,500 on the following project, although it said it did on the website. IfcOpenShell/IfcOpenShell#1153 |
Removing bountysource, since they scammed everyone: bountysource/core#1586
Removing bountysource, since they scammed everyone: bountysource/core#1586
I'm a maintainer of Gitpay (https://gitpay.me/), which is entirely Open Source. We don't retain the bounty funds. I've been building and working on the platform for five years already. |
What do you mean you don't retain the bounty funds? Are funds held in escrow until the project is completed? Basically, why is Gitpay better than (Bountysource)? |
[Bountysource is dead](bountysource/core#1586). So remove them from our repo.
@kdumontnu Yeah, the funds are retained for Credit Card payments until the issue is merged, and the author can automatically claim the bounties based on the criteria (issue closed and associated PR merged). We will not possess the funds paid by the sponsors. We have better payout support, we're fully Open Source, and we provide Bonuses for solving issues from Gitpay itself. |
Please read my clarification about me not having anything to do with Bountysource: #1597 |
Main Action
Bounty-Issuers
Activate your Paypal Buyer Protection (if payed within last 180 days), see #1586 (comment)
Bounty-Workers
Criminal Liability
Summary.
one can safely assume that bountysource/Blockchain Group embezzles the escrowed bounty funds (e.g. using the money somewhere else, like investing/loosing-it in crypto etc.).
Action is necessary in order to avoid loss of funds.
Your Possible Actions
Important to realize
delays payments for monthshas stopped paying out cash-outs (since months)This is an abuse of the escrow, essentially an embezzlement.
There are thousands of $ in open bounties (e.g. from IBM), this is really becoming strange here.
Bountysource People
CEO
People
https://github.com/orgs/bountysource/people
@rappo@CervatorOn the main videos on website:
@FrancescoBorzi
Company
Bountysource Inc.
548 Market Street #40189, San Francisco, CA 94104-5401
Parent Company
Regulators
dfpi, USA
Possibly:
https://dfpi.ca.gov/
Possible Complaint
French Financial Authorities
(received via email)
I suggest that you contact the French Financial
Authorities through their official "whistle blowing" portal:
https://www.amf-france.org/en/forms-and-declarations/whistleblowing
https://www.amf-france.org/fr/formulaires-et-declarations/lanceur-dalerte-0
and report that The Blockchain Group cannot pay their financial obligations.
That's the regulatory body for The Blockchain Group.
Unpaid
Further Issues
Special Case:
@FrancescoBorzi is complaining about Bountysource here:
Today, he has a role within bountysource (see videos) :
https://bountysource.com/
But bountysource still abuses/embezzles the escrowed funds.
The text was updated successfully, but these errors were encountered: