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