Topic: Bitcoin-qt is not opening (Read 947 times)

getblockhash BLOCKNUMBER

getblock BLOCK_HASH

addnode 10.0.2.5 add

checkpointData = {
            {
                
            }
        };

checkpointData = {
            {
                { 0, uint256S("0x0")}
            }
        };

pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;

int64_t nMaxTipAge = DEFAULT_MAX_TIP_AGE * 10000;

checkpointData = { };

consensus.nMinimumChainWork = uint256S("0x0000000000000000000000000000000000000000000000000000000100010001");

Changing the ports won't stop you from interacting with the "original blockchain" (I believe you mean Bitcoin Mainnet). It's entirely possible to run Bitcoin Core using whatever port number you like.

There is even a runtime argument that allows you to change it
[code]
-port=  Listen for connections on  (default: 8333, testnet: 18333, regtest: 18444) 

sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status" # Disable WSL support for Win32 applications.
make
sudo bash -c "echo 1 > /proc/sys/fs/binfmt_misc/status" # Enable WSL support for Win32 applications.

PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var
sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status" # Disable WSL support for Win32 applications.
cd depends
make HOST=x86_64-w64-mingw32
cd ..
./autogen.sh # not required when building from tarball
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/
make

pchMessageStart[0] = 0xf4;
pchMessageStart[1] = 0xb5;
pchMessageStart[2] = 0xb6;
pchMessageStart[3] = 0xd7;