Topic: [ANN][Main] Bitcore- BTX - Datacarriersize up to 220 bytes - page 947. (Read 729875 times)

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

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

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.

 
Ok that is cool, the size is just ok by me cuz im running out of space at the moment, thanks for the info!

for desktop around 150mb actually...android is around 40mb, I guess

Hi, what is the size of the blockchain and is the android wallet an electrum wallet? im interested in the weekly airdrops but i would liike to know how large the blockchain is if im to sync

Nope: i got some deposits, but they are "closed" again : Investigating blockchain issues

Hi,

you have to hold min. 10 BTX in ur desktop or mobile wallet to reach the monday airdrops. every week 3% dropping to your wallet till november.

Greetz
Steve

Hello,
i have a few question about airdrop because i can't see it the OP and only a few information i got from page to page.
from Bitcore community comments,i will get 3% for my total BTX in my own wallet right ?
what's the minimum for BTX coin and maximum ?
how long the airdrop will run for ?

thank you for your time,i hope you can clearing my doubt

Dear Bitcore community,

please hold on. Cryptopia is working very hard...They have to structurize also their newest stuff for their shareholders. The incoming BTC fork needs also their biggest attention. So, we reached them on every channel and are waiting now for their answer...

We are very thankful, that cryptopia listed us as the first exchange for bitcore and sharing our mission. So, we all are experienced and wait for the next moves. 

Greetz
Steve

the only thing that's changed on my end is the new version of your wallet

Everything works fine here, on multiple computers.
The problem is on your end I'm afraid.

Here a valid list with core 0.14.1.6 nodes.

My wallet need for sync from scratch 4 min. I can't see any error. Please give me your debug header.

Sent funds to Cryptopia they are not, today the status of the purse was online now, again, it is on maintenance, is it really that Cryptopia's insipid creatures are forever in their trouble, that it does not immediately go wrong, it does not squeak.

what no one is comprehending is there is something wrong with the new version of the wallet.. it wont sync, get no connections, and is stuck. Pervious version worked with no issues. This new version will not do anything but sit stuck, not syncing. and YES, ive deleted what I had to, backed up wallet.dat, all that stuff. Even deleted the entire bitcore folder and started over with the wallet and guess what, still same issue, wont sync. I'm not new at this and know what I'm doing but there is an issue. I posted the debug data further up showing initial errors...

and here are new errors from debug

2017-07-30 16:00:54 init message: Loading addresses...
2017-07-30 16:00:54 ERROR: Read: Failed to open file C:\Users\separ\AppData\Roaming\BitCore\peers.dat
2017-07-30 16:00:54 Invalid or missing peers.dat; recreating
2017-07-30 16:00:54 init message: Loading banlist...
2017-07-30 16:00:54 ERROR: Read: Failed to open file C:\Users\separ\AppData\Roaming\BitCore\banlist.dat
2017-07-30 16:00:54 Invalid or missing banlist.dat; recreating
2017-07-30 16:00:54 init message: Starting network threads...
2017-07-30 16:00:54 dnsseed thread start
2017-07-30 16:00:54 opencon thread start
2017-07-30 16:00:54 Loading addresses from DNS seeds (could take a while)
2017-07-30 16:00:54 msghand thread start
2017-07-30 16:00:54 addcon thread start
2017-07-30 16:00:54 net thread start
2017-07-30 16:00:54 3 addresses found from DNS seeds
2017-07-30 16:00:54 init message: Done loading
2017-07-30 16:00:54 dnsseed thread exit
2017-07-30 16:00:54 GUI: Platform customization: "windows"
2017-07-30 16:00:55 GUI: PaymentServer::LoadRootCAs: Loaded  52  root certificates
2017-07-30 16:00:58 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:12 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:19 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:27 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:27 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:29 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:30 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:33 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:35 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:36 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:38 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:40 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:42 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:43 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:46 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2017-07-30 16:01:47 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:48 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 16:01:49 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2017-07-30 16:01:50 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2017-07-30 16:01:51 socket recv error An existing connection was forcibly closed by the remote host.  (10054)

Try download bootstrap: https://drive.google.com/file/d/0B4RoSPunQ45EdXNXZjBTTDlpYms/view

Copy the folder to C:\Users\User_Name\AppData\Roaming\


I try send 1 BTX to my wallet, but didn't arrive and transaction not appear on block explorer, so send message to staff support and then they disabled withdrawals again.

I think quantum computer which could harm bitcoin are in the near future and people have to prepare for it

I think the cryptopia team try the best.