<p>A transaction will be distrusted if</p>

<ul>
<li>it conflicts with a transaction already in the blockchain, or</li>
<li>it is from someone else, and it is not confirmed.</li>
</ul>

<p>A transaction will be trusted if</p>

<ul>
<li>it has confirmations.</li>
</ul>

<p>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.)</p>

<p>Once that transaction is confirmed, the trusted field in <code>listtransactions</code> will be true.</p>

CC BY-SA 3.0
2016-11-21T01:03:03.930Z
But this IS a transaction I created and it's currently in limbo.
Rob
CC BY-SA 3.0
2016-11-21T01:03:30.567Z
https://blockchain.info/search/ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024
Rob
CC BY-SA 3.0
2016-11-21T02:51:48.090Z
It can also show as nontrusted if the transaction isn't in your node's memory pool.
Nick ODell
CC BY-SA 3.0
2016-11-21T03:03:41.007Z
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
CC BY-SA 3.0
2016-11-21T03:15:30.120Z
Hmm. Could you try `getrawtransaction <txhash>` followed by `sendrawtransaction <tx>` ?
Nick ODell
CC BY-SA 3.0
2016-11-21T03:47:16.767Z
`$ bitcoin-cli getrawtransaction ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024
error code: -5
error message:
No information available about transaction`
Rob
CC BY-SA 3.0
2016-11-21T00:57:32.333Z
2016-11-21T00:57:32.333Z
Nick ODell
<p>I'm running a full node without the GUI, so I'm controlling it with <code>bitcoin-cli</code>.</p>

<p>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 <code>bitcoin-cli gettransaction ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024</code>, it comes back with:</p>

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

<p>I've never seen <code>"trusted": false</code> 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.</p>

<p><strong>EDIT:</strong>
Pasting the hex format of the raw transaction into blockchain.info/pushtx and pushing it that way has set it to <code>trusted: true</code> 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.</p>

CC BY-SA 3.0
2016-11-21T00:20:11.827Z
This field is discussed in [the 0.12.0 changelog](https://github.com/bitcoin/bitcoin/blob/57b34599b2deb179ff1bd97ffeab91ec9f904d85/doc/release-notes/release-notes-0.12.0.md), 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
CC BY-SA 3.0
2016-11-21T00:36:02.890Z
@NateEldredge Thanks! I'm still mostly clueless but at least now I have a new lead to look at
Rob
CC BY-SA 3.0
2016-11-21T01:20:07.527Z
@NateEldredge: "Coming from ourself" means that your wallet controls the private keys corresponding to the transaction inputs.
Murch
<bitcoind><bitcoin-core><unconfirmed-transactions><bitcoin-cli>
Bitcoin Core telling me transaction is not "trusted"
Rob
# Bitcoin Core telling me transaction is not "trusted"

(Asked by: username_0 on 2016-11-20)

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.

**Tags:** bitcoind, bitcoin-core, unconfirmed-transactions, bitcoin-cli

> **Comments:**
> **username_1**: This field is discussed in [the 0.12.0 changelog](https://github.com/bitcoin/bitcoin/blob/57b34599b2deb179ff1bd97ffeab91ec9f904d85/doc/release-notes/release-notes-0.12.0.md), 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`.  
> **username_0**: @username_1 Thanks! I'm still mostly clueless but at least now I have a new lead to look at  
> **username_2**: @username_1: "Coming from ourself" means that your wallet controls the private keys corresponding to the transaction inputs.  

---

## 1 answers

### Answer by username_3 on 2016-11-21. Score: 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.

> **Comments:**
> **username_0**: But this IS a transaction I created and it's currently in limbo.  
> **username_0**: https://blockchain.info/search/ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024  
> **username_3**: It can also show as nontrusted if the transaction isn't in your node's memory pool.  
> **username_0**: 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?  
> **username_3**: Hmm. Could you try `getrawtransaction <txhash>` followed by `sendrawtransaction <tx>` ?  
> **username_0**: `$ bitcoin-cli getrawtransaction ad2dfbd06b15f0721c2c1864e4cf0989833727c6eec038472c2a2789f4b5d024 error code: -5 error message: No information available about transaction`  

---

