{"type":"rich","version":"1.0","author_name":"npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","author_url":"https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-20\n📝 Original message:Afaik, BIP73 needs an external server (the web server).\n\n\nOn 03/20/2014 04:31 AM, Jeff Garzik wrote:\n\u003e Take a look at BIP 73:\n\u003e https://github.com/bitcoin/bips/blob/master/bip-0073.mediawiki\n\u003e \n\u003e \n\u003e \n\u003e \n\u003e On Wed, Mar 19, 2014 at 10:22 PM, Alex Kotenko \u003calexykot at gmail.com\n\u003e \u003cmailto:alexykot at gmail.com\u003e\u003e wrote:\n\u003e \n\u003e     Hi Andreas\n\u003e \n\u003e \n\u003e     I'm implementing support for BIP70 in my POS at the moment, and I've\n\u003e     just realized that with options you're proposing usecase I'm looking\n\u003e     for is not covered.\n\u003e \n\u003e     Right now, before BIP70, I'm sending BIP21 URI via NFC or QR code,\n\u003e     and I need to still be able to use it for backwards compatibility.\n\u003e     But at the same time I want to be able to support BIP70. And also I\n\u003e     want to avoid using external servers, the concept of my POS is that\n\u003e     everything is happening between just payer's phone and payee's POS\n\u003e     device. This means that BIP72 HTTP(S) link inside Bitcoin URI is not\n\u003e     suitable for me. \n\u003e \n\u003e     You're also offering an option to include Base43 encoded PR body\n\u003e     right inside the Bitcoin URI, but in a way that is not backwards\n\u003e     compatible with BIP21. \n\u003e \n\u003e     In the end this all means that there is no way for me to at the same\n\u003e     time keep backwards compatibility with all wallets not supporting\n\u003e     NFC and BIP70 (all other wallets right now), and keep things inside\n\u003e     POS without need for external servers. \n\u003e \n\u003e     I understand your intention behind base43 encoding and noncompatible\n\u003e     URI - you want to make most possible use of QR codes. But I wonder -\n\u003e     did you compare this base43 to base64 encoded request in a binary QR\n\u003e     code format? How much do we actually win in total bytes capacity at\n\u003e     a price of noncompatibility and increased complexity?\n\u003e \n\u003e     And also maybe we can extend BIP72 to include encoded payment\n\u003e     request in the URL directly in a backwards compatible way?\n\u003e \n\u003e \n\u003e     Best regards, \n\u003e     Alex Kotenko\n\u003e \n\u003e \n\u003e     2014-03-02 11:50 GMT+00:00 Mike Hearn \u003cmike at plan99.net\n\u003e     \u003cmailto:mike at plan99.net\u003e\u003e:\n\u003e \n\u003e         Thanks Andreas.\n\u003e \n\u003e         For BIP standardisation, I think the VIEW intent seems like an\n\u003e         obvious one. Bluetooth support probably should come later\n\u003e         if/when we put encryption/auth on the RFCOMM link (probably SSL).\n\u003e \n\u003e         ------------------------------------------------------------------------------\n\u003e         Flow-based real-time traffic analytics software. Cisco certified\n\u003e         tool.\n\u003e         Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow\n\u003e         Analyzer\n\u003e         Customize your own dashboards, set traffic alerts and generate\n\u003e         reports.\n\u003e         Network behavioral analysis \u0026 security monitoring. All-in-one tool.\n\u003e         http://pubads.g.doubleclick.net/gampad/clk?id=126839071\u0026iu=/4140/ostg.clktrk\n\u003e \n\u003e         _______________________________________________\n\u003e         Bitcoin-development mailing list\n\u003e         Bitcoin-development at lists.sourceforge.net\n\u003e         \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e         https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\u003e \n\u003e \n\u003e     ------------------------------------------------------------------------------\n\u003e     Learn Graph Databases - Download FREE O'Reilly Book\n\u003e     \"Graph Databases\" is the definitive new guide to graph databases and\n\u003e     their\n\u003e     applications. Written by three acclaimed leaders in the field,\n\u003e     this first edition is now available. Download your free book today!\n\u003e     http://p.sf.net/sfu/13534_NeoTech\n\u003e     _______________________________________________\n\u003e     Bitcoin-development mailing list\n\u003e     Bitcoin-development at lists.sourceforge.net\n\u003e     \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e     https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\u003e \n\u003e \n\u003e \n\u003e -- \n\u003e Jeff Garzik\n\u003e Bitcoin core developer and open source evangelist\n\u003e BitPay, Inc.      https://bitpay.com/\n\u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Learn Graph Databases - Download FREE O'Reilly Book\n\u003e \"Graph Databases\" is the definitive new guide to graph databases and their\n\u003e applications. Written by three acclaimed leaders in the field,\n\u003e this first edition is now available. Download your free book today!\n\u003e http://p.sf.net/sfu/13534_NeoTech\n\u003e \n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e"}