<blockquote>
  <p>The wallet itself is still downloading the block and is 3 years and 29 months behind. Does this mean I must wait until this finishes before it shows up?</p>
</blockquote>

<p>Yes, in order to understand the current state of the network (which includes the transaction that you received funds in), your node will need to work through the blockchain history. Otherwise, your node will be unable to determine whether or not a transaction you receive is in fact valid. </p>

<p>Once synced with the network, your balance should display correctly. </p>

CC BY-SA 4.0
2019-12-24T09:51:40.483Z
can i rescan to pick up the transaction. if so how do i do it?
burchbit
CC BY-SA 4.0
2019-12-24T10:10:29.407Z
No, in order for your wallet to understand that the transaction is valid, it needs to first sync to the network.
chytrik
CC BY-SA 4.0
2019-12-24T18:18:21.763Z
@wizzwizz4 ‘rescanblockchain’ is a specific rpc call that can be used *after* the sync is complete
chytrik
CC BY-SA 4.0
2019-12-24T04:37:53.307Z
2019-12-24T04:37:53.307Z
chytrik
<blockquote>
  <p>The transaction has been cleared on the blockchain</p>
</blockquote>

<p>How did you know that? Did you query the corresponding transaction on an online blockchain explorer?</p>

<p>If you are happy to trust third party services (like the online blockchain explorer you had used), then generally speaking, (you believed that) you have already received these bitcoins.</p>

<p>You just have not validated the transaction with your own full node yet.</p>

<blockquote>
  <p>can i rescan to pick up the transaction. if so how do i do it?</p>
</blockquote>

<p>Rescanning requires full blockchain data, the thing which you have not finished downloading and validating yet.</p>

<p>(In future versions of Bitcoin Core, this might be improved. With BIP158 blockfilterindex, even pruned full nodes can do rescanning as well)</p>

<p>Rescanning would be required only if you had just imported something, or you were not quite sure whether the available balances/transaction history showed by the wallet were correct.</p>

CC BY-SA 4.0
2019-12-24T13:41:51.657Z
can i import this wallet into another wallet?  i need this money asap.
burchbit
CC BY-SA 4.0
2019-12-24T14:01:01.237Z
@burchbit Of course you can. You can execute the "dumpprivkey YOUR_RECEIVING_ADDRESS" in the debug console of Bitcoin Core to get the WIF private key, then you may import it into lightweight wallets like Electrum. However, manual operations on private keys are generally not adviced, since human errors may lead to tragic outcomes, eg. the classical "screw-up-by-change-address", or leaking the private key to trojan horses/malicious QR code generators, ... etc.
Chris Chen
CC BY-SA 4.0
2019-12-24T14:36:26.607Z
thank you.... i got this error........Please enter the wallet passphrase with walletpassphrase first. (code -13)
burchbit
CC BY-SA 4.0
2019-12-24T14:39:15.013Z
@burchbit You need to unlock the wallet first, use the "walletpassphrase" command. It will unlock the wallet for a while. If the wallet is successfully unlocked, this command shows nothing as output.
Chris Chen
CC BY-SA 4.0
2019-12-24T14:47:47.227Z
@burchbit If you want to import the WIF private key into Electrum, you will need to create a new wallet with it firstly, then you should choose "Import bitcoin addresses or private keys", after pasting the WIF private key, you need to add a "p2wpkh-p2sh:" prefix to the private key in order to generate 3-starting compatible segwit address, or "p2wpkh:" prefix to generate bc1-starting bech32 native segwit address.
Chris Chen
CC BY-SA 4.0
2019-12-28T06:03:21.110Z
i added the key and it imported another address.  the address i wanted to add cannot be verified by signing message because no key associated
burchbit
CC BY-SA 4.0
2019-12-28T12:11:15.657Z
Oh, you must be talking about segwit. A compressed (starting with K/L) private key can derive three types of address: 1-starting P2PKH "legacy" address, 3-starting P2SH-wrapped "compatible SegWit" address, bc1-starting bech32 "native SegWit" address. Unfortunately, there is still no unanimously adopted standard of message signing/verifying of SegWit addresses, that's probably why you received "no key associated" error message (shoud be shown by bitcoin core?)
Chris Chen
CC BY-SA 4.0
2019-12-28T12:15:42.173Z
AFAIK, both Electrum and Trezor had implemented this message sign/verify feature of SegWit addresses, however, they are not compatible with each other.
Chris Chen
CC BY-SA 4.0
2019-12-28T19:19:58.613Z
it is a base58 p2sh
burchbit
CC BY-SA 4.0
2019-12-28T19:26:21.890Z
You are still using Bitcoin Core, aren't you? If so, don't worry about the "no associated key" error message when you attempt to sign a message with a P2SH SegWit address.
Chris Chen
CC BY-SA 4.0
2019-12-28T20:57:34.720Z
so how to sign and unlock these funds? or generate a private key.
burchbit
CC BY-SA 4.0
2019-12-29T06:40:45.613Z
The "no key associated" error message is incorrect and misleading. There's definitely a public/private key pair associated to a SegWit address. If you want to send the coins out, just send them as usual, there won't be any problem (if you have finished syncing). It's just detailed implementation of the message signing feature that has not been determined by the developers of Bitcoin Core.
Chris Chen
CC BY-SA 4.0
2019-12-29T06:44:34.393Z
If you want to export them to wallets other than Bitcoin Core, you can use the dumpprivkey command in the debug console. If you want to import the private key to Electrum, you need to choose the "New/Recover" option in the "File" menu first, then the "import Bitcoin private keys or addresses" should be chosen, after that, you need to add a "p2wpkh-p2sh:" prefix to the private key.
Chris Chen
CC BY-SA 4.0
2019-12-24T13:30:54.767Z
2019-12-24T13:30:54.767Z
Chris Chen
<p>Today I sent bitcoin to my bitcoin core wallet.  I used an address under recieve bitcoins.  The transaction has been cleared on the blockchain for several hours but is not showing up in my wallet.    The wallet itself is still downloading the block and is 3 years and 29 months behind.</p>

