Topic: Dash - Is this code as damning as it looks or nothing out of the ordinary? - page 2. (Read 1543 times)

The only thing damning about this whole post is that people just fall so easily for troll posts like these. It is like those bait articles you find on the internet
that just serve to trick people into reading them and they pretty much always are a big waste of time.

* point 1 : official Dash github is found here --> https://github.com/dashpay/dash

I will let that sink in for awhile, for the more slower trolls on this thread

* point 2 : the code that is referred to in this thread is for Testnet



Which means OP is making us read a post about code from 2014, ment for Testnet (which obviously need to have other conditions then Mainnet).
In other words this is all a big waste of time.

Come on guys, i know you are all worried sick about Dash catching up and all, but when you want to troll at least try to troll with some class.

so Evan had planned already for his coin..when did "the plan" become a plan? 2 days after the launch? i believe the plan was a plan waaaay back.

he showed the plans a month after he said he had plans..delayed it on purpose for the accumulation with his friends.


Even after the instamine, accumulation, fork from 84 million to 21 million supply

Evan still putting the masternode specifics under the rug so he and his friends can further accumulate dash.


I provided the link between Evan's January 20, 2014 post to February 21, 2014 post, showing what he had in mind all along..

you see it is not about the instamine all alone, it is about the whole story, what was in Evan's mind the whole time 

Can't speak about this specific bit of code but the general premine issue is known and was well known from the time Dash was called Darkcoin. it has been been a topic thoroughly discussed, especially by the bitcoin community.

This is what the Dev had to say after being criticized years ago: https://archive.fo/QdhCh


Relevant bitcointalk thread https://bitcointalksearch.org/topic/why-the-darkcoindashdashpay-instamine-matters-999886

---------------------------------------------------------------------------------------------------------------------

Here ch you may find this interesting


https://github.com/vertoe/darkcoin_subsidy/blob/master/darkcoin_subsidy.cpp

Code:
double ConvertBitsToDouble(unsigned int nBits)
{
int nShift = (nBits >> 24) & 0xff;
double dDiff =
(double)0x0000ffff / (double)(nBits & 0x00ffffff);
while (nShift < 29)
{
dDiff *= 256.0;
nShift++;
}
while (nShift > 29)
{
dDiff /= 256.0;
nShift--;
}
return dDiff;
}
Code:
long long static GetBlockBaseValue(int nBits, int nHeight, bool fTestNet = false)
{
double dDiff = (double)0x0000ffff / (double)(nBits & 0x00ffffff);
/**
  * Stop instamine (easy difficulty) at block # 4500. - JC
  */
if(nHeight > 4500) dDiff = ConvertBitsToDouble(nBits);
else
/**
  * Return the (instamine) easy difficulty. - JC
  */
This should be quite clear on what Evan did, he corrupted the value of the bits to return an "easy difficulty" then once he got enough coins he stopped it @ block # 4500. ANY testing would have shown this bug prior to launch as it would have very fast block timing. It was 100% "by design".

https://explorer.dash.org/block/000000000c260a60825cafb0ca292fa5cbd6d2b655ca59ebc7ca895aec54c183

You'll notice all blocks before 4500 are extremely close in timing, not 2.5 mins as advertised.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------



What is this? clear real coded in evidence for the premeditated captive instamine or just someones interpretation of deliberate instamine measures in the code?

If this is as clear as this person sees it then how has it taken this long to come to light?

coders opinions only please else we are just guessing....

Was this code released on the main net of xcoin and removed or edited later or was it never released and was only a test net bug?