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

[z0rr0]

bottlecrap

[1714033524]

1714033524

[1714033524]

1714033524

[1714033524]

1714033524

[1714033524]

1714033524

[1714033524]

1714033524

[rav3n_pl]

I`m on 78540 but some node reported 79366 ....

[feeleep]

I`m on 78540 but some node reported 79366 ....

On previous server i stuck on the same block...

[Lauda]

I`m on 78540 but some node reported 79366 ....

What people don't understand that this takes time to fix, theoretically the fix is in place, but it will take time to get rid of all the bad nodes. It's the people using outdated versions..
http://bottlecaps.kicks-ass.net/block_crawler.php
Is the correct one. I guess i'm one of the lucky few but I have had no problems yet at all.

Just give it time to resolve itself.

[butjust41day]

Well I think most people coming on here would be using the latest version (since hopefully they come here to read the posts) and since as of yesterday the latest version only listens to the newest version........looking forward to problem being solved.

[rav3n_pl]

I have deleted peers.dat (again) and make addone from list http://bottlecaps.kicks-ass.net/peers.php
BUT
after few moments all peers except 192.241.216.151 getting BANNED

Code:

Misbehaving: 199.180.115.100:7685 (0 -> 100) DISCONNECTING
Misbehaving: 4.30.96.132:1521 (0 -> 100) DISCONNECTING
Misbehaving: 76.170.130.175:65105 (0 -> 100) DISCONNECTING
Misbehaving: 67.167.228.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 85.17.31.120:60154 (0 -> 100) DISCONNECTING
Misbehaving: 60.184.47.62:27617 (0 -> 100) DISCONNECTING
Misbehaving: 106.187.100.78:7685 (0 -> 100) DISCONNECTING
Misbehaving: 178.49.118.233:53728 (0 -> 100) DISCONNECTING
Misbehaving: 80.229.2.127:7685 (0 -> 100) DISCONNECTING
Misbehaving: 92.5.104.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 115.76.20.64:7685 (0 -> 100) DISCONNECTING
Misbehaving: 97.81.165.175:7685 (0 -> 100) DISCONNECTING
Misbehaving: 50.137.233.14:55044 (0 -> 100) DISCONNECTING
Misbehaving: 4.30.96.132:7802 (0 -> 100) DISCONNECTING
Misbehaving: 106.186.115.181:7685 (0 -> 100) DISCONNECTING
Misbehaving: 24.10.97.6:7685 (0 -> 100) DISCONNECTING
Misbehaving: 106.186.115.58:7685 (0 -> 100) DISCONNECTING
Misbehaving: 64.121.106.144:60698 (0 -> 100) DISCONNECTING
Misbehaving: 98.167.196.51:7685 (0 -> 100) DISCONNECTING
Misbehaving: 198.211.116.19:7685 (0 -> 100) DISCONNECTING
Misbehaving: 81.105.30.173:7685 (0 -> 100) DISCONNECTING
Misbehaving: 173.56.112.109:7685 (0 -> 100) DISCONNECTING
Misbehaving: 105.236.213.165:37884 (0 -> 100) DISCONNECTING
Misbehaving: 66.112.71.193:58903 (0 -> 100) DISCONNECTING
Misbehaving: 107.217.208.215:51943 (0 -> 100) DISCONNECTING
Misbehaving: 83.26.32.63:61754 (0 -> 100) DISCONNECTING
Misbehaving: 88.195.204.114:40775 (0 -> 100) DISCONNECTING
Misbehaving: 213.103.202.73:56581 (0 -> 100) DISCONNECTING
Misbehaving: 95.73.249.239:16992 (0 -> 100) DISCONNECTING
Misbehaving: 77.172.80.106:15267 (0 -> 100) DISCONNECTING
Misbehaving: 92.100.75.51:52641 (0 -> 100) DISCONNECTING
Misbehaving: 188.165.211.202:51392 (0 -> 100) DISCONNECTING
Misbehaving: 91.154.104.63:49668 (0 -> 100) DISCONNECTING
Misbehaving: 85.228.195.71:32804 (0 -> 100) DISCONNECTING
Misbehaving: 174.52.220.23:56448 (0 -> 100) DISCONNECTING
Misbehaving: 5.53.170.119:53205 (0 -> 100) DISCONNECTING
Misbehaving: 71.86.172.110:52949 (0 -> 100) DISCONNECTING
Misbehaving: 60.242.225.227:50766 (0 -> 100) DISCONNECTING
Misbehaving: 93.188.224.253:63208 (0 -> 100) DISCONNECTING
Misbehaving: 76.26.0.231:50925 (0 -> 100) DISCONNECTING
Misbehaving: 213.5.30.10:64841 (0 -> 100) DISCONNECTING
Misbehaving: 218.0.3.20:59585 (0 -> 100) DISCONNECTING
Misbehaving: 76.27.247.150:47851 (0 -> 100) DISCONNECTING
Misbehaving: 71.86.172.110:54557 (0 -> 100) DISCONNECTING
Misbehaving: 97.81.165.175:7685 (0 -> 100) DISCONNECTING
Misbehaving: 106.187.100.78:7685 (0 -> 100) DISCONNECTING
Misbehaving: 5.53.170.119:53617 (0 -> 100) DISCONNECTING
Misbehaving: 67.167.228.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 213.103.202.73:58640 (0 -> 100) DISCONNECTING
Misbehaving: 115.76.20.64:7685 (0 -> 100) DISCONNECTING
Misbehaving: 76.26.0.231:51291 (0 -> 100) DISCONNECTING
Misbehaving: 81.105.30.173:7685 (0 -> 100) DISCONNECTING
Misbehaving: 85.228.195.71:35280 (0 -> 100) DISCONNECTING
Misbehaving: 213.5.30.10:65512 (0 -> 100) DISCONNECTING
Misbehaving: 50.137.233.14:7685 (0 -> 100) DISCONNECTING
rav3n@ubu32:~$ grep DISCONNECTING .BottleCaps/debug.log
Misbehaving: 199.180.115.100:7685 (0 -> 100) DISCONNECTING
Misbehaving: 4.30.96.132:1521 (0 -> 100) DISCONNECTING
Misbehaving: 76.170.130.175:65105 (0 -> 100) DISCONNECTING
Misbehaving: 67.167.228.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 85.17.31.120:60154 (0 -> 100) DISCONNECTING
Misbehaving: 60.184.47.62:27617 (0 -> 100) DISCONNECTING
Misbehaving: 106.187.100.78:7685 (0 -> 100) DISCONNECTING
Misbehaving: 178.49.118.233:53728 (0 -> 100) DISCONNECTING
Misbehaving: 80.229.2.127:7685 (0 -> 100) DISCONNECTING
Misbehaving: 92.5.104.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 115.76.20.64:7685 (0 -> 100) DISCONNECTING
Misbehaving: 97.81.165.175:7685 (0 -> 100) DISCONNECTING
Misbehaving: 50.137.233.14:55044 (0 -> 100) DISCONNECTING
Misbehaving: 4.30.96.132:7802 (0 -> 100) DISCONNECTING
Misbehaving: 106.186.115.181:7685 (0 -> 100) DISCONNECTING
Misbehaving: 24.10.97.6:7685 (0 -> 100) DISCONNECTING
Misbehaving: 106.186.115.58:7685 (0 -> 100) DISCONNECTING
Misbehaving: 64.121.106.144:60698 (0 -> 100) DISCONNECTING
Misbehaving: 98.167.196.51:7685 (0 -> 100) DISCONNECTING
Misbehaving: 198.211.116.19:7685 (0 -> 100) DISCONNECTING
Misbehaving: 81.105.30.173:7685 (0 -> 100) DISCONNECTING
Misbehaving: 173.56.112.109:7685 (0 -> 100) DISCONNECTING
Misbehaving: 105.236.213.165:37884 (0 -> 100) DISCONNECTING
Misbehaving: 66.112.71.193:58903 (0 -> 100) DISCONNECTING
Misbehaving: 107.217.208.215:51943 (0 -> 100) DISCONNECTING
Misbehaving: 83.26.32.63:61754 (0 -> 100) DISCONNECTING
Misbehaving: 88.195.204.114:40775 (0 -> 100) DISCONNECTING
Misbehaving: 213.103.202.73:56581 (0 -> 100) DISCONNECTING
Misbehaving: 95.73.249.239:16992 (0 -> 100) DISCONNECTING
Misbehaving: 77.172.80.106:15267 (0 -> 100) DISCONNECTING
Misbehaving: 92.100.75.51:52641 (0 -> 100) DISCONNECTING
Misbehaving: 188.165.211.202:51392 (0 -> 100) DISCONNECTING
Misbehaving: 91.154.104.63:49668 (0 -> 100) DISCONNECTING
Misbehaving: 85.228.195.71:32804 (0 -> 100) DISCONNECTING
Misbehaving: 174.52.220.23:56448 (0 -> 100) DISCONNECTING
Misbehaving: 5.53.170.119:53205 (0 -> 100) DISCONNECTING
Misbehaving: 71.86.172.110:52949 (0 -> 100) DISCONNECTING
Misbehaving: 60.242.225.227:50766 (0 -> 100) DISCONNECTING
Misbehaving: 93.188.224.253:63208 (0 -> 100) DISCONNECTING
Misbehaving: 76.26.0.231:50925 (0 -> 100) DISCONNECTING
Misbehaving: 213.5.30.10:64841 (0 -> 100) DISCONNECTING
Misbehaving: 218.0.3.20:59585 (0 -> 100) DISCONNECTING
Misbehaving: 76.27.247.150:47851 (0 -> 100) DISCONNECTING
Misbehaving: 71.86.172.110:54557 (0 -> 100) DISCONNECTING
Misbehaving: 97.81.165.175:7685 (0 -> 100) DISCONNECTING
Misbehaving: 106.187.100.78:7685 (0 -> 100) DISCONNECTING
Misbehaving: 5.53.170.119:53617 (0 -> 100) DISCONNECTING
Misbehaving: 67.167.228.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 213.103.202.73:58640 (0 -> 100) DISCONNECTING
Misbehaving: 115.76.20.64:7685 (0 -> 100) DISCONNECTING
Misbehaving: 76.26.0.231:51291 (0 -> 100) DISCONNECTING
Misbehaving: 81.105.30.173:7685 (0 -> 100) DISCONNECTING
Misbehaving: 85.228.195.71:35280 (0 -> 100) DISCONNECTING
Misbehaving: 213.5.30.10:65512 (0 -> 100) DISCONNECTING
Misbehaving: 50.137.233.14:7685 (0 -> 100) DISCONNECTING
Misbehaving: 60.242.225.227:51625 (0 -> 100) DISCONNECTING
Misbehaving: 199.180.115.100:7685 (0 -> 100) DISCONNECTING
Misbehaving: 76.26.0.231:51439 (0 -> 100) DISCONNECTING
Misbehaving: 213.103.202.73:58946 (0 -> 100) DISCONNECTING
Misbehaving: 92.5.104.42:7685 (0 -> 100) DISCONNECTING
Misbehaving: 174.52.220.23:60177 (0 -> 100) DISCONNECTING
Misbehaving: 5.53.170.119:53737 (0 -> 100) DISCONNECTING
Misbehaving: 115.76.20.64:7685 (0 -> 100) DISCONNECTING
Misbehaving: 106.187.100.78:33408 (0 -> 100) DISCONNECTING
Misbehaving: 71.86.172.110:55189 (0 -> 100) DISCONNECTING

[digitalindustry]

Well it looks like Caps is having a slightly hard time of it, but what we need to remember is this is all a learning process , and in a way , good will come from this . 

[mullick]

Here is 1.4.2 More checkpoints to help you sync. Github updated as well Make sure your port is forwarded Default:7685

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

Please add reservebalance=1000000 to your .conf for now to prevent your client from generating proof of stake blocks until we are all on the same chain and stable

Hers is a copy of the blockchain up to about block 79500 if you are still having trouble syncing. Your connections may start low but will grow with time

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

Heres a short list of peers displaying the correct starting height

addnode=92.5.104.42
addnode=92.100.75.51
addnode=80.229.2.127
addnode=85.228.195.71
addnode=77.172.80.106
addnode=67.167.228.42
addnode=223.64.63.132
addnode=4.30.96.132
addnode=217.169.211.146
addnode=188.165.211.202
addnode=188.165.194.201
addnode=115.76.20.64
addnode=97.81.165.175
addnode=68.43.193.187
addnode=24.52.207.220
addnode=67.11.24.42
addnode=221.2.149.227
addnode=106.186.115.181
addnode=223.64.63.17
addnode=50.137.233.14
addnode=24.56.243.130
addnode=60.242.225.227
addnode=192.241.216.151
addnode=82.46.148.115

[hax0red]

Also having trouble getting the wallet to sync. Sometimes it shows it has then others it jumps from 1700 blocks to 2700 needing to be synced. I have solo mined around 800 coins and now have tried to withdraw them in the times I got it to show synced and still an hour later nothing...could the transfer reach 15 confirms if the coins I mined were bad/out of sync? Am I screwed out of my time spent mining? hope not...things are already thin for profits as it is.

[Pmalek]

OK I followed Mullicks instructions and synced with no problems!

Is this ok?

"version" : "v1.4.2.0-g32a928e-caps",
"protocolversion" : 70000,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 79581,
"moneysupply" : 789436.25290000,
"connections" : 6,
"proxy" : "",
"ip" : "178.148.116.36",
"difficulty" : 1.18015163,
"testnet" : false,
"keypoololdest" : 1372270346,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""

[hax0red]

I downloaded the blockchain posted starting at 79500 and it seems to be synced, I'm guessing the coins I mined were a fork but I'm kinda miffed at how they could confirm, sucks I wasted so much time. I wont assume a wallet is working properly next time

[ISAWHIM]

You don't get it...

We are all being disconnected...

The chains are all going rogue after a certain period of time... All of them... any one we connect to...

Stopping POS has nothing to do with it... We are generating POS fine for hours...

Versions have nothing to do with it... The new versions are being booted too...

There is a problem with the clients. They are either f-ing up with something related to the block-heights, f-ing up with something related to "sending data" or "reading sent data", or f-ing up because someone figured-out an exploit and is exploiting the miners through the IRC rooms.

That, or the one we keep following is just the only one f-ed up and causing all the issues for all of us. Someones "special compiled version" that they screwed-up and are persistently convincing us to connect to.

Then there is that guy a few posts back who said something about branching his own version of CAP from some other client. Could his rogue-branch creation be f-ing up the network, feeding us invalid data because he has no f-ing clue what the hell he is doing with his "branch".

Connecting to the right chain does not solve anything. It keeps disconnecting us. Like the logs show... we are all acting-up after time. No... that client is not reading our information correctly, or he is right, because our clients are not sending information correctly. Then it isolates itself, and we isolate ourselves from everyone else, doing the same... refusing connections because they are acting-up too. Creating one fork for every client, until no-one new can connect to us, and our fork just dies and sits there not mining or doing anything.

P.S. This happens at about 1:00 AM (GMT -5) and at 11:00 AM (GMT -5) for me, every day... it is that predictable for those times, by observation of my wallet filling with (?) blocks, which all start around those times. (There are other times too... but those two times it absolutely disconnects, and goes into a fork.)

And the fact that the program doesn't even attempt to fix the issue by looking for taller chains, or joining taller chains when found or reported... is making the issue a game-stopper. Even when you find the right chains, you have to delete the whole chain, or manually delete and restore a point where the chain was below that point, or it never connects and keeps forcing you back onto the wrong chain, because it is not fixing itself with the correct longer chain. Without THAT fixed, or working... this will never have resolution.

How to do that is simple. If you need guidance on that.. don't hesitate for me to outline HOW. Not sure why it doesn't do that in the first place, or why it was removed as a function.

[skyhigh2004]

Wow I am glad I stopped mining CAP awhile ago.  I figured I'd stop and come back in a week or two when the issues were fixed and now that its been that long this still is looking like a waste of time to mine.  Everytime a fix is in place it forks again, is this a coding issue or just the fact that the wallet software still isn't working correctly?

[DrGoose]

I did follow mullick instructions, seems fine for me with 8 active peers now. I will update my post if it goes bad.


getmininginfo on August 18, 2013, ~03:10 PM UTC:

{
"blocks" : 79651,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.18377558,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}

[ISAWHIM]

I did follow mullick instructions, seems fine for me with 8 active peers now. I will update my post if it goes bad.

{
"blocks" : 79651,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.18377558,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}

Yes, you will have to do this every few hours... because you will again be booted from the chain you are on, or they will leave. (They = the one largest pool that becomes the new tallest chain, every time.)

I am making a list of every time I was severed from "the tall chain", when my program was forced to mine with the others who were booted off the chain, which leads us into creating the many small isolated chains. In hopes that this will help to identify the exact issue... but without knowing why "we are all seen as misbehaving"... it will be of no real use.

If misbehaving = resubmitting a block that is not acceptable... due to being beat by another block... then that code has to be changed. CGminer is told to resubmit up to 12 times, which is NOT misbehaving, that is called persistence when the client does not respond with a valid reason for rejection, or does not respond with a rejection at all.

This is where a port-snooper comes in handy. You can actually see what it is sending before the program chews it up and spits out something that can't be translated.

[ISAWHIM]

These are the times/dates where the network has severed me from connection... I have no idea what the blocks are, because the wallet doesn't show that information. All times are (GMT -5)

(Last block found before being severed from 25+ conn - first block isolated on 1-2 conn, now is a ? block.)
Date: Just now connected again... after I woke-up...
Date: 8/18/2013 01:31 - 01:35
Date: 8/17/2013 16:31 - 16:34
Date: 8/17/2013 11:50 - 11:55
Date: 8/17/2013 00:53 - 00:57
Date: 8/15/2013 05:26 - ? (Stopped mining until 8/15/2013 12:51, when I could get back on any chain.)
Date: 8/15/2013 02:25 - ? (Same as above - 8/15/2013 04:55)
Date: 8/12/2013 23:41 - ? (Same as above - 8/14/2013 21:12)
Date: 8/12/2013 17:30 - ? (Same as above - 8/12/2013 20:32)

Prior to this date, I mined fine... on version 1.4.0

Note: Always eventually connecting to the chain that is listed on http://bottlecaps.kicks-ass.net/block_crawler.php using the peer-list from http://bottlecaps.kicks-ass.net/peers.php

Also note: Only version 1.4.1 connections after 8/17/2013 00:53, and POS has nothing to do with "all of us getting rejected and disconnected for misbehaving at the same time".

[lemons]

1.4.2 ? 

[ISAWHIM]

1.4.2 ?  

Crossing fingers... UPDATE, UPDATE, UPDATE!

Pfft... front page still has 1.4.1... Don't update yet... That was premature... lol.

How to update 101
1: Update and compile and test all versions
2: Upload all compiled versions and source
3: Update information and links on post
4: Check that everything is correctly listed and working as links
5: Change title of post to "Update 1.4.2"

You got 1 and 5... now try 2,3 and 4.

P.S. Potential fork detected... The block-crawler just returned 0 connections again, and 0 block-height... Last time it did that, it began killing our connections, and we forked. It was severed, and now we are about to be severed, I assume, again. (Prepare for reconnection when the big-guns get severed from that list, that is where the new tallest branch will be.)

Hmm, right at noon... 12:00... Guess it will happen within the hour, when it sees us all as "misbehaving" by about 01:00 again... Time-glitch or time-hack?

ARG... lol... I was mining the last half hour on my locked wallet... that is sooo annoying... I knew I would forget that one of these times... lol.

[lemons]

1.4.2 ?  

Crossing fingers... UPDATE, UPDATE, UPDATE!

Pfft... front page still has 1.4.1... Don't update yet... That was premature... lol.

How to update 101
1: Update and compile and test all versions
2: Upload all compiled versions and source
3: Update information and links on post
4: Check that everything is correctly listed and working as links
5: Change title of post to "Update 1.4.2"

You got 1 and 5... now try 2,3 and 4.

He has been working here,at least , much better than the CNC' issuer

[ISAWHIM]

I wasn't complaining, just making a joke about the lack of the actual 1.4.2 being listed before the title was changed. I am about 99% sure that the forum ate his post submission, and he is retyping it all up, as we post now. xD That, or he just assumed it was actually posted... and left to go back to other things.

Even with this issue, this is still the one-of-the-best coins to mine. (Opinion)