should be fixed now.
Yep, thank you. 
Topic: BlockChain Different Transaction Hash (Read 1634 times)
should be fixed now.
We made a change to more properly handle the malleable transactions, which required a new normalized index. Our servers are re-indexing transactions from the most recent to oldest. Some older hashes (if the transaction as altered) will not show up until they are indexed. Give it some time, and you should be able to search for the transaction again.
Hope this helps.
Hope this helps.
This is still an issue. The tx_hash values being returned from the /payment wallet endpoint are not in the Blockchain and are different from the tx_hash values in the Blockchain.info Wallet web interface.
Is there a fix incoming or has someone found a workaround?
We made a change to more properly handle the malleable transactions, which required a new normalized index. Our servers are re-indexing transactions from the most recent to oldest. Some older hashes (if the transaction as altered) will not show up until they are indexed. Give it some time, and you should be able to search for the transaction again.
Hope this helps.
Hope this helps.
This is still an issue. The tx_hash values being returned from the /payment wallet endpoint are not in the Blockchain and are different from the tx_hash values in the Blockchain.info Wallet web interface.
Is there a fix incoming or has someone found a workaround?
We made a change to more properly handle the malleable transactions, which required a new normalized index. Our servers are re-indexing transactions from the most recent to oldest. Some older hashes (if the transaction as altered) will not show up until they are indexed. Give it some time, and you should be able to search for the transaction again.
Hope this helps.
Hope this helps.
Yap, same thing to me.
I though Blockchain.info wasn't affected by this?
I though Blockchain.info wasn't affected by this?
Their wallet-service wasn't affected in the way that balances would still display correctly, but they have no influence over which version of a transaction ends up being included in the blockchain, so if that's a different version than the one you originally sent, you will still get lookup errors.
Not every transaction was altered.
Yap, same thing to me.
I though Blockchain.info wasn't affected by this?
I though Blockchain.info wasn't affected by this?
Their wallet-service wasn't affected in the way that balances would still display correctly, but they have no influence over which version of a transaction ends up being included in the blockchain, so if that's a different version than the one you originally sent, you will still get lookup errors.
Yap, same thing to me.
I though Blockchain.info wasn't affected by this?
I though Blockchain.info wasn't affected by this?
Their wallet-service wasn't affected in the way that balances would still display correctly, but they have no influence over which version of a transaction ends up being included in the blockchain, so if that's a different version than the one you originally sent, you will still get lookup errors.
bump
Yap, same thing to me.
I though Blockchain.info wasn't affected by this?
I though Blockchain.info wasn't affected by this?
You're not doing anything wrong.
Look around on the forums for "transaction malleability". It's kind of a big thing the last few days.
Look around on the forums for "transaction malleability". It's kind of a big thing the last few days.
Hello, I've sent a couple of transactions via PHP using BlockChains Wallet API, and a var_dump of the response comes back similar to;
string(118) "{"message":"Sent To Multiple Recipients","tx_hash":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}"
However when I lookup the tx_hashs returned by BlockChain's API on their website they come back as an invalid transaction IDs, and when checking my wallet through the BlockChain website, the transactions now have totally different IDs.
Am I doing something wrong?
string(118) "{"message":"Sent To Multiple Recipients","tx_hash":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}"
However when I lookup the tx_hashs returned by BlockChain's API on their website they come back as an invalid transaction IDs, and when checking my wallet through the BlockChain website, the transactions now have totally different IDs.
Am I doing something wrong?
Jump to: