Pages:
Author

Topic: Bitcoin bounty website (Read 4308 times)

member
Activity: 462
Merit: 10
March 11, 2019, 07:00:00 PM
#41
Really great, but very rare case. Less chances to avail these opportunities.
full member
Activity: 574
Merit: 100
Bitway.net - The Best Bitcoin Mining Network
March 03, 2019, 09:27:10 PM
#40
I am most interesting with bounty campaign always use only fill the form without have created website or connect our wallet with bounty account, how ever by using erc20 wallet more better and easy for doing task.
member
Activity: 201
Merit: 10
March 03, 2019, 08:42:39 PM
#39
How get btc from bounty?  Huh
newbie
Activity: 20
Merit: 0
February 13, 2018, 02:32:10 PM
#38
Hi Everyone,

I want to start off with apologizing for not being an extremely active member on the site and offering a bounty program. This one is a little different as it is for an event. The crypto thought leaders speaking at this summit and I are putting together a bounty program and we wanted to gauge some initial interest in it.

The summit is virtual and will have around 15 speakers at it. Gil Penchina, Miko Matsumura, Cindicator, and many more will be speaking. The business model is a free live ticket for anyone interested with an upgraded $67 All Access Pass for those who want to keep all of the recorded sessions forever. It's a two day virtual event.

http://icovirtualsummit.com/

If you are interested in a bounty campaign for this, please reply as such in response to this thread. We are organizing this virtual summit from San Francisco, California and wanted to do it to welcome the international community and give people a place to hear about how the industry leaders want to shape the future of the ICO industry. We want to teach and network around how to make the entire industry better. Topics that will be covered are:

LEARNING FROM THE PAST:
Tons Of Money or Survival Bias

TOKEN ECONOMY PANEL:
Is It The Evolved Stock Market?

LEAN ICOS EXPLAINED:
Learning From Traditional Investor Wisdom

ESCROW:
Technology & Principles

ICO & Legal Compliance

KEYNOTE:
A Startup’s Secret Guide To ICO Success

BLOCKCHAIN STRUCTURED:
Maslow’s Heirarchy For Blockchain

PANEL:
Industries Most Likely To Become Blockchained

BLOCKCHAIN IN THE MEDIA:
Make or Break

PROFESSIONAL ICO INVESTOR PANEL:
Inside Investor’s Minds

CRYPTO COMMUNITY EVOLUTION:
A Look Into The (Realistic) Future

KEYNOTE:
Blockchain Without Borders: A Global Scope

Please let me know if you are interested in a bounty campaign and I'll post the details if enough people are.
full member
Activity: 322
Merit: 103
November 23, 2017, 07:58:51 AM
#37


A co-creation platform is already running a beta version. Crowdholding is building a strong community, where you can earn crypto now only from BOUNTIES, but from general tasks as well.
And any ICO project can run their bounty on Crowdholding as well!

ANYONE can participate. It's similar to Quora
Join the community now Smiley

check out the BOUNTY here: https://bitcointalksearch.org/topic/bounty-ico-crowdholding-2097228
aq
full member
Activity: 238
Merit: 100
June 13, 2012, 07:45:24 AM
#36
WOW, after waiting almost a full year (without bitcoinstarter delivering anything) someone else finally made it:
https://bitcointalksearch.org/topic/ann-boosterio-kickstarter-meets-flattr-meets-bitcoin-87314
aq
full member
Activity: 238
Merit: 100
August 22, 2011, 06:28:16 PM
#35
BitcoinStarter.com will entertain any kind of project even smaller ones - I agree elementary usability features would be very helpful to the community to have.  Smiley
Any time frame on when this will be ready?
Will it hold the pledged bitcoins in escrow?


Earliest this weekend ( this is my goal at least! ) and latest at the end of this month. The pledged Bitcoins will be held in escrow and released if project is successful. If not successful all Bitcoins are returned to their perspective pledgers.

Good question!

