|
Title: BlockChain Different Transaction Hash Post by: jayc89 on February 13, 2014, 06:55:43 PM 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? Title: Re: BlockChain Different Transaction Hash Post by: Rannasha on February 13, 2014, 08:34:45 PM 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. Title: Re: BlockChain Different Transaction Hash Post by: ingrownpocket on February 14, 2014, 03:47:16 PM Yap, same thing to me.
I though Blockchain.info wasn't affected by this? Title: Re: BlockChain Different Transaction Hash Post by: ingrownpocket on February 17, 2014, 04:58:47 PM bump
Title: Re: BlockChain Different Transaction Hash Post by: Rannasha on February 17, 2014, 05:07:13 PM Yap, same thing to me. 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. Title: Re: BlockChain Different Transaction Hash Post by: ingrownpocket on February 17, 2014, 05:30:13 PM Yap, same thing to me. 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. Title: Re: BlockChain Different Transaction Hash Post by: Rannasha on February 17, 2014, 05:59:58 PM Yap, same thing to me. 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. Title: Re: BlockChain Different Transaction Hash Post by: cpzhao on February 18, 2014, 07:17:23 AM 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. Title: Re: BlockChain Different Transaction Hash Post by: robee on February 25, 2014, 06:35:32 PM 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. 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? Title: Re: BlockChain Different Transaction Hash Post by: ingrownpocket on March 02, 2014, 12:14:12 PM 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. 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? Title: Re: BlockChain Different Transaction Hash Post by: cpzhao on March 04, 2014, 01:52:04 PM should be fixed now.
Title: Re: BlockChain Different Transaction Hash Post by: ingrownpocket on March 04, 2014, 05:41:16 PM should be fixed now. Yep, thank you. |