Sorry for not posting for a while, I do monitor this thread daily and read everyone's suggestions (As do Mandrik, Nick and Roger).
Bug, when using android app (last version), it adds a fee of 0.0005 instead of 0.0001 btc.
Fixed in the latest update.
BIP32 support?
Eventually.
I'd like a refresh button in the new blockchain chrome extension.
Added.
Looking for feedback from those that have used shared coin. Did you experience any errors? Were you happy with the results?
There's a problem with opening wallets with 20 000 iterations of PBKDF2, couldn't log in at first, got a "syntax error" message, after managing to log in all my BTC addresses were zeroed, and loading one of the previous wallet backup only helped after trying about 10 times (with different backup). My browser is Chrome (newest version).
From some quick testing I couldn't replicate this but will look into the problem further.
[Chrome extension (maybe others?)] Using Custom Send to send a transaction to multiple addresses, one of the addresses was invalid when I clicked Review Payment: the whole interface locks up leaving all buttons useless.
Should be fixed in the chrome extension. The web interface will be fixed next update.
Could you reduce minimum transaction amount for the Receiving API? 0.001 BTC is worth $0.7 now...
It is now 0.0005. I don't really want to lower it any further yet until the network fee is reduced.
I'm having a problem with a stuck "shared send" transaction now for more than 24 hours. I've sent a couple of support requests, and even provided more info that they asked for.
Sorry for this problem, this issue was your payment into shared send took a long time to confirm. Shared send will not accept zero confirmation transactions unless some very specific conditions are met.
It appears the Firstbits API is broken. Neither of the two API calls return any data.
https://bitcointalk.org/index.php?topic=339981.0Getting this error every time I send some coins: "An outpoint is already spent [(94024681, 1)]" - using the Firefox extension, v3.1.3.
Doesn't seem to affect the transaction though. Any ideas?
I believe this is because the request to /pushtx is timing out causing the app to try and re-submit the transaction, then the second submission is seen as a double spend. An update has been submitted to the firefox extension but it could take a while to get approved.
how can we buy BTC with SMS ? i cant find any option in my wallet
Sorry, this option isn't available anymore.
When using the API to receive payment of certain payments do not reach the destination. They do not go to the primary address. Support is silent and does not respond to tickets. Very bad service!
I think the problem is your payments are below the minimum 0.0005 BTC value. Until the balance of a forwarding address reaches the minimum it will not be forwarded. If it is not due to this then please PM me your ticket number.
-----
- Encrypted paper wallets can now be scanned in the web interface and android app.