Author

Topic: Bitcoin Core synchronizing problem (Read 194 times)

HCP
legendary
Activity: 2086
Merit: 4361
January 29, 2021, 03:25:51 PM
#8
This is too harsh Cry Cry Cry, there is no way to use BitcoinCore wallet or complete the synchronization without having to completely download full blockchain?
If this is "too harsh", then using a full node client like Bitcoin Core is not for you. You need to stop and ask yourself why you are wanting to use Bitcoin Core? Huh

If you don't have the time/patience and resources to be able to sync the full blockchain, then Bitcoin Core (or any other full node client) is probably not the solution you need/want and you'd be far better off using an SPV (aka "light") client that "syncs" quickly and doesn't require as many resources.
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
January 29, 2021, 07:14:13 AM
#7
This is too harsh Cry Cry Cry, there is no way to use BitcoinCore wallet or complete the synchronization without having to completely download full blockchain?
And if there was a method, how much data would I have to consume.

The whole point of Bitcoin Core is to verify everything before it allows you work with it. "Don't trust, verify".
If you prune you save disk space (and some features with that), but you still have to verify.
If you have good internet, good RAM, some temporary spare space on SSD and a bit of skill or help, all this is not that painful. And you basically do it only once. Of course, you have to see if you really want this.


On the other hand, if you don't want to do this (I don't), just use a SPV wallet, that "syncs" in seconds. But you know this already.
legendary
Activity: 2170
Merit: 1789
January 29, 2021, 07:05:29 AM
#6
This is too harsh Cry Cry Cry, there is no way to use BitcoinCore wallet or complete the synchronization without having to completely download full blockchain?
And if there was a method, how much data would I have to consume.
That's how most full node works, whether it is Bitcoin or not. If you don't want to do it then you should use a light client like Electrum, as mentioned above.
legendary
Activity: 3038
Merit: 4418
Crypto Swap Exchange
January 28, 2021, 11:20:30 AM
#5
What is the benefit of prune mode if I need to download the full-size-blockchain?  Huh Huh
Your storage space can be limited.

I am downloading this wallet for the first time, I would like to try its features, so what are the security features that I will sacrifice with? How many megabytes will the sync take to complete?
Assuming that the block hash being entered is valid. You will download the entire blockchain. If you don't want to wait, use Electrum.
by hurry, Do you think I will wait 11 years for the sync to complete?  Roll Eyes Roll Eyes
No. Come on, the first reply clarified that already.
legendary
Activity: 1596
Merit: 1288
January 28, 2021, 11:18:25 AM
#4
Bitcoin Core will  prune blocks after downloading  the full-size-blockchain.
What is the benefit of prune mode if I need to download the full-size-blockchain?  Huh Huh

The synchronization process actually gets way slower when it nears the current block height, the assumevalid makes the synchronization way faster at the start and slower at the end; you can actually speed up the end if you're in a hurry by specifying assumevalid= currentblockhash with some sacrifice in terms of security.
I am downloading this wallet for the first time, I would like to try its features, so what are the security features that I will sacrifice with? How many megabytes will the sync take to complete?

by hurry, Do you think I will wait 11 years for the sync to complete?  Roll Eyes Roll Eyes
legendary
Activity: 3038
Merit: 4418
Crypto Swap Exchange
January 28, 2021, 10:46:50 AM
#3
Choose BIP39 when you import it.
Bitcoin Core doesn't adopt BIP39 standards. You should be importing individual private keys instead.

Bitcoin Core will  prune blocks after downloading  the full-size-blockchain. It doesn't do this before that point.
It prunes the blocks as it goes. It wouldn't make a difference to the user if it gets deleted during or after the synchronizes and the former would benefit the user more. It's worth noting that pruning actually slows down the synchronizing process somewhat since it has to delete the block files as it goes to fit within the size.

The synchronization process actually gets way slower when it nears the current block height, the assumevalid makes the synchronization way faster at the start and slower at the end; you can actually speed up the end if you're in a hurry by specifying assumevalid= currentblockhash with some sacrifice in terms of security.
sr. member
Activity: 966
Merit: 306
January 28, 2021, 09:17:04 AM
#2
Description of Problem: I don't have enough space to download Full blockchain, so I added prune=550 dbcache=1000 to bitcoin.conf file.
Do you have private key of the wallet or the address that stores your bitcoin? If you have it, it will be easier for you to pass through the space limit, import that private key to Electrum.

Choose BIP39 when you import it.

Quote
However, the sync is taking a long time (11 years).
It is the total time your wallet is behind the latest block on the bitcoin public ledger. It is not the required time to sync your wallet. Depends on your computer capacity as RAM and do you run multi-programs on your computer when you are syncing wallet, the internet connection speed, the total time to sync it will be different. It can be days, weeks or months.

With prune node, you will get troubles to -- reindex -- to redownload chainstate for your wallet every time it was broken.

Electrum is synced in seconds or minutes.
legendary
Activity: 1596
Merit: 1288
January 28, 2021, 09:12:38 AM
#1
Bitcoin Client Software and Version Number: Windows v0.20.1
Operating System: Windows 10
System Hardware Specs: + 150 GB
Description of Problem: I don't have enough space to download Full blockchain, so I added prune=550 dbcache=1000 to bitcoin.conf file. However, the sync is taking a long time (11 years).
Any Related Addresses: non
Any Related Transaction IDs: non
Screenshot of the problem:




Log Files from the Bitcoin Client:
Quote
2021-01-28T14:05:15Z Default data directory C:\Users\¬¬¬\AppData\Roaming\Bitcoin
2021-01-28T14:05:15Z Using data directory C:\Users\¬¬¬\AppData\Roaming\Bitcoin
2021-01-28T14:05:15Z Config file: C:\Users\¬¬¬\AppData\Roaming\Bitcoin\bitcoin.conf
2021-01-28T14:05:15Z Config file arg: dbcache="1000"
2021-01-28T14:05:15Z Config file arg: prune="550"
2021-01-28T14:05:15Z Using at most 125 automatic connections (2048 file descriptors available)
2021-01-28T14:05:15Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-01-28T14:05:15Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-01-28T14:05:15Z Script verification uses 3 additional threads
2021-01-28T14:05:15Z scheduler thread start
2021-01-28T14:05:15Z Using wallet directory C:\Users\¬¬¬¬\AppData\Roaming\Bitcoin\wallets
2021-01-28T14:05:15Z init message: Verifying wallet(s) ...
Jump to: