Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 110.

ymod123

sr. member

Activity: 432

Merit: 250

Quote from: Tranz on June 17, 2014, 03:45:02 PM

Quote from: ghostlander on June 17, 2014, 08:37:05 AM

The fork happened at block 491911 and those clients trapped on the shorter chain cannot re-organise to the longer chain:

Code:

17/06/14 12:28:22 REORGANIZE
17/06/14 12:28:22 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 12:28:22 REORGANIZE: Connect 8226 blocks; 000000000dd458745575..7d8c51bf9b063fcaa768
17/06/14 12:28:29 ERROR: DisconnectInputs() : UpdateTxIndex failed
17/06/14 12:28:29 ERROR: Reorganize() : DisconnectBlock afddc6baaef6389282cf failed
17/06/14 12:28:29 InvalidChainFound: invalid block=7d8c51bf9b063fcaa768  height=500137  trust=2003988848859  date=17/06/14 12:27:28
17/06/14 12:28:29 InvalidChainFound:  current best=00000000185b11596f0a  height=494537  trust=2004038605111  date=17/06/14 12:11:53
17/06/14 12:28:29 ERROR: SetBestChain() : Reorganize failed
17/06/14 12:28:29 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 7d8c51bf9b063fcaa768f865551f8e79d0382a927923067203a8be43af1d58ba

Why? Because the DB wasn't supposed to handle such load.

Code:

Lock table is out of available lock entries
Lock table is out of available object entries

The solution? Create DB_CONFIG file in your %APPDATA% / BottleCaps directory and put the following in:

Code:

set_lg_dir database
set_lk_max_locks 500000
set_lk_max_objects 50000

Restart your client.

Code:

17/06/14 13:26:23 REORGANIZE
17/06/14 13:26:23 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 13:26:23 REORGANIZE: Connect 8289 blocks; 000000000dd458745575..8bc0c8f7881230740c0c
[...]
17/06/14 13:27:49 REORGANIZE: done
17/06/14 13:28:07 SetBestChain: new best=00000000061aa230f715  height=500201  trust=2004039184082  date=17/06/14 13:17:03
17/06/14 13:28:07 SetBestChain: new best=000000001268558811c0  height=500202  trust=2004039184130  date=17/06/14 13:17:37
17/06/14 13:28:08 SetBestChain: new best=000000000a060d20d1fb  height=500203  trust=2004039184178  date=17/06/14 13:22:55
17/06/14 13:28:08 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000a060d20d1fb3f076edc761792a496e84275627f8d4d9e803d4fe25c
17/06/14 13:28:08 ProcessBlock: ACCEPTED

Enjoy. I also suggest Tranz to put a checkpoint at 491915 or so to prevent this from happening.

Thanks! I will put in a few more HardCheckpoints and update the clients for download.

As far as making this a perm change. Probably not right now, as we are going to have enough fun on July 4th as it is! :-)

HELLO , I NEED HELP TO MY WALLET ITS CXONNECTED TO 8 NETWORKS
BUT IT SAYS "WARNING: INVALID CHECKPOINT FOUND! TRABSACTION MAY NOT BE CORRECT!YOU MAY NEED TO UPGRADE OR NOTIFY.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: ghostlander on June 17, 2014, 08:37:05 AM

The fork happened at block 491911 and those clients trapped on the shorter chain cannot re-organise to the longer chain:

Code:

17/06/14 12:28:22 REORGANIZE
17/06/14 12:28:22 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 12:28:22 REORGANIZE: Connect 8226 blocks; 000000000dd458745575..7d8c51bf9b063fcaa768
17/06/14 12:28:29 ERROR: DisconnectInputs() : UpdateTxIndex failed
17/06/14 12:28:29 ERROR: Reorganize() : DisconnectBlock afddc6baaef6389282cf failed
17/06/14 12:28:29 InvalidChainFound: invalid block=7d8c51bf9b063fcaa768  height=500137  trust=2003988848859  date=17/06/14 12:27:28
17/06/14 12:28:29 InvalidChainFound:  current best=00000000185b11596f0a  height=494537  trust=2004038605111  date=17/06/14 12:11:53
17/06/14 12:28:29 ERROR: SetBestChain() : Reorganize failed
17/06/14 12:28:29 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 7d8c51bf9b063fcaa768f865551f8e79d0382a927923067203a8be43af1d58ba

