Bitcoin Forum
September 27, 2018, 10:38:16 PM *
News: ♦♦ New info! Bitcoin Core users absolutely must upgrade to previously-announced 0.16.3 [Torrent]. All Bitcoin users should temporarily trust confirmations slightly less. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Under what conditions would a coin wallet fail for a call to getrawtransaction?  (Read 482 times)
DocJeff
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
April 25, 2014, 07:58:18 AM
 #1

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?
1538087896
Hero Member
*
Offline Offline

Posts: 1538087896

View Profile Personal Message (Offline)

Ignore
1538087896
Reply with quote  #2

1538087896
Report to moderator
1538087896
Hero Member
*
Offline Offline

Posts: 1538087896

View Profile Personal Message (Offline)

Ignore
1538087896
Reply with quote  #2

1538087896
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1538087896
Hero Member
*
Offline Offline

Posts: 1538087896

View Profile Personal Message (Offline)

Ignore
1538087896
Reply with quote  #2

1538087896
Report to moderator
1538087896
Hero Member
*
Offline Offline

Posts: 1538087896

View Profile Personal Message (Offline)

Ignore
1538087896
Reply with quote  #2

1538087896
Report to moderator
1538087896
Hero Member
*
Offline Offline

Posts: 1538087896

View Profile Personal Message (Offline)

Ignore
1538087896
Reply with quote  #2

1538087896
Report to moderator
fbueller
Sr. Member
****
Offline Offline

Activity: 412
Merit: 250


View Profile
April 25, 2014, 08:16:58 AM
 #2

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?

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.

Bitwasp Developer.
DocJeff
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
April 25, 2014, 08:24:46 AM
 #3

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?

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
DocJeff
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
April 25, 2014, 08:36:58 AM
 #4

Turns out it worked, thanks a lot.
There's a massive number of vout instances. Is this normal for large transactions?
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!