Topic: [ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP* - page 19. (Read 199669 times)

Gamecoin GME has a similar problem. You can't average your diff over a large number of block without making it overshoot and lock you at high diff. To solve it, they settled on a recalc ever 12 block with a 48 block history, even that's too much history to average over, but they only do a 10% diff change on each recalc so it compensated a bit.
 If you were going to do a diff recalc every block, you wouldn't want to average over the last 120blocks, more like 4 or 5 blocks would be enough.

Now you have a real problem, it will probably need a new client release to fix as the next diff change will be higher not lower. Better get onto it quickly before exchanges and pools get mad. The changes will probably have to kick in on the next block, or the client will have to start at a lower diff somehow.

In my opinion this is not the result of a fork, but a difficulty adjustment stall.

At block 245000, the developer changed the difficulty retarget method.  Before 245000, the code appeared to adjust the difficulty every 120 blocks, based on the block solving time of those 120 blocks.  The Difficulty would adjust by a maximum of 4x (four times).  After 245000, in an effort to reduce the strip mining effects by the multipools, the retarget scheme changed to adjust every block based on the block solving time of the previous 120 blocks with a maximum adjustment of 4x.  This turned out to be a disaster with the most recent hash rate increase on the coin, because in the space of 10 blocks, the difficulty increased by a factor of over 1 million.  Using the old method (pre 245000), the difficulty would have only increased by a factor of 4. 


The hash rate reported by the client is incorrect.  The client reports 35.7 GH/s.  The hashrate calculation does not account for the changing difficulty.  Instead it assumes that last 120 blocks had a difficulty of 114.74, which results in a 35.7 GH/s number.  The code for calculating the network hash rate is another place an alt coin needs to be changed, when cloned from Litecoin.

My calculations for hash rate are as follows:

Since these hashrates are based on individual block times, they cannot be taken to be exact network hash rates due to luck.  The size of the multipool that was added may have been around 1 to 2 GH/s.

I also had a sync problem. But when I get the version 1.7 and sync'ed from the scratch (delete everything in the config dir except wallet and config files), the sync seems OK. And I sync'ed to block 247330. I am not sure if this is a forked chain or is the good chain. I looked at the block explorer in the OP, and it shows at block 246953 for about 2 days, is the block explorer stuck? or there's a fork?

Anyway, I am glad to get over the block 246953, and be in a block close to the diff retarget switch block of 248000.

I think its a few of them.  

Or it could be some kind of hashpower/ share submission exploit.. or whatever they are talkin about here ..  https://bitcointalksearch.org/topic/asic-testing-on-scrypt-285656

Kapoop went the ifc?

I cannot make heads or tails of what is happening in this block chain...

What caused this? Fork, exploit, hack the world 1st scrypt asic?

Anyone currently running an IFC pool (no p2p please) lease contact me. I would like to provide some incentives to miners to get us to the turnover

This paints an interesting picture

http://exploretheblocks.com:2750/chain/Infinitecoin?count=2016&hi=246953

I hope someone knows what happened and how to fix it.  The current difficulty, as was mentioned above, is 249.59.  It doesn't look like a fork.  It has been about 33 hours since the last block was solved according to http://exploretheblocks.com:2750/chain/Infinitecoin.


I upgraded to 1.7 and it was able to sync the block chain 12 hours ago.

Someone has to know what the hell is going on with IFC? 35,732,342 KH, but difficulty is 1/10th what is should be.. more hash on IFC than LTC? no way....Fork or hash exploit?

After taking the source code and allowing the following to be output in the debug file, it was determined that the current difficulty is 250 (for block 246954).


The network hashrate according to the working pools adds up to about 7.5 MH/s (Although the client and coinchoose report something like 36Gh/s)

All things being equal, it looks like it will take 1.7 days to solve a block, after which the difficulty will adjust to about 62.  At this point in time, it has been 1.0 days.  Hopefully just another half day to go.

http://www.infinitedice.net has been updated to V1.7

waiting for that 248000 block switch.

Everything is fine now and infinitecoin.org website has been updated.
Regards Heju

Thanks dream for informing me the issue. The download links in infinitecoin.org are not updated, which caused some confusions. I posted two messages there, so hope everyone is getting the right download links now.

All the links here in this thread are correct. I don't own infinitecoin.org, so I can not update there. I PM'ed Heju22 to update them. Please use the download links in OP here. And you can verify the version by checking Help->About Infinitecoin.

Thanks all for your patience.

I am using v1.7 from the Google link. I don't know what you are having so much trouble with.

All the links in OP work fine for me. Which link you used did not give you the right files? You should get Infinitecoin17.zip, in which there's a folder Infinitecoin that contains all files.

You should use the OP links in this thread. Other links for downloads may be outdated.

And after you download, open the qt client, At help->About Infinitecoin window, you should see v1.7.0.0.

http://coin-base.net/infinitecoin/

Pool updated

Everyone, please upgrade to version 1.7 as soon as possible. 

Just tried sending IFC to cryptsy and bter,it worked fine

I am using the latest version 1.7