[ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP*

[anoncuber]

Good god! Might have to retire from IFC mining with the 23.62+ difficulty at the moment  

[Stefan]

What happened? Difficulty is increasing rapidly but hashrate dropped. I expected that every block would have 30 seconds average to be found and to achieve such time, correct difficulty would be computed after each previous block. Now it seems to be one block per hour if not more...

11:28:15

{
"blocks" : 245394,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 22.27329694,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 10531715441,
"pooledtx" : 238,
"testnet" : false
}


13:22:39

getmininginfo


13:22:39

{
"blocks" : 245395,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 73.56347644,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 4824319513,
"pooledtx" : 1543,
"testnet" : false
}

[tokyoghetto]

so whats the deal guys? Am I reading this correctly.

73 Diff, 4 gighash network speed???

[erundook]

# infinitecoind getmininginfo
{
    "blocks" : 244999,
    "currentblocksize" : 7365,
    "currentblocktx" : 13,
    "difficulty" : 1.08697816,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 162242767,
    "pooledtx" : 19,
    "testnet" : false
}

are we forked or what

[saamxx]

# infinitecoind getmininginfo
{
    "blocks" : 244999,
    "currentblocksize" : 7365,
    "currentblocktx" : 13,
    "difficulty" : 1.08697816,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 162242767,
    "pooledtx" : 19,
    "testnet" : false
}

are we forked or what

Version 1.6 changed the diff retarget to each block, starting from block *245000*. We are currently at block 243736.

"blocks" : 244999
Are you have a newest version of daemon?

[erundook]

# infinitecoind getmininginfo
{
    "blocks" : 244999,
    "currentblocksize" : 7365,
    "currentblocktx" : 13,
    "difficulty" : 1.08697816,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 162242767,
    "pooledtx" : 19,
    "testnet" : false
}

are we forked or what

Version 1.6 changed the diff retarget to each block, starting from block *245000*. We are currently at block 243736.

"blocks" : 244999
Are you have a newest version of daemon?

yep, we were running the latest version. though re-downloading the blockchain fixed the fork, but our blocks worth of ~25M IFC were orphaned

[Stefan]

good news, hope it will do better

{
"blocks" : 245396,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 33.69753891,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 980665121,
"pooledtx" : 2877,
"testnet" : false
}

[saamxx]

It's fantastic
From 72 to 1.7 within one hour
Good test.
Very impressive!

[Stefan]

Something is still slowing down the block find process, even when high hashrate while low difficulty. We are waiting almost a hour for a single block again:

Last block time: 16:04:35

{
"blocks" : 245523,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 1.77078548,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2,293,105,249,
"pooledtx" : 797,
"testnet" : false
}

16:45:23

{
"blocks" : 245523,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 1.77078548,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2,293,105,249,
"pooledtx" : 1678,
"testnet" : false
}

[Hippie Tech]

Something is still slowing down the block find process, even when high hashrate while low difficulty. We are waiting almost a hour for a single block again:

Last block time: 16:04:35

{
"blocks" : 245523,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 1.77078548,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2,293,105,249,
"pooledtx" : 797,
"testnet" : false
}

16:45:23

{
"blocks" : 245523,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 1.77078548,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2,293,105,249,
"pooledtx" : 1678,
"testnet" : false
}

Every client Ive seen can be slow and/or very off when reporting the network's hashrate. Thus very unreliable.

There is only 21 mhash showing here. https://ifc.coin.lu/index.php

Sad to see the coin hoppers 'forkin' you guys some more.

Nice 'fix'.

[killdemon]

No forking, everything is fine. Difficulty just rising and failing after each block, working perfect and someone should inform those middlepoolers to jump on some another coin or their profit will be low , very low.

[erundook]

i think each block diff change should have some limit, like maximum 50% jump per adjust

[RoadTrain]

http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.

[saamxx]

http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.

yeh, something wrong

[Hippie Tech]

http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.

Its not the algo.. its the dev and the ever more apparent confilct of interest.

Click the 100 or 500 tab and you'll see how the update has made things easier for the poolhoppers to eat up the blocks.

Over 100 blocks were found in less than 2 minutes. Not cool.

[monocolor]

http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.

Its not the algo.. its the dev and the ever more apparent confilct of interest.

Click the 100 or 500 tab and you'll see how the update has made things easier for the poolhoppers to eat up the blocks.

Over 100 blocks were found in less than 2 minutes. Not cool.

The algorithm is not his, it's the same as before, using the last 120 blocks to determine the next diff. The only difference is that instead of doing it every 120 blocks, now it is doing it every block. But the base is still last 120 blocks, I'd expect fluctuations should be smoothed out, but apparently it is not the case.

Do a diff in the code, there's no change in the algorithm itself, except diff retarget at every block instead of every 120 blocks.

[monocolor]

http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.

Yes I guess the PPCoin algorithm is better than this linear algorithm, which seems cause big oscillations.

It is surprising yet understandable: for IFC 120 blocks take about 60 mins by design. If two consecutive blocks took 50 mins, then when they enter or leave the 120 blocks used for retargeting, they cause huge changes for the next target, which cause this oscillation.

Two possible ways to solve this:
1. Use PPCoin algo, which is exponentially approach to the desired target, so it is not linear.
2. Set the allowable change factor much lower, say each diff change is allowed only 5%-10% (instead of a factor of 4, or 400%), this way the big diff block won't disrupt the normal diff calculations.

[fisheater]

http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.

Yes I guess the PPCoin algorithm is better than this linear algorithm, which seems cause big oscillations.

It is surprising yet understandable: for IFC 120 blocks take about 60 mins by design. If two consecutive blocks took 50 mins, then when they enter or leave the 120 blocks used for retargeting, they cause huge changes for the next target, which cause this oscillation.

Two possible ways to solve this:
1. Use PPCoin algo, which is exponentially approach to the desired target, so it is not linear.
2. Set the allowable change factor much lower, say each diff change is allowed only 5%-10% (instead of a factor of 4, or 400%), this way the big diff block won't disrupt the normal diff calculations.

Thanks monocolor for the suggestions. I will look into them. Yes it looks like the linear retarget format not working fine, although we used a pretty long block interval (120 blocks) to determine the diff. It oscillates now with a few high diff blocks every 120 blocks or so. But at least the overall block time is averaged at the design time, and there are just a few high diff blocks that won't block for long. Before it can be stuck for a day in the high diff zone (for 120 blocks).

This is similar to the Galaxycoin, which also used a linear formula with fewer blocks used.

Let's observe the behavior for a while, if the community thinks we need to move to PPCoin retarget algorithm, which seems smoother, we could do it. But I don't want to release too many patches. So let's watch for a while first.

[Hippie Tech]

Yup.. watching 2 ghash eat up 120 blocks in 2 minutes, then bail, is fun ! Let not do it again !

The coin hoppers are making more than they were before the update .. ALOT more..

[sam53]

you are in an equal position and can do the same, so no complain.

The problem is when at lower diff it's like instamine so most people will get orphans.