[ANN] DustCoin DUST 100% PoS Yobit ICO (v1.2)

[Brob12321]

Why is everyone saying that the stake rate is 1000% when it clearly says on the ann that the stake rate is 100% ??

[DustCoinDev]

Why is everyone saying that the stake rate is 1000% when it clearly says on the ann that the stake rate is 100% ??

Because its 1000% from block 23200 to 26400

[Brob12321]

Why is everyone saying that the stake rate is 1000% when it clearly says on the ann that the stake rate is 100% ??

Because its 1000% from block 23200 to 26400

Ohh I see now lol so what the users aren't getting the stated stake rates then ?

[DustCoinDev]

Why is everyone saying that the stake rate is 1000% when it clearly says on the ann that the stake rate is 100% ??

Because its 1000% from block 23200 to 26400

Ohh I see now lol so what the users aren't getting the stated stake rates then ?

Thats right, but I think I've found it already.

[Brob12321]

Oh good, hopefully the fix comes soon as the 1000% rate only lasts for 51.7 more hours if my calculations are correct.

[DustCoinDev]

Oh good, hopefully the fix comes soon as the 1000% rate only lasts for 51.7 more hours if my calculations are correct.

I might extend it for some time as compensation.

[clarkjhaley13]

I do not see any error in the code:

Code:

int64_t GetProofOfStakeReward(int64_t nCoinAge, int64_t nFees)
{
    int64_t nRewardCoinYear = 10 * COIN;
	
	if (pindexBest->nHeight >= FORK_HEIGHT)
	{
		nRewardCoinYear = nRewardCoinYear * 100;
		?
		if (pindexBest->nHeight <= FORK_HEIGHT+3200)
		{
			nRewardCoinYear = nRewardCoinYear * 10;
		}
	}
	
    int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

    if (fDebug && GetBoolArg("-printcreation"))
        printf("GetProofOfStakeReward(): create=%s nCoinAge=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nCoinAge);

    return nSubsidy + nFees;
}

If I am seeing this right you are missing a bracket where the question mark is. Not a coder per say but seems that way to me.

[DustCoinDev]

I do not see any error in the code:

Code:

int64_t GetProofOfStakeReward(int64_t nCoinAge, int64_t nFees)
{
    int64_t nRewardCoinYear = 10 * COIN;
	
	if (pindexBest->nHeight >= FORK_HEIGHT)
	{
		nRewardCoinYear = nRewardCoinYear * 100;
		?
		if (pindexBest->nHeight <= FORK_HEIGHT+3200)
		{
			nRewardCoinYear = nRewardCoinYear * 10;
		}
	}
	
    int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

    if (fDebug && GetBoolArg("-printcreation"))
        printf("GetProofOfStakeReward(): create=%s nCoinAge=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nCoinAge);

    return nSubsidy + nFees;
}

If I am seeing this right you are missing a bracket where the question mark is. Not a coder per say but seems that way to me.

Thanks, but its not missing a curly bracket. The if statement is nested.

[Brob12321]

that ? still should not be there though lol.  I dont think it affects anything but it is just a random question mark lol

[Lenore]

I do not see any error in the code:

Code:

int64_t GetProofOfStakeReward(int64_t nCoinAge, int64_t nFees)
{
    int64_t nRewardCoinYear = 10 * COIN;
	
	if (pindexBest->nHeight >= FORK_HEIGHT)
	{
		nRewardCoinYear = nRewardCoinYear * 100;
		?
		if (pindexBest->nHeight <= FORK_HEIGHT+3200)
		{
			nRewardCoinYear = nRewardCoinYear * 10;
		}
	}
	
    int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

    if (fDebug && GetBoolArg("-printcreation"))
        printf("GetProofOfStakeReward(): create=%s nCoinAge=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nCoinAge);

    return nSubsidy + nFees;
}

If I am seeing this right you are missing a bracket where the question mark is. Not a coder per say but seems that way to me.

Thanks, but its not missing a curly bracket. The if statement is nested.

you do not need a "?" for a nested statement.  just sayin.

[dag59]

There seems to be a problem...  block generation appears to be stuck at 24547 with the last generated block being several hours ago.....

[kiklo]

There seems to be a problem...  block generation appears to be stuck at 24547 with the last generated block being several hours ago.....

Hmm,

There are not yet enough blocks staking to keep the dust network running at the rated Block time of 100 seconds.
Easy Fix, no one recombine their blocks into only 1 block , let them split every time for the next few days.
Also when withdrawing dust from yobit, split up the amounts so it does not all come down in 1 block.
As the # of blocks increase the network will get closer to its normal network block time.  

This looks like it is going to be a fun coin.

 

[kiklo]

I checked codebase of this coin and found that dev removed check for LAST_POW_BLOCK. It means that this coin still accept PoW blocks. Why it is important?
1) First of all, this coin has risk of double spends(anybody can create chain fork with desired length)
2) Coin uses shared difficulty_retarget and if anybody rent 10Gh(for instance) for 5 minutes to create PoW blocks not only PoW difficulty rises to infinity, but PoS difficulty too and blockchain will be stopped.

I don't know about your 1st statement if PoW mining is possible or not, 
I did just try setgenerate true 4 in the console and it did not work to generate a PoW block,
if there are more commands, please share.

Your line 2 is totally wrong, PoS & PoW difficulty are not shared among any coin, they can't be , there are two independent ways to generate coins.

Same issue with the block freezing happened with PHS a few weeks ago, no big deal , as more blocks are available for staking the network returns to normal speed.   


 
 

[DustCoinDev]

I do not see any error in the code:

Code:

int64_t GetProofOfStakeReward(int64_t nCoinAge, int64_t nFees)
{
    int64_t nRewardCoinYear = 10 * COIN;
	
	if (pindexBest->nHeight >= FORK_HEIGHT)
	{
		nRewardCoinYear = nRewardCoinYear * 100;
		?
		if (pindexBest->nHeight <= FORK_HEIGHT+3200)
		{
			nRewardCoinYear = nRewardCoinYear * 10;
		}
	}
	
    int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;

    if (fDebug && GetBoolArg("-printcreation"))
        printf("GetProofOfStakeReward(): create=%s nCoinAge=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nCoinAge);

    return nSubsidy + nFees;
}

If I am seeing this right you are missing a bracket where the question mark is. Not a coder per say but seems that way to me.

Thanks, but its not missing a curly bracket. The if statement is nested.

you do not need a "?" for a nested statement.  just sayin.

Its not in the code

[DustCoinDev]

I checked codebase of this coin and found that dev removed check for LAST_POW_BLOCK. It means that this coin still accept PoW blocks. Why it is important?
1) First of all, this coin has risk of double spends(anybody can create chain fork with desired length)
2) Coin uses shared difficulty_retarget and if anybody rent 10Gh(for instance) for 5 minutes to create PoW blocks not only PoW difficulty rises to infinity, but PoS difficulty too and blockchain will be stopped.

