Well you have a great start with this idea! Gamifying the donation's process as an incentive is the way to go and providing a lottery on top of an address  is simple and elegant. But to be more "socially engaging" the users must have an incentive to "collaborate" to achieve some goals and so sharing the offer as much as possible. For this i think a great way is to provide the donation process as a mean to unlock the access of a bonus content that is unlocked when a threshold amount is reached. This can be as simple as a widget with a progress-bar and a qr-code to accept donations, when the goal is reached the progress-bar is replaced with the link of the desired content.

Use multiaddr instead of rawaddr (it return additional data but all is there in the "wallet" hash).

It looks good.
But I wonder why you are using Yahoo's YQL since you just need to add cors=true at the end of yours Blockchain.info's query? see: https://blockchain.info/api/blockchain_api CORS headers. The rawaddr, latestblock, unspent, and pushtx APIs are all supported by that.

Maybe you could contact this guy: https://bitcointalk.org/index.php?topic=498575.0
He is looking for a developer.

Your game remind me of this idea: https://bitcointalk.org/index.php?topic=521297.0
I like the way that you provide a game dynamics for tipping and incentivize customers in a fun way.

Will the jar owner display the capacity of the jar in advance or is it unknown for the customer what is the remaining amount before it breaks?
Also It may be good that there is a 1st, a 2nd and a 3rd prize provided by the business owner if he/she want to...

Pretty Cool! I like the concept.   The graphics are nice but the color for the top of the walls is a bit confusing with the floor at first sight, and add an explanation for how the cash-price work on your website.

Keep up the good work!

An ATM is a good idea, what are you planning for the hardware part and manufacturing it? The software side is not too complicated however building and servicing it are much more harder. I can help with electronics and programming.

Good luck with your project, launching an ATM company is a very long and costly road and in the end can be very profitable.

Create a marketplace where peoples who need bitcoins will buy products in stores with cash for the peoples who want to sell their bitcoins... So instead of treading directly between cash and bitcoins we will trade between bitcoins and products... Later if the person really want cash he can directly resell the product...

For ONLINEBITCOINGAMES.COM a list of trending/new Bitcoin based games may be cool, with affiliation etc... or even hosting and providing embedded games on your pages from other developers.

For BITCOINYE.COM I have always thought of adapting the concept of "Penny Auctions" to Bitcoin as this may be very rewarding! You can sell gift-cards and other trendy devices like what are actually doing all these sites. But you can go further in the specialization and sell only virtual currencies. I mean, users buy packs of 100/200/500 bids credits with BTC/LTC/DOGE... and you sell packs of 1.5 BTC, packs of 55 LTC, packs of 700K DOGE... This can offer the chance of winning a big prize for a modest spending, and also converting their coins to another type.

I finally made the first (quick and dirty) implementation of this service.

HERE IT IS: https://github.com/jsbitcoin/bpp-client

What is it? :
* A mean to receive and send bitcoins on a unique address that resemble a email address.
* A mean to attach some datas with each payments like an invoice number, a reference, a comment or even an order form... whatever you want!
* A payment manager with the history of payments and all its data and return address for each payments available with an RPC-API. (Later...)
* Very light and fast! Based on electrum.
* Secure without having to rely on a PKI, a security code is embedded directly on the address to verify the signature of all communications.
 
To test it create your own account on a xmpp server (just click create new account and enter a new address), add some funds on your receipt address, send payments, and have fun...
For testing purposes you can create two copies of it in different folders and launch them for sending money between the two clients. The Tx fee is set to 0.0001 by default. Currently the ONLY?! public xmpp server I have found on the internet with Vcards feature enabled is sibergad.ru , So dedicated servers must be made available by me and anyone that want to create services based on it.
To receive money all you have to do is to publish your secure BPP address like mine: bppmaster@sibergad.ru&bf8FrAWCgFtJuVfbrC5wUiEKVW . The security part (after the &) is optional, you can send payment to an address without it but the signature of information can not be verified (in case of compromised server)!  For each payments you will receive bitcoins in a brand new Bitcoin address, so you can print your BPP address on a QR code on a static medium safely.

