search

blockchain / unused-My-Wallet

Legacy Blockchain Web Wallet - current version is at https://github.com/blockchain/My-Wallet-V3-Frontend
205 stars 127 forks source link

Send Many Transactions API returns wrong tx_hash #72

Closed sashazykov closed 9 years ago

sashazykov commented 10 years ago

It's a critical bug for our project. I had to suspend withdrawals.

If you can't fix it, it would be great to have an option not to receive Http Callbacks for outgoing transactions, because there is no way for us to see difference between change and deposits.

muddymess commented 10 years ago

Also an issue on single send. Both return an incorrect tx_hash, and the correct transaction id doesn't retain the included note.

YellowGreenBlue commented 10 years ago

I have the same problem with both the Blockchain API and RPC, an incorrect tx_hash is being returned by the request.

tigerss commented 10 years ago

I have noticed this problem too when sending multiple transactions

pelle commented 10 years ago

This is also a problem with the /unspent api from from JSON. The HTML version shows the correct tx_hash.

FreeTrade commented 10 years ago

Noticing the same problem.

these two reference the same transaction - but have different values -

https://blockchain.info/tx/6c56385823d6bdfe12af0c174ae89e3c31c77eb298f27a6e1956f216ba519150?show_adv=true

https://blockchain.info/unspent?address=1A5Me3tuSKYqp4RnFmHcWTURexZ42VfJQq

However, bizarrely, brainwallet uses the unspent api, and seems to require having the wrong tx_hash here to function correctly - see here - http://memorywallet.org

What is the tx_hash value in unspent?

FreeTrade commented 10 years ago

see here - https://github.com/blockchain/My-Wallet/issues/74

sashazykov commented 10 years ago

Fixed for me