Topic: [ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP* - page 21. (Read 199671 times)
September 19, 2013, 08:08:16 PM
Infinitecoin Developers need to fix this diff/adjustment problem quickly, miners are giving up on this coin. As of right now diff is extremely high and network hash rate is over 2.5ghs, the pool I usually mine in is completely abandoned (I have never seen this pool without at least a few miners working). I have been mining this coin quite regularly, but it's not worth it like this, coin diff is to unstable and unpredictable for me to mine with any confidence. You can not expect us loyal miners to waste our time and resources forever, this is starting to get a little ridiculous. Please fix this coin soon before it is left for dead, time is of the essence...
September 19, 2013, 07:15:44 PM
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.
The 5-10% diff increase/decrease factor may result in that if a lot of blocks is mined while high difficulty, and hashrate drops significantly, in that there will be long time between blocks in order to reach low difficulty back. I think that up and down factor should be left about 100% to prevent instamining by increasing hashrate rapidly and then recover in reasonable time. 
September 19, 2013, 06:06:40 PM
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.
The problem is when at lower diff it's like instamine so most people will get orphans.
If I was a douche that enjoys stomping on the early adoptors, then yes... I would join a multi pool.
Dont mind me.. I'm just sitting back eating my popcorn.
September 19, 2013, 05:56:38 PM
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.
The problem is when at lower diff it's like instamine so most people will get orphans.
September 19, 2013, 04:36:56 PM
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..
The coin hoppers are making more than they were before the update .. ALOT more..
September 19, 2013, 04:18:36 PM
http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
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.
September 19, 2013, 02:14:14 PM
http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
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.
September 19, 2013, 02:06:10 PM
http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
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.
September 19, 2013, 12:40:13 PM
http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
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.
September 19, 2013, 12:31:36 PM
http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
yeh, something wrong
September 19, 2013, 12:27:19 PM
http://exploretheblocks.com:2750/chain/Infinitecoin
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
Omg, this new algorithm is terrible.
I'd propose swithing to ppcoin's algo.
September 19, 2013, 12:02:13 PM
i think each block diff change should have some limit, like maximum 50% jump per adjust
September 19, 2013, 10:38:44 AM
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.
, very low. September 19, 2013, 10:02:16 AM
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
}
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'.
September 19, 2013, 09:48:46 AM
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
}
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
}
September 19, 2013, 09:15:49 AM
It's fantastic
From 72 to 1.7 within one hour
Good test.
Very impressive!
From 72 to 1.7 within one hour
Good test.
Very impressive!
September 19, 2013, 08:43:36 AM
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
}
{
"blocks" : 245396,
"currentblocksize" : 2715,
"currentblocktx" : 3,
"difficulty" : 33.69753891,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 980665121,
"pooledtx" : 2877,
"testnet" : false
}
September 19, 2013, 08:11:20 AM
# 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
{
"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?
September 19, 2013, 08:02:43 AM
# 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
{
"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?
September 19, 2013, 07:47:39 AM
# 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
{
"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
Jump to: