Re: [ANN] Bitcore - BTX - SEGWIT - BLOOM - ONLINE - CORE 0.14.1 -142000+ BTX Claimed
There 2 way to use the Wallet 140106 on a Linux Server, you can compile it from the Git :
or you can use the release Ubuntu release :
If you use a new server there cant problem with old files, if you update a running maschine its better to do it like this :
Sync Time on a new Server was like 3 Minutes and Block High is : "blocks": 22456
You dont need any addnode in your config file because the main nodes will spread the other ips to you, just connect with a small config file like its in the tar.gz file
Code:
git clone https://github.com/LIMXTEC/BitCore.git
./autogen.sh
./configure
make
./autogen.sh
./configure
make
or you can use the release Ubuntu release :
Code:
cd
wget https://github.com/LIMXTEC/BitCore/releases/download/0.14.1.6/Xenial-0-14-1-6.tar.gz
tar xvf Xenial-0-14-1-6.tar.gz
mkdir .bitcore
cp bitcore.conf .bitcore/
./bitcored
wget https://github.com/LIMXTEC/BitCore/releases/download/0.14.1.6/Xenial-0-14-1-6.tar.gz
tar xvf Xenial-0-14-1-6.tar.gz
mkdir .bitcore
cp bitcore.conf .bitcore/
./bitcored
If you use a new server there cant problem with old files, if you update a running maschine its better to do it like this :
Code:
cd
cd .bitcore/
rm peers.dat
rm banlist.dat
rm -rf blocks/
rm -rf chainstate/
cd .bitcore/
rm peers.dat
rm banlist.dat
rm -rf blocks/
rm -rf chainstate/
Sync Time on a new Server was like 3 Minutes and Block High is : "blocks": 22456
You dont need any addnode in your config file because the main nodes will spread the other ips to you, just connect with a small config file like its in the tar.gz file
Code:
rpcallowip=127.0.0.1
rpcuser=RANDOMUSERNAME3402934803294823094
rpcpassword=RANDOMPASSWORDrgkdhfgkjdfhgkdjfghdfkjg
server=1
daemon=1
listen=1
rpcuser=RANDOMUSERNAME3402934803294823094
rpcpassword=RANDOMPASSWORDrgkdhfgkjdfhgkdjfghdfkjg
server=1
daemon=1
listen=1
That build made no difference, however I think I found the issue
There seems to be a few nodes on the network that are totally breaking sync, the only way we could sync was to find a good node an connect to it directly, to do this you need to set listen=0 in your bitcore.conf and replace "addnode" with "connect" to some nodes you know are synced.
e.g.
listen=0
connect=105.235.159.43
If we set listen=1 it stops syncing immediately, and will kill the wallet at block 3799 on resync, not sure if this information will help anyone else.
There seems to be a few nodes on the network that are totally breaking sync, the only way we could sync was to find a good node an connect to it directly, to do this you need to set listen=0 in your bitcore.conf and replace "addnode" with "connect" to some nodes you know are synced.
e.g.
listen=0
connect=105.235.159.43
If we set listen=1 it stops syncing immediately, and will kill the wallet at block 3799 on resync, not sure if this information will help anyone else.
we use fresh vm's for new compiles (automated deploy) so old files are not the issue
listen=1 breaks the wallet immediately, I just tried it again, even without addnodes, connect=xxx.xxx.xxx.xxx and listen=0 is the only fix we have found
soon as we connect to one of those bad nodes, the syncing stops, all connection drop, then the wallet silently crashes