[ANN] RISKCOIN - Scrypt - Bittrex - More to come...

[placebo]

If everyone closes his wallet and stops staking for an hour, we'll see if those PoW blocks get generated again.

I think you are 100% right. There is nothing wrong with the coin, there are just a lot of POS blocks. Of course when now suddenly people stop mining then the difficult will be so high to find that block and it will even take longer to find the next POW block.

[doeboy1023]

Last blocks found on our pools was an hour ago.

Eeeek!!! I still have 2.5 hours left on my rental...in your opinion what coin should I point it at for the time being?

point it to http://hansa.manhattanmine.com theyre still paying 200 per block.

Done.. Thank you!

[raveneye]

PoW is effectively over.  There is a bug in GetNextTargetRequired which creates negative targets for PoW blocks which are not allowed in CheckProofOfWork when the block is submitted.  This was triggered by 10 PoS blocks in a row with no PoW blocks.

Code:

    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);

nTargetTimespan is hard coded to be 15 * 40 = 600.
nTargetSpacing is being set to nTargetSpacingWorkMax which is 12 * nStakeTargetSpacing = 720.
nInterval = 600 / 720 = 0 (because it is defined as an int, it is rounded down to 0)
    bnNew *= ((0 - 1) * nTargetSpacing + nActualSpacing + nActualSpacing);  <<< From this point on, bnNew is negative because it is multiplied by -1

CreateNewBlock assigns nbits to a negative target. 

ProcessBlock will never accept the block because the CheckBlock fails when it calls CheckProofOfWork.
Altering the nbits won't work because ProcessBlock will fail when it calls AcceptBlock and nBits != GetNextTargetRequired.

[tm2013]

PoW is effectively over.  There is a bug in GetNextTargetRequired which creates negative targets for PoW blocks which are not allowed in CheckProofOfWork when the block is submitted.  This was triggered by 10 PoS blocks in a row with no PoW blocks.

Code:

    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);

nTargetTimespan is hard coded to be 15 * 40 = 600.
nTargetSpacing is being set to nTargetSpacingWorkMax which is 12 * nStakeTargetSpacing = 720.
nInterval = 600 / 720 = 0 (because it is defined as an int, it is rounded down to 0)
    bnNew *= ((0 - 1) * nTargetSpacing + nActualSpacing + nActualSpacing);  <<< From this point on, bnNew is negative because it is multiplied by -1

CreateNewBlock assigns nbits to a negative target. 

ProcessBlock will never accept the block because the CheckBlock fails when it calls CheckProofOfWork.
Altering the nbits won't work because ProcessBlock will fail when it calls AcceptBlock and nBits != GetNextTargetRequired.

Well, at least PoS works.. I think the community should vote to keep PoS going like this or fork and continue with PoW until the original block target.

[padrino]

PoW is effectively over.  There is a bug in GetNextTargetRequired which creates negative targets for PoW blocks which are not allowed in CheckProofOfWork when the block is submitted.  This was triggered by 10 PoS blocks in a row with no PoW blocks.

Code:

    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);

nTargetTimespan is hard coded to be 15 * 40 = 600.
nTargetSpacing is being set to nTargetSpacingWorkMax which is 12 * nStakeTargetSpacing = 720.
nInterval = 600 / 720 = 0 (because it is defined as an int, it is rounded down to 0)
    bnNew *= ((0 - 1) * nTargetSpacing + nActualSpacing + nActualSpacing);  <<< From this point on, bnNew is negative because it is multiplied by -1

CreateNewBlock assigns nbits to a negative target. 

ProcessBlock will never accept the block because the CheckBlock fails when it calls CheckProofOfWork.
Altering the nbits won't work because ProcessBlock will fail when it calls AcceptBlock and nBits != GetNextTargetRequired.

That stings... What are your thoughts on the recourse, in short is PoW done and that is that, is PoS working properly at least?

[scorpio18]

Hmm , i see on my stratum that the daemon refusing the blocks found and my wallet started to stake even if i have on my conf file staking=0 so any news from the dev about this


EDIT: I just stoped the stratum on coinminers pool until dev fix this

[Mr.Joker]

Dev needs to fork the coin or decide whether stop PoW and continue in PoS

Easiest is to just edit coin specs and continue PoS

[riskcoin]

Dear Community,

There is indeed a bug  . This is sad as this will mean that i have to fork the coin. I will let the community decide if we will fork the coin or if i'll adjust the coin specs.

[bitkokos]

Question.
ANN was writing there will only be 250000 risk coins
We have
75000 ico from block 1
28800 till block 2880
57600 till block 5760
86400 till block 11520

Total is 247800

How does this coin have 50% PoS?
In one year there will be around 375000 coins

Dev, would you mind clarifying this please?

[riskcoin]

Question.
ANN was writing there will only be 250000 risk coins
We have
75000 ico from block 1
28800 till block 2880
57600 till block 5760
86400 till block 11520

Total is 247800

How does this coin have 50% PoS?
In one year there will be around 375000 coins

Dev, would you mind clarifying this please?

That was the original spec. Currently there is a little bug in the code that will either fix it by a fork or the coin specs will be modified to represent the current situation. I have added a pool so community has to decide.

[Mr.Joker]

Dear Community,

There is indeed a bug  . This is sad as this will mean that i have to fork the coin. I will let the community decide if we will fork the coin or if i'll adjust the coin specs.

Fork it.

That's the most fair and honest thing.

Fork it quickly, because the longer you will wait, the more damage to the coin.

[jc12345]

How long does it take for staking to begin - 24h? Wallet has been unlocked for the whole day and there is no indication like "you do not have mature coins" or "your weight is x and network is y". Normally there are indicators in a wallet that tells you you are staking successfully and what the current attributes are.

[Mr.Joker]

Question.
ANN was writing there will only be 250000 risk coins
We have
75000 ico from block 1
28800 till block 2880
57600 till block 5760
86400 till block 11520

Total is 247800

How does this coin have 50% PoS?
In one year there will be around 375000 coins

Dev, would you mind clarifying this please?

50% inflation would mean that every coin is staking 24/7.

In real life, probably <25% will stake and not even 24*7

[Mr.Joker]

How long does it take for staking to begin - 24h? Wallet has been unlocked for the whole day and there is no indication like "you do not have mature coins" or "your weight is x and network is y".

After 24h coins will be mature enough. It doesn't mean you will find PoS block directly.

You are not the only one that is staking. It's also a factor of having luck

[jc12345]

How long does it take for staking to begin - 24h? Wallet has been unlocked for the whole day and there is no indication like "you do not have mature coins" or "your weight is x and network is y".

After 24h coins will be mature enough. It doesn't mean you will find PoS block directly.

You are not the only one that is staking. It's also a factor of having luck

I know what staking is and how it works. I could not find any indicators in the wallet to tell me that it is staking or the conditions preventing it from staking. I just thought that perhaps with this coin there are some other additional steps to take before the wallet gives you the status and then just waiting for coins to mature after that.

[bitkokos]

what will fork do in this case?

[Mr.Joker]

what will fork do in this case?

Install new wallet, and PoW continues from a certain block. That's the most easy thing I guess.

[doeboy1023]

I vote, change specs. From an investment standpoint, It cant hurt to have less initial supply...correct me if I'm wrong.

[doeboy1023]

I vote, change specs. From an investment standpoint, It cant hurt to have less initial supply...correct me if I'm wrong.

But before you do that let me know so I can go buy some up real quick lol.

[hayan]

I vote, change specs. From an investment standpoint, It cant hurt to have less initial supply...correct me if I'm wrong.

It's kind of a "fuck you" to people who've got rented rigs that they were pointing at this, though. I'm in support of just ending it, but there again, I'm done with mining so I kind of benefit from that decision anyway... but it also keeps things simpler, too.