Topic: [ANN][GRA] Graincoin - New PoW/PoS coin | Fast, secure | Version 1.5 Released! - page 101. (Read 177059 times)

I think everyone just loves it so much were all keeping it. 

is there any trading site or thread for this coin yet ?

is there any trading site or thread for this coin yet ?

im enjoying the low diff, soon as it hits cryptsy, coinmarketcap, coinwarz, and coinex the diff will be 50-250.  Load your silos now while you still can.

Don't know ?

Did YOU copy n paste/ code this coin ?

If not, then who ?

Lol wish this could be traded already i mean this is older then most the newer coins and its still not on an exchange...

The diff adjusting code for Grain is the standard one from PPCoin, which is used by most pow/pos coins (with a few exceptions, such as Galaxycoin):


When there are a lot of pos blocks, the pow block can be generated slower, but this is the normal behavior. The algorithm side I don't see issues. But sometimes I see the block time is out of sequence. This probably the reason why sometimes we see the diff behave very strangely. I don't know why/how the block time can become incorrect, maybe some network clock issue? I don't know now.

BTW, I saw some other pow/pos coin behave the same. For example, a few weeks ago, when I tried to mine Lucky7Coin, I see its diff very low, apparently the pos diff, and when I look into somewhat details, I found that the block time is completely wrong, which caused the diff adjusting algorithm to give wrong diffs (it has the same diff algo as PPCoin, I think).

Lol wish this could be traded already i mean this is older then most the newer coins and its still not on an exchange...

When there are a lot more pos blocks, the pow interval increases, this is in the algo:
the target pow can go to as high as 12X normal. But that's very rare, you need something like at least 12 pos generated in between pow blocks.

The reason for this algo is to maintain the network not overly busy which could cause orphan issues. While there are less pos generated, pow returns to its normal target of 30sec.

maybe some network clock issue? I don't know now.

AND, can I have a question ?

in transaction windows, there are some coin addressed,
I guess it is address for the minded coin.
I have two addresses,
actually, it is keep change when get the mined coin.
Can I know what is this address ?

Actually, today (from 4-6 hours ago),
It become very stable,
and the ratio between PoW and PoS,
the number of PoW block is much higher than PoS,
but, number of transactions between PoW and PoS are similar.
and PoW block time is between 30~40s
and Coinage is increased from 3.x to 4.x (because of PoW blocks are too much now?)
 
I feel,
when PoS blocks have generated too much,
the PoW block time suddenly streched 15-20 minutes,
and, Diff also shasking so much, 

Maybe when retarget Diff,
need to use some kind of linear interpolation.
At least,
miner will see the actual Diff,
and Hashrate.
if just use the timer gap betwen block (PoW and PoS mostly),
it should be happen mostly,

I have started the mining with 2Mh/s in the morning (after capture the screen)
I have got 4 accepted, 2 rejected, and 2 stales over 3 hours,
and than, I have stopped for two hours,
I got 5 acceptance, 0 rejected, and 0 stale over 2 hours (now)

Maybe I have to run more longer time frame to findout,

and coinblockchain.com/grain is not updating the block information from 300 blocks ago.


AND, can I have a question ?

in transaction windows, there are some coin addressed,
I guess it is address for the minded coin.
I have two addresses,
actually, it is keep change when get the mined coin.
Can I know what is this address ?

Anyway, Thank you for much for your answers

int64 nTargetSpacing = fProofOfStake? nStakeTargetSpacing : min(nTargetSpacingWorkMax, (int64) nStakeTargetSpacing * (1 + pindexLast->nHeight - pindexPrev->nHeight));

