Did someone just double spend?

[madmadmax]

I have a txid that I can get with gettransaction but get an "No information available about transaction (code -5)" if I use getrawtransaction, also the transaction has zero fees and doesn't show up on blockchain.info even though it was sent 4 days ago.

I had already spent it and have multiple stuck transaction on zero conf, I figured it's a little weird since I would at least have the key the transaction got signed with.

[btbrae]

Don't know if you did it but you have to load bitcoin with -reindex -txindex to make getrawtransaction work for spent transactions, or something like that...

[madmadmax]

Don't know if you did it but you have to load bitcoin with -reindex -txindex to make getrawtransaction work for spent transactions, or something like that...

Already did...

[madmadmax]

I have launched the client with -rescan and now I am able to grab the raw transaction, when I push it with https://blockchain.info/pushtx I get "unable to find all tx inputs" yet it still appear in the client for some reason.

[kjj]

I have launched the client with -rescan and now I am able to grab the raw transaction, when I push it with https://blockchain.info/pushtx I get "unable to find all tx inputs" yet it still appear in the client for some reason.

Could be.  The client doesn't report (or, in general, even know) why a transaction isn't getting confirmations, it just accurately reports zero.

You could track down all of the inputs to your 0-conf.  One or more of them either has been already used, or wasn't confirmed (perhaps because it wasn't broadcast).

[madmadmax]

I have launched the client with -rescan and now I am able to grab the raw transaction, when I push it with https://blockchain.info/pushtx I get "unable to find all tx inputs" yet it still appear in the client for some reason.

Could be.  The client doesn't report (or, in general, even know) why a transaction isn't getting confirmations, it just accurately reports zero.

You could track down all of the inputs to your 0-conf.  One or more of them either has been already used, or wasn't confirmed (perhaps because it wasn't broadcast).

Says "an outpoint is already spent" when I try to push the other one, I don't understand why they keep showing up on the client though, shouldn't -rescan eliminate all the transactions with spent inputs?

[tysat]

Post some links to transactions IDs or addresses involved?  Maybe others can help investigate.

[kjj]

-rescan reads the block chain and adds any missing transactions to your wallet's collection.  It does not remove anything.  Actually, there is no mechanism in the standard client to remove transactions from the wallet database.

[madmadmax]

Post some links to transactions IDs or addresses involved?  Maybe others can help investigate.

I would rather not I think the inputs were already spent and it will never confirm, thanks for your help guys.