In the future there will be many different online bitcoin providers holding your money in a virtual wallet.dat online.
Many websites will want to accept bitcoin payments from a 'Tip Jar' button that requires minimal effort to click if you're logged in through OpenID.
The many content providers will need to agree on a method for allowing tipping, together with the online bitcoin services.
- Sign up to mybitcoin.com or whatever wallet service using an OpenID.
- Viewing video on dansblog.org. You like that.
- Click Tip Jar first time.
- OpenID sign up screen.
- dansblog.org contacts distributed database (like DNS) to lookup your wallet provider.
- dansblog.org redirects you to https://mybitcoin.com/mywallet.php?send=5&address=dsjsdjksdjksdjdsk23iuweewkc
- mybitcoin.com saves redirect header (who redirected). Displays confirmation page.
- You click OK
- Redirects back to previously viewing webpage.
Now I propose that we all decide on the distributed database part, so that we can start adding in wallet providers and provide an easy way to provide consistent service between many different services.
The returned URL would have an option for the amount to send and the address to send to.
What do you think? It'd be good to write a spec and put it out there. Even if it isn't written yet, there would be a definitive document that we point people to and say 'this is how it's done. comply with the standard.'
dansblog.org and felixsweb.org could both use different databases but they both sync with each other.