Why? Because the DB wasn't supposed to handle such load.

Code:

Lock table is out of available lock entries
Lock table is out of available object entries

The solution? Create DB_CONFIG file in your %APPDATA% / BottleCaps directory and put the following in:

Code:

set_lg_dir database
set_lk_max_locks 500000
set_lk_max_objects 50000

Restart your client.

Code:

17/06/14 13:26:23 REORGANIZE
17/06/14 13:26:23 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 13:26:23 REORGANIZE: Connect 8289 blocks; 000000000dd458745575..8bc0c8f7881230740c0c
[...]
17/06/14 13:27:49 REORGANIZE: done
17/06/14 13:28:07 SetBestChain: new best=00000000061aa230f715  height=500201  trust=2004039184082  date=17/06/14 13:17:03
17/06/14 13:28:07 SetBestChain: new best=000000001268558811c0  height=500202  trust=2004039184130  date=17/06/14 13:17:37
17/06/14 13:28:08 SetBestChain: new best=000000000a060d20d1fb  height=500203  trust=2004039184178  date=17/06/14 13:22:55
17/06/14 13:28:08 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000a060d20d1fb3f076edc761792a496e84275627f8d4d9e803d4fe25c
17/06/14 13:28:08 ProcessBlock: ACCEPTED

Enjoy. I also suggest Tranz to put a checkpoint at 491915 or so to prevent this from happening.

Thanks! I will put in a few more HardCheckpoints and update the clients for download.

As far as making this a perm change. Probably not right now, as we are going to have enough fun on July 4th as it is! :-)

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: NuShrike on June 17, 2014, 12:07:12 PM

Quote from: presstab on June 17, 2014, 09:56:47 AM

I heard through the grapevine that Cryptsy has massive updates rolling out ASAP. Apparently all lag and everything will be eliminated, I am hoping they will also be able to get CAP back online at the same time.

My 7244 confirmations transfer is the blockchain, but not at Cryptsy yet. It's been 5 days so far and more for others.

I think they are on the old fork... They need to update to 2.0 or 2.0.0.1 and get caught up.

nj_m715

newbie

Activity: 39

Merit: 0

I created bottlecaps.conf and added this. Hope that's where it goes.

Quote from: Tranz on June 17, 2014, 06:53:02 AM

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

nj_m715

newbie

Activity: 39

Merit: 0

shows as synced, but its 5k blocks short:
15:51:27

getblockcount

15:51:30

495039

Guess I need to re dl the blockchain and try again.

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

http://cap.blockx.info/ appears to be online, and is on the correct chain, as is the main block explorer. My client is fully synced, and appears to be running well, on 2.0.0.1 now.

ghostlander

legendary

Activity: 1242

Merit: 1020

No surrender, no retreat, no regret.

Quote from: nj_m715 on June 17, 2014, 12:26:54 PM

I added the db.conf. I think it worked because my previously synced wallet instantly wanted to download another 5k blocks but it's painfully slow.

How can I be sure I'm on the correct fork? The debug window says there's a total of 500303 blocks. before it said 494000.

It's fine now.

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: brian_23452 on June 17, 2014, 11:45:45 AM

Quote from: presstab on June 17, 2014, 09:56:47 AM

Quote from: crackfoo on June 17, 2014, 08:52:06 AM

Quote from: Tranz on June 17, 2014, 06:53:02 AM

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

I sent a msg to Cryptsy to get the new wallet and to please put CAP back online!

Cheers!

www.xpool.ca

I heard through the grapevine that Cryptsy has massive updates rolling out ASAP. Apparently all lag and everything will be eliminated, I am hoping they will also be able to get CAP back online at the same time.

