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

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. 

Hooray! Finally, the missing coins were credited to the balance of the crypto purse. However, it is unfortunate that they can not (temporarily) be taken out to a local wallet, in order to get more coins from the 3% offered tomorrow.
Again, wait)

D Waves offers a quantum computer with 2000 qubits for 15 millionen dollar.

Here is the correct Xenial Build bitcore.cc/btx140106-300717.tar.gz

Xenial online https://github.com/LIMXTEC/BitCore/releases/tag/0.14.1.6

I hope Cryptopia sorts out the withdrawal issue fast

there'll still be millions and millions of coins to distribute

The information isn't that hard to find using google to search for the exact phrase you quoted.
https://hacked.com/quantum-resistant-ledger-readies-battle-quantum-computing-hires-testers-seeks-feedback/

Well its in maintenance again, missed it!

some more info please, what are you talking about ?

thanks, but done all that, new version and everything. started having this issue with new version. Stuck at syncing headers 88.9%, 13 weeks behind, shows no connections to network.

2017-07-30 12:18:16 UpdateTip: new best=3afb67d750b0310f4f0bf41fea0f373d3d4ce53683779d3b65556acee8d6e36f height=144 version=0x20000000 log2_work=27.699929 tx=147 date='2017-04-26 00:21:45' progress=0.000000 cache=0.0MiB(146tx)
2017-07-30 12:18:16 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 8fbf54a0362d03a1b54d1bbb3898067a04d07c0235bcb14631c9c3ad58ae5b4f, bad-diffbits, incorrect proof of work (code 16)
2017-07-30 12:18:16 Misbehaving: 163.172.4.66:8555 peer=1 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-07-30 12:18:16 ERROR: invalid header received
2017-07-30 12:18:16 ProcessMessages(headers, 88536 bytes) FAILED peer=1
2017-07-30 12:18:16 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 8fbf54a0362d03a1b54d1bbb3898067a04d07c0235bcb14631c9c3ad58ae5b4f, bad-diffbits, incorrect proof of work (code 16)
2017-07-30 12:18:16 Misbehaving: 37.221.198.57:8555 peer=3 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-07-30 12:18:16 ERROR: invalid header received
2017-07-30 12:18:16 ProcessMessages(headers, 3160 bytes) FAILED peer=3
2017-07-30 12:19:04 receive version message: /BitCore:0.14.1.1/: version 70015, blocks=21093, us=71.171.109.198:61808, peer=4
2017-07-30 12:19:04 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 8fbf54a0362d03a1b54d1bbb3898067a04d07c0235bcb14631c9c3ad58ae5b4f, bad-diffbits, incorrect proof of work (code 16)
2017-07-30 12:19:04 Misbehaving: 139.59.233.128:8555 peer=4 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-07-30 12:19:04 ERROR: invalid header received
2017-07-30 12:19:04 ProcessMessages(headers, 3160 bytes) FAILED peer=4
2017-07-30 12:41:41 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-30 12:41:42 socket recv error An existing connection was forcibly closed by the remote host.  (10054)

20 MB blocks are very good Maybe you should also think about quantum resistant addresses

A final Xenial build isn't online. You can use this Source here https://github.com/LIMXTEC/BitCore/archive/master.zip or you wait. I going to ask Jon to build a new Xenial client.