here a bash script for see the live progress
create a file nano [nom fichier] and copy the code below
run script with bash [nom fichier]
stop script by type on your keyboard
sleepTime=4 #set time between updates
blocksTotal=$(wget -O - http://blockchain.info/q/getblockcount 2>/dev/null)
The problem is that your wallet version is extremely old - it predates support for compressed public keys (which was added in v0.6.0, released in March 2012). As segwit addresses require compressed public keys, Bitcoin Core is failing with the keys you have, and defaulting to legacy addresses instead.
The solution is restart with -upgradewallet (just once), ...
For set up the dns seed node, the parameter can be directly specified in chainparam.cpp if you are using bitcoin source in line that reads as "
vSeeds.push_back(CDNSSeedData("someaddress.com or IP addy", "someaddress.com"));
And you need to add all the seed node IP address to the A records where you have your domain name from. You might need to do it on ...
I would assume the issue is not Bitcoin Core, even with default RPC settings I do see noticeable increase in client performance when using async/await (C# library). My suggestion is to investigate how the client code handles the RPC request/response + block parsing.
You cannot. Bitcoin Core cannot reason about arbitrary scripts and does not have the capability to sign for them. As such, it cannot create arbitrary scripts and store them.
You can create the script yourself and import it into a wallet using importmulti. This will only add the script to the wallet to be tracked. This will only let your wallet see ...
Is this wallet.dat with balance some sort of scam or exploit?
It looks like a scam.
There is never a good reason to buy a wallet.dat.
Looking at these videos, you will notice
I guess we will notice whatever the video creator tricks us into noticing. As I'm sure you know, making an app that looks like another app is trivial. As is editing video to make ...
First, make sure you have listen=1 in your bitcoin.conf file, and that the P2P port is open on your VPS so that it can make more than 8 connections.
Then you'll want to make sure you have a high disk speed or IO specified (definitely not HDD - I have a feeling you meant SSD). The faster the SSD the better. 2GB RAM should be fine, but you may want to up it ...
- stop bitcoind; download the blocks from another source (there are some through torrent) and copy them to the data directory; You then restart bitcoind and let it go through the blockhain validating everything.
- increase the database cache size with the command line -dbcache. You can increase this to max 4GB. But you'll need a more ram in your ...
If node B isn't connected to internet, only to node A, and its status is pruned, it means it saves the recent history defined by the pruned flag with a value in MB (last X MB).
But your node A only have the 120GB (about a third) of the blockchain data, starting from block 0. It won't cover the data which pruned node needs as it's not fully synced.
I think ...
A node won't sync blocks from another node (peer node) if the peer node is not fully synced. There might be a message in your debug.log that says as much. Your best bet is to wait until node A is fully synced.
This is the only reason the node won't sync.