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

[eBit]

This looks like it might need to be fixed.

http://bottlecaps.kicks-ass.net/block_crawler.php

[eBit]

whats the diff right now?

It's constantly changing. You can check it at any of the pools listed here: https://bitcointalk.org/index.php?topic=241445.msg2559942#msg2559942

Hey admin, can we get the current difficulty to display in the QT as LiteCoin has it?

[Lauda]

Still way undervalued 

[SpaceCadet]

I performed a clean install of this client v1.3 for Windows. I needed to manually add nodes to begin synching, but once completed, get the error message, "WARNING: Checkpoint is too old. Contact the development team."

I had the same problem. One of the added nodes was the cause of that problem. The problem node has been deleted from the original post and the following currently works:

addnode=186.95.162.209
addnode=70.79.24.157
addnode=70.98.114.229
addnode=188.165.211.65
addnode=199.192.205.46
addnode=176.34.210.88
addnode=70.69.238.84
addnode=70.98.114.237

Good to know. I was not at my pc to verify.

It looks like the node removed was:
addnode=69.85.86.195


I removed this from the .conf file, restarted the client, but the error message was still there. I'll wait for the next version. Everything else seems to work well.

I deleted all except for the wallet and my .conf file (c/w with the revised addnodes) and re-downloaded the blockchain to correct the problem. I was able to re-create the problem on several different computers and cure it.

Okay, I deleted all files except wallet and conf and downloaded the entire blockchain again. I can assure you the problem is still there. I verified again that every ip in addnode is correct. If a new client is released and this is mentioned as a fix and some people still have problems, it's not gonna look good.  Running on Windows XP, virtual mode on Win7, client v1.3.

The only other thing I can think of is that I downloaded the associated dll's from one link, but since the client was not there, I downloaded that from the other link. I don't know if the issue could be in the DLL's, but in that case the update should probably be fine.

I got the same problem, couldn't sync the blockchain with the CAP client, got same WARNING in the bottom left box, followed directions by removing blockchain and redownloading it. Alas, now the CAPs in the wallet are showing unconfirmed, and the same WARNING persists. The next step is to notify the developers, it says. So there.

Ditto.  Just downloaded 1.3 (verified the version after the install) today for the first time (fresh install) on win8pro-64, copied the addnode list on the OP into the .conf file (matches the one quoted above) and still I get ring around the collar, er, the blockchain warning.  An issue with 1.3?

[BitJohn]

I performed a clean install of this client v1.3 for Windows. I needed to manually add nodes to begin synching, but once completed, get the error message, "WARNING: Checkpoint is too old. Contact the development team."

I had the same problem. One of the added nodes was the cause of that problem. The problem node has been deleted from the original post and the following currently works:

addnode=186.95.162.209
addnode=70.79.24.157
addnode=70.98.114.229
addnode=188.165.211.65
addnode=199.192.205.46
addnode=176.34.210.88
addnode=70.69.238.84
addnode=70.98.114.237

Good to know. I was not at my pc to verify.

It looks like the node removed was:
addnode=69.85.86.195


I removed this from the .conf file, restarted the client, but the error message was still there. I'll wait for the next version. Everything else seems to work well.

I deleted all except for the wallet and my .conf file (c/w with the revised addnodes) and re-downloaded the blockchain to correct the problem. I was able to re-create the problem on several different computers and cure it.

Okay, I deleted all files except wallet and conf and downloaded the entire blockchain again. I can assure you the problem is still there. I verified again that every ip in addnode is correct. If a new client is released and this is mentioned as a fix and some people still have problems, it's not gonna look good.  Running on Windows XP, virtual mode on Win7, client v1.3.

The only other thing I can think of is that I downloaded the associated dll's from one link, but since the client was not there, I downloaded that from the other link. I don't know if the issue could be in the DLL's, but in that case the update should probably be fine.

I got the same problem, couldn't sync the blockchain with the CAP client, got same WARNING in the bottom left box, followed directions by removing blockchain and redownloading it. Alas, now the CAPs in the wallet are showing unconfirmed, and the same WARNING persists. The next step is to notify the developers, it says. So there.

Ditto.  Just downloaded 1.3 (verified the version after the install) today for the first time (fresh install) on win8pro-64, copied the addnode list on the OP into the .conf file (matches the one quoted above) and still I get ring around the collar, er, the blockchain warning.  An issue with 1.3?

Dev should have a new update very soon he got delayed should be no issues with 1.3

[eBit]

Please check for a fork. It appears BigVern is on a different chain that the other two pools, and at least my client. BigVern has the big chain. I guess that's what the Big stands for.

[Petr1fied]

There's definitely a fork, I updated my block crawler right before it happened due to the last fork that BitJohn advised me had frozen my crawler. It was in sync with http://bot.webboise.com:2760/chain/Bottlecaps but then gradually got further and further ahead of the other explorer.

This is the current state as I type this:

49,311 [84 blocks ahead]

[digitalindustry]

I just sent - Cap to Cryptsy , they confirmed on my Wallet , haven't appeared as pending on Cryptsy , so I'm guess in they just went into the wrong fork ?

they are on your crawler but  ?

963a2e04383fb957fe82823c74bcd69aba1f79359e6abf89c714de39db4f7e1e

[eBit]

Please check for a fork. It appears BigVern is on a different chain that the other two pools, and at least my client. BigVern has the big chain. I guess that's what the Big stands for.

Re-downloaded blockchain but it syncs to the shorter chain, the one the other pools are on. It synched up rather quickly, maybe 20 minutes.  I'm just going by the blocks numbers the pools are working on. BigVern's is almost 100 blocks ahead right now. I wonder if the other clients are syncing to the smaller chain too.

[captainfuture]

i am mining on epools. hope thats the right chain....

[kagula323]

I sent 90 caps to my wallet but got nothing in it. http://bot.webboise.com:2760/address/EmLcr3BAhCxZ7eEuVyrd7LQG2XDvFVs6ww

[mercSuey]

i am mining on epools. hope thats the right chain....

BigVern's pool is forked.  You should stop mining at BigVern's pool. 

https://bitcointalk.org/index.php?topic=263735.0

[ikal]

What's wrong ?

[John Eden]

I am logged in.

The forks seem to be coming from multipool. The network hashrate has been relativity stable around 100-150Mh the last week or so. When mutlipool added caps to the rotation the network hashrate jumped by up to 700Mh in a matter of minutes

The difficulty adjusted rather quickly and the pool moved on. The difficulty once again adjusted rather quickly and they came back. This seems to have caused the fork yesterday. It appears to be the same issue today. The chain was forked and verns pool and the cryptsy wallet followed the longer chain. Vern pool was  the only pool to be moved to the new chain so the hashrate dropped to 50Mh when multipool left. Causing the difficulty to drop dramatically and bring multipool back in a continuing cycle.

Due to the difficulty algorithm coin generation should only be minimally effected by this. I have asked for caps to be removed from the multipool rotation. When i return home i will release a temporary client with the new checkpoints awaiting the release of 1.4

I am sorry for any loss created by this unfortunate situation. I am doing my best to get the chain as reliable as it once was. I assure you i will do everything in my power to prevent this in the future.

[markm]

Why would changing hashrate cause forks?

-MarkM-

[captainfuture]

i am mining on epools. hope thats the right chain....

BigVern's pool is forked.  You should stop mining at BigVern's pool. 

https://bitcointalk.org/index.php?topic=263735.0

so why is now bigverns chain the "right" one??
plz explain me?

the bigger wins?

[Damnsammit]

Look forward to 1.4 fixing these problems!  I'd like to mine some more CAP but it's way too jacked up right now

[John Eden]

It is believed that the sudden large hashrate increase is the cause. The timing and circumstances fit. But we cant be 100% certain

The reason will will be going with the longer chain is for a few reasons. First of all to minimize the damage caused by this. Since more coins are generated on the longer chain.

Second of all the only 2 exchanges and block explorers seem to be on the longer chain as well.

Once i get everything sorted I will get the update out and make a full announcement.

[flound1129]

Multipool has had all your addnodes in our client config since we started mining.  Perhaps others haven't?

We mine much coins with much smaller networks (MNC, LKY, ARG) and there have not been any forks on those to my knowledge.

[Jaden]

Sounds like a great time to start mining this. I'm in with one GPU.