On Tue, Jul 15, 2014 at 10:23 AM, Jeff Garzik <jgar...@bitpay.com> wrote: > On Tue, Jul 15, 2014 at 4:19 AM, Wladimir <laa...@gmail.com> wrote: > There are major gaps that the payment protocol doesn't cover. > > There are several deployed use cases where you are provided/request an > address, an API provides one, and one or more incoming payments arrive > as the user sends them over minutes/hours/days/weeks.
Couldn't these services return a payment message instead of an address? I agree that there is currently an UI issue here: there is no way in current wallets to store a payment message and pay to it later. We will need something like that for recurring payments as well. Bitcoin addresses were never designed with extensibility in mind. Before the payment protocol there have been lots of ideas to add functionality to them, but the underlying idea that they have to be handled by users manually means that they have to be as short as possible, which is a conflicting aim with extensibility... Wladimir ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