Any updates on the project yet? Yes, I know I am impatiently Smiley
full member
Activity: 168
Merit: 100
Firstbits: 175wn
August 17, 2011, 03:22:48 PM
#34
I'm taking this proposal as an idea to possibly working on. The only thing pop me in mind is, Is this method won't be to hard for the average user ? I wanna keep every escrowed transactions easy for everyone.

Well, the idea is that this happens behind the scenes on the server side. The users might not even know you're doing it. The goal is that anyone who now hacks your server can't send the bitcoins to themself, only to one of the parties in the transaction. In other words, it becomes impossible for anyone to steal bitcoins off of the server, thus increasing security.
sr. member
Activity: 243
Merit: 250
BTCrow.com
August 17, 2011, 09:26:48 AM
#33
1 and 2 is doable using the current system:
Upon receiving some funds you can create an temporary address/private key pair, send the funds to this new address, and use the generated private key to generate the two outgoing transactions. Now store both transactions and throw away the temporary private key.
That way the original address does not vanish and so no coins will be lost.

Nice, didn't think of that.

Are there any escrow services that use this method? If not, there should be!

Agreed. Maybe we should contact Btcrow, and suggest it to them? (I don't think anyone's using it yet.)

I'm taking this proposal as an idea to possibly working on. The only thing pop me in mind is, Is this method won't be to hard for the average user ? I wanna keep every escrowed transactions easy for everyone.
full member
Activity: 168
Merit: 100
Firstbits: 175wn
August 13, 2011, 10:28:05 PM
#32
1 and 2 is doable using the current system:
Upon receiving some funds you can create an temporary address/private key pair, send the funds to this new address, and use the generated private key to generate the two outgoing transactions. Now store both transactions and throw away the temporary private key.
That way the original address does not vanish and so no coins will be lost.

Nice, didn't think of that.

Are there any escrow services that use this method? If not, there should be!

Agreed. Maybe we should contact Btcrow, and suggest it to them? (I don't think anyone's using it yet.)
sr. member
Activity: 321
Merit: 250
Firstbits: 1gyzhw
August 13, 2011, 04:57:02 PM
#31
1 and 2 is doable using the current system:
Upon receiving some funds you can create an temporary address/private key pair, send the funds to this new address, and use the generated private key to generate the two outgoing transactions. Now store both transactions and throw away the temporary private key.
That way the original address does not vanish and so no coins will be lost.
This idea rocks! Are there any escrow services that use this method? If not, there should be!
aq
full member
Activity: 238
Merit: 100
August 13, 2011, 04:47:08 PM
#30
Thinking of security, would it be possible to write the platform in a way which prevents the site owners, moderators and any intruders from having access to the funds?

You could generate a new address every time that a sponsor wants to sponsor a project. Then when payment arrives, generate one transaction for every possible outcome (one transaction that sends the bitcoins back to the sponsor, and one that sends it to the developer) but don't broadcast them. After that, you delete the address' private key. When the outcome is determined (bounty should be sent to developer or returned to sponsor), simply broadcast that transaction on the network.

This way, the most damage an attacker could do would be to choose whether the bounty went to the developer or the sponsor. The attacker could never send any of the coins to himself (unless he was the dev/sponsor).

This has a few downsides:
  • If the sponsor sends coins to an address after its private key is destroyed, those coins are gone.
  • You still keep the private key around until a payment is received.
  • All developers must be known before the bounty is moved to escrow. Any developer that appears late in the game cannot collect bounties held in escrow before he started work on a project.