<p>Does this mean I must wait until this finishes before it shows up?</p>

CC BY-SA 4.0
2019-12-24T16:54:15.303Z
3 years and 29 months behind??? Why not 5 years and 5 months? As a non-bitcoin person arriving here via HNQ this post further validates my abstinence from cryptocurrencies. I don't know what it means to be 5 years behind but if that's how long you wait to receive your funds then woof.
MonkeyZeus
CC BY-SA 4.0
2019-12-24T17:56:02.957Z
@MonkeyZeus it only takes a few hours for a brand new node to sync the 10 year Blockchain history. Up to a few days on a slower machine. The progress indicator may report "5 years behind" but that's not how much time you need to wait until your node is synced :-)
pinhead
<bitcoin-core><blockchain><synchronization><wallet-recovery><receiving>
When will I receive bitcoins
burchbit
# When will I receive bitcoins

(Asked by: username_0 on 2019-12-24)

Today I sent bitcoin to my bitcoin core wallet. I used an address under recieve bitcoins. The transaction has been cleared on the blockchain for several hours but is not showing up in my wallet. The wallet itself is still downloading the block and is 3 years and 29 months behind.

Does this mean I must wait until this finishes before it shows up?

**Tags:** bitcoin-core, blockchain, synchronization, wallet-recovery, receiving

> **Comments:**
> **username_1**: 3 years and 29 months behind??? Why not 5 years and 5 months? As a non-bitcoin person arriving here via HNQ this post further validates my abstinence from cryptocurrencies. I don't know what it means to be 5 years behind but if that's how long you wait to receive your funds then woof.  
> **username_2**: @username_1 it only takes a few hours for a brand new node to sync the 10 year Blockchain history. Up to a few days on a slower machine. The progress indicator may report "5 years behind" but that's not how much time you need to wait until your node is synced :-)  

---

## 2 answers

### Answer by username_3 on 2019-12-24. Score: 3

> The wallet itself is still downloading the block and is 3 years and 29 months behind. Does this mean I must wait until this finishes before it shows up?

