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

[Jaden]

Are there any active pools? Looks like Silverwolf's is on the wrong chain, Bottlecapspool.com is down, and I believe CAP is disabled at Multipool.

[Lauda]

Looks like I managed to fork NVC P2Pool to work on CAP
My git repo: https://github.com/Rav3nPL/p2pool-rav
use "cap" branch
My 1st block: http://bottlecaps.kicks-ass.net/block_crawler.php?block_hash=00000001a43f7af2523c3d390889e916c301b79876bd323d33d32edea3c115f0

Nice! Good job.

[ISAWHIM]

The block explorers just went down... but I am on height 78103 on IP: 50.137.233.14 which oddly reports the starting-height as 78026... That is the only connection I get from the list of connections.

Even blockcrawler is having connection issues, as we are... http://bottlecaps.kicks-ass.net/block_crawler.php

Just reported 0 connections, and 0 blocks, and now is back up with 15 connections and my height.

Now also having IP: 92.5.104.42 connect with the correct height as the starting height. Apparently the other IP isn't getting the missing blocks delivered, and is hung-up, but still relaying the top block.

[rav3n_pl]

my daemon  "blocks" : 77901,
block crawler: Block Count: 78,113
Sooo.....

[Petr1fied]

Now, I am sitting at an uncomfortable 2 connections, out of the 25 listed... so that is a lot of connections not talking/communicating with anyone, on that list at http://bottlecaps.kicks-ass.net/block_crawler.php

The list isn't necessarily complete since a client only tells you how many blocks it has on the initial connection, it doesn't update you to the number of blocks it has as time goes by. I try to restart the daemon periodically to get fresh block counts from the peers and raise the bar on the number of blocks required to be included on the list so that I'm sure they're definitely on the same chain as me.

Currently I have 21 connections, all are on the same chain and only 1 of them is using a older version of Bottlecaps. Only 2 hours and 45 minutes to go until old clients start getting blacklisted, that'll be where the real fun begins.

[ISAWHIM]

my daemon  "blocks" : 77901,
block crawler: Block Count: 78,113
Sooo.....

Shut-down your daemon... (Wait for it to completely die)... Then delete peers, and reconnect with the peers in that list. Wait a minute for it to run through the connections and find and link the right heights.

If it doesn't get the right height... do that again... until you do get the right height.

Also, save yourself some time... once you get the right height... save a backup of everything in your folder... so when/if this happens again, you can just restore that backup and continue from that point on... you connect faster that way too.

Apparently no-one wants to send the whole chain to everyone that keeps connecting with 0 blocks downloaded. Leaving the burden to one IP to deliver the whole chain over and over... and the chain it is sending is the wrong ending... you have to HOPE to get a taller connection before it begins sending you the wrong blocks. (Because if it does, you have to do it all over again.)

[rav3n_pl]

In what list?
I have restarted daemon like 2 hrs ago deleting peers.dat
It should connect to hardcoded nodes in 1st place.

[ISAWHIM]

In what list?
I have restarted daemon like 2 hrs ago deleting peers.dat
It should connect to hardcoded nodes in 1st place.

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

Though, in that list... I still only get 2 connections...

I think everyone has connections set too low... (Due to the wallets not accepting more than 8 connections, it is like 8 are connecting to the same 8, and isolating themselves over and over. And the ones accepting more connections, are connecting, but not talking, or not sending data that the wallets are able to read/use.)

Got 4 connections now... lol... love the start-height variance...
09:30:11
[
{
"addr" : "92.5.104.42:7685",
"services" : "00000001",
"lastsend" : 1376746126,
"lastrecv" : 1376746182,
"conntime" : 1376744432,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 78102,
"banscore" : 0
},
{
"addr" : "50.137.233.14:7685",
"services" : "00000001",
"lastsend" : 1376746182,
"lastrecv" : 1376746182,
"conntime" : 1376745877,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 78125,
"banscore" : 0
},
{
"addr" : "115.76.11.1:7685",
"services" : "00000001",
"lastsend" : 1376746182,
"lastrecv" : 1376746130,
"conntime" : 1376746046,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 78127,
"banscore" : 0
},
{
"addr" : "91.235.254.37:7685",
"services" : "00000001",
"lastsend" : 1376746188,
"lastrecv" : 1376746188,
"conntime" : 1376746159,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 77921,
"banscore" : 0
}
]

Apparently they are catching-up... so I assume I am delivering blocks that they are reading... I hope.

My IP in the list of the 25 is 107.217.208.215