unsigned int GetNextTargetRequired(const CBlockIndex* pindexLast, bool fProofOfStake)
{
    CBigNum bnTargetLimit = bnProofOfWorkLimit;

    if(fProofOfStake)
    {
        bnTargetLimit = bnProofOfStakeLimit;
    }

    if (pindexLast == NULL)
        return bnTargetLimit.GetCompact(); // genesis block

    const CBlockIndex* pindexPrev = GetLastBlockIndex(pindexLast, fProofOfStake);
    if (pindexPrev->pprev == NULL)
        return bnTargetLimit.GetCompact(); // first block
    const CBlockIndex* pindexPrevPrev = GetLastBlockIndex(pindexPrev->pprev, fProofOfStake);
    if (pindexPrevPrev->pprev == NULL)
        return bnTargetLimit.GetCompact(); // second block

    int64 nActualSpacing = pindexPrev->GetBlockTime() - pindexPrevPrev->GetBlockTime();

    CBigNum bnNew;
    bnNew.SetCompact(pindexPrev->nBits);
    int64 nTargetSpacing = fProofOfStake? nStakeTargetSpacing : min(nTargetSpacingWorkMax, (int64) nStakeTargetSpacing * (1 + pindexLast->nHeight - pindexPrev->nHeight));
    int64 nInterval = nTargetTimespan / nTargetSpacing;
    bnNew *= ((nInterval - 1) * nTargetSpacing + nActualSpacing + nActualSpacing);
    bnNew /= ((nInterval + 1) * nTargetSpacing);

    if (bnNew > bnTargetLimit)
        bnNew = bnTargetLimit;

    return bnNew.GetCompact();
}

mkimid, thanks for your detailed analysis. I will do some more investigation and report back here.

Hi, Bosian

How are you ?
I have capature a screen to explain what is happening now.

1. I am living in NJ, USA : EST TIME ZONE
    so, Please, just compare the minutes and seconds only (not hours)

2. in BFGMiner Screen
    The network speed is going up, and hit Diff 4
    and, keep couple of hours,
    and than, it is going down to Diff 1
    and, this process is keep doing again
    This kind of pattern is happen always, my means, each block will have the difference Diff,
    and, It affect on reject (?, maybe, I am not sure, just guess)
    and, it affect on stale (my means, the keep chaing of time... anyway, sorry for too stupid idea)

3. The networkhashs from Grain-QT 1.2 (actually, 1.1 also same)
    at block #60327,
    at block #60328,
    The hash rate has been decreased dramatically, and Diff also have been changed.
    Technically, something wrong
    it is hard to believe the actual network speed is changed like this

4. Check the time between Grain-QT 1.2 and Minder
    * I have used 1s scan time, and 1s logging time for miner
    * I have put, getminerinfo every 10 seconds, to find the changing point
    -> Actually, Miner Detect the change of diffculty much earler than QT
    -> The changing point from 4 to 1
         (in Miner)  xx:08:08
         (in QT)      xx:08:53
    -> I have thought, need one more block to update the current hashrate in QT, yes, it is right,
         but, sometime, it is happen over couple of blocks (After couple of new block detected on network message)
      
Anyway, I am not sure, what is the problem,
maybe, It is just my computer problem,
or maybe, it is just my network problem,
But, only happen in GrainCoin
I have tried to with QT1.1/1.2, Actually, when blockchain explorer has recovered, I have tracked block chains,
and, I found it is matched

and, I feel, there are too many PoS blocks via PoW
(the diff on screen and actual diff is too much difference and growing more and more)
I know it is a technical choice, but,
it makes less attactive for this coin for mining.
In fact, it is why there is not many miners interest on mining PoW/PoS type even it is much more advanced but too early to accepted in this area
(just my person opinion)




p/s : sorry for bothering you again, I like graincoin too much ~ that is why I have too many stupid question, please forgive me.

The fact, You are right absolutely, it is NOT PoS Only coin.
The reality, Did you checked the ratio between PoS and PoW ?

and,

Most important thing, This coin must have a kind of attractive things to the miner,
When this coin became more popular (much more miner)
It will have a chace to become a real market (become a real coin).
 
I believe, this coin is the one of best coins, I have no doubt,
but, I am thinking & thinking about "this coin is the one what the miner want to mine it"

more fud, the thread you listed is from the original giveaway, no one has posted in 8 days in that thread, the message reflects the attack/fork.

the coin is not PoS only, no more fud plz.