Cryptsy has been making that claim for how long now?

Look at their website right now

Quote

Important System Notification

We will be performing some hardware upgrades to increase internal networking capacity at our datacenter over the next couple hours. You may experience intermittent delays, but we do not expect any downtime.

nj_m715

newbie

Activity: 39

Merit: 0

and on the blockchain is where they will stay until cryptsy runs and syncs their wallet.

I added the db.conf. I think it worked because my previously synced wallet instantly wanted to download another 5k blocks but it's painfully slow.

How can I be sure I'm on the correct fork? The debug window says there's a total of 500303 blocks. before it said 494000.

NuShrike

full member

Activity: 178

Merit: 100

Quote from: presstab on June 17, 2014, 09:56:47 AM

I heard through the grapevine that Cryptsy has massive updates rolling out ASAP. Apparently all lag and everything will be eliminated, I am hoping they will also be able to get CAP back online at the same time.

My 7244 confirmations transfer is the blockchain, but not at Cryptsy yet. It's been 5 days so far and more for others.

ghostlander

legendary

Activity: 1242

Merit: 1020

No surrender, no retreat, no regret.

Quote from: eBit on June 17, 2014, 11:35:23 AM

Upon reload, most of the chain was able to load fast, but after the fork painfully syncing at 1 to 2 blocks per minute again. Your suggestion fixed this and got me synced in under two minutes.

In addition to the checkpoint, do you think it might be a good idea to either update the BottleCaps client with these parameters or include the DB_CONFIG file to prevent this from happening in the future?

db.cpp can be patched this way as the current defaults are 10000 each, but this change must be made to every client to avoid a chain fork situation when the old clients fail to follow the new ones. Something like this happened in March of 2013 to Bitcoin when v0.7 and v0.8 clients disagreed on block 225430. I'm leaving it up to Tranz.

brian_23452

sr. member

Activity: 350

Merit: 250

Quote from: presstab on June 17, 2014, 09:56:47 AM

Quote from: crackfoo on June 17, 2014, 08:52:06 AM

Quote from: Tranz on June 17, 2014, 06:53:02 AM

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

I sent a msg to Cryptsy to get the new wallet and to please put CAP back online!

Cheers!

www.xpool.ca

I heard through the grapevine that Cryptsy has massive updates rolling out ASAP. Apparently all lag and everything will be eliminated, I am hoping they will also be able to get CAP back online at the same time.

Cryptsy has been making that claim for how long now?

eBit

member

Activity: 91

Merit: 10

Quote from: ghostlander on June 17, 2014, 08:37:05 AM

The fork happened at block 491911 and those clients trapped on the shorter chain cannot re-organise to the longer chain:

Code:

17/06/14 12:28:22 REORGANIZE
17/06/14 12:28:22 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 12:28:22 REORGANIZE: Connect 8226 blocks; 000000000dd458745575..7d8c51bf9b063fcaa768
17/06/14 12:28:29 ERROR: DisconnectInputs() : UpdateTxIndex failed
17/06/14 12:28:29 ERROR: Reorganize() : DisconnectBlock afddc6baaef6389282cf failed
17/06/14 12:28:29 InvalidChainFound: invalid block=7d8c51bf9b063fcaa768  height=500137  trust=2003988848859  date=17/06/14 12:27:28
17/06/14 12:28:29 InvalidChainFound:  current best=00000000185b11596f0a  height=494537  trust=2004038605111  date=17/06/14 12:11:53
17/06/14 12:28:29 ERROR: SetBestChain() : Reorganize failed
17/06/14 12:28:29 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 7d8c51bf9b063fcaa768f865551f8e79d0382a927923067203a8be43af1d58ba

Why? Because the DB wasn't supposed to handle such load.

Code:

Lock table is out of available lock entries
Lock table is out of available object entries

The solution? Create DB_CONFIG file in your %APPDATA% / BottleCaps directory and put the following in:

Code:

