On 01/13/2014 05:43 PM, Pieter Wuille wrote: > As an optimization (and I believe this is what Mike plans to implement > in BitcoinJ), if a payment_url is present, it should be encouraged to > only send the payment there, and not broadcast the transaction at all > on the P2P network (minimizing the risk that the transaction confirms > without the payment being received; it can't be guaranteed however).
Can you explain what the problem is here? The payment message can be transmitted after the payment has been received through the P2P network. Am I missing something? Furthermore, if we give up the robustness of the P2P network, we will likely end up with more failed payments. There is so much that can go wrong when trying to connect via HTTP (proxies etc.), Bluetooth endpoints can go away, etc. At least we should provide fallback payment_url's in this case. As for you proposal, just be aware I'd like to use the payment protocol for face to face payments as well. That meant payment request via NFC or QR, payment message and payment confirmations via Bluetooth. I think it can be done by putting a Bluetooth mac address into the payment_url. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