It would be nice if we could create transactions that said to forward all funds sent to one address, present and future, to another address. That would kill problems 1 and 2. (Also useful for ex. importing an untrusted address into one's wallet.) If this isn't possible currently w/ script, it sure would be nice to see implemented. (Bounty anyone?  Tongue Gotta love irony.)

1 and 2 is doable using the current system:
Upon receiving some funds you can create an temporary address/private key pair, send the funds to this new address, and use the generated private key to generate the two outgoing transactions. Now store both transactions and throw away the temporary private key.
That way the original address does not vanish and so no coins will be lost.
full member
Activity: 168
Merit: 100
Firstbits: 175wn
August 11, 2011, 11:28:37 PM
#29
Thinking of security, would it be possible to write the platform in a way which prevents the site owners, moderators and any intruders from having access to the funds?

You could generate a new address every time that a sponsor wants to sponsor a project. Then when payment arrives, generate one transaction for every possible outcome (one transaction that sends the bitcoins back to the sponsor, and one that sends it to the developer) but don't broadcast them. After that, you delete the address' private key. When the outcome is determined (bounty should be sent to developer or returned to sponsor), simply broadcast that transaction on the network.

This way, the most damage an attacker could do would be to choose whether the bounty went to the developer or the sponsor. The attacker could never send any of the coins to himself (unless he was the dev/sponsor).

This has a few downsides:
  • If the sponsor sends coins to an address after its private key is destroyed, those coins are gone.
  • You still keep the private key around until a payment is received.
  • All developers must be known before the bounty is moved to escrow. Any developer that appears late in the game cannot collect bounties held in escrow before he started work on a project.

It would be nice if we could create transactions that said to forward all funds sent to one address, present and future, to another address. That would kill problems 1 and 2. (Also useful for ex. importing an untrusted address into one's wallet.) If this isn't possible currently w/ script, it sure would be nice to see implemented. (Bounty anyone?  Tongue Gotta love irony.)
hero member
Activity: 481
Merit: 529
August 11, 2011, 09:52:42 PM
#28
Maybe we should ask for this topic to be moved to Project Development?
Yep that would be good Smiley
A similar thread there started yesterday: https://bitcointalksearch.org/topic/feeler-bitcoin-bounty-project-36361
sr. member
Activity: 321
Merit: 250
Firstbits: 1gyzhw
August 11, 2011, 08:12:03 AM
#27
  • A developer that has done some work on a bounty can post his initial work to prove that he is working on it; it might be that this still requires rework, but moderators can "lock" the bounty in his name so no one else can claim it in the meantime.
Yes but only for a short time, depending on the trustworthiness value of that developer. Maybe have milestones for larger projects.
We'll also have to watch out for scumbags submitting copyrighted code from other projects as their own and it being released under an incompatible license.

Each bounty must have a "due date", by which the posters get back their escrowed money if there is no initial submission by then
Yep, I'm thinking that each project has an address and we just post the funds back to the address that sent them, so there's no need for people to register accounts to donate. Completed projects would have new funds posted directly to the person who completed the task. Not sure about new funds, maybe new funds being added should re-open / extend a project, or maybe they're just posted back to the address that sent them.

They system should have a (primitive) discussion thread on each bounty to discuss requirements etc.
I think the requirements should be set in stone when the project is created. We're dealing with donations from many people who are donating because they agree with the requirements. This is horribly bureaucratic but IMO the only way to do it fairly.

Registration / authentication simply using OpenID
Absolutely, I hate sites that force me to sign up with a new password, almost as much as I hate having to store user passwords! Cheesy

Thinking of security, would it be possible to write the platform in a way which prevents the site owners, moderators and any intruders from having access to the funds? For example we could encrypt the private key with a "project key" (owned by the site) and a "sponsor key" (one sponsor per donation address, potentially many per project). Once the site moderators agree that the requirements have been met, the project sponsors enter their key and the funds are released. Or maybe something is possible using scripting?

This would have the down-side of projects running forever and funds potentially being lost if the sponsors disappear, as we couldn't close a project without knowing the sponsor key. But it would IMO be a better option than running an escrow site given all the recent hackings!

Maybe we should ask for this topic to be moved to Project Development?
Yep that would be good Smiley
hero member
Activity: 812
Merit: 1022
No Maps for These Territories
August 11, 2011, 03:37:06 AM
#26
Also, if I'm gonna step up and run this project then only free software projects will be eligible for bounty/payout, because I'm a dirty socialist like that Wink
I agree; and nothing socialist about that: Either you fund for-profit projects and you get a share of the profit, or you fund free software and get the code.

The second is more useful for the bitcoin community right now. I really want to aim it at improving bitcoin-related open source projects.
Quote
@John Smith, I'm a Python hacker and FSF member. I've never done Python web dev (aside from writing my own webserver based on SimpleHTTPServer). Here's an example of my work in Python

Interested in working together?
Sure! Python for web is quite easy to learn, if you already know Python (especially advanced stuff like you did) that's the most important part.

My ideas:
  • People can post a new bounty, or add to an existing one (all in escrow, of course, to make sure payouts happen).
  • For each bounty there needs to be a (or more) "moderators" that decide if the bounty can be claimed, or that rework still needs to be done. Moderators should be developers, so that code quality is also looked at.
  • A developer that has done some work on a bounty can post his initial work to prove that he is working on it; it might be that this still requires rework, but moderators can "lock" the bounty in his name so no one else can claim it in the meantime.
  • Each bounty must have a "due date", by which the posters get back their escrowed money if there is no initial submission by then
  • They system should have a (primitive) discussion thread on each bounty to discuss requirements etc.
  • Registration / authentication simply using OpenID


Maybe we should ask for this topic to be moved to Project Development?
hero member
Activity: 484
Merit: 500
August 10, 2011, 05:24:16 PM
#25
It is pledging for a project before it is started with only a few differences in that it has to meet some requirements to do so. In this case, the amount needed in Bitcoins (10 BTC) and days (15 days) to reach it . Really, no different then the pledging you are mentioning above.

There is one other difference the Project Creator offer's ( optional ) incentives to pledge and in return the "pledger" gets the rewards mentioned for his/her pledge.  All in all it is basically the same.

Okay, that clears things up, thanks.


You're welcome. Grin
full member
Activity: 168
Merit: 100
Firstbits: 175wn
August 10, 2011, 05:23:02 PM
#24
It is pledging for a project before it is started with only a few differences in that it has to meet some requirements to do so. In this case, the amount needed in Bitcoins (10 BTC) and days (15 days) to reach it . Really, no different then the pledging you are mentioning above.

There is one other difference the Project Creator offer's ( optional ) incentives to pledge and in return the "pledger" gets the rewards mentioned for his/her pledge.  All in all it is basically the same.

Okay, that clears things up, thanks.
hero member
Activity: 484
Merit: 500
August 10, 2011, 05:16:10 PM
#23
Hi Drawoc - the Project Creator sets the time frame to be met so say it is - 10 Btc in say 15 days - if 15 days pass and 10 Btc is pledged to the project then the project is labeled a success and funding is released to the Project Creator.  Hopefully, this helps.  Smiley

Oh, so is this for funding projects before they've started? I initially got the impression that it was more for pledging money for a project, and after the project was finished, the person who completed the project receives a bounty.

It is pledging for a project before it is started with only a few differences in that it has to meet some requirements to do so. In this case, the amount needed in Bitcoins (10 BTC) and days (15 days) to reach it . Really, no different then the pledging you are mentioning above.

There is one other difference the Project Creator offer's ( optional ) incentives to pledge and in return the "pledger" gets the rewards mentioned for his/her pledge.  All in all it is basically the same.
full member
Activity: 168
Merit: 100
Firstbits: 175wn
August 10, 2011, 05:06:54 PM
#22
Hi Drawoc - the Project Creator sets the time frame to be met so say it is - 10 Btc in say 15 days - if 15 days pass and 10 Btc is pledged to the project then the project is labeled a success and funding is released to the Project Creator.  Hopefully, this helps.  Smiley

Oh, so is this for funding projects before they've started? I initially got the impression that it was more for pledging money for a project, and after the project was finished, the person who completed the project receives a bounty.
Pages:
Jump to: