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

doeboy1023

member

Activity: 90

Merit: 10

Quote from: hayan on February 24, 2015, 03:08:40 PM

Quote from: doeboy1023 on February 24, 2015, 03:06:49 PM

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.

Agreed, but if they were quick to re direct their miners, they can mine something else to recover some of their rental losses, and the initial coins they mined will be worth much more to begin with.

Mr.Joker

hero member

Activity: 868

Merit: 1000

IMO it depends on in which timeframe does the dev thinks he can fix the issue.

if it takes too long, then we can just continue POS

hayan

newbie

Activity: 56

Merit: 0

Quote from: doeboy1023 on February 24, 2015, 03:06:49 PM

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.

doeboy1023

member

Activity: 90

Merit: 10

Quote from: doeboy1023 on February 24, 2015, 03:06:49 PM

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.

doeboy1023

member

Activity: 90

Merit: 10

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

Mr.Joker

hero member

Activity: 868

Merit: 1000

Quote from: bitkokos on February 24, 2015, 03:02:28 PM

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.

bitkokos

hero member

Activity: 490

Merit: 500

0_0

what will fork do in this case?

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: Mr.Joker on February 24, 2015, 02:57:42 PM

Quote from: jc12345 on February 24, 2015, 02:56:01 PM

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.

Mr.Joker

hero member

Activity: 868

Merit: 1000

Quote from: jc12345 on February 24, 2015, 02:56:01 PM

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

Mr.Joker

hero member

Activity: 868

Merit: 1000

Quote from: bitkokos on February 24, 2015, 02:52:21 PM

Quote from: bitkokos on February 23, 2015, 07:23:20 PM

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

jc12345

legendary

Activity: 1638

Merit: 1013

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

hero member

Activity: 868

Merit: 1000

Quote from: riskcoin on February 24, 2015, 02:50:11 PM

Dear Community,

There is indeed a bug Cry

. 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.

riskcoin

newbie

Activity: 56

Merit: 0

Quote from: bitkokos on February 24, 2015, 02:52:21 PM

Quote from: bitkokos on February 23, 2015, 07:23:20 PM

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.

bitkokos

hero member

Activity: 490

Merit: 500

0_0

Quote from: bitkokos on February 23, 2015, 07:23:20 PM

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

newbie

Activity: 56

Merit: 0

Dear Community,

There is indeed a bug Cry

. 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.

Mr.Joker

hero member

Activity: 868

Merit: 1000

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

scorpio18

legendary

Activity: 1722

Merit: 1000

Admin of CoinMiners Pools

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

padrino

legendary

Activity: 1428

Merit: 1000

https://www.bitworks.io

Quote from: raveneye on February 24, 2015, 02:01:47 PM

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?

tm2013

hero member

Activity: 644

Merit: 500

Quote from: raveneye on February 24, 2015, 02:01:47 PM

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.

raveneye

full member

Activity: 122

Merit: 100

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.

Topic: [ANN] RISKCOIN - Scrypt - Bittrex - More to come... - page 39. (Read 53003 times)