set_lg_dir database
set_lk_max_locks 500000
set_lk_max_objects 50000

Restart your client.

Code:

17/06/14 13:26:23 REORGANIZE
17/06/14 13:26:23 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 13:26:23 REORGANIZE: Connect 8289 blocks; 000000000dd458745575..8bc0c8f7881230740c0c
[...]
17/06/14 13:27:49 REORGANIZE: done
17/06/14 13:28:07 SetBestChain: new best=00000000061aa230f715  height=500201  trust=2004039184082  date=17/06/14 13:17:03
17/06/14 13:28:07 SetBestChain: new best=000000001268558811c0  height=500202  trust=2004039184130  date=17/06/14 13:17:37
17/06/14 13:28:08 SetBestChain: new best=000000000a060d20d1fb  height=500203  trust=2004039184178  date=17/06/14 13:22:55
17/06/14 13:28:08 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000a060d20d1fb3f076edc761792a496e84275627f8d4d9e803d4fe25c
17/06/14 13:28:08 ProcessBlock: ACCEPTED

Enjoy. I also suggest Tranz to put a checkpoint at 491915 or so to prevent this from happening.

Upon reload, most of the chain was able to load fast, but after the fork painfully syncing at 1 to 2 blocks per minute again. Your suggestion fixed this and got me synced in under two minutes.

In addition to the checkpoint, do you think it might be a good idea to either update the BottleCaps client with these parameters or include the DB_CONFIG file to prevent this from happening in the future?

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: crackfoo on June 17, 2014, 08:52:06 AM

Quote from: Tranz on June 17, 2014, 06:53:02 AM

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

I sent a msg to Cryptsy to get the new wallet and to please put CAP back online!

Cheers!

www.xpool.ca

I heard through the grapevine that Cryptsy has massive updates rolling out ASAP. Apparently all lag and everything will be eliminated, I am hoping they will also be able to get CAP back online at the same time.

crackfoo

legendary

Activity: 3486

Merit: 1126

Quote from: Tranz on June 17, 2014, 06:53:02 AM

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

I sent a msg to Cryptsy to get the new wallet and to please put CAP back online!

Cheers!

www.xpool.ca

ghostlander

legendary

Activity: 1242

Merit: 1020

No surrender, no retreat, no regret.

The fork happened at block 491911 and those clients trapped on the shorter chain cannot re-organise to the longer chain:

Code:

17/06/14 12:28:22 REORGANIZE
17/06/14 12:28:22 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 12:28:22 REORGANIZE: Connect 8226 blocks; 000000000dd458745575..7d8c51bf9b063fcaa768
17/06/14 12:28:29 ERROR: DisconnectInputs() : UpdateTxIndex failed
17/06/14 12:28:29 ERROR: Reorganize() : DisconnectBlock afddc6baaef6389282cf failed
17/06/14 12:28:29 InvalidChainFound: invalid block=7d8c51bf9b063fcaa768  height=500137  trust=2003988848859  date=17/06/14 12:27:28
17/06/14 12:28:29 InvalidChainFound:  current best=00000000185b11596f0a  height=494537  trust=2004038605111  date=17/06/14 12:11:53
17/06/14 12:28:29 ERROR: SetBestChain() : Reorganize failed
17/06/14 12:28:29 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 7d8c51bf9b063fcaa768f865551f8e79d0382a927923067203a8be43af1d58ba

Why? Because the DB wasn't supposed to handle such load.

Code:

Lock table is out of available lock entries
Lock table is out of available object entries

The solution? Create DB_CONFIG file in your %APPDATA% / BottleCaps directory and put the following in:

Code:

set_lg_dir database
set_lk_max_locks 500000
set_lk_max_objects 50000

Restart your client.

Code:

