[Critical Update] Feathercoin 0.6.4 - Hard Fork at block 33,000

[WeTradeCoins]

Please check this BushStar, there is an error in the latest update.

https://github.com/FeatherCoin/FeatherCoin/issues/6

I have been running it on linux since it came out as the backend of a p2pool server without a hitch.

Well after we built it and loaded it it was crashing every 5 minutes and restarting.  We switched back to the old build and everything was fine.  If we wait for a block to be found could this solve the issue?

Build it yourself from source.

They were all built from source.  The old version which has no issues and the new version that crashes were built on the same box, using the exact same packages.  I am going to try to recompile again and see what happens.

[bushstar]

They were all built from source.  The old version which has no issues and the new version that crashes were built on the same box, using the exact same packages.  I am going to try to recompile again and see what happens.

Did you clone a fresh copy from GitHub?

I think they have to released another version with another correction. We will never be able to touch this block within 20 days.

I agree.  At best, you'll see today's network hashrate hold up.  At worst, it will shrink by half every week as the savior miners throw in the towel.

Block 33,000 is too far out if we want to see any rebound.  It might be best to release again with a fork at 32,900.  Or even 38,500.

Carry the FTC momentum while we still have it.  It's painful to release again, I know. But waiting another 3+ weeks might kill the coin entirely. 

33,000 is getting closer. I've just got up and will now continue the mission to get us some hash power.

[smoothie]

At this rate FtC will retarget in 30 days or so.

[bushstar]

At this rate FtC will retarget in 30 days or so.

Actually it looks like we are picking up a bit of steam as blocks are ticking faster. We should not be sitting around for that long.

Smoothie where have you been anyway?

There have been so many coins coming out and a lot of them need your attention. This is not one of them by the way. The fact that you are chasing us now makes me think you only target coins you deem a threat. If true this puts you on par with the trolls in the troll box, I always thought you were better than them but just misguided

Back to business, I mine 35 coins a day now that I've tripled my mining setup. Looking forward to the next difficulty though it cannot come soon enough now.

[erk]

Doesn't seem to be getting any faster to me, current block is 32837

Code:

Block  	Timestamp 	Delta(secs)	Min. per block
			
32000	1367773886		
32050	1367778134	4248	1.42
32100	1367784431	6297	2.10
32150	1367789247	4816	1.61
32200	1367794958	5711	1.90
32250	1367800251	5293	1.76
32300	1367814493	14242	4.75
32350	1367827487	12994	4.33
32400	1367844513	17026	5.68
32450	1367882120	37607	12.54
32500	1367942063	59943	19.98
32550	1368031928	89865	29.96
32600	1368139213	107285	35.76
32650	1368240752	101539	33.85
32700	1368345509	104757	34.92
32750	1368482631	137122	45.71
32800	1368654713	172082	57.36
32837	1368871932	217219	97.85

97min per block average for the last 37 blocks. The stats on feathercoin.com is still claiming it's 30min per block which is just crazy wrong.

At this rate even if the difficulty reduces from 188 to 110, the block rate will still be terrible.

[bushstar]

97min per block average for the last 37 blocks. The stats on feathercoin.com is still claiming it's 30min per block which is just crazy wrong.

At this rate even if the difficulty reduces from 188 to 110, the block rate will still be terrible.

We would need to put some custom code to get the time from a smaller sample of blocks. What do you think would be a suitable number for a sample of block at this point in time?

After the change transactions will move quicker and we will be able to pick up some additional miners on the way. This should restore some confidence to the market without seeing people mining just to dump. We are looking for a slow and steady recovery the first step of which is to get to block 33,000, after which we only have 264 block to get to the next change at 33,264.

[erk]

97min per block average for the last 37 blocks. The stats on feathercoin.com is still claiming it's 30min per block which is just crazy wrong.

At this rate even if the difficulty reduces from 188 to 110, the block rate will still be terrible.

We would need to put some custom code to get the time from a smaller sample of blocks. What do you think would be a suitable number for a sample of block at this point in time?

After the change transactions will move quicker and we will be able to pick up some additional miners on the way. This should restore some confidence to the market without seeing people mining just to dump. We are looking for a slow and steady recovery the first step of which is to get to block 33,000, after which we only have 264 block to get to the next change at 33,264.

No more than 200 blocks in the sample, if you look at my table the rapid decline started at block 32450, I am using 50 block data points since then and when I chart them it has a steep gradient.

A better technique would be to use a number of days, say an average over the past 7 days. (604,800 secs) so you subtract that from the last blocks timestamp and find the closest block to it, in this case it would be block 32656  which means 181 blocks in the past 7 days or 55.69min per block average over the past 7 days.

[6135870]

Can someone post a link to the 0.6.3 client? I need a client that works for now until 0.6.4 is repaired.

[erk]

Can someone post a link to the 0.6.3 client? I need a client that works for now until 0.6.4 is repaired.

What's supposed to be wrong with the 0.6.4 client? Work fine fore me on Window, Mac, Linux.

[6135870]

