Client seems to sync now, can anyone verify current block?
I'm at:
getinfo
Blocks: 423
Last block hash: 22B32DBEAE5004772E0758E6EAAF9068653D1BCDF9F6FED7C280E3F808F0C97
B
Difficulty: 50000000
Main address: S15W5NW37NSRY27GR53DG3JY7TCEBNOEDVOWMD
Main address balance: 65000000000
Edit: Pretty sure i've forked blocks stopped increasing after closing testnet miner.
Edit2: Started from scratch seem to be stuck at block 410 daemon is just spamming same stuff over and over.
got data: NETWORK_STATE 410 C24DB47300D0...568F4286931416C6D7C5E6CF51C97C
got data: TRANSACTION net.curecoin.sigmax.Transaction@54bedef2
got data: TRANSACTION net.curecoin.sigmax.Transaction@8efb846
got data: TRANSACTION net.curecoin.sigmax.Transaction@2a84aee7
got data: TRANSACTION net.curecoin.sigmax.Transaction@a09ee92
got data: NETWORK_STATE 410 C24DB47300D0...568F4286931416C6D7C5E6CF51C97C
got data: TRANSACTION net.curecoin.sigmax.Transaction@54bedef2
got data: TRANSACTION net.curecoin.sigmax.Transaction@8efb846
got data: TRANSACTION net.curecoin.sigmax.Transaction@2a84aee7
got data: TRANSACTION net.curecoin.sigmax.Transaction@a09ee92
got data: NETWORK_STATE 410 C24DB47300D0...568F4286931416C6D7C5E6CF51C97C
got data: TRANSACTION net.curecoin.sigmax.Transaction@54bedef2
got data: TRANSACTION net.curecoin.sigmax.Transaction@8efb846
got data: TRANSACTION net.curecoin.sigmax.Transaction@2a84aee7
got data: TRANSACTION net.curecoin.sigmax.Transaction@a09ee92
Sent:: REQUEST_NET_STATE
PUTTING INTO WRITE BUFFER: REQUEST_NET_STATE
Sending REQUEST_NET_STATE to /155.94.254.14
got data: REQUEST_NET_STATE
PUTTING INTO WRITE BUFFER: NETWORK_STATE 410 C2...
got data: GET_BLOCK 410
Sending block 410 to peer...
PUTTING INTO WRITE BUFFER: BLOCK {1461110264025...
got data: GET_BLOCK 411
got data: GET_BLOCK 412
got data: GET_BLOCK 413
got data: GET_BLOCK 414
Sending NETWORK_STATE 410 C2 to /155.94.254.14
Sending BLOCK {1461110264025 to /155.94.254.14
got data: GET_BLOCK 415
got data: GET_BLOCK 416
got data: GET_BLOCK 417
got data: GET_BLOCK 418
got data: GET_BLOCK 419
got data: GET_BLOCK 420
got data: GET_BLOCK 421
got data: GET_BLOCK 422
got data: GET_BLOCK 423
got data: GET_BLOCK 424
got data: GET_BLOCK 425
got data: GET_BLOCK 426
got data: GET_BLOCK 427
Etc... uptil Block 645 then it repeats.
Hey merc, is your client still stuck on block 645? If you type "getinfo" in the client, what is the block hash of your latest block? As of right now, the latest block appears to be 1212 with block hash 3A47C5DB73C1DFDB431E211732F1259A73EC82AC53F1EFEB389CAFAE5BF1FF6D.
The daemon will spam data for a while while it's syncing, you can see more in-depth progress (or lack there-of, in the case of desynchronization issues) by typing "getblock" into the client periodically. The spam is mostly caused by network 'reverb' or delayed block processing, which is something I'll try to address in the next beta release to make the debug output more useful.