Topic: [ A N N ] RedOakCoin::{ R O C } Scrypt Currency By: RedOakIndustries [ R O I ] - page 9. (Read 16207 times)

I hope the assholes go away soon - best of luck...

see my signature....

What other pool this is the only one??

read the thread - its all explained - it's a great time to get these coins before they get listed on a MAJOR exchange

launched at yesterday , but now at 9052 block , WTF 

I followed the directions in the opening post too,now is ok.

I followed the directions in the opening post for the windows wallet and it synched fine

still not sync

Hey, try this:

Yes, Out of sync here also!!

out of sync. Is there any node?

Hi,guys, you are doing a great job. Leading ROC to the top 50. 

Still so tired all!

ROC-QT Signature Security Check 001 @ 1410739203 [EpochTime]
http://i.imgur.com/mAE2pLz.png

I feel bad, I will catch up with everything soon; including Cryptocointalk! I'm still so tired!

LOL

1.5 Day(s) Re-Target Time

Today 64

tomorrow = 7 ;-)

waiting for the next Day ;-)

difficulty is going to rise dramatically soon - there has never been a better opportunity to mine than now.

I am not complaining about missing the ninja launch...
Blocks are just arriving too fast for what the OP claims, that's my point. Hence why we pass on it. We are not the top pool nor claim to be.

Sorry all for the delay. We all have been up for over 24 Hours This project was a long while in the making. Though it may seem easy for people to make mistakes, I would like to bring your attention to our Main.cpp Source Code situated on our GitHub page: https://github.com/RedOakCoin/RedOakCoin

static const int64 nDiffChangeTarget = 17280; //initiate 'Rolling Roc' @
static const int64 patchBlockRewardDuration = 1; //per block decay

int64 GetROCSubsidy(int nHeight)
{
    // Special thanks to P.B. for working out a truly unique and stable decay function
    int64 qSubsidy = 115.0 * COIN;
    int blocks = nHeight - nDiffChangeTarget;
    int weeks = (blocks / patchBlockRewardDuration)+1;                       //can int64 qSubsidy handle this with out a double handle
    for(int i = 0; i < weeks; i++)  qSubsidy -= (qSubsidy * 0.00000164847); //decrease reward by calculated amount 0.00016%
    return qSubsidy;
}


int64 static GetBlockValue(int nHeight, int64 nFees) {
    int64 nSubsidy = COIN;

    if(nHeight < nDiffChangeTarget) {
        //this is PreDecay Subsidy Value, reward is 129.53
        nSubsidy = 129.53 * COIN;
    } else {
        //takes effect after 17280 blocks
        nSubsidy = GetROCSubsidy(nHeight);
    }

    // ( @REM -> UsageID: 0078659 )
    //if(nSubsidy < COIN) {
    //  nSubsidy = COIN;
    //}

    return nSubsidy + nFees;
}


int nTargetTimespan = 1.5 * 24 * 60 * 60; // 1.5 days
int nTargetSpacing = 2.5 * 60; // 2.5 minutes

Naturally, this is what we, the RedOakCoin Devs., have stated in the OP.

We chose to base our Scrypt Coin after one of the first coins I ever miner, https://www.feathercoin.com/, it was their brilliant code and advanced security checkpointing system that has, and will continue to help us realize our goals with RedOakCoin & RedOakIndustries.

Inside of their custom, uniqueunsigned int static GetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHeader *pblock) function

int nInterval = nTargetTimespan / nTargetSpacing;

    if(nInterval >= nHeight) nInterval = nHeight - 1;

// Go back by nInterval
    const CBlockIndex* pindexFirst = pindexLast;
    for(int i = 0; pindexFirst && i < nInterval; i++)
      pindexFirst = pindexFirst->pprev;
    assert(pindexFirst);

    int nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();

    printf("RETARGET: nActualTimespan = %d before bounds\n", nActualTimespan);

This means that the difficulty adjustments you are seeing are minor changes as per-the above stated code; this code, to those who are less adapted to reading C++ can be viewed as a KimotoGravityWell of sorts, but more customized.

After the natural 1.5 days, there will be the natural triggered difficulty adjustment. Honestly, we were not expecting this many people at this rate to jump on all at once. My partner looks at me and says, "We should have pre-mined."

But really, if it wasn't forjjj0923 & pool-darktech a year's worth of work would have made the people of Bitcointalk very wealthy. They saved the Coin and my Team's compensations from my personal 40MH/s. farm. I look forward to keeping their pools on as the Official RedOakCoin Pools.

What am I doing wrong? I'm getting an overwhelming number of rejected shares

your sarcastic comment seems to insinuate that suchpools is somehow the epitomy of mining pools and that they're missing out on something since you pool has chosen not to participate

no need to be so cavalier...

being so negative because it was a ninja launch and you're missing out on several gh/s is no reason to slam these guys.

judging from the network hash my guess is that they're doing just fine without your pool.

I just happened to be up and online getting another pool ready when they announced their coin - lucky for me I guess and that was good since I have to go to an in-laws funeral this afternoon so good news was welcome today.

Regardless of how cool you think you are, there is definately a flaw in the code. 8000 blocks at 2.5 minutes time just can't happen within that short amount of time. Also I never mentionned premining, nor looking to ninja everything up here.

Sometimes it's better to sit back and wait to see how it pans out before rolling it You'll get that overtime.

At least a recognition of the issue by the developpers would be a honest start.