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

[Pmalek]

Something wrong with CAPS again. Big Verns pool diff is 1.xxx, and Erundook pool is 0.xxx?

[flound1129]

Something wrong with CAPS again. Big Verns pool diff is 1.xxx, and Erundook pool is 0.xxx?

My pool is showing 0.71..  Coinchoose 1.145

[butjust41day]

Yes my wallet just suddenly went out of sync.....and seems to be behind block wise....was mining away at 6 to 7 blocks an hour so do I loose those? Or does the chain I was on win? And still finding blocks. Only 10 connections had maybe 30 earlier.

Actually 13 blocks in last hour and based on the number of confirms...it's almost like I'm on my own unique chain now from 12 blocks back only 14 confirms.

Any recommendations here? Do shutdown and reload the block chain (assume I'll loose that last hour). With difficulty dropping like a stone sure mining a lot of useless blocks.


Best I can tell from the block explorers is I've been on the wrong chain since noon....at the two wallet addresses it seems to have alternated between it shows the last mined blocks back in July. So of the 40 or so blocks mined since noon none are in the Block Explorer....considering the large number of nodes I was connected to I really would like an explanation.

Back to litecoin mining for now.

[flound1129]

redownloaded block chain, now my wallet is showing 2.x, coinchoose still showing 1.x, and all our blocks for the past day are orphaned.

[flound1129]

Looks like your connect= node isn't responding anymore..  That might be the reason the network split again.

[flound1129]

So, the blockchain I downloaded now was split at block 62731 (at least, that's the last block we found, after that all are orphans).  That block is from 8/6 at 18:59 GMT...

[butjust41day]

I get my connect nodes directly from the OP although I've noticed they are not always the same from forum to forum. It did sync up again; but, I'm still on a different chain. I think when it was trying to sync that my wallet briefly saw the other chain and I guess the other network. Shutting it down now and will down load the block chain again in a few days when it's sorted out.

[BitJohn]

Still no issues with mine

Block 65866 matching the block explorers using:
connect=199.180.115.100
addnode=199.180.115.100
addnode=199.180.115.125
addnode=50.137.233.14

I heard one of the trusted nodes is running the wrong client I'm guessing its not the one I am connected to or the 50.137.233.14. I am also told 1.4.1 will address this as well as add UPNP and should be out tomorrow. Maybe more cap lovers could offer up some good trusted nodes would help the folks with issues.

[butjust41day]

Still no issues with mine

Block 65866 matching the block explorers using:
connect=199.180.115.100
addnode=199.180.115.100
addnode=199.180.115.125
addnode=50.137.233.14

I heard one of the trusted nodes is running the wrong client I'm guessing its not the one I am connected to or the 50.137.233.14. I am also told 1.4.1 will address this as well as add UPNP and should be out tomorrow. Maybe more cap lovers could offer up some good trusted nodes would help the folks with issues.

Well I just cut and pasted the list above into my .conf file....deleted everything except the wallet and .conf file. When I open the wallet it briefly connects to one of the above nodes and then disconnects and that's it. I guess I'll wait for the new version.

Edit: Deleted the line connect=199.180.115.100 and download started....not a big loss...always good to have an adventure or two with these things.

[snaidervp]

i cant remember which was the bad node but i think it was that addnode=199.180.115.125 as mullick verified. i left only the 2 from OP

[flound1129]

Still no issues with mine

Block 65866 matching the block explorers using:
connect=199.180.115.100
addnode=199.180.115.100
addnode=199.180.115.125
addnode=50.137.233.14

I heard one of the trusted nodes is running the wrong client I'm guessing its not the one I am connected to or the 50.137.233.14. I am also told 1.4.1 will address this as well as add UPNP and should be out tomorrow. Maybe more cap lovers could offer up some good trusted nodes would help the folks with issues.

I can't connect to 199.180.115.100 at all, I just get the following over and over again in my log:

Code:

send version message: version 60008, blocks=0, us=0.0.0.0:0, them=199.180.115.100:7685, peer=199.180.115.100:7685
socket closed
disconnecting node 199.180.115.100
trying connection 199.180.115.100 lastseen=0.0hrs
connected 199.180.115.100
send version message: version 60008, blocks=0, us=0.0.0.0:0, them=199.180.115.100:7685, peer=199.180.115.100:7685
socket closed
disconnecting node 199.180.115.100
trying connection 199.180.115.100 lastseen=0.0hrs
connected 199.180.115.100
send version message: version 60008, blocks=0, us=0.0.0.0:0, them=199.180.115.100:7685, peer=199.180.115.100:7685
socket closed
disconnecting node 199.180.115.100
trying connection 199.180.115.100 lastseen=0.0hrs
connected 199.180.115.100
send version message: version 60008, blocks=0, us=0.0.0.0:0, them=199.180.115.100:7685, peer=199.180.115.100:7685
socket closed
disconnecting node 199.180.115.100
trying connection 199.180.115.100 lastseen=0.0hrs
connected 199.180.115.100
send version message: version 60008, blocks=0, us=0.0.0.0:0, them=199.180.115.100:7685, peer=199.180.115.100:7685
socket closed
disconnecting node 199.180.115.100
trying connection 199.180.115.100 lastseen=0.0hrs
connected 199.180.115.100
send version message: version 60008, blocks=0, us=0.0.0.0:0, them=199.180.115.100:7685, peer=199.180.115.100:7685

Also, won't the connect line prevent addnodes from being used?  My understanding was if you have a connect= line, the daemon will ONLY try to connect to that server and not connect to any other nodes.

[mullick]

Great...

My home server is on the right chain still yet again with 48 connections now.  50.137.233.14 Looking into the other server which I fixed last night

1.4.1 will be out tomorrow if not late tonight. I have 3 days off work now.  A kind soul has setup another node at addnode= 54.221.200.186

connect= should only be used if you are on the wrong chain to sync to the correct one. That will force your client to download from that node. Once you are synced change to addnode and add the others

[butjust41day]

Thank you mullick for all your hard work....I hope you have sometime for a little r&r during the next three days. As much as I like to see things working well we all do need a break now and again.

[mullick]

199.180.115.100

50.137.233.14

Still on the right chain looking into it more now

[flound1129]

199.180.115.100

50.137.233.14

Still on the right chain looking into it more now

Well I'm not getting the chain I was on earlier in the day, I had confirmed transactions to cryptsy up till 2 hours ago, the new chain I downloaded is all orphans back to 2.5 days ago.

[butjust41day]

...downloading now; but, it really started to hang at the 7 days left mark...and is downloading very slowly

[BitJohn]

1.41 should fix a bunch of this lets get some more trusted nodes

[mullick]

199.180.115.100

50.137.233.14

Still on the right chain looking into it more now

Well I'm not getting the chain I was on earlier in the day, I had confirmed transactions to cryptsy up till 2 hours ago, the new chain I downloaded is all orphans back to 2.5 days ago.

What is the block height of the chain you are on? If it does not match the explorer here http://bottlecaps.kicks-ass.net/block_crawler.php

You are not on the right chain. When I checked last night multipool was on the correct chain.

Unless there is a new fork that just occured 2.5 days ago that you just switched over too, when you get on the correct chain the tx's  from the last 2.5 days should be valid

Ill be working on 1.4.1 and wont stop until it is finished

[butjust41day]

Okay using the addnodes listed above I downloaded the same block chain I was on before; but, both block explorers can't locate the transactions for what I mined this afternoon. Currently it shows the current block as 65853. So if I used the "trusted nodes"  and still ended up on the wrong chain how is that possible?

[BitJohn]

Okay using the addnodes listed above I downloaded the same block chain I was on before; but, both block explorers can't locate the transactions for what I mined this afternoon. Currently it shows the current block as 65853. So if I used the "trusted nodes"  and still ended up on the wrong chain how is that possible?

Did you delete  your old database folder, blk0001.dat and blkindex.dat? Before redownloading?