17/06/14 13:26:23 REORGANIZE
17/06/14 13:26:23 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 13:26:23 REORGANIZE: Connect 8289 blocks; 000000000dd458745575..8bc0c8f7881230740c0c
[...]
17/06/14 13:27:49 REORGANIZE: done
17/06/14 13:28:07 SetBestChain: new best=00000000061aa230f715  height=500201  trust=2004039184082  date=17/06/14 13:17:03
17/06/14 13:28:07 SetBestChain: new best=000000001268558811c0  height=500202  trust=2004039184130  date=17/06/14 13:17:37
17/06/14 13:28:08 SetBestChain: new best=000000000a060d20d1fb  height=500203  trust=2004039184178  date=17/06/14 13:22:55
17/06/14 13:28:08 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000a060d20d1fb3f076edc761792a496e84275627f8d4d9e803d4fe25c
17/06/14 13:28:08 ProcessBlock: ACCEPTED

Enjoy. I also suggest Tranz to put a checkpoint at 491915 or so to prevent this from happening.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

PressF1

full member

Activity: 216

Merit: 100

Quote from: eBit on June 17, 2014, 03:11:27 AM

Quote from: eBit on June 17, 2014, 02:58:40 AM

Quote from: Tranz on June 16, 2014, 09:23:02 PM

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more. If you are ok on 2.0 no need to change.

With peers.dat cleared out on 2.0.0.1 it's syncing now at about 1 to 2 blocks per minute. At this rate, with 5400 blocks left, that's 45 hours. Any thoughts?

Nope, upon restart it likes the other chain again. I'm going to try to redownload from the beginning with a blank wallet.

Seems I have similar problems.

Edit

I did 2 clean installs of 2001 and one of them picked up the 500K chain which is the right one I think. The other picked up the other chain, 494K. No idea what causes this difference.

eBit

member

Activity: 91

Merit: 10

Quote from: eBit on June 17, 2014, 02:58:40 AM

Quote from: Tranz on June 16, 2014, 09:23:02 PM

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more. If you are ok on 2.0 no need to change.

With peers.dat cleared out on 2.0.0.1 it's syncing now at about 1 to 2 blocks per minute. At this rate, with 5400 blocks left, that's 45 hours. Any thoughts?

Nope, upon restart it likes the other chain again. I'm going to try to redownload from the beginning with a blank wallet.

eBit

member

Activity: 91

Merit: 10

Quote from: Tranz on June 16, 2014, 09:23:02 PM

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more. If you are ok on 2.0 no need to change.

With peers.dat cleared out on 2.0.0.1 it's syncing now at about 1 to 2 blocks per minute. At this rate, with 5400 blocks left, that's 45 hours. Any thoughts?

