- From: Mark Leck <markpleck@gmail.com>
- Date: Mon, 22 Dec 2014 18:45:12 +0000
- To: Anders Rundgren <anders.rundgren.net@gmail.com>
- Cc: Web Payments CG <public-webpayments@w3.org>, Steven rowat <sn0281@uniserve.com>
- Message-ID: <CAM5HRAgpFMWGeMRx2OB4YY7jkdqtPLY8Cv=G2HnYffdtn68hWA@mail.gmail.com>
The server and client are basically the shopkeeper and customer the whole BTC network is the shops security if you like. Not very different to the problems faced by VISA transactions over the internet, except that even with a MITM attack nothing more than the conversation could be gleaned as the payment network is a separate entity all together. As for the APP owning the GUI? You could always write your own, I am sure many third parties will be doing just that. The beauty with network is that no one can own it. On 22 Dec 2014 18:36, "Anders Rundgren" <anders.rundgren.net@gmail.com> wrote: > On 2014-12-22 18:14, Mark Leck wrote: > >> Broadcasting to the network is instant. So you can safely say that the >> > > funds are in the bank. Well in the wallet. There is more chance of a > > Visa going out of business than that BTC transaction not arriving. > > Pardon for not being entirely enthusiastic; I just don't like the idea that > the seller app "owns" the payment GUI regardless if it is $10 000 or just > a dime. > > If there's a pay-to-view-URL (sounds like a typical XXX-site thing > [No, I'm not supposed to know that :-)]), shouldn't it have a price tag? > > Then of course I have my usual questions like: how do you authenticate to > your BTC (wallet?). > > Anders > > >> On 22 Dec 2014 16:59, "Steven rowat" <sn0281@uniserve.com <mailto: >> sn0281@uniserve.com>> wrote: >> >> On 2014-12-20, at 7:36 AM, Anders Rundgren < >> anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> >> wrote: >> >> > On 2014-12-20 15:36, Melvin Carvalho wrote: >> >> http://challengepost.com/software/zero-click-bitcoin- >> micropayments >> > >> > Hi Melvin, >> > You mentioned the HTTP 402 thing before and I didn't got it. >> > Now I do, but this solution is really a service dealing with HTTP >> 402. >> > >> > They didn't provide much details on how it works but I guess >> that's obvious for you bitconiers :-) >> > The question is if their protocol would stand a security review, >> my guess is that it would not. >> >> Looks so beautiful and simple. There must be a problem -- security, >> browser buy-in, wait times for bitcoin confirmation. If not, I'm ready to >> start using it anytime. :-) >> >> Here's a discussion by bitcoin people of this idea from two years >> ago, including some detail about all those issues, especially security. >> It's not exhaustive but for me at least it was good background. >> >> https://bitcointalk.org/index.php?topic=3895.0 >> >> >> Steven Rowat >> >> >> >> >> >
Received on Monday, 22 December 2014 18:45:40 UTC