Do not use that as a connect, except for temporary connection... My IP changes hourly, I believe. But if you need a quick-connect... add it, then remove it once connected, so you don't restart with it next time you connect... a week later.

[butjust41day]

I agree connections are set low in that list I had a hard time connecting to more than 4 initially; but, when I forwarded the port I seemed to end up on the wrong chain after several hours of mining. So I closed it and had no problems mining.....although blocks seemed to really slow down about 9 hours ago.

I'll wait for the change over to be complete and then open the port back up. Definitely don't want to have to download the block chain again.

[ISAWHIM]

I am watching this like a hawk until 5:00 PM (GMT -5)...

Might as well, since I am here. I need my port-snooper to check-out the raw packet data. lol. Where did I put that program...

[rav3n_pl]

Ok, I connecting to those nodes, but looks like onely 2 have over 78k blocks.
I have 21 connections.... still on block 77937...
I stoppped mining, waitin till it will settle.
Looks like i mine half day in fork :/

[Walking Glitch]

Ok, I connecting to those nodes, but looks like onely 2 have over 78k blocks.
I have 21 connections.... still on block 77937...
I stoppped mining, waitin till it will settle.
Looks like i mine half day in fork :/

I must be on the same chain as you. What nodes have over 78k? Can I get an IP for them? I briefly connected to one, but whoever it was dropped me before I could sync, which sucks, as I'm connected to over a dozen other nodes.

[Petr1fied]

Got 4 connections now... lol... love the start-height variance...
09:30:11
[
{
"addr" : "92.5.104.42:7685",
"services" : "00000001",
"lastsend" : 1376746126,
"lastrecv" : 1376746182,
"conntime" : 1376744432,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 78102,
"banscore" : 0
},
{
"addr" : "50.137.233.14:7685",
"services" : "00000001",
"lastsend" : 1376746182,
"lastrecv" : 1376746182,
"conntime" : 1376745877,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 78125,
"banscore" : 0
},
{
"addr" : "115.76.11.1:7685",
"services" : "00000001",
"lastsend" : 1376746182,
"lastrecv" : 1376746130,
"conntime" : 1376746046,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 78127,
"banscore" : 0
},
{
"addr" : "91.235.254.37:7685",
"services" : "00000001",
"lastsend" : 1376746188,
"lastrecv" : 1376746188,
"conntime" : 1376746159,
"version" : 70000,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 77921,
"banscore" : 0
}
]