6/17/2014 07:41:32 received block 000000001bff93475f5e
6/17/2014 07:41:32 SetBestChain: new best=000000001bff93475f5e height=494390 trust=2003686276231 date=6/17/2014 07:40:32
6/17/2014 07:41:32 ProcessBlock: ACCEPTED
6/17/2014 07:41:35 Flushing wallet.dat
6/17/2014 07:41:35 Flushed wallet.dat 51ms
6/17/2014 07:41:36 connection timeout
6/17/2014 07:41:36 trying connection 37.187.73.182:7685 lastseen=3.1hrs
6/17/2014 07:41:36 connected 37.187.73.182:7685
6/17/2014 07:41:36 send version message: version 70003, blocks=494390, us=108.36.3.37:7685, them=37.187.73.182:7685, peer=37.187.73.182:7685
6/17/2014 07:41:37 trying connection 107.209.115.183:7685 lastseen=6.5hrs
6/17/2014 07:41:39 partner 37.187.73.182:7685 using an old client 70001, disconnecting
6/17/2014 07:41:39 disconnecting node 37.187.73.182:7685
6/17/2014 07:41:40 getblocks -1 to 00000000000000000000 limit 500
6/17/2014 07:41:42 connection timeout
6/17/2014 07:41:42 trying connection 70.109.50.114:7685 lastseen=7.4hrs
6/17/2014 07:41:43 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:45 received block 0000000004232927aa9c
6/17/2014 07:41:45 ProcessBlock: ORPHAN BLOCK, prev=00000000009b5bd44885
6/17/2014 07:41:47 connection timeout
6/17/2014 07:41:48 trying connection 24.249.152.169:7685 lastseen=2.8hrs
6/17/2014 07:41:48 connected 24.249.152.169:7685
6/17/2014 07:41:48 send version message: version 70003, blocks=494390, us=108.36.3.37:7685, them=24.249.152.169:7685, peer=24.249.152.169:7685
6/17/2014 07:41:49 trying connection 24.79.26.236:7685 lastseen=8.5hrs
6/17/2014 07:41:53 partner 24.249.152.169:7685 using an old client 70001, disconnecting
6/17/2014 07:41:53 disconnecting node 24.249.152.169:7685
6/17/2014 07:41:54 connection timeout
6/17/2014 07:41:54 trying connection 212.111.15.232:7685 lastseen=31.1hrs
6/17/2014 07:41:59 connection timeout
6/17/2014 07:42:00 trying connection 24.4.45.219:7685 lastseen=5.7hrs
6/17/2014 07:42:05 connection timeout
6/17/2014 07:42:05 trying connection 24.71.151.25:7685 lastseen=8.8hrs
6/17/2014 07:42:08 received block 00000000132935b0740a
6/17/2014 07:42:08 SetBestChain: new best=00000000132935b0740a height=494391 trust=2003686276248 date=6/17/2014 07:41:00
6/17/2014 07:42:08 ProcessBlock: ACCEPTED
6/17/2014 07:42:10 Flushing wallet.dat
6/17/2014 07:42:10 Flushed wallet.dat 50ms
6/17/2014 07:42:10 connection timeout
6/17/2014 07:42:11 trying connection 192.3.8.163:7685 lastseen=3.7hrs
6/17/2014 07:42:16 connection timeout
6/17/2014 07:42:16 trying connection 205.197.252.28:7685 lastseen=3.9hrs
6/17/2014 07:42:19 getblocks -1 to 00000000000000000000 limit 500
6/17/2014 07:42:21 connection timeout
6/17/2014 07:42:22 trying connection 89.212.241.225:7685 lastseen=3.3hrs
6/17/2014 07:42:27 connection timeout
6/17/2014 07:42:27 trying connection 86.130.243.167:7685 lastseen=3.1hrs
6/17/2014 07:42:29 received block 0000000027d09967a087
6/17/2014 07:42:29 SetBestChain: new best=0000000027d09967a087 height=494392 trust=2003686276265 date=6/17/2014 07:41:27
6/17/2014 07:42:29 ProcessBlock: ACCEPTED
6/17/2014 07:42:31 Flushing wallet.dat
6/17/2014 07:42:31 Flushed wallet.dat 60ms
6/17/2014 07:42:32 connection timeout
6/17/2014 07:42:33 trying connection 70.109.50.114:7685 lastseen=7.4hrs
6/17/2014 07:42:38 connection timeout
6/17/2014 07:42:38 trying connection 85.65.10.239:7685 lastseen=9.2hrs
6/17/2014 07:42:43 connection timeout
6/17/2014 07:42:44 trying connection 41.150.98.237:7685 lastseen=5.4hrs
6/17/2014 07:42:49 connection timeout
6/17/2014 07:42:50 trying connection 94.29.4.181:7685 lastseen=4.5hrs
6/17/2014 07:42:55 connection timeout
6/17/2014 07:42:55 trying connection 174.55.191.118:7685 lastseen=5.6hrs
6/17/2014 07:43:00 received block 0000000036b441b229c7
6/17/2014 07:43:00 SetBestChain: new best=0000000036b441b229c7 height=494393 trust=2003686276283 date=6/17/2014 07:41:42
6/17/2014 07:43:00 ProcessBlock: ACCEPTED
6/17/2014 07:43:00 connection timeout
6/17/2014 07:43:01 trying connection 107.188.144.125:7685 lastseen=6.9hrs
6/17/2014 07:43:02 Flushing wallet.dat
6/17/2014 07:43:02 Flushed wallet.dat 50ms
6/17/2014 07:43:06 connection timeout
6/17/2014 07:43:06 trying connection 174.55.191.118:7685 lastseen=5.6hrs
6/17/2014 07:43:11 connection timeout
6/17/2014 07:43:12 trying connection 75.97.39.235:7685 lastseen=80.6hrs
6/17/2014 07:43:12 received block 0000000019fb5b55c72b
6/17/2014 07:43:12 SetBestChain: new best=0000000019fb5b55c72b height=494394 trust=2003686276301 date=6/17/2014 07:42:28
6/17/2014 07:43:12 ProcessBlock: ACCEPTED
6/17/2014 07:43:14 Flushing wallet.dat
6/17/2014 07:43:14 Flushed wallet.dat 50ms
6/17/2014 07:43:17 connection timeout
6/17/2014 07:43:17 trying connection 70.109.50.114:7685 lastseen=7.5hrs
6/17/2014 07:43:19 received block 4f7030ced030c0af2bc8
6/17/2014 07:43:19 ProcessBlock: ORPHAN BLOCK, prev=0000000004232927aa9c
6/17/2014 07:43:19 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:19 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:20 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:20 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:21 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:22 connection timeout
6/17/2014 07:43:23 trying connection 104.34.125.117:7685 lastseen=3.3hrs
6/17/2014 07:43:28 connection timeout
6/17/2014 07:43:28 trying connection 70.67.166.14:7685 lastseen=9.9hrs
6/17/2014 07:43:33 connection timeout
6/17/2014 07:43:34 trying connection 71.232.87.227:7685 lastseen=18.2hrs
6/17/2014 07:43:39 connection timeout
6/17/2014 07:43:39 trying connection 213.136.73.120:7685 lastseen=5.6hrs
6/17/2014 07:43:44 connection timeout
6/17/2014 07:43:45 trying connection 46.164.21.136:7685 lastseen=88.6hrs
6/17/2014 07:43:50 connection timeout
6/17/2014 07:43:50 trying connection 89.128.142.140:7685 lastseen=5.5hrs
6/17/2014 07:43:55 connection timeout
6/17/2014 07:43:56 trying connection 68.195.32.64:7685 lastseen=3.4hrs
6/17/2014 07:44:01 connection timeout
6/17/2014 07:44:01 trying connection 81.143.68.198:7685 lastseen=29.2hrs
6/17/2014 07:44:06 connection timeout
6/17/2014 07:44:07 trying connection 70.109.50.114:7685 lastseen=7.5hrs
6/17/2014 07:44:12 connection timeout
6/17/2014 07:44:12 trying connection 81.164.85.197:7685 lastseen=3.6hrs
6/17/2014 07:44:17 connection timeout
6/17/2014 07:44:18 trying connection 109.74.193.220:7685 lastseen=5.2hrs
6/17/2014 07:44:23 connection timeout
6/17/2014 07:44:24 trying connection 216.54.25.130:7685 lastseen=3.5hrs
6/17/2014 07:44:29 connection timeout
6/17/2014 07:44:29 trying connection 68.195.32.64:7685 lastseen=3.4hrs
6/17/2014 07:44:32 received block 000000002dc0b5375b28
6/17/2014 07:44:32 SetBestChain: new best=000000002dc0b5375b28 height=494395 trust=2003686276319 date=6/17/2014 07:42:32
6/17/2014 07:44:32 ProcessBlock: ACCEPTED
6/17/2014 07:44:33 getblocks 494394 to 000000002dc0b5375b28 limit 500
6/17/2014 07:44:33 getblocks stopping at 494395 000000002dc0b5375b28
6/17/2014 07:44:34 Flushing wallet.dat
6/17/2014 07:44:34 Flushed wallet.dat 50ms
6/17/2014 07:44:34 connection timeout
6/17/2014 07:44:35 trying connection 75.76.52.206:7685 lastseen=84.7hrs

Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 110. (Read 388610 times)