Your totally wrong about things here

[DustCoinDev]

Mandatory update (Release 1.2.0.0)
Please update before block 25000

This release fixes the stake rate:
Block 25000 to 31400 stake rate 1000%
Block 31401 and greater stake rate 100%

Windows: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0.zip
Linux: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0_linux.zip

[GreenDefender]

Mandatory update (Release 1.2.0.0)
Please update before block 25000

This release fixes the stake rate:
Block 25000 to 31400 stake rate 1000%
Block 31401 and greater stake rate 100%

Windows: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0.zip
Linux: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0_linux.zip

that was lovely fast work, later today we get result ...

btw pls explain this unusual block explorer address:

 #1   dNbdcS2uhDL45yuz12fr6gHCCQpKDPgDED   938278041.42831540 dust   93.83%

[zsnorbi]

Mandatory update (Release 1.2.0.0)
Please update before block 25000

This release fixes the stake rate:
Block 25000 to 31400 stake rate 1000%
Block 31401 and greater stake rate 100%

Windows: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0.zip
Linux: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0_linux.zip

that was lovely fast work, later today we get result ...

btw pls explain this unusual block explorer address:

 #1   dNbdcS2uhDL45yuz12fr6gHCCQpKDPgDED   938278041.42831540 dust   93.83%

That's yobit address i guess

[DustCoinDev]

Mandatory update (Release 1.2.0.0)
Please update before block 25000

This release fixes the stake rate:
Block 25000 to 31400 stake rate 1000%
Block 31401 and greater stake rate 100%

Windows: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0.zip
Linux: https://github.com/DustCoinProject/DustCoin/releases/download/1.2.0.0/dustcoin-qt_1.2.0.0_linux.zip

that was lovely fast work, later today we get result ...

btw pls explain this unusual block explorer address:

 #1   dNbdcS2uhDL45yuz12fr6gHCCQpKDPgDED   938278041.42831540 dust   93.83%

Thats Yobits address

[xadsa418]

I don't know about your 1st statement if PoW mining is possible or not, 
I did just try setgenerate true 4 in the console and it did not work to generate a PoW block,
if there are more commands, please share.

Your line 2 is totally wrong, PoS & PoW difficulty are not shared among any coin, they can't be , there are two independent ways to generate coins.

Same issue with the block freezing happened with PHS a few weeks ago, no big deal , as more blocks are available for staking the network returns to normal speed.   

Yep, you are right.
I still think that blockchain accept PoW blocks, however i missed that GetLastBlockIndex in this coin account on whether block is PoS or PoW. My mistake.
I will delete my previous message because it's partially untrue.

Your totally wrong about things here

Here is comparison of CBlock::AcceptBlock between standart codebase abd yours.
https://www.diffchecker.com/mc8jqidu
Left is yours.
You deleted check for Last_Pow_Block there. Where did wallet restrict PoW blocks?