It'd probably help if you ensure you're connectible. All of those connections are initiated by you as can be seen by inbound returning false in all 4 peers. If you want more peers you need to forward the default P2P port (7685) in your router or enable the UPnP option if the QT wallet comes with UPnP support (I self compile a daemon so I don't know if it does or not) and your router supports it.

[ISAWHIM]

It has UPnP checked, but no option to uncheck it... It is locked that way.

I don't need port-forwarding, as all connections are unblocked in my router, except the most extreme known viral and attack detected packets themselves. (Nothing shows in logs as being blocked. Nor do I have any problem connecting to over 40 connections on other coins who have wallets that have had the 8-connection limit removed.) I have not altered anything except my RPC port, to keep people from reading my personal info, or attacking my miners.

NOTE: When I say my versions below... I am talking about the windows wallet, used as a daemon, for mining and as a wallet. Not the linux compiles or OSX compiles...

I see people connect, and drop-off, after a few minutes, so I assume they got a faster connection or disconnected, or the program itself is having connection issues.

Everything was fine, up until the last few days, with the old 1.4.0 program. Nothing has changed in the 1.4.1 program, except now I get POS blocks, where I didn't before, on the 1.4.0 program.

My connections to the older 1.3 programs was perfect, from 1.4.0... It was when the 1.3 programs disappeared, that the issues began. Thus, whatever was changed from 1.3 to 1.4 is the actual issue, related to connections. Because those 1.3 programs were talking finem and keeping us 1.4 users connected, but 1.4 to 1.4 connections have been the trouble for me... Though 1.3 was just not doing POS well. 1.4 didn't do POS well, and also had/has comm issues... 1.4.1 has POS fine, but comm issues still.

Even the block-explorer which has 100 possible connections, is only able to get 25... Though, I am sure there are more than 100 attempting to connect to that daemon.

How is the IPV4:IPV6 and IPV6:IPV4 connections? That is a major f-up, for most sockets. Could that be an issue here? Packets forward and have multiple forwards which can shift packet data out of the MTU range. Check that data fits within the MTU range for UPnP, and is also not being chewed-up by a IPV4->IPV6 or IPV6->IPV4 conversion that ISP's like to break, and programs don't like to digest.

EG, with 1 forward of IPV4:IPV6 and (data) the MTU may be fine... but if a packet hits another forward, or multiple 4->6 then 6->4 then 4->6... it pushes data out of the packet to make room for the growing header in the packet. Causing it to break the TCP send link. Change the data-size to a little less, and see if that helps. If it does, then that is the issue with the connections. Multiple failed TCP connections due to corruption from MTU failures will kill the TCP connection. It won't try to resend more than 6 times.

[rav3n_pl]

I have only ONE node >78k

 "addr" : "95.72.68.42:29670",
        "services" : "00000001",
        "lastsend" : 1376749254,
        "lastrecv" : 1376748478,
        "conntime" : 1376748399,
        "version" : 70000,
        "subver" : "/Satoshi:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 78165,

[ISAWHIM]

I have only ONE node >78k

 "addr" : "95.72.68.42:29670",
        "services" : "00000001",
        "lastsend" : 1376749254,
        "lastrecv" : 1376748478,
        "conntime" : 1376748399,
        "version" : 70000,
        "subver" : "/Satoshi:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 78165,

That is all you need... the heights are the heights when they first connected... they will not update the start-heights, unless they disconnect and reconnect to you, after getting the missing blocks. Then you see the new heights.

What you don't want to see is this... (corrupted or NULL or invalid or cut/trimmed packet data)

 "addr" : "95.72.68.42:29670",
        "services" : "00000000",
        "lastsend" : 0,
        "lastrecv" : 0,
        "conntime" : 1376748399,
        "version" : 70000,
        "subver" : "",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : -1,

or connections to older versions 60001, 60002, 60003

[rav3n_pl]

That missing 100 blocks should be resend in matter of minutes, it is over hour and I`m still on "blocks" : 77977
Something is not right IMO.

[ISAWHIM]

That missing 100 blocks should be resend in matter of minutes, it is over hour and I`m still on "blocks" : 77977
Something is not right IMO.

Did you restart the client... if it hangs, it will not continue until you shut down the client and restart again. Don't delete your blocks data if you are that far... it just hung on a bad send. (I had to do that multiple times, to get the last 200+ blocks)

The wallet never reported the final height once... until I hit a POS block... that refreshed the screen. Then it showed I was up to date... the whole time I was actually up to date, but the wallet just didn't display I was, when I actually was.

Unlock it, and try mining... if you start mining, then you are up to date, if you see one correct height in your list of peers.

78197 current height (CGminer reported diff 79-83K... if you see less, you are not on the right chain.)

[Walking Glitch]

That missing 100 blocks should be resend in matter of minutes, it is over hour and I`m still on "blocks" : 77977
Something is not right IMO.

Did you restart the client... if it hangs, it will not continue until you shut down the client and restart again. Don't delete your blocks data if you are that far... it just hung on a bad send. (I had to do that multiple times, to get the last 200+ blocks)

The wallet never reported the final height once... until I hit a POS block... that refreshed the screen. Then it showed I was up to date... the whole time I was actually up to date, but the wallet just didn't display I was, when I actually was.

Unlock it, and try mining... if you start mining, then you are up to date, if you see one correct height in your list of peers.

78197 current height (CGminer reported diff 79-83K... if you see less, you are not on the right chain.)

It's pissing me off that I'm connected to several peers with the right chain, the 78k+ one, but it flat out refuses to download or even acknowledge that that is the right chain. On top of that this stupid forum gave me a database error when posting, so I had to wait 15 minutes between posts because it thought I posted.........


EDIT: This is seriously pushing me away from this coin. How hard is it to code it so that the client recognizes that the longer chain is gthe proper one, and to sync to that one? Too hard I guess...

I'm also loving how it crashes every time I exit it.

[ISAWHIM]

You might just want to wait until after noon, when the old versions are kicked and the new versions are the only ones mining.

Then, sadly... redownload the whole DB again, deleting everything except your config file and your wallet.dat...

Once you hit block 72000, stop the client/wallet... wait for it to actually die... and save everything it created, except the config and wallet... into a folder called "backup". Then, if you do get on the wrong chain... (let it try and try... you may get the wrong one at first, but it should eventually hit the correct one... if it does not, then just delete what it downloaded, and paste your backup data back into your wallet folder, so you start again from 72000.)

Eventually one of these connections will lock and begin working for you. (I hope.)

Or mine on a pool that is working... (The easier option, until the connection issue is resolved.)