Hi piuk,
I noticed that the receive api callback from blockchain.info is no longer immediate. I was accepting zero-confirmation payments successfully up until maybe a couple of weeks ago. Here is an example of a generated address for which I'm still awaiting blockchain.info's response:
https://blockchain.info/address/14TdZ3nRTcfLUkRUb8DUTXUZf8Pe6pPwEGDid you make a change to the callback so it no longer responds immediately?
No, no changes have been made to the callbacks recently. Is it the both the forwarding payment and callback the callback which is being delayed or just the callback?
Could you add the ability to archive/unarchive multiple address at once?
Like a check box next to each address and a button to Archive/Unarchive those addresses.
The unarchived icons are pretty quick to tap for me. I can see a need to a checkbox for archive but the interface needs to be kept uncluttered at the same time.
I've set the 'Default Fee Policy' to 'Generous', but my transactions are still being send with 0.0005 BTC fee.
What's going on?
(I'm using 'Bitcoin-Qt Compatible JSON RPC', 'sendmany')
The fee policy set in the javascript interface does not currently affect the API. However I have fixed this my development version and it will be fixed next update.
Is anyone else getting "Unrecognized search pattern" on every bitcoin address lookup?
This should be fixed now.
Also fixed a bug related to the "address contains a very large number of unspent outputs" issues.