This is what I get in the console: {
"version" : 60400,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 64.33841680,
"blocks" : 32828,
"connections" : 0,
"proxy" : "",
"difficulty" : 188.19010869,
"testnet" : false,
"keypoololdest" : 1368285686,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

I have no connections to the network and out of sync. Ideas?

[YipYip]

Many on here are very impatient. Expecting a few week old coin to have basically overnight success are delusional. FTC will only be a success when the support and development for it persists past at least a year from its launch.

4 weeks and Already a fork? Lolz

At least they now have some hardship to help build character for a real coin/community

Lets see if they can even get to the for position of 32000 as It is looking really really bad....

Of all the total rubbish that has come out recently FTC had a flash mob community feel to it

Anyway good luck..i hope u provide some diff relief to LTC.....but it is a long and hard road to call yourself a coin...everybody has to start somewhere

[slavach]

Injected 650 kHps into network. The block 33,000 becomes closer. Good luck.

[bushstar]

This is what I get in the console: {
"version" : 60400,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 64.33841680,
"blocks" : 32828,
"connections" : 0,
"proxy" : "",
"difficulty" : 188.19010869,
"testnet" : false,
"keypoololdest" : 1368285686,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

I have no connections to the network and out of sync. Ideas?

Can you backup your wallet.dat, then remove everything from your .feathercoin folder except your wallet.dat, start the client up again and let me know if it connects?

Try leaving it running for a while as well.

Injected 650 kHps into network. The block 33,000 becomes closer. Good luck.

Thanks

[bushstar]

No more than 200 blocks in the sample, if you look at my table the rapid decline started at block 32450, I am using 50 block data points since then and when I chart them it has a steep gradient.

A better technique would be to use a number of days, say an average over the past 7 days. (604,800 secs) so you subtract that from the last blocks timestamp and find the closest block to it, in this case it would be block 32656  which means 181 blocks in the past 7 days or 55.69min per block average over the past 7 days.

Time would work fine now but probably not as much once we are three or four difficulty adjust in and looking at retargets every day. It would be ideal to have something that works better when blocks are going slow and fast. I think it would be safer to aim for 50 blocks at the moment and see how that behaves now and after the difficulty adjust.

[pajamaz]

I pointed 4.5 Mh/s at FTC last night.

[6135870]

My wallet has been backed up. I deleted the client and the file in Appdata/Roaming. I re-downloaded the .zip and ran the client, still nothing.
Could it be something with UPnP? Should I try the  SOCKS proxy?


EDIT 1:I installed the feather coin client (0.6.4) on a windows 8 laptop I have and it too is not connecting to the network. My location is Ottawa, Ontario.

EDIT 2:I need to try the 0.6.3 client again to confirm its not the client. Any download links available?

[bushstar]

That is very odd indeed and I'm wondering if it is something local if multiple computers are having the issue.

Have you restarted your router?

Can you ping and get a response from the Feathercoin DNS Seed nodes below?

dnsseed.feathercoin.com
dnsseed.fc.altcointech.net
dnsseed.alltheco.in
dnsseed.btcltcftc.com

There is no old copy of Feathercoin online. If you PM me your email address I can mail it to you.

[6135870]

That is very odd indeed and I'm wondering if it is something local if multiple computers are having the issue.

Have you restarted your router?

Can you ping and get a response from the Feathercoin DNS Seed nodes below?

dnsseed.feathercoin.com
dnsseed.fc.altcointech.net
dnsseed.alltheco.in
dnsseed.btcltcftc.com

There is no old copy of Feathercoin online. If you PM me your email address I can mail it to you.

So while trouble shooting I noticed Steam could not also connect to it's network. I contacted my ISP and they reset a switch to my home, after 20min, I can now connect to the steam network and most importantly; the feathercoin network! Thanks for you assistance, if this issue arises again I will inquire about changing ISP's.


EDIT1: To restore the wallet backup I have, I typed -rescan in the console so the client can find the .dat but it's not. Where do I place the backed up wallet so it can be restored?

EDIT2: Solved, I just replaced the wallet.dat in the roaming file with my back up, and done! back to mining!

[smoothie]

At this rate FtC will retarget in 30 days or so.

Actually it looks like we are picking up a bit of steam as blocks are ticking faster. We should not be sitting around for that long.

Smoothie where have you been anyway?

There have been so many coins coming out and a lot of them need your attention. This is not one of them by the way. The fact that you are chasing us now makes me think you only target coins you deem a threat. If true this puts you on par with the trolls in the troll box, I always thought you were better than them but just misguided

Back to business, I mine 35 coins a day now that I've tripled my mining setup. Looking forward to the next difficulty though it cannot come soon enough now.

At the rate these new coins get created even I can't keep up. Now I resort to picking and choosing the most entertaining one to troll.

[bushstar]

At the rate these new coins get created even I can't keep up. Now I resort to picking and choosing the most entertaining one to troll.

In that case you should head over to Bitcoin, I bet a lot of them do not know that Bitcoin is just a Litecoin clone. That would be an interesting reaction.