The derived keys (BIP32) are generated randomly from what it get on the vcard of the recipient address at payment time. The Vcards and all messages are stored on the xmpp servers. If the recipient is offline there are ~2 billions possible keys that can be generated. When a client is online his Vcard is updated with a new Master Public Key each 5min.  So an online merchant will have always enough MPKs to process an gigantic flow of payments without collisions/reuse of the same Bitcoin address.

Each MPK on the Vcard is signed by a unique Bitcoin private key and it's address is the "security code". It is shared with the BPP address so when someone want to send a payment to it, the client will check that the security code correspond to the signature of the MPK on the Vcard. No need to use a Public Key Infrastructure like SSL. All is embedded on the address itself. So as long as you trust the source from which you have got the address, it's safe. Like with any Bitcoin address today. 

Of course you can enter a regular bitcoin address for sending funds too. It is in alpha and need much more work but all the basic functions are there. I plan to evolve/extend this to build a complete system based on "tokens" (coins) which I will sell at a fixed price for bitcoins and rebuy them for bitcoins too, this is for enabling an ecosystem for donations, game/apps credits, micro payments and more...

Take a look at the code in the /gui/bpp.py file especially, all the protocol and mechanisms are there.

BPP - The ULTIMATE Bitcoin Payment Protocol:

I finally made the first (quick and dirty) implementation of this software.

HERE IT IS: https://github.com/jsbitcoin/bpp-client

What is it? :
* A mean to receive and send bitcoins on a unique address that resemble a email address.
* A mean to attach some datas with each payments like an invoice number, a reference, a comment or even an order form... whatever you want!
* A payment manager with the history of payments and all its data and return address available with an API. (Later...)
* Very light and fast! Based on electrum.
* Secure without having to rely on an PKI, a security code is embedded directly on the address to verify the signature of all communications.
 
To test it create your own account on a xmpp server (just click create new account and enter a new address), add some funds on your receipt address, send payments, and have fun...
For testing purposes you can create two copies of it in different folders and launch them to send money between the two clients. The Tx fee is set to 0.0001 by default. Currently the ONLY?! public xmpp server I have found on the internet with vcards enabled is sibergad.ru , So dedicated servers must be made available to support this service later. 
To receive money all you have to do is to publish your secure BPP address like mine: bppmaster@sibergad.ru&bf8FrAWCgFtJuVfbrC5wUiEKVW . The security part (after the &) is optional, you can send payment to an address without it but the signature of information will not be verified (in case of compromised server)!  For each payments you will receive bitcoins in a brand new Bitcoin address, so you can print your BPP address in a QR code on a static support safely.

I will create a new thread for this with more details...

LOL... I agree with you As has already been said, it has nothing to do with BANKS.


It's a mean to send bitcoins to email addresses! Nothing more nothing less. And on top of that an ecosystem of services can be built. It's a major simplification for all Bitcoin users and open a lot of opportunity for businesses, conceptually it's like what PayPal propose but on your own computer and as decentralized as the email system is. I have advanced a lot on the alpha version of this software and expect to see it in a few days... There is not a server specific part you can use an existing xmpp server on the internet to create your account, even your own server, the clients communicate and send payments between them directly. Actually the software is based on electrum and so is a self contained wallet and also a mean to easily handle incoming payments on your website with a simple RPC API soon.

Thanks. The website is up, again. But I'll use this domain for another project soon...

All of this let me think that I must separate the communication part and the more higher level services for the server. So in fact we will have each merchant installing their own server on their domain that handle the basic level of communication and generating addresses for the client software, and for all the higher services that require some form of centralization like CoinJoin operations etc, there will be independent services providers that each client software can subscribe to from a public list.  For the general user they must still pass through a trusted server if they don't want to/cannot maintain their own server.

