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

[presstab]

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.

[eBit]

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?

[brian_23452]

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?

[ghostlander]

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.

[NuShrike]

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.

[nj_m715]

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.

[presstab]

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

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.

[ghostlander]

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.

[ofeefee]

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.

[nj_m715]

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.

[nj_m715]

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

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.

[Tranz]

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.

[Tranz]

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! :-)

[ymod123]

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.

[choppy123]

Hope cryptsy can get Bottlecaps online as this becoming annoying, i don't think it takes a week to get back a wallet online!

Well, i'm waiting for more than 40 days for my PHS withdrawal and i didn't get any response to my tickets. You are very optimistic if you think that CRAPTSY can resolve your issue in one week.

I second that, i've also waited 40 days for my PHS withdrawal, ridiculous.

[Maverick_br]

Tranz DB_CONFIG need extension like .CONF or something ? My wallet it's on the wrong chain and say this "Lock table is out of available lock entries" V2.0.0.1

[ghostlander]

Tranz DB_CONFIG need extension like .CONF or something ? My wallet it's on the wrong chain and say this "Lock table is out of available lock entries" V2.0.0.1

It needs no extension.

[Maverick_br]

Tranz DB_CONFIG need extension like .CONF or something ? My wallet it's on the wrong chain and say this "Lock table is out of available lock entries" V2.0.0.1

It needs no extension.

Thanks

[Rumhurius]

with the new .conf.
Its syncing with 1 connection for 1-2 mins and losing it then.

listen=1
addnode=50.137.233.14         
addnode=69.10.44.115           
addnode=192.64.86.238

My first caps wallet now and i did a clean install of 2.0.0.1g

[Tranz]

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.

Sometimes after the initial sync a quick shutdown and restart of the client will remove that message.