On Wed, Jul 31, 2013 at 05:30:46PM -0600, E willbefull wrote: > I think it's important to expect PaymentRequest-only bitcoin URIs in the > future. Some types of payments (exotic transactions) may not make sense to > have a single fallback address. Or, a page with a bitcoin URI link may be > relying on a separate service provider to assemble the transaction.
Also: * There may be a desire to minimize the URL length when used in a QR code * Some applications might specifically require some of the features of the payment protocol - e.g. it may be a requirement that a print-media QR code cannot be used after a cut-off date, or a vendor may have a specific requirement not to accept payments without a refund address There are pros and cons, but it's not clear to me that the benefits of enforced backward compatibility outweigh the benefits of allowing application designers to innovate as they see fit. roy ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