We can also imagine a much more "decentralized" model where we have light clients that can just connect to a merchant's server when sending payments and without email(xmpp) address for themselves, but can still benefit of all the ecosystem of high level service providers on the whole network, thus making this project really a "communication layer" / "service hub" for "Bitcoin service providers" / "software agents". So basically we don't need a third party to mess with our BIP32 addresses...

A service hub is a good definitions of this project. The xmpp protocol handle the SSL communications and prevent address spoofing already, of course each server would have their certificate, we are not trying to reinvent the wheel.

I think a lot about security of the whole system and for the BIP32 part although it's an elegant solution it must not belong to the server to take it because I think the strongest for security is that each client can sign every bit of information they transmit with a unique, publicly identified Bitcoin address that any willing client can verify to correspond with the intended entity. And for this the client software must generate a list of 100 addresses in advance, sign each of it and send it to the server for storing it and repeating this when addresses are used. Of course we can sign only a public masterkey and clients can verify it... but then anyone can tell all the future addresses resulting in a loss of privacy.

A good compromise is that regularly the client publish and sign a new public masterkey this way we have a strong scheme where even a corrupted server cannot forge addresses because of the signature and by repeatedly generating new masterkey we maintain a good level of privacy. I have already framed the majority of this protocol and a very early pre-alpha (proof of concept) implementation in python will be published on github very soon...

Yeah Bitcoin-Qt is very hungry on resources, electrum is what I intend for the majority of users and running his own electrum server on a VPS would be great and can already be made. For this thing I will publish the client and the server part so you can have your own server on your own domain if you want... It's a pretty light protocol on resources and every merchant sites can have their own server installed, so maximum security for customers and a nice business payment address with their own domain.

And what is the point of running your own electrum server? Why not just running the full Bitcoin-Qt then? Think of this project more like a DNS for bitcoin addresses. The server doesn't directly handle any bitcoins at all, it's just a communication/routing layer between clients for building higher level sevices on top of it. That's the whole point of this, convenience through the use of memorizable "email" (xmpp) addresses and to transparently enabling all the complex contract scheme that exist with Bitcoin. It's primarily a payment protocol and in fact can be implemented on every Bitcoin client including electrum.

Edit:
What is especially great with the "email" thing is that one can print it on a magazine or a Ads and each user can send payment with an invoice number attached or even join a complete order form with his payment. The server generate a unique Bitcoin address automatically at each client's request and reroute the payment information on the merchant's client software.  

!!! Public derivation mean that the public masterkey can only serve to generate bitcoin addresses NOT private key! Each client software on the other hand keep the Private master key encrypted for Private derivation to spend their coins... Read this carefully:  https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki . It's like what electrum implement with their watch-only wallet.

With this each server can even act as "buffer" for micro-payment. When a client want to send a micro-payment at first he send 0.001 BTC to the server account and his micro-payment is credited on the recipient account on his server. When a micro-payment account reach the 0.001 threshold his server make the Bitcoin transaction...  Each server owner can have their own policy and services to monetize it.

I'm already working on an early implementation in python with Qt and xmpp. A public derivation of the masterkey for generating addresses is much better than P2SH enforced. The server only need to store the public master key for each account and generate incrementally new Bitcoin addresses at each request. It work together with bitcoind and can easily be implemented as a plugin for electrum or any Bitcoin back-end... I see it as a great merchant tool for payment processing as a main target but even an auction market scheme can "easily" be implemented with this protocol and client software...


I fully agree with that.

Exactly all the communications can be signed with a Bitcoin address publicly know to be associated with the intended user. This can involve a directory look-up service but just move the MITM problem... So the most simple solution is to add the public signing address that the user directly grab from the website of the merchant to his own trust list on the client software.  Or by extension an self identifying address scheme that i am currently working on...