Major Retail Point of Sale Initiative in USA
Our little “New York City Bitcoin Users Meetup” we created on meetup.com ( http://www.meetup.com/bitcoin/ ) has yielded some major brainstorming, collaboration, and development projects. For example, there is now a new Bitcoin Users Meetup in the Washington, DC area too. ( http://www.meetup.com/BitcoinDC/ )
Also… Here in New York City, our little group is already working on quickly developing two FOSS software products:
- Bitcoin POS (& SDK)
- Bitcoin AH
The point of sale software (& SDK) is the component that the retail store merchant runs. Many Bitcoin POS stations talk to one Bitcoin AH (Account Hub). The Bitcoin AH processes transactions instantly.
The Bottom Line:
Customer walks into coffee shop. Orders coffee. At cash register he says, “I’d like to pay with Bitcoin please”. Merchant touches the “Bitcoin” button on his cash register, the cash register displays, “Code: 736”. Merchant tells customer “Code 736”. The Customer then touches the “Pay” button (on the Bitcoin App on his Android or iPhone), and his app prompts him to touch in the code, “736”. The app displays, “Chelsea Coffee, Mocha Latte large, US$2.57, BTC 8.57”. Customer touches “Yes” button. Cash register instantly says, “Paid”. Done.
A Bit about How it Works:
On the Bitcoin AH ( account hub ) side, the coffee shop’s POS system sends an “invoice” to it… which the AH matches to the customer’s Pay command by cordinating geolocation + time + unique 3 digit code.
( If the Geolocations do not match, and only the Time and the Code match, an additional confirmation prompt will pop up, so that telephone orders could also be processed with this same system. For example, it will pop up a message to say, “You are in Toledo, OH and you are about to make a payment to London, England, UK. Is this correct?” )
All of this software will be free open source.
Meanwhile, we are also working with 3 point of sale / cash register vendors… including 2 of the most used restaurant / coffee shop cash register systems in Manhattan… to get them to include the Bitcoin POS components.
So far, 1 has already agreed to do so.
:-)
Related entries (1)
Related entries
That’s really cool bruce! Why don’t we have an european bruce wagner??
LOL
Hey, I’m GLOBAL, Baby! 😊
First stop on the “Bruce Wagner Europe Tour 2011” is definite…
Barcelona ---> (dates to be announced, some time around… between 13-23 March) Can you guys make it there then?
This is my email… planning our weekly skype conference call. A few of us hold a weekly skype conference call to brainstorm and discuss our Bitcoin projects…
Tuesday’s good for me too. Wow. Tuesday’s a big Bitcoin day for me. Earlier Tuesday afternoon, Ed & I will be meeting Jed of MtGox (again) at Andrew’s office. We’ll be introducing those two guys for the first time, and talking all about the POS / AH / Mobile Apps… and how they will tie in to MtGox for instant US$ or Euro conversion, and daily merchant bank deposits. Also, late Tuesday evening I’ll be doing another “radio interview” about Bitcoin for that Libertarian podcast. (They contacted me a few weeks ago.) And… last night (about 12 hours ago), we had our monthly Bitcoin Users Meetup. ( By the way, I highly recommend starting one on Meetup.com ! It’s been a gold mine for building a network of awesome local Bitcoin contacts! ) We met two new people - Ravi and Ivy - both brand new to Bitcoin. It was sort of a “Bitcoin 101” beginners class… But the brainstorming ended with some new serious commitments to work together on a grassroots promotion campaign. The idea is: We’ll target a group of merchants, and use social engineering to convince them that they really want to accept Bitcoin. Ivy is really enthusiastic about leading the charge on this project to market Bitcoin acceptance to local brick & mortar merchants, and she & I totally see eye to eye on the most effective ways to sell them on it. Ed wants to help with the calls too. ( Random customers call and ask if they accept Bitcoin yet. Sometimes asking for the manager, or owner. Other times not. Sometimes male. Sometimes female. Consistently, every few days. Also, we call or stop in person with a complete Bitcoin Merchant package - almost like an informational Press Kit - a Bitcoin Merchant Kit. This gives them something physical to hold on to, and a business card, and the basic information about the advantages of Bitcoin and links to BitcoinMe.com … so, as they keep getting a continuous stream of emails and phone calls from customers asking if they accept Bitcoin, they know who to call… for more information and to pursue it. We figure we’ll start by targeting Only independent coffee shops, Only in one neighborhood. Hell’s Kitchen (which is our own neighborhood). As soon as we get the first business to accept Bitcoin, we’ll begin holding weekly meetups THERE… to support their business by spending Bitcoins there. Also, by sticking to one type of business, in one area, it’ll be an easier sell. “But why doesn’t Cuppa Joe accept Bitcoin? All the other coffee shops here in the neighborhood do. Wisdom Coffee does. The Normal Grind does. Why don’t you?” After penetration of one neighborhood, we expand to coffee shops in other neighborhoods… Eventually, we expand to restaurants… Then to independent grocery stores, etc. A grass roots movement… a new local economy. It won’t be long before the media gets wind of it, and decides to do a story about it for the newspaper or local tv… spreading the word and spawning more growth even faster. The idea is: We want to get every merchant in the country to accept Bitcoin as fast as possible — before The Fed even notices. It’ll happen so fast, they won’t know what hit them! Of course, it’s crucial that our FOSS software systems — the point of sale system sdk, account hub, and smartphone apps, must be ready to implement FAST… in order for this plan to work. That’s why Andrew’s development work is so essential. And my own project of working with the major cash register/point of sale vendors to incorporate Bitcoin POS into their systems… is also crucial. We’ve already established a working relationship with one such POS vendor, and they’ve agreed to include our Bitcoin POS software into their system! It’s called ShopKeep.com Soon… Every merchant in the world who uses ShopKeep.com will automatically be set up to accept Bitcoin if they choose to. Their entire cash register software will be going open source soon. The other two major POS vendor companies I plan to reach out to… are Micros and Aloha. If all of us work hard on this… we really WILL change the world. …very quickly. As Andrew gets his software to an alpha state, I’m sure he’ll publish it on his githib, so all the developers out there all over the world can begin scouring it, reviewing it, suggesting improvements, studying it for security bugs, etc. What we do here in New York City — the plan is — should be a cookie-cutter prototype for exactly what YOU will do in your own town… Petaluma California, Bern Switzerland, Taipei Taiwan, London England, Hamburg Germany, …and the main street merchants and shopkeepers of YOUR town. Exciting stuff. PS - Ed and I are happy to see our investment in buying Bitcoins going up in value. It’s growing much faster than numismatic gold and silver coins are! PPS - Ed and I are planning to launch a new Bitcoin “tv talk show” --- a weely video netcast that’s a talk show all about Bitcoin. We’ll have guests — both locally here in New York, and globally via skype video. Cool eh!?!
Related entries (1)
Related entries
It really sounds like you have got a lot of great ideas and might actually be making progress. I would like to hear how this develops. Also the NY meetup is intriguing. Where do you do this I might not be too far away.
I encourage EVERYONE to go to http://bitcoin.meetup.com and sign up as “I am interested in a Bitcoin Meet-up in my area…
Our NYC Bitcoin Meet-up is held here at Ed & I’s apartment, here in Midtown Manhattan… for now. As we outgrow our apartment, we’ll most likely begin meeting at a local restaurant or coffee shop that accepts Bitcoin ( to support them ). Last night was only our 2nd monthly Meet-up.
Related entries (1)
Related entries
I am in tight with a community supported cafe/community center here in Portland, OR. I could probably get them on board, even if its only me who uses BTC at first. I help with their accounting, business planning, etc, and spend about $25 a week at the cafe, so I could probably convince them 😊. Keep me posted!
Absolutely! You’re in charge of the Portland initiative. Keep in touch with me… and I’ll keep you abreast of the status of the POS system, and its readiness. I HIGHLY recommend creating a Portland Bitcoin Meet-up on Meetup.com and schedule a regular monthly Meetup to be held at that same cafe you mentioned!
This reply just came in from Andrew…
Exciting!
I’ll try to get part of AH posted today.
And regarding…
CQuote from: creighto on January 05, 2011, 6:57:34 PM UTCOutstanding, Bruce!
I was wondering where you had disappeared to lately. I didn’t think that someone with so much enthusiasim would simply just drop off the forum.
Is there a website that we could go and look at these projects?
Thanks, creighto.
As for a place to see the progress of the project’s code development. See Andrew’s github page:
Some rough notes I wrote up a couple days ago:
https://gist.github.com/767423
Sounds good.
I am curious about your Android/iPhone apps though. I take it you’re already making them, or … ?
I ask because I’m also working on an Android app.
That’s Great, mh ! I encourage you to work together with Andrew and see how your work can benefit each other’s work. Everything he does, he has committed, will definitely be FOSS. See his github page: https://gist.github.com/767423
Hey, is the app 2-way transaction enabled? Ex, could I pay|lend|gift bitcoins to a friend?
Yes. Absolutely.
By the way, to explain a little more about this system: The Bitcoin AH (Account Hub) + Bitcoin POS (Point of Sale SDK) + The Bitcoin Mobile Apps = the complete system
The primary problem it solves is: The need for instantaneous transfer
This way, there’s no waiting for an hour for a transaction to clear (get verified by 7+ standard bitcoin nodes). The transaction happens instantly… so there’s no waiting when you buy a large cafe latte… and there’s a line of people waiting behind you.
However, yes, the Mobile App will let you pay anyone who has an account on the Bitcoin Account Hub.
I’m going to recommend that Andrew also include the capability to pay NON-Bitcoin AH members using the standard Bitcoin network… as long as the user is notified of, and approves of, the necessary delay in the transaction fully clearing.
The “Bitcoin Account Hub” acts very similarly to a MyBitcoin.com-type service. Both parties must have an active account on a trusted “Bitcoin AH” in order for the transaction to clear instantly.
The main differences are:
- All of the software is to be completely FOSS (Free Open Source Software)
- Anyone can set up a Bitcoin AH Account Hub (community groups, church groups, university IT labs, Linux user groups, merchants, anyone!)
- Multiple Account Hubs can establish “trust relationships” with each other (this extends the network to all account holders of all trusted networks)
- Transactions always happen instantly - no matter which Bitcoin AH the two parties have accounts on (unless the recipient doesn’t have an AH account; in which case the normal Bitcoin network is used)
- The Mobile Apps will have the same abilities to easily make AND RECEIVE transactions, just like the POS system can, and works exactly the same way: The recipient touches “RECEIVE” button on his phone app, then enters a NAME OF RECIPIENT, and a TEXT DESCRIPTION and an AMOUNT, in either US$ or Euro or Bitcoin, then touches OK. He sees, “Code 953”. The recipient then tells the payer verbally, “The code is 953.” Next, the payer touches “PAY” button on his phone app, then he see, “Enter Code”, he enters 9-5-3, then he sees the NAME OF RECIPIENT, the TEXT DESCRIPTION, and the AMOUNT listed in US$ and Euros and BTC equivalents. He touches PAY again to confirm. The payment is instantly acknowledged on both devices.
- The Mobile App might also have extra features, like the ability to Display your Bitcoin Address as a QR Code
and/orScan someone else’s Bitcoin Address as a QR Code (for non-Account Hub transactions; since the recipient’s Bitcoin Address is not needed if both parties have an AH account — the transaction is connected by time + 3-digit-confirmation-code + confirmation screen with transaction details for sender to acknowledge) - Everything you can do with the Mobile App, can also be done with a web browser via the web interface to the Account Hub
Sound good? Thoughts? Ideas?
The more I think about it…
The more I think that we should develop this in three phases:
PHASE ONE
First, the Bitcoin AH which does everything MyBitcoin.com can do and more… but AH-style… And, all transactions can be completed using any WEB BROWSER via the internet and the AH’s Web Interface.
This way, anyone can use Bitcoin AH now immediately… via any computer or phone with a web browser… from ANYWHERE… GLOBALLY… (even if there’s only one operational AH at the moment).
Also, designed from the ground up to inter-operate with other Bitcoin AH (account hubs) running this identical software, with it’s own internal database of “trusted relationships” between other AH’s.
PHASE TWO
Second, the Bitcoin Mobile App… which does everything the web interface does… plus a few other additional mobile features, like QR Codes.
This way, merchants could actually use the Mobile App or any Web Browser… as their POS solution… for now. Instantly. They could ring up the sale using some unused “Comp Sale” button or code… which would indicate to their internal accounts that it’s a Bitcoin transaction… and then they’d just ring up the RECEIVE transaction using either: The Mobil App on a phone, or the AH Web Interface on a computer or a phone.
PHASE THREE
Third, the Bitcoin POS SDK.
The POS software would also contain built-in calls to API’s to automatically upload Bitcoin to MtGox (and/or potentially any other exchange sites), and initiate the sale of those Bitcoins for USD or Euros, and initiate the request for a direct bank deposit of the USD or Euros into the merchant’s bank account.
Since merchants could begin transacting business after only Phase One (above) is complete… That’s gotta be first. Of course, friends could also make instant transactions to each other at this point too.
Phase Two would add lots more convenience… and mobility.
Phase Three would just be the slick professionalism for merchant processing on a large scale --- the icing on the cake.
Also, I think that it’s important that the Payment Process ALWAYS be consistent… and work the same way… on all platforms… for ease of use, and easy consumer adoption…
- Recipient/Merchant touches the RECEIVE button.
- Recipient/Merchant is asked to enter these text fields: NAME, DESCRIPTION, AMOUNT, USD/EUR/BTC (if on web or phone, cash register POS-SDK does not enter these automatically).
- Recipient/Merchant’s display shows, “Confirm Code 745” (for example).
- Recipient/Merchant verbally tells the Payer/Customer the confirm code.
- Payer/Customer touches PAY button.
- Payer/Customer’s display shows, “Enter the Confirm Code”.
- Payer/Customer enters 745 (for example).
- Payer/Customer sees the correct information displayed for: NAME, DESCRIPTION, AMOUNT, USD/EUR/BTC and sees, “OK TO PAY”
- Payer/Customer touches “OK TO PAY”.
- Both the Recipient/Merchant
andthe Payer/Customer see, “Payment Confirmed” on their respective displays.
… no matter whether either party is using…
- The Web Interface for the AH,
- The Mobile App, or
- The POS SDK integration
One “Receive” request, and one matching “Payment” request, makes one complete Transaction, once confirmed. These requests are matched up by the system based on near enough: CURRENT TIME + CONFIRM CODE + GEOLOCATION If the CURRENT TIME + CONFIRM CODE agree… but the GEOLOCATION is more than 5 miles off, one additional confirmation dialog is displayed for the Payer/Customer. For example, “You are near Cleveland Ohio USA and you are about to send a payment to Bangkok Thailand. Is this correct?” The Payer/Customer must touch, “YES” to proceed with making the payment.
Whatta ya think?
Agree?
Also, designed from the ground up to inter-operate with other Bitcoin AH (account hubs) running this identical software, with it’s own internal database of “trusted relationships” between other AH’s.
that is not the right way to do it. specify a protocol that all AH’s have to adhere to, do NOT specify the software they have to run.
Yes. You are correct. That’s exactly correct. I misspoke when I said “running the identical software”. I should have said, “running the AH Protocol”.
Maybe you would like to get the Ripple P2P implementation up and running instead of the Account Hub.
http://ripple-project.org/Protocol/IndexIf you get it implemented I will send you 10 BTC. 😊 (Will add more as I mine)
EDIT: BTW, feel free to improve the design. 😊
I don’t really understand what Ripple is… but I will pass this suggestion on to Andrew. Is Ripple something that would be used to replace the AH Protocol?
An update from Andrew…
I put up three stub repositories:
https://github.com/tafa/account-hub
https://github.com/tafa/account-hub-mobile
https://github.com/tafa/account-hub-sdkYou might want to sign up for a GitHub account and follow them.
Bruce:
Stupid Question:
What’s your best guess at when a working version will actually be available that we could INSTALL for a merchant who agrees?
Andrew:
That’s hard to say. Possibly a couple weeks.
I’ll make it my highest-priority side project this week, after which a better estimate could be made.
More answers from Andrew…
Bruce:
I’m going to recommend that Andrew also include the capability to pay NON-Bitcoin AH members using the standard Bitcoin network… as long as the user is notified of, and approves of, the necessary delay in the transaction fully clearing.
Andrew:
I never thought that wouldn’t be the case. It just didn’t seem to need any discussion.
Bruce:
• Transactions always happen instantly - no matter which Bitcoin AH the two parties have accounts on (unless the recipient doesn’t have an AH account; in which case the normal Bitcoin network is used)
Andrew:
The normal Bitcoin network is used in both cases. (AH X —> AH Y) transfers just supplement that with an extra message (a copy of the standard bitcoin transfer signature + a signature showing that X controls that key and promises not to multi-spend) delivered rapidly to all AHs on a side-network.
Bruce:
• Transactions always happen instantly - no matter which Bitcoin AH the two parties have accounts on (unless the recipient doesn’t have an AH account; in which case the normal Bitcoin network is used)
Andrew:
Not quite. The 0/uncomfirmed happens “instantly”, along with the extra signature showing that the AH claiming to be the sender for that transfer has access to its private key.
Whether the receiving AH decides to insure its customer against double-spend is totally up to that AH.
would you mind me translating BitcoinMe to spanish and making fliers/leaflets/etc?
Would LOVE it. Email me at email@bitcoinme.com 😊 Thanks! Note: Pardon problem with images displaying on the site. I am fixing that asap.
NFC seems to be an upcoming technology particularly suited to this type of thing.
Near field communication seems like a very promising technology, however it doesn’t yet exist in most cash register or smartphone hardware.
It will certainly be possible to add support for it in the future though.
So awesome that you’re here, “endian7000” !
Sorry if I jumped the gun by talking about AH here. I assumed you were too busy to jump into the Forum for now… but I’m so glad to see you here. I know you developers will have LOTS to talk about. 😊
I watched the video about Ripple. ( on this page http://ripple-project.org )
And the web-based implementation… ( https://ripplepay.com )
And the Technical paper here… ( http://ripple-project.org/decentralizedcurrency.pdf )
It looks like a cool way that Account Hubs could track transactions between themselves. AH’s are only really “loaning” or “guaranteeing” small amounts… between themselves… and only for about 60 minutes… (the time it takes for the transaction to be completely verified on the actual underlying bitcoin network).
Because we’re normally talking about small transactions (i.e. coffee, lunch, dry cleaning, vending machines, etc.)… And because the Bitcoin network WILL clear the transaction within an hour anyway… The entities who run Account Hubs only have to “trust” each other for VERY SMALL AMOUNTS and for VERY SHORT PERIOD OF TIME.
This means that it’ll be VERY easy to establish and build trust relationships between many entities. Hell, I’ll trust anyone in this forum for $20… for only an Hour… Right? Even complete strangers would almost be willing to do that.
This, combined with the FOSS nature of the AH software, is a VERY VERY GOOD THING for quickly building up an amazing network (web) of linked AH’s all over the world.
As someone pointed out, if links can be developed to existing well-know entities --- like MtGox.com and MyBitcoin.com --- then almost every AH will instantly be connected to almost every other AH with at least a trusted dollar amount ($20? $50? $100? $1000?)… trusted for only the ONE HOUR it takes to clear the Bitcoin network.
It seems like the concept of the AH + the AH Mobile client app + Ripple + the standard Bitcoin network = a brilliant automated way to transact generally-smaller-dollar-amount transactions instantly --- whether in person, over the phone, or online.
But even if Ripple is not needed for AH’s to work… It seems like, at the very least, it would be super cool to somehow include, or integrate support for, Ripple into the AH network… No?
Personally, I think that the Bitcoin network is an ingenious idea. And the Account Hub with Mobile & POS clients is an ingenious idea. And Ripple is an ingenious idea.
Combine the 3 and Bitcoin takes over the world. Over night.
An unnamed friend of mine (not bitbot) replied to this thread suggesting “heh interesting… seems like a large fancy system, for basically replicating mybitcoin…”
Yep. Except:
- FOSS
- Decentralized / P2P
- Instantaneous Transactions - even if not on the same node - (which is not true of mybitcoin, btw)
- Mobile Apps
- POS Integration
- Not to mention other potential additions being discussed, like Ripple
MyBitcoin is fantastic for what it is. But it not FOSS, and it’s not Decentralized. Some people have VERY strong objections to promoting --- not to mention asking all the retailers of the world to reply on --- anything that is not FOSS and decentralized.
I woke up this morning with a picture in my mind.
Yesterday, just after reading this thread, I was reading the discussion thread about the need for development of a Bitcoin Web Button --- a simple universal button that could be used to pay, or donate, via Bitcoin, with one click.
After thinking about this problem a bit yesterday… I woke up this morning with a picture in my mind.
This solution for the need for a “universal web button” --- a “PAY WITH BITCOIN” button, a “DONATE BITCOIN” button --- could, and perhaps SHOULD, be integrated into the Bitcoin AH system.
( By the way, there IS A NEED for instantaneous transactions --- not only at point of sale cash registers and vending machines — even OVER THE WEB. For example, consider ordering a pizza online. Neither the pizza shop, nor you, want to wait the extra hour for your payment to “clear” the bitcoin network… BEFORE they start making your pizza. This is true of anything you could order online, with a need for immediate payment, like: delivery.com, lunch orders, any sort of immediate delivery business, a car service, any sort of business that doesn’t want to delay new orders by an extra hour—possibly missing today’s shipping deadline, etc., etc. )
Here’s what I envision:
I visit a web site (it could be a store or a charity), I order what I want, then I click the PAY WITH BITCOIN button.
That button would take me to a centralized web page (maintain by a non-profit entity, ‘the bitcoin foundation’), and it would simply say, “Please select the Bitcoin Account Hub where you have an account (or would like to create an account):” …from a list of all known Account Hubs. There would also be a choice called “Other” where the user could enter the URL of an AH not listed there. (Once enough requests for a new not-listed AH were logged, that new AH could be added to the list on this page.)
The user would simply select the AH where they have an account. Optionally, if this is their own computer, they could check the checkbox, “Save this as the default AH for all transactions from this computer. Saves it as a cookie.” ( Just below that, there’d also be a button, “Clear Default AH — Clear the Default AH Cookie from this Computer”.)
( see image 1: http://dl.dropbox.com/u/993053/Created/Business/BitcoinMe/Images%20for%20BitcoinAH%20Discussion%20-%20Shared/BitcoinAH_Web_Button_Result_Page1.jpg )
Anyway… Upon selecting the AH you use… You would click CONTINUE… and you would be taken to a Send Payment screen on that AH.
( Of course, just like Paypal, you would be responsible to always verify the URL of the AH you are on, before initiating anything. )
All the details of this transaction would have been passed through… from the BUTTON —> the SELECT YOUR AH page —> the actual SEND A PAYMENT page on the AH where your account is held.
The details would show up as pre-filled, but still editable fields: TO (name), TO (domain), TO (email address), BITCOIN ADDRESS, INVOICE NUMBER (possibly blank), DESCRIPTION (text description), AMOUNT-CURRENCY (i.e. btc, usd, euro, etc.), amount AMOUNT-QUANTITY.
( see image 2: http://dl.dropbox.com/u/993053/Created/Business/BitcoinMe/Images%20for%20BitcoinAH%20Discussion%20-%20Shared/BitcoinAH_Web_Button_Result_Page2.jpg )
After clicking the SEND PAYMENT button, you would be asked to either LOGIN or SIGN UP on that Account Hub (basically just like Paypal does).
In the future, if you selected to Save your Default AH as a cookie… Future clicks of a PAY WITH BITCOIN button, or a DONATE BITCOIN button, would take your directly to the Account Hub YOU have an account with… directly… to their SEND PAYMENT form. (The exact amount would be listed in Bitcoin, and the amount in other currencies would be clearly labelled, “approximated based on current exchange rate of ____”.)
Advantages:
- This solution would provide a universal way of making instantaneous ONLINE payments and donations, using Bitcoin, to any entity online with one click.
- You would still be in full control of which AH you trust and deal with.
- You could even set up and run your Own Personal AH, if you wanted to. (if you don’t trust anyone 😉 )
- Other similar services could also be called from that page as well --- like MtGox and MyBitcoin (although those payments would not be instantaneous, unless they add AH capabilities to their sites)
Open AH (Account Hub) integration, into a standard button, could be the solution to this. It could initiate a payment for ANY bitcoin payment processor of your choice (i.e. MyBitcoin, MyGox, or ANY Bitcoin AH in the world, even your own AH running on your server at home,…)
I know. Centralization sucks. But I think that to create a “universal bitcoin button” there needs to be at least one web page that is centrally maintained — kinda like a FOSS program itself. Otherwise, there’s no way to agree on what that button will actually do.
As for the trust relationship between any sort of ‘bitcoin payment processors’/‘hub’/‘bitcoin centrals’… I think this has already been designed. I would not recommend reinventing the wheel.
I’ve seen two excellent approaches to this in: the Ripple protocol, and in the proposed BitcoinAH method
It’s possible that the BitcoinAH method is already superior, by design, to the Ripple system (for this specific purpose — instantaneous bitcoin transactions) because of the way it broadcasts it’s “promise to pay” to ALL nodes… then it pays… then ALL nodes can verify that it ‘kept its word’ by simply looking at the public bitcoin blockchain. There’s no delay, and every node can track the ‘performance record’ of all other nodes… and there’s no ‘chain reaction’… the transaction is still directly from node A to node B… with no intermediaries.
One thing to point out: As I understand it, Ripple is NOT a system of debt. It’s really a system of fast payment processing between entities who don’t know/trust each other. It uses the concept of ‘debt/trust/credit limits’ among ‘friends’, to permit IOUs to pass freely through a web of connected nodes.
I don’t know if, or how, or why, the Ripple protocol might be somehow used. or incorporated into, or as an overlay on top of, the AH system… Perhaps to help those running an AH to decide / control which peers to trust, and for how much? Or for a system of trust between AHs…
For example, the AH protocol is for making instantaneous transactions between AHs. And the Ripple component helps AH administrators find and evaluate their “trust levels” of new AH connections…?
Absolutely. Centralization is unnecessary and insane for an online “Pay with BitCoin” button.
All the merchant site needs to provide the client with is e.g. {hub_url:, bitcoin_address:} and e.g. a BitCoin browser plugin can take it from there.
Though there could be some site(s) with an intro-to-bitcoin-payments page that the button would lead to if you didn’t have the plugin.
But remember, that would require a browser plug-in for every user everywhere all the time. And, if they didn’t have a browser plug-in, the ability to go to that intro-to-bitcoin payments page would have to be built-in to every browser everywhere all the time… (not to mention how hard it might be to get a consensus on WHAT that “intro” page would teach people).
Either way, without some central web page that helps users redirect to their own AH, we would need all the browsers to adopt a standard way of handling the button. I think that will be a much more difficult proposition --- getting Safari and IE and Firefox and Chrome and Opra and… to ALL agree and implement ANYTHING in the same way… is a nightmare. They’re unlikely to even acknowledge the existence of Bitcoin at this point.
One example of this is: Click Add-ons within Firefox. You’re taken to a directory maintained by Mozilla of all Firefox Add-ons. It is “centralized”, yes. But it is community-maintained. And as long as you can always select, “Other”, “Enter the URL: ________________” You can’t get much more open than that.
Think of the ‘centralized web page’ as a sort of FOSS program itself. Community maintained… just like the Bitcoin app itself. Changes must be universally agreed upon, just like changes to the source code of the Bitcoin app itself (or any other FOSS source code). Then, the only thing that would be ‘centralized’ would be the hosting of the page. But couldn’t that be hosted on github or …?
Even if every user in the world added that browser plug-in, they would still have extra work/steps in that they would have to TELL the plug-in which AH they have an account with. They’d have to make that selection somewhere… if not on a web page, it would have to be done within the browser plug-in. And who is going to control all the many different versions of the Bitcoin plug-in… for all the various browsers of the world’s computer and phones…?
At the end of day, SOMEBODY maintains it somewhere. Even if it’s Google maintaining the list of plug-ins for Chrome, Mozilla maintaining the plug-ins for Firefox, Microsoft maintaining the add-ons for Internet Explorer, Apple maintaining the plug-ins for Safari, etc., etc. The ‘centralization’ simply moves to Google, Mozilla, Microsoft, and Apple!
You’ve basicly just described the Ripple web of trust. Deposits really just raise the bar of trust threshold.
I totally agree that that describes Ripple’s web of trust.
Deposits, however, I don’t really get. Not sure how that adds anything. If I have $1000 of yours. And you have $1000 of mine. Does that make me trust you? ( If complete strangers exchange $100 bills, are they now trusting of one another?? ) If you deplete the $1000 I have that belongs to you (by me guaranteeing your expenses)… then you refuse to return the $1000 of mine that you have… We’re right back to where we started. I’m trusting you for $1000. And you’re trusting me for $1000. The result would be EXACTLY the same thing as if we both agreed to simply… “trust each other for up to $1000”… (except we wouldn’t need to tie up $2000 of capital to do it). There’s no need to have deposits with each other. Mutual deposits of the same amount simply “cancel themselves out” anyway. Or am I totally lost??
Hubs could have a “settlement hour” once a day wherein they transfer bitcoins in order to balance out ripple debts that have accumulated across the day…
Yes, but… The hubs’ “settlement hour” could happen 10,000 times a day… 5 milliseconds after the actual transaction. Then the VERIFICATION that the “settlement” has cleared, would happen 5 minutes after the transaction, by simply looking at the normal bitcoin block chain. (or 60 minutes after)… but… No need to wait for a once-a-day event.
My goal would be to eliminate the need for trust, that what I’m aiming for.
I think trust cannot be completely eliminated 100%… when offering instant transfers on a network that takes 60 minutes for transactions to be 100% “cleared”.
However, endian7000’s scheme of “signing the transaction”… by the “owner” of that Bitcoin… (AH-x) and Broadcasting, in effect, a “promise”, to all other AH’s on the network, like:
“I promise to transfer these exact bitcoins (block number) from myself (AH-x’s bitcoin address) to this other AH (AH-y’s bitcoin address) at this very moment, and not attempt to double-spend them.”
Then, every AH on the network could — within only a couple of minutes — be able to independently VERIFY that, “AH-x kept its promise.” …or… “AH-x did NOT keep its promise.”
The entire AH network would know, within only a few minutes, that “AH-x is NOT keeping its promise.” … for whatever reason. …and they could immediately stop accepting “transaction promises” (as instant transactions) from that AH-x --- processing them only as the slow traditional bitcoin method until AH-x is back online and the transactional failure is sufficiently explained… and/or, it’s later promises are now being kept (again, the entire AH network would already KNOW — by independently verifying them — whether AH-x’s promises are being kept… at any given point in time).
Sort of a sidebar question, but still related to the development of AH…
We have a Tonido Plug.
I wonder if the AH could / should be integrated with any other FOSS projects like:
Tonido (the FOSS Dropbox) Amahi (the FOSS server) Tiki.org (the FOSS Groupware/CMS) Drupal (another FOSS CMS) Others?
Bruce you are awesome. Your energy is unbounded. Cant wait to see the new show.
Thanks! 😊
By the way, as an update: The new show is called, “The Bitcoin Show”. It will be LIVE every week… every Friday… at 10AM to 11AM Easter Time (New York City time).
You will be able to watch LIVE, and join and ask questions, etc., in the LIVE chatroom, starting this coming Friday, January 21, 2011… at 10am… at http://onlyonetv.com
If you have suggestions for Guests we should interview about any aspect of Bitcoin, email me: [e-mail address]
If you can’t make it online at that time, it will be available for streaming or downloading, later, on that same site.
See you there! 😊
