Bounty for BitCauses. NFC Tip Jar implemented in Andreas' Android Bitcoin client

[nofuture]

Attached are some slides that lay out the purpose of this project.   Also linked below is the thread where Mike Hearn elaborates on project requirements. 

http://www.scribd.com/doc/135708740/Bitcoin-2012-BitCauses-Slide-Presentation

https://bitcointalk.org/index.php?topic=110345.0

The code is to be stored on Github.


The Reward for the first complete solution that is submitted is 15 BTC.  The deadline for completion of this project is May 1, 2013.   The complete solution also needs to have functionality elucidated by Mike Hearn's design requirements detailed in his post regarding tip jars.   The solution needs to have a mode that a mode where tip collectors can program tags to be used as collection jars.

The target is Andreas Schildbach's Bitcoin Client for Android.   There is a 10 BTC bonus when these extra features are  merged into the main client.  The deadline for this additional bounty is June 1, 2013.


Please respond with any questions or suggestions.   I appreciate any feedback that anyone may have.   

[1715297821]

1715297821

[1715297821]

1715297821

[1715297821]

1715297821

[1715297821]

1715297821

[1715297821]

1715297821

[Mike Hearn]

It's super cool you're willing to fund this. But May 1st is an extremely aggressive deadline. I am not sure it is completable by then.

I would recommend abandoning the bounty approach. It's common because of it's simplicity, but that's about the only thing it has going for it:

1) It's winner takes all. If you submit something much better a day later than someone else, you lose everything and the bounty is claimed by the guy who took short cuts.

2) There's no way to know who else is working on it. That disincentivises people who don't want to take the risk, see (1)

3) You can't work closely with whoever is doing the work.

If you're serious about making that project a reality, I would change course and talk to Andreas himself directly about implementing it, using a real contract. The advantages are protection for you (you specify the contract well and you should get exactly what you want), for him (he can't lose by someone making a crap half-working implementation a bit earlier), and you can get/submit feedback during the development process.

Also, although I hate to say it, you should specify prices in dollars or Euros. Right now specifying prices in Bitcoins is just asking for people to get screwed by FX volatility. Peg your price and do the final settlement at the spot rate.

Hope that helps.

[nofuture]

Hey Mike,

Thanks for the suggestions.   I agree with everything you said.   Based on your comments I am going to suspend the bounty for this project for now.  If anyone has started work on this project in hopes of obtaining the bounty please suspend development now.    I'll get in touch with Andreas and see if we can come to an arrangement. 

If I need to go back and ask the community directly for help I will lay out a more flexible series of milestones and an achievable project deadline.    Regardless of who does this project I need to do some additional design work and work closely with a developer to get a quality implementation.

I thought about pegging the bounty in USD but it felt like heresy to use USD instead of BTC     Given the current volatility I do agree that is not viable to use a bounty and even less so to use a bounty set in BTC.  I'll come up with another compensation scheme with a real contract.   

Thanks