Turns out it worked, thanks a lot.
There's a massive number of vout instances. Is this normal for large transactions?
Topic: Under what conditions would a coin wallet fail for a call to getrawtransaction? (Read 560 times)
April 25, 2014, 03:36:58 AM
April 25, 2014, 03:24:46 AM
So I'm not specifically crawling the bitcoin blockchain, simply because it's too big to wait for a download right now, but I'm trying to dig through other altcoin transaction histories instead.
Using the process:
tx = decoderawtransaction(getrawtransaction(txid_initial))
repeat again for tx['vin']['txid']
After going back a tx or two, the transaction doesn't seem to exist. Or at least that's what the wallet thinks. I know the transaction took place though, because I've got the coins from that transaction sitting in another wallet, and I checked the txid they're the same.
Is this a product of the coin wallet I've chosen, or is this a product of how the bitcoin-rpc interface is "supposed" to behave?
Using the process:
tx = decoderawtransaction(getrawtransaction(txid_initial))
repeat again for tx['vin']['txid']
After going back a tx or two, the transaction doesn't seem to exist. Or at least that's what the wallet thinks. I know the transaction took place though, because I've got the coins from that transaction sitting in another wallet, and I checked the txid they're the same.
Is this a product of the coin wallet I've chosen, or is this a product of how the bitcoin-rpc interface is "supposed" to behave?
Before you can query arbitrary transactions, add the txindex=1 entry to your config file, and then reindex Bitcoind.this is standard.
As usual there are circumstances you should be aware of, if its not fully synced it will fail. If you recorded an incoming payment I'd at zero confirmations then you have malleability to worry about.
This should be sufficient, currect?
Change config -> stop daemon -> start daemon -> daemon --reindex
April 25, 2014, 03:16:58 AM
So I'm not specifically crawling the bitcoin blockchain, simply because it's too big to wait for a download right now, but I'm trying to dig through other altcoin transaction histories instead.
Using the process:
tx = decoderawtransaction(getrawtransaction(txid_initial))
repeat again for tx['vin']['txid']
After going back a tx or two, the transaction doesn't seem to exist. Or at least that's what the wallet thinks. I know the transaction took place though, because I've got the coins from that transaction sitting in another wallet, and I checked the txid they're the same.
Is this a product of the coin wallet I've chosen, or is this a product of how the bitcoin-rpc interface is "supposed" to behave?
Using the process:
tx = decoderawtransaction(getrawtransaction(txid_initial))
repeat again for tx['vin']['txid']
After going back a tx or two, the transaction doesn't seem to exist. Or at least that's what the wallet thinks. I know the transaction took place though, because I've got the coins from that transaction sitting in another wallet, and I checked the txid they're the same.
Is this a product of the coin wallet I've chosen, or is this a product of how the bitcoin-rpc interface is "supposed" to behave?
Before you can query arbitrary transactions, add the txindex=1 entry to your config file, and then reindex Bitcoind.this is standard.
As usual there are circumstances you should be aware of, if its not fully synced it will fail. If you recorded an incoming payment I'd at zero confirmations then you have malleability to worry about.
April 25, 2014, 02:58:18 AM
So I'm not specifically crawling the bitcoin blockchain, simply because it's too big to wait for a download right now, but I'm trying to dig through other altcoin transaction histories instead.
Using the process:
tx = decoderawtransaction(getrawtransaction(txid_initial))
repeat again for tx['vin']['txid']
After going back a tx or two, the transaction doesn't seem to exist. Or at least that's what the wallet thinks. I know the transaction took place though, because I've got the coins from that transaction sitting in another wallet, and I checked the txid they're the same.
Is this a product of the coin wallet I've chosen, or is this a product of how the bitcoin-rpc interface is "supposed" to behave?
Using the process:
tx = decoderawtransaction(getrawtransaction(txid_initial))
repeat again for tx['vin']['txid']
After going back a tx or two, the transaction doesn't seem to exist. Or at least that's what the wallet thinks. I know the transaction took place though, because I've got the coins from that transaction sitting in another wallet, and I checked the txid they're the same.
Is this a product of the coin wallet I've chosen, or is this a product of how the bitcoin-rpc interface is "supposed" to behave?
Jump to: