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

[snaidervp]

we did, thank YOU

[mullick]

we did, thank YOU

Thank ya very much

It appears some peers are getting stuck on a previous sync checkpoint all 3 nodes listed in the OP are currently broadcasting the correct height currently

addnode=50.137.233.14                
addnode=192.64.86.238  


If your behind or some are slightly ahead please redownload the chain 1 final time. The server caused a little hiccup due to it being turned on a little soon. The checkpoint too old warning may be present just ignore it for now it wiill go away when I turn the node back on

[eBit]

we did, thank YOU

Thank ya very much

It appears some peers are getting stuck on a previous sync checkpoint all 3 nodes listed in the OP are currently broadcasting the correct height currently

addnode=50.137.233.14                
addnode=192.64.86.238  


If your behind or some are slightly ahead please redownload the chain 1 final time. The server caused a little hiccup due to it being turned on a little soon. The checkpoint too old warning may be present just ignore it for now it wiill go away when I turn the node back on

Que Pasa?


Did this. Wallet is stuck at 136823 of 137967.

connect=50.137.233.14 - up but doesn't connect
connect=192.64.86.238 - up but doesn't connect
connect=69.10.44.115 - not up

http://cap.coinmine.pl/ is at block 138,010

http://bottlecaps.kicks-ass.net/block_crawler.php is at block  129,068

http://www.bottlecapspool.com/ was synced up with http://bottlecaps.kicks-ass.net/block_crawler.php but site is now down

https://www.multipool.us/ - CAP disabled

Transfer made to Cryptsy last night - gone. (transaction id: c9351e129fdb69a73f7a13c70f4f31ec1d9266df534b1d31737f59647291b075)

[Petr1fied]

There is something seriously wrong with CAPS. I finally got fully synced on my Block Crawler with v1.5.1 and was at block 138093 (generated about 30 minutes ago) and all of a sudden I was knocked back 1270 blocks to block 136823 generated 3 hours earlier. If it's because of the auto checkpoint it's checkpointing a much shorter chain.

[ISAWHIM]

There are three forks...

Those still using the old wallet 1.5, and two for 1.5.1...

138200 is the tallest height I have now... Diff 123K (1.87184028)

Connections:

addnode=24.249.152.169
addnode=162.211.225.175
addnode=193.106.92.5
addnode=66.58.170.165
addnode=198.211.116.19
addnode=91.154.90.163
addnode=216.158.85.123
addnode=72.78.100.7

I did notice one connection that came-up was completely invalid... On block-crawler's list of connections.

node showed as "[2001", not valid IPv6 format... "[2001:0:........." Just the 2001 part.

That is not valid, and was killing my connections, until I manually connected to a chain without that invalid relayed node ID, which was killing any prior nodes connections that followed that one bad node ID.

The block-chain is on the wrong chain, and Multi may be on the correct one. The list of connections on block-crawler is refusing all my connections. Even starting from scratch, again. Though it says he has orphans, he is getting that info from the wrong chain, as the slower chain builds to smother his valid blocks, turning them into apparent orphans. (The third chain.)

This is the same issue as before, which wasn't addressed. Where the program sees the taller chain, but it isn't moving to it. (Either because it is rejecting our connections, making us branch, or because of invalid communications that just can't be processed by the person trying to connect.

It should NEVER reject a "read-only" connection. (Getting block data is read-only.) It should only reject "submit data", if submission data seems "bad". However, we are flat-out being rejected, just trying to download the correct height. Topping that off with the wallet not correctly "fixing itself" with the corrected data, once found and gotten. Which indicates it is a communication issue with TCP. (Again, over IPv4-IPv6 and IPv6-IPv6, where wallets are talking to headless daemons from pool servers. {windows -> linux})

[Pmalek]

I didnt understand a word you are saying! 

Is it serious or just update nodes and wallets problem?

[ISAWHIM]

I didnt understand a word you are saying!  

Is it serious or just update nodes and wallets problem?

I updated, downloaded the whole chain again, from scratch... it keeps throwing me on the taller chain.

Those not updated, or just continuing to mine, are stuck on the smaller of the two updated chains...

A: Tallest ~138,000 (correct?) {updated wallet, updated sync} Me and everyone who updated wallet, and also re-synced chain.
B: Short ~137,000 {updated wallet, running on isolated chain with others} Block-crawler and most pools who ONLY updated wallet.
C: Old-Short ~136,000 {old wallet, isolated chain with few people} Coin choose and some pools.

Although B was the majority... pools are disconnecting, due to seeing the orphans, leaving solo miners and pools on the correct chain, A. When they re-sync, they are moving to this taller chain, only if they also delete the old block-chain data... otherwise they keep going back to chain B, the wrong one.

The program should just assume that with every update, the data from the last checkpoint was invalid, and auto-rebuild. Instead, it just keeps building off invalid data, since it can't rebuild with the correct data from an invalid block.

EG...
If you are at block 300,000 when you updated but didn't delete the invalid blocks (delete the old block-data and rebuild the DB also)... thus the last 1,000 are invalid... (Because everyone else updated 1,000 blocks ago.) it just keeps going, to 300,001 300,002 remaining invalid. As opposed to removing 1,000 and building off-of, 299,000 or getting the correct 2,000 blocks that were built off 299,000 making the new block-height 301,000 not 300,000 which it keeps building on, isolated from the rest of the world.

[Petr1fied]

B: Short ~137,000 {updated wallet, running on isolated chain with others} Block-crawler and most pools who ONLY updated wallet.

This is an incorrect assumption. I synced the chain on the block crawler from nothing twice and I'm now doing so for a third time. It was on the taller chain but got thrown back.

Perhaps this happened at the point the number of peers stating that the shorter chain was correct outweighed those stating the longer chain was correct. Who knows?

[Pmalek]

So they shouldnt have released the new wallet yet?! Is it officialy another fork?

[eBit]

There is something seriously wrong with CAPS. I finally got fully synced on my Block Crawler with v1.5.1 and was at block 138093 (generated about 30 minutes ago) and all of a sudden I was knocked back 1270 blocks to block 136823 generated 3 hours earlier. If it's because of the auto checkpoint it's checkpointing a much shorter chain.

It takes me back to 136897 and then never syncs. ..or is not marked a synced if on a shorter chain.  I hope Mullick is working on a fix.

[eBit]

There is something seriously wrong with CAPS. I finally got fully synced on my Block Crawler with v1.5.1 and was at block 138093 (generated about 30 minutes ago) and all of a sudden I was knocked back 1270 blocks to block 136823 generated 3 hours earlier. If it's because of the auto checkpoint it's checkpointing a much shorter chain.

It takes me back to 136897 and then never syncs. ..or is not marked a synced if on a shorter chain.  I hope Mullick is working on a fix.

Update: Finally syncing. 1397 blocks remaining.

It looks like http://bottlecaps.kicks-ass.net/block_crawler.php and http://www.bottlecapspool.com/ are updated with version v1.5.1.0  and are syncing at the same rate that my client is.

At this rate though, slower than one block per minute, it could take 24 hours to be rid of this problem.

[mullick]

Ok if your having problems with that checkpoint please revert back to the previous client 1.5 I will change the links now ill have another client tonight that will fix it correctly

[Lauda]

Waiting for the fix, and will update. 

[bandjhughes]

Okay, I'm clueless (as usual).   So which chain is the official chain?  Is it the tallest?

[794259332]

where is the v1.5.1 link?

[mullick]

Okay, I'm clueless (as usual).  So which chain is the official chain?  Is it the tallest?

On 1.5 there is only one i will release 1.5.2 in a few minutes

The only invalid chain didnt advance very far the majority stayed on the main chain

Was just a minor issue will not happen again

[flound1129]

Okay, I'm clueless (as usual).  So which chain is the official chain?  Is it the tallest?

On 1.5 there is only one i will release 1.5.2 in a few minutes

The only invalid chain didnt advance very far the majority stayed on the main chain

Was just a minor issue will not happen again

Will 1.5.2 fix the crashing?  Were you able to look into that at all?

[mullick]

Okay, I'm clueless (as usual).  So which chain is the official chain?  Is it the tallest?

On 1.5 there is only one i will release 1.5.2 in a few minutes

The only invalid chain didnt advance very far the majority stayed on the main chain

Was just a minor issue will not happen again

Will 1.5.2 fix the crashing?  Were you able to look into that at all?

I have been unable to reproduce this I wonder if somehow along the way the wallet got corrupted. Hopefully not but Github is updated to 1.5.1.1 that should get you going. PM sent

Windows QT 1.5.2:

https://docs.google.com/file/d/0B0V-7FME2rcyd254QXUtNjZwSWs/edit?usp=sharing

Source:

https://github.com/bottlecaps-foundation/bottlecaps.git

Sorry to make you update again. There wont be another upgrade asked of you for some time now as the next one will require much work and take some time

[John Eden]

Get to mining folks. VERY exciting news coming in the next few days. Stay tuned 

Windows QT 1.5.2:

https://docs.google.com/file/d/0B0V-7FME2rcyd254QXUtNjZwSWs/edit?usp=sharing

Source:

https://github.com/bottlecaps-foundation/bottlecaps.git

[mullick]

If you get the checkpoint warning just ignore it for now. You will need to redownload the blockchain one last time but there should be no need to again as the checkpointing server will be online shortly

Enjoy one last redownload of the blockchain