<oembed><type>rich</type><version>1.0</version><author_name>npub147edljttlezv8m5dugzg4ka8cg3073j3t2hq4h8ncxaz9sm5swuq4tnsv4</author_name><author_url>https://nostr.ae/npub147edljttlezv8m5dugzg4ka8cg3073j3t2hq4h8ncxaz9sm5swuq4tnsv4</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-02-23&#xA;📝 Original message:On Mon, Feb 23, 2015 at 05:59:34PM +0100, Mike Hearn wrote:&#xA;&gt; &gt;&#xA;&gt; &gt; At the moment I&#39;m also modifying BitPay&#39;s memo field to contain &#39;ack&#39;, as&#xA;&gt; &gt; Andreas&#39; wallet otherwise reports a failure if I transmit the original via&#xA;&gt; &gt; Bluetooth. :-)&#xA;&gt; &gt;&#xA;&gt; &#xA;&gt; Huh?&#xA;&#xA;For HTTP it checks whether &#39;nack&#39; is _not_ presented:&#xA;&#xA;  https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/schildbach/wallet/offline/DirectPaymentTask.java#L133&#xA;&#xA;But via Bluetooth it checks for &#39;ack&#39; directly:&#xA;&#xA;  https://github.com/schildbach/bitcoin-wallet/blob/master/wallet/src/de/schildbach/wallet/offline/DirectPaymentTask.java#L238&#xA;&#xA;The latter should probably be at least changed to the reverse check as&#xA;for HTTP, but in general some non-memo way of doing that would be nice&#xA;of course.&#xA;&#xA;Jan</html></oembed>