2

I'm running a full node without the GUI, so I'm controlling it with bitcoin-cli.

I sent bitcoin to another address, same as I always do, but this time I can't pull up the transaction on any of the block explorers and when I use bitcoin-cli gettransaction ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024, it comes back with:

  "amount": -0.01949732,
  "fee": -0.00007460,
  "confirmations": 0,
  "trusted": false,
  "txid": "ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024",
  "walletconflicts": [
  ],
  "time": 1479664206,
  "timereceived": 1479664206,
  "bip125-replaceable": "unknown"

I've never seen "trusted": false on any other transaction, so I assume that has something to do with it, but I can't find any information online to tell me what it means.

EDIT: Pasting the hex format of the raw transaction into blockchain.info/pushtx and pushing it that way has set it to trusted: true and now it's showing up. I'd still like to know why it happened and/or how I can fix it myself without relying on blockchain.info's pushtx tool.

Improve this question
3
  • 1
    This field is discussed in the 0.12.0 changelog, see under "Negative confirmations". I'm not sure what "coming from ourself" means, though. The code that implements it is in CWalletTx::IsTrusted() in wallet.cpp.
    – Nate Eldredge
    Nov 21, 2016 at 0:20
  • @NateEldredge Thanks! I'm still mostly clueless but at least now I have a new lead to look at
    – Rob
    Nov 21, 2016 at 0:36
  • @NateEldredge: "Coming from ourself" means that your wallet controls the private keys corresponding to the transaction inputs.
    – Murch ♦
    Nov 21, 2016 at 1:20

1 Answer 1

Reset to default
3

A transaction will be distrusted if

  • it conflicts with a transaction already in the blockchain, or
  • it is from someone else, and it is not confirmed.

A transaction will be trusted if

  • it has confirmations.

If a transaction is not trusted, the client won't create transactions that spend it. (You wouldn't want a transaction you created to be in limbo because one of its inputs wasn't confirmed.)

Once that transaction is confirmed, the trusted field in listtransactions will be true.

Improve this answer
6
  • But this IS a transaction I created and it's currently in limbo.
    – Rob
    Nov 21, 2016 at 1:03
  • blockchain.info/search/…
    – Rob
    Nov 21, 2016 at 1:03
  • It can also show as nontrusted if the transaction isn't in your node's memory pool.
    – Nick ODell
    Nov 21, 2016 at 2:51
  • But if I sent it, why would it not be in my memory pool? Or how would I check if its in the mempool? And how would I add it?
    – Rob
    Nov 21, 2016 at 3:03
  • Hmm. Could you try getrawtransaction <txhash> followed by sendrawtransaction <tx> ?
    – Nick ODell
    Nov 21, 2016 at 3:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.