<oembed><type>rich</type><version>1.0</version><author_name>npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4</author_name><author_url>https://nostr.ae/npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-20&#xA;📝 Original message:Hi Andreas&#xA;&#xA;&#xA;I&#39;m implementing support for BIP70 in my POS at the moment, and I&#39;ve just&#xA;realized that with options you&#39;re proposing usecase I&#39;m looking for is not&#xA;covered.&#xA;&#xA;Right now, before BIP70, I&#39;m sending BIP21 URI via NFC or QR code, and I&#xA;need to still be able to use it for backwards compatibility. But at the&#xA;same time I want to be able to support BIP70. And also I want to avoid&#xA;using external servers, the concept of my POS is that everything is&#xA;happening between just payer&#39;s phone and payee&#39;s POS device. This means&#xA;that BIP72 HTTP(S) link inside Bitcoin URI is not suitable for me.&#xA;&#xA;You&#39;re also offering an option to include Base43 encoded PR body right&#xA;inside the Bitcoin URI, but in a way that is not backwards compatible with&#xA;BIP21.&#xA;&#xA;In the end this all means that there is no way for me to at the same time&#xA;keep backwards compatibility with all wallets not supporting NFC and BIP70&#xA;(all other wallets right now), and keep things inside POS without need for&#xA;external servers.&#xA;&#xA;I understand your intention behind base43 encoding and noncompatible URI -&#xA;you want to make most possible use of QR codes. But I wonder - did you&#xA;compare this base43 to base64 encoded request in a binary QR code format?&#xA;How much do we actually win in total bytes capacity at a price of&#xA;noncompatibility and increased complexity?&#xA;&#xA;And also maybe we can extend BIP72 to include encoded payment request in&#xA;the URL directly in a backwards compatible way?&#xA;&#xA;&#xA;Best regards,&#xA;Alex Kotenko&#xA;&#xA;&#xA;2014-03-02 11:50 GMT+00:00 Mike Hearn &lt;mike at plan99.net&gt;:&#xA;&#xA;&gt; Thanks Andreas.&#xA;&gt;&#xA;&gt; For BIP standardisation, I think the VIEW intent seems like an obvious&#xA;&gt; one. Bluetooth support probably should come later if/when we put&#xA;&gt; encryption/auth on the RFCOMM link (probably SSL).&#xA;&gt;&#xA;&gt;&#xA;&gt; ------------------------------------------------------------------------------&#xA;&gt; Flow-based real-time traffic analytics software. Cisco certified tool.&#xA;&gt; Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer&#xA;&gt; Customize your own dashboards, set traffic alerts and generate reports.&#xA;&gt; Network behavioral analysis &amp; security monitoring. All-in-one tool.&#xA;&gt;&#xA;&gt; http://pubads.g.doubleclick.net/gampad/clk?id=126839071&amp;iu=/4140/ostg.clktrk&#xA;&gt; _______________________________________________&#xA;&gt; Bitcoin-development mailing list&#xA;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt;&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140320/bc8cc362/attachment.html&gt;</html></oembed>