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

[almightyruler]

How does one tell which chain they're on? My client is currently showing 75,003 blocks with a difficulty of 0.0256. I installed it for the first time about a week ago.

[myweblife]

How does one tell which chain they're on? My client is currently showing 75,003 blocks with a difficulty of 0.0256. I installed it for the first time about a week ago.

75025

[snoopdoug]

I will be working on getting it patched up before I leave town tonight but no guarantees. I will be back 9-9-2013 and have it fixed then if not tonight

This is not going to be good for some people. the two chains separated over 15,000 blocks ago it seems

Invalid chain:

Code:

received block c6db6c62a25bec74cb52
SetBestChain: new best=c6db6c62a25bec74cb52  height=48123  trust=1174598002  date=08/24/13 07:09:53

Valid chain:

Code:

SetBestChain: new best=00000001bc20a5faa994  height=48123  trust=1157820531  date=08/24/13 07:09:49

I agree that 00000001bc20a5faa994 is the valid block.

The bottlecaps fix has been propagated to my github repo at: https://github.com/snoopcode/coins

I also added a checkpoint at height 64,000.

Check it out and see if you agree with the changes.

Let's keep Lebowskis alive - don't let the Dude down!

[Desten]

If cryptsy will be on invalid chain then dude died already.

[broken_pixel]

v1.0.0.0-g32a928e-dude-abides

The wallet syncs and is generating stake.

[broken_pixel]

At which chain is cryptsy?
I spent some btc's (lot for me) to bought some of them. And now they delisted more than 13 days.
This is not the best occasion for the exchange and for cryptos at all. Fix that asap.
I think that after that accident this cryptocoin most likely will be dead. And trust for others assforks will be knocked down a little...

Cryptsy is on the longer chain with the higher difficulty and the majority of peers. I was sent 1.8 LBW from coins-e to a wallet on a forked chain yesterday. It arrived and confirmed

Ummm! What happened to my coins after Crpyptsy delisted them. HYC has been dead for a long time and is still listed on Cryptsy.

[broken_pixel]

yesi can start it and it sync's, but i mined like 130 lbw's at diggers pool, sent them to myself and they have still never shown up, that was 4 days ago.

j

post your address I will send you one to test.

[FinShaggy]

Wait so is this real?

[Don007]

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.

[jelikish]

Anyone knows if lbw.ltcoin.net is synced ?

We need LBW re-listed on cryptsy so that we can understand who is on the correct chain and who is not.

[Don007]

That's Digger's pool, which I'm talking about (http://lbw.ltcoin.net/).

[jelikish]

Yeah, i transferred some coin from that pool to coins-e and it never made it. I hope it will make it to cryptsy once its re-listed.

[myweblife]

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

[Don007]

Thanks for that. It seems that my client is stuck now (while synching). How can I fix this? Can I re-install my wallet or will I loose my LBW's then?

[myweblife]

Just recive some coin,it look my client is fine
Status: 30 confirmations
Date: 2013/9/20 14:25
From: unknown
To: 68JZK4UfpGXCaBkTkQrRQVx1fYMrJZb9iK (own address)
Credit: 10000.00 LBW
Net amount: +10000.00 LBW
Transaction ID: 36272559c4f49f5e1bf581633ef1ed35b72b338c9bf0e11ed7b214abcce66b11

[Don007]

It looks like my client does synch, from about 400 blocks till 0. But after that there are about 3400 blocks remaining, which can't be synched or something. Does someone have a solution for this?

[mullick]

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

[almightyruler]

How do you tell when a fork happens?

My client is currently showing block 83321 with a hash of 00000001d38fa9e7a43c129e2c6fdc27223bb366dc647c9511f968f1a0ab3d85

If this is the correct chain you want (ie you DON'T have this block) then let me know.

Can you get onto the right chain by forcing connect to a specific node?

[BugSpirit]

I see this picture now


> getinfo
{
"version" : "v1.0.0.0-g32a928e-dude-abides",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 1012.89809700,
"newmint" : 0.00000000,
"stake" : 40.15227200,
"blocks" : 79338,
"moneysupply" : 1581363.25251100,
"connections" : 5,
"proxy" : "",
"ip" : "128.68.38.185",
"difficulty" : 0.00781238,
"testnet" : false,
"keypoololdest" : 1374757052,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"errors" : ""
}

> getpeerifo


[
{
"addr" : "198.50.233.21:7245",
"services" : "00000001",
"lastsend" : 1379741639,
"lastrecv" : 1379741639,
"conntime" : 1379741292,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79335,
"banscore" : 0
},
{
"addr" : "70.98.114.237:7245",
"services" : "00000001",
"lastsend" : 1379741971,
"lastrecv" : 1379741971,
"conntime" : 1379741299,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 83627,
"banscore" : 0
},
{
"addr" : "216.158.85.123:7245",
"services" : "00000001",
"lastsend" : 1379741971,
"lastrecv" : 1379741971,
"conntime" : 1379741349,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 83628,
"banscore" : 0
},
{
"addr" : "198.199.83.168:7245",
"services" : "00000001",
"lastsend" : 1379741639,
"lastrecv" : 1379741639,
"conntime" : 1379741355,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79335,
"banscore" : 0
},
{
"addr" : "198.211.116.19:7245",
"services" : "00000001",
"lastsend" : 1379741971,
"lastrecv" : 1379741971,
"conntime" : 1379741428,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 83629,
"banscore" : 0
}
]

So there are 2 chains, half of the peers support one of them, the other half another. Now we are to decide which one is correct. Then mine it with all you got and most of clients will follow. Do this or Donnie died in vain.

[almightyruler]

So you're basically starting the client fresh so that all connections are new, then use startingheight as an indicator of which chain they're on? My mix is not on the fence like yours:

        "startingheight" : 84068,
        "startingheight" : 84068,
        "startingheight" : 84068,
        "startingheight" : 84069,
        "startingheight" : 84069,
        "startingheight" : 84069,
        "startingheight" : 84069,
        "startingheight" : 84069,

I did getpeerinfo a few times and did see one at 79379, but that disappeared a few seconds later.

edit: going by the heights from your post roughly 8 hours ago...

79335 (then), 79379 (now)
83627 (then), 84068 (now)

First chain has only advanced about 44 blocks, whilst the second has advanced 441 over the same period.

This assumes that the peer which appeared briefly @79379 had the complete chain (even if it was the wrong one)