Yes, in order to understand the current state of the network (which includes the transaction that you received funds in), your node will need to work through the blockchain history. Otherwise, your node will be unable to determine whether or not a transaction you receive is in fact valid.

Once synced with the network, your balance should display correctly.

> **Comments:**
> **username_0**: can i rescan to pick up the transaction. if so how do i do it?  
> **username_3**: No, in order for your wallet to understand that the transaction is valid, it needs to first sync to the network.  
> **username_3**: @wizzwizz4 ‘rescanblockchain’ is a specific rpc call that can be used *after* the sync is complete  

---

### Answer by username_4 on 2019-12-24. Score: 0

> The transaction has been cleared on the blockchain

How did you know that? Did you query the corresponding transaction on an online blockchain explorer?

If you are happy to trust third party services (like the online blockchain explorer you had used), then generally speaking, (you believed that) you have already received these bitcoins.

You just have not validated the transaction with your own full node yet.

> can i rescan to pick up the transaction. if so how do i do it?

Rescanning requires full blockchain data, the thing which you have not finished downloading and validating yet.

(In future versions of Bitcoin Core, this might be improved. With BIP158 blockfilterindex, even pruned full nodes can do rescanning as well)

Rescanning would be required only if you had just imported something, or you were not quite sure whether the available balances/transaction history showed by the wallet were correct.

> **Comments:**
> **username_0**: can i import this wallet into another wallet?  i need this money asap.  
> **username_4**: @username_0 Of course you can. You can execute the "dumpprivkey YOUR_RECEIVING_ADDRESS" in the debug console of Bitcoin Core to get the WIF private key, then you may import it into lightweight wallets like Electrum. However, manual operations on private keys are generally not adviced, since human errors may lead to tragic outcomes, eg. the classical "screw-up-by-change-address", or leaking the private key to trojan horses/malicious QR code generators, ... etc.  
> **username_0**: thank you.... i got this error........Please enter the wallet passphrase with walletpassphrase first. (code -13)  
> **username_4**: @username_0 You need to unlock the wallet first, use the "walletpassphrase" command. It will unlock the wallet for a while. If the wallet is successfully unlocked, this command shows nothing as output.  
> **username_4**: @username_0 If you want to import the WIF private key into Electrum, you will need to create a new wallet with it firstly, then you should choose "Import bitcoin addresses or private keys", after pasting the WIF private key, you need to add a "p2wpkh-p2sh:" prefix to the private key in order to generate 3-starting compatible segwit address, or "p2wpkh:" prefix to generate bc1-starting bech32 native segwit address.  
> **username_0**: i added the key and it imported another address.  the address i wanted to add cannot be verified by signing message because no key associated  
> **username_4**: Oh, you must be talking about segwit. A compressed (starting with K/L) private key can derive three types of address: 1-starting P2PKH "legacy" address, 3-starting P2SH-wrapped "compatible SegWit" address, bc1-starting bech32 "native SegWit" address. Unfortunately, there is still no unanimously adopted standard of message signing/verifying of SegWit addresses, that's probably why you received "no key associated" error message (shoud be shown by bitcoin core?)  
> **username_4**: AFAIK, both Electrum and Trezor had implemented this message sign/verify feature of SegWit addresses, however, they are not compatible with each other.  
> **username_0**: it is a base58 p2sh  
> **username_4**: You are still using Bitcoin Core, aren't you? If so, don't worry about the "no associated key" error message when you attempt to sign a message with a P2SH SegWit address.  
> **username_0**: so how to sign and unlock these funds? or generate a private key.  
> **username_4**: The "no key associated" error message is incorrect and misleading. There's definitely a public/private key pair associated to a SegWit address. If you want to send the coins out, just send them as usual, there won't be any problem (if you have finished syncing). It's just detailed implementation of the message signing feature that has not been determined by the developers of Bitcoin Core.  
> **username_4**: If you want to export them to wallets other than Bitcoin Core, you can use the dumpprivkey command in the debug console. If you want to import the private key to Electrum, you need to choose the "New/Recover" option in the "File" menu first, then the "import Bitcoin private keys or addresses" should be chosen, after that, you need to add a "p2wpkh-p2sh:" prefix to the private key.  

---

