<p>I've had the same issue after restoring from wallet.dat. It's probably a bug described in <a href="https://github.com/bitcoin/bitcoin/issues/20293" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/issues/20293</a>. Possible way to fix it is by setting an empty label to the address that became change:</p>
<pre><code>bitcoin-cli setlabel &quot;{address}&quot; &quot;&quot; 
</code></pre>

CC BY-SA 4.0
2022-01-04T22:00:13.417Z
FYI, this bug should be fixed in the next release :)
meshcollider
CC BY-SA 4.0
2021-04-09T15:32:21.280Z
2021-04-09T15:32:21.280Z
anon
<p>After restoring wallet from wallet.dat balance is identical, </p>

<p>but <code>listreceivedbyaddress 0</code> do not have the transactions associated with wallet.</p>

<p><code>listunspent 0</code> show all the transactions, but it will not list anymore after spending.</p>

<p>is it a bug? or do i have to perform some special scan? <code>rescanblockchain</code> found all the transactions, but they are still missing in the <code>listreceivedbyaddress</code>.</p>

<p><strong>EDIT #1</strong></p>

<p>Is there a way to get all the transactions associated with specific address, what will get accurate result from blockchain? Was supposed to be bellow command what is not working sometimes.</p>

<pre><code>listreceivedbyaddress 0 true true {ADDRESS}
</code></pre>

<p><strong>EDIT #2</strong></p>

<p>Output of <code>getaddressinfo {ADDRESS}</code> differences between recent, and backup wallet:</p>

<pre><code>+  "solvable": true,
+  "desc": "sh(wpkh([6f8c0001/0'/0'/306']034e{SCRAMBLED_LONG_CODE}e50f))#ejlphmc0",
+  "ischange": true,
-  "hdmasterkeyid": "f9248{SCRAMBLED_LONG_CODE}53587b4",
+  "hdmasterfingerprint": "6f8c0001",
   "labels": [
-    {
-      "name": "default_wallet",
-      "purpose": "receive"
-    }
   ]
</code></pre>

CC BY-SA 4.0
2019-06-16T17:36:38.430Z
If you run `getaddressinfo` on the address whose incoming tramsactions are missing, what does it say about being change?
Pieter Wuille
CC BY-SA 4.0
2019-06-18T05:48:01.867Z
@PieterWuille, ```getaddressinfo``` shows that restored wallet consider address as "change"
staticgeek
CC BY-SA 4.0
2019-06-21T20:41:12.657Z
Can you give an as detailed history of how you got into this state? It's possibly a bug that this address is being considered change.
Pieter Wuille
<address><json-rpc><api>
listreceivedbyaddress missing transactions after restore
staticgeek
# listreceivedbyaddress missing transactions after restore

(Asked by: username_0 on 2019-06-16)

After restoring wallet from wallet.dat balance is identical, 
but listreceivedbyaddress 0 do not have the transactions associated with wallet.
listunspent 0 show all the transactions, but it will not list anymore after spending.
is it a bug? or do i have to perform some special scan? rescanblockchain found all the transactions, but they are still missing in the listreceivedbyaddress.
EDIT #1
Is there a way to get all the transactions associated with specific address, what will get accurate result from blockchain? Was supposed to be bellow command what is not working sometimes.
listreceivedbyaddress 0 true true {ADDRESS}

EDIT #2
Output of getaddressinfo {ADDRESS} differences between recent, and backup wallet:
+  "solvable": true,
+  "desc": "sh(wpkh([6f8c0001/0'/0'/306']034e{SCRAMBLED_LONG_CODE}e50f))#ejlphmc0",
+  "ischange": true,
-  "hdmasterkeyid": "f9248{SCRAMBLED_LONG_CODE}53587b4",
+  "hdmasterfingerprint": "6f8c0001",
   "labels": [
-    {
-      "name": "default_wallet",
-      "purpose": "receive"
-    }
   ]

**Tags:** address, json-rpc, api

> **Comments:**
> **username_1**: If you run `getaddressinfo` on the address whose incoming tramsactions are missing, what does it say about being change?  
> **username_0**: @PieterWuille, ```getaddressinfo``` shows that restored wallet consider address as "change"  
> **username_1**: Can you give an as detailed history of how you got into this state? It's possibly a bug that this address is being considered change.  

---

## 1 answers

### Answer by username_2 on 2021-04-09. Score: 1

I've had the same issue after restoring from wallet.dat. It's probably a bug described in https://github.com/bitcoin/bitcoin/issues/20293. Possible way to fix it is by setting an empty label to the address that became change:
bitcoin-cli setlabel "{address}" ""

> **Comments:**
> **username_3**: FYI, this bug should be fixed in the next release :)  

---

