Network hash rate @ 4.4 GH/s
Difficulty is going to reach about 800
Then they'll jump ship and leave the coin stock on the same block for days
What can be done if this happens?
Devs need to move on this new difficulty algorithm fast.....
It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
Current solution used: PID with 8 block averaging with 20 second dead zone.
Dip of difficulty to 0 denotes catcoind change time.
Last 100 blocks in text.
Slow gains: pGain=-0.005125, iGain=-0.0225, dGain=-0.0075 - When average between 2.5 and 17.5 min.
Fast gains: pGain=-0.005125, iGain=-0.0525, dGain=-0.0075 - When average is outside 2.5 and 17.5 min.
i=0; // Zero bit-shift counter
while(bnNew>0) // Loop while bnNew > 0
{
i++; // Increment bit-shift counter
bnNew = bnNew >> 1; // shift bnNew lower by 1 bit
if(i>256) bnNew = 0; // overflow test, just to make sure that it never stays in this loop
}
bnNew.SetCompact(pindexLast->nBits); // Get current difficulty again
error = nActualTimespan - nTargetSpacing; // Calculate the error to be fed into the PID Calculation
if(error >= -450 && error <= 450) // Slower gains for when the average time is within 2.5 min and 7.5 min
{
pCalc = pGainUp * (double)error; // Calculate P ... pGain defined at beginning of routine
iCalc = iGainUp * (double)error * (double)((double)nTargetSpacing / (double)nActualTimespan); // Calculate I ... iGain defined at beginning of routine
dCalc = dGainUp * ((double)error / (double)nActualTimespan) * iCalc; // Calculate D ... dGain defined at beginning of routine
}
else // Faster gains for block averages > 7.5 minutes or faster than 2.5 minutes
{
pCalc = pGainDn * (double)error; // Calculate P ... pGain defined at beginning of routine
iCalc = iGainDn * (double)error * (double)((double)nTargetSpacing / (double)nActualTimespan); // Calculate I ... iGain defined at beginning of routine
dCalc = dGainDn * ((double)error / (double)nActualTimespan) * iCalc; // Calculate D ... dGain defined at beginning of routine
}
if(error > -10 && error < 10) // 20 second dead zone, between 9:50 and 10:10 minute block average
{
if(fTestNet) printf("Within dead zone. No change! error: %"PRI64d"\n", error);
return(bnNew.GetCompact());
}
dResult = pCalc + iCalc + dCalc; // Sum the PID calculations
result = (int64)(dResult * 65536); // Adjust for scrypt calcuation
while(result > 8388607) result = result / 2; // Bring the result within max range for overflow condition
bResult = result; // Set the bignum value
if(i>24) bResult = bResult << (i - 24); // bit-shift integer value of result to be subtracted from current diff
2014-03-06 20:44:35 pCalc: -1.107000, iCalc: -3.573529, dCalc: 0.007095, Result: -306278 (-4.673435)
2014-03-06 20:44:35 Actual Time: 816, error: 216
2014-03-06 20:44:35 Result: 1ccac660 000000004ac66000000000000000000000000000000000000000000000000000
2014-03-06 20:44:35 Before: 1d0c4a91 0000000c4a910000000000000000000000000000000000000000000000000000
2014-03-06 20:44:35 After: 1d0c9557 0000000c95576000000000000000000000000000000000000000000000000000