[ANN] Lebowskis [LBW] - *Updated Client and Seednode*

[Don007]

How to solve this? Or how to switch chains with my client? i'm obviously on the wrong one, cuz I haven't received any Lebowski from my pool mining.

[BugSpirit]

How to solve this? Or how to switch chains with my client? i'm obviously on the wrong one, cuz I haven't received any Lebowski from my pool mining.

Delete everything in appData folder apart from wallet.dat. Then your client should download the most 'popular' chain.

I've mined roughly 200 blocks in 82k chain. But now I have only 2 peers connected. Is that so little people here or i'm in a limb again?

[myweblife]

Well i finally got around to working on this again last night I had done the initial fixes a few weeks ago but was waiting for a response from coins-e

I got it past the initial forks and fixed the self forking issue with POS. But now it appears there is another drastic fork about 2k blocks ago. I cant seem to get on the right side of. If anyone is synced past block 81484 and on what appears to be the correct height of 82910 could you possibly send your appdata folder Minus you wallet.dat to bottlecapsfoundation@gmail.com

Just your debug.log would be helpfull but due to the lack of explorer I will need a full copy of the chain to get the full hash for the good block as well as stake modifiers

Here is the repo but it still needs this final fork resolved

https://github.com/Mullick/coins

Thanks to balthazar again for his help with caps which is making this possible

Just send it to you ( block 84298)

[Don007]

How to solve this? Or how to switch chains with my client? i'm obviously on the wrong one, cuz I haven't received any Lebowski from my pool mining.

Delete everything in appData folder apart from wallet.dat. Then your client should download the most 'popular' chain.

I've mined roughly 200 blocks in 82k chain. But now I have only 2 peers connected. Is that so little people here or i'm in a limb again?

Thanks. I think i'm on the other chain now indeed. I had to restart the Lebowski client a couple of time, but it seems my client is up to date now.


 

Same here. I mined over 1000 LBW @ Digger's pool, he has the prove that he had paid it out to me but I haven't received a single Lebowski yet..  Atleast, I have none in my wallet yet (6AcyCBF9LyTym3HPNDvoNZRNu4F7GhiiCq).

I think somehome the wallet isn't fully sych'ed, however it shows it is.

Just send some coin to you for test

Status: 0/unconfirmed, broadcast through 4 node(s)
Date: 2013/9/20 06:11
To: 6AcyCBF9LyTym3HPNDvoNZRNu4F7GhiiCq
Debit: -10.00 LBW
Transaction fee: -0.001 LBW
Net amount: -10.001 LBW
Transaction ID: a867133b5c50489a78e9ca8f51ede4f601e4d158510ff277d8574f64c83d24bc

Thanks! I've got them. Do you want them back?


However, this still means that I haven received my coins of Digger's pool (http://lbw.ltcoin.net/) ;\

[almightyruler]

Restarted the client, startingheight is a lot more varied this time...


        "startingheight" : 79388,
        "startingheight" : 79403,

        "startingheight" : 84254,
        "startingheight" : 84254,

        "startingheight" : 84564,
        "startingheight" : 84566,
        "startingheight" : 84566,

I've rearranged them into chronological order. Note the 312 block difference between 84566 and 84254. Then there's still 79388. Do we now have 3 forks???

[myweblife]

How to solve this? Or how to switch chains with my client? i'm obviously on the wrong one, cuz I haven't received any Lebowski from my pool mining.

Delete everything in appData folder apart from wallet.dat. Then your client should download the most 'popular' chain.

I've mined roughly 200 blocks in 82k chain. But now I have only 2 peers connected. Is that so little people here or i'm in a limb again?

Thanks. I think i'm on the other chain now indeed. I had to restart the Lebowski client a couple of time, but it seems my client is up to date now.


 

Same here. I mined over 1000 LBW @ Digger's pool, he has the prove that he had paid it out to me but I haven't received a single Lebowski yet..  Atleast, I have none in my wallet yet (6AcyCBF9LyTym3HPNDvoNZRNu4F7GhiiCq).

I think somehome the wallet isn't fully sych'ed, however it shows it is.

Just send some coin to you for test

Status: 0/unconfirmed, broadcast through 4 node(s)
Date: 2013/9/20 06:11
To: 6AcyCBF9LyTym3HPNDvoNZRNu4F7GhiiCq
Debit: -10.00 LBW
Transaction fee: -0.001 LBW
Net amount: -10.001 LBW
Transaction ID: a867133b5c50489a78e9ca8f51ede4f601e4d158510ff277d8574f64c83d24bc

Thanks! I've got them. Do you want them back?


However, this still means that I haven received my coins of Digger's pool (http://lbw.ltcoin.net/) ;\

no

[BugSpirit]

I'm with 4 other guys now in branch that has 84906 blocks

"addr" : "69.147.229.226:7245",
"startingheight" : 84906,

"addr" : "74.207.225.170:7245",
"startingheight" : 84907,

"addr" : "216.158.85.123:7245",
"startingheight" : 84908,

I'd suggest  everyone who want to resolve this fork to sync with theese nodes and mine that chain. Even if you have only CPU on difficulty 550-600 (in CGMiner) it should solve a dosen blocks a day.

[almightyruler]

According to my client there's 84072 blocks, with the last block having a time of about 17 1/2 hours ago. There are several peers connected and most have block numbers much higher than this, but 84072 isn't anywhere near the 'other' chain either (currently @79430). Does this mean my client has realised there's a fork and has been hiding its head in the sand for the past 17 1/2 hours, hoping that some outside force will resolve things, rather than trying to decide which chain is the correct one by itself?

peer 1: 79430  <-- chain 1?
peer 2: 79430
my client: 84072  <-- ? ? ?
peer 3: 84254  <-- chain 2?
peer 4: 84933  <-- chain 3?
peer 5: 84937
peer 6: 84937

[BugSpirit]

peer 1: 79430  <-- chain 1?
peer 2: 79430
my client: 84072  <-- ? ? ?

Well, I think there is a bug in client in counting the blocks. I think it counts only PoW ones. My client shows 84908 in peers, by 85021 in itself. But it sees blocks from peers which is impossible in case we are in different chains.

I repeat. I think the best way to solve the fork is to pick the most lengthy chain and mine it. Cause the 84908 chain is already the most mineable one.

[almightyruler]

Would be handy if the *coind source had a function to temporarily ban peers if certain parameters are off, such as presenting a block count that's significantly different to our own (assuming everything is synced), or offering a block hash from an unwanted chain. In addition the client would TELL the other client that it's banning them, so that if this happens enough times the operator is alerted to something being amiss.

Even automated fork detection would be handy, although I guess it's not always black and white.


edit: I removed peers.dat and addnode'd 3 IPs which were on the higher block chain, but a couple of minutes after restarting my client has already found nodes on the other chain. Back to the exact same position, stuck on block 84072.

Is there a way to manually ban peers, tell the client to ignore the peers that appear to be on the wrong chain?


edit #2: deleting the block db and restarting seems to have kicked it back into gear; now at height 85138 with all 5 connected peers within a few blocks of each other.

[BugSpirit]

Are we OK now?

[myweblife]


[
{
"addr" : "70.98.114.237:7245",
"services" : "00000001",
"lastsend" : 1380023607,
"lastrecv" : 1380023607,
"conntime" : 1380021997,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 87752,
"banscore" : 0
},
{
"addr" : "216.158.85.123:7245",
"services" : "00000001",
"lastsend" : 1380023607,
"lastrecv" : 1380023607,
"conntime" : 1380022014,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 87752,
"banscore" : 0
},
{
"addr" : "74.207.225.170:7245",
"services" : "00000001",
"lastsend" : 1380023607,
"lastrecv" : 1380023607,
"conntime" : 1380022020,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 87752,
"banscore" : 0
}
]

[8bitfish]

ok, well, could someone just hand out blockchain files for download that are on the valid blockchain, this is probably the easiest and most convenient way to fix this

[NaNaec]

any working pools in right chain?

[duuuuude]

i have the correct blockchain going, and i am working on making a LEB pool, it is my first attempt so it may take a bit. i will list here as soon as its up.

j

[snoopdoug]

Please read if you're going to mine Lebowskis!

The Lebowski client code has been updated to correct the self-forking problem.

If you're going to mine, please:

• download and compile the latest code from https://github.com/lebowskis/coins
• connect to a node that's running the correct version

To check your Qt client's version, click the 'Help' menu and then 'Debug window'.  In the 'Information' tab, you should see a Client version that begins with 'v1.1.0.0'.  Version 1.1 has the latest updates.

There are a few nodes that clients can connect to.  The node at 74.207.225.170 is running the latest updates.  The other nodes may have the correct blockchain, but they might not.  To see the nodes you're connected to, open the debug window, click the 'Console' tab and type 'getpeerinfo' in the command input box.  You should only connect to peers running version 65000.  An earlier version is not the latest code.

To connect to a specific peer, update your Lebowskis.conf file with 'connect=74.207.225.170' instead of 'addnode'.

Finally, check out the new Lebowskis block explorer at http://lbw.blockprobe.com/

Lebowskis are really the only 'fun' coin, let's get it back online!

[loveys]

why don't give the link for windows qt?

[snoopdoug]

why don't give the link for windows qt?

We're working on the Qt client for windows, but I'm having issues compiling the dependencies.

[mullick]

why don't give the link for windows qt?

We're working on the Qt client for windows, but I'm having issues compiling the dependencies.

Merry Christmas

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

Glad to see someone else got to this. I had the forks revolved up to about 60k but got distracted for a few days to come back and find yet another. Just not enough time

[snoopdoug]

Merry Christmas

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

That's awesome.  Thanks for the help!

I've committed those files to the github repo at https://github.com/lebowskis/Qt