what is worse, is that the dev premined, changed the code, and check in the code in github without any trace of premine:int64 static GetBlockValue(int nHeight, int64 nFees)
{
int64 nSubsidy = 25 * COIN;
if(nHeight < 90)
{
nSubsidy = 0 * COIN;
}
else if(nHeight < 180)
{
nSubsidy = 1 * COIN;
}
else if(nHeight < 270)
{
nSubsidy = 2 * COIN;
}
else if(nHeight < 360)
{
nSubsidy = 3 * COIN;
}
else if(nHeight < 450)
{
nSubsidy = 6 * COIN;
}
else if(nHeight < 540)
{
nSubsidy = 8 * COIN;
}
else if(nHeight < 630)
{
nSubsidy = 12 * COIN;
}
else if(nHeight < 720)
{
nSubsidy = 15 * COIN;
}
else if(nHeight < 810)
{
nSubsidy = 18 * COIN;
}
else if(nHeight < 900)
{
nSubsidy = 22 * COIN; Now, how can you explain the 1.2+ million coins premine shown by the start block explorer? 
Clearly, the dev premined 1.2+ million coins, then remove the traces in the code, check the code in github, and cheated everyone in the forum, what a shame!!! wow, how dirty this is! people on purpose cheating now, this is unbelievable. Before when premine, people at least say something like "this is for bounty", etc etc  |
|
|
|
I wish I will have that much, lol
I wish too, lol. This is a "look-rich" coin.  |
|
|
|
|
Add4H86Zn94Z2HespH7bA82EBXEmwpw2aa
thanks.
|
|
|
|
|
old client still works right? I like this coin.
|
|
|
|
|
it is a fail, not the right mentality...oh man
|
|
|
|
People just take advantage of other people's work, without even recognize it! |
|
|
|
IT WON'T WORK!
if you'll make "random" block rewards - all other clients won't be able to verify block and chain will be split.
say on block 1500 we have 100 "nodes" in network:
node 1 calculates next block to be 2 coins
node 2 calculates next block to be 3 coins
node 3 finds a block but calculated it to be 5 coins.
this way node 1 and node 2 won't ever "confirm" block found by node 3.
only nodes that calculated this block to be 5 coins will confirm.
Same thing will happen with all other blocks.... and coin will die.
heard "deterministic randomness", lol |
|
|
|
facepalm 1:
why not calculate nSubsidy in a simpler way?
int64 nSubsidy = 5 * COIN;
if(rand < 20000)
nSubsidy = 1 * COIN;
else if(rand < 40000)
nSubsidy = 2 * COIN;
else if(rand < 60000)
nSubsidy = 3 * COIN;
else if(rand < 80000)
nSubsidy = 4 * COIN;
//or is it possible, that generateMTRandom returns something greater than 100000, and the subsidy remains 0, lol
facepalm 2:
why not calculate it even simpler?
int64 nSubsidy = generateMTRandom(seed, 100000) / 20000 + 1;
//i suppose generateMTRandom returns a pseudorandom integer from 0 to it's second argument - 1, inclusive
facepalm 3:
why not calculate it even simpler?
int64 nSubsidy = generateMTRandom(seed, 5) + 1;
facepalm 4:
subsidy of a block is known, once the previous block is found. What could be better for forkhoppers?
generateMTRandom function is created by the JKC, make sure you guys when using it put the proper copyright there. |
|
|
|
Thanks for making it clear dreamhouse. And yes, that's what happen, instamining. I see the flaw now, and that the code need to be reviewed.
thanks for your positive altitude |
|
|
|
sounds like an interesting game, will try it. fish, how's your coin going?  |
|
|
|
another instamine candidate, lol |
|
|
|
this is the worst coin I've ever seen, can't you explain what happened to the 9000 blocks??
If you read the whole thread you will notice that it was typed wrong by me, and I corrected it. The 9000 blocks where mined within few hours/days after the release. A blockexporer will soon be up, and you can see the datestamps yourself. Here it is:
what a liar. Only half day (or less), that 9000+ blocks are gone?? premined? instamined? it's a crap..
Sorry, typed a bit fast there. post is updated. On the launch it was only 1000 premined. Now it's more since people have been mining a day. The retargeting is at 420 blocks, not 420 blocks per day. Thanks for noticing and sorry for the confusion. See https://github.com/Anoncoin/anoncoin/blob/master/src/main.cpp#L845 for more deep-info. It is not the typo thing. From your code the block time is 3.42 min, and per day there are 24*60 / 3.42 = 420 blocks, there's nothing wrong there. You still did not answer what happened to the 9000 blocks?? PREMINED!!  Arlington, I agree with you, this is the worst coin I ever seen too. I went through some code, it is evidently done by a novice programmer: static const int64 nTargetTimespan = 420 * 205.2; // Anoncoin: 420 blocks
static const int64 nTargetSpacing = 3.42 * 60; // Anoncoin: 3.42 minutes
static const int64 nInterval = nTargetTimespan / nTargetSpacing; The novice programmer tries to assign a float (3.42 * 60 = 205.2) to an integer, he apparently did not know the value of nTargetSpacing is 205 and not 205.2. Magically, with the rounding, he still get 420 blocks per retarget. Then the dev starts to play cool: int64 nActualTimespanMax = ((nTargetTimespan*99)/70);
int64 nActualTimespanMin = ((nTargetTimespan*70)/99);
instead of using the factor 4 in the original Litecoin code, the dev used sqrt(2) as the factor of adjustment. In normal coins, the initial diff adjustment is big, usually at least by a factor of 128. Even with 4 it caused a lot of instaminings. That's why coins like Luckycoin etc added accelerated diff adjusting (using a factor much bigger than 4). With this stupid sqrt(2), it slows 4 times the diff adjustment even compared to Litecoin. To make 128 times adjustment, it needs 14 retargets: (sqrt(2))^14 = 128. The retarget time for this coin is 3.42 min * 420 = 24 hrs. This means that this coin needs 14 block days to adjust its diff to a level that is comparable to its design! What a fail! this will cause huge instaminings in between, and make this coin completely useless. So Arlington, the 9000 blocks missing could be premined, or instamined, we can see it in blockbrowser. but in any case, this coin is completely worthless. I am sure there will be other code glitches, but I have no interests to do debugging and code review there, lol |
|
|
|
lol, let me also restore my post there, what a crap! [Quote from: iANDROID on June 07, 2013, 10:53:45 PM] {
"version" : "v0.4.0.0-g32a928e-beta",
"protocolversion" : 60005,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 0,
"moneysupply" : 0.00000000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : 0.00024414,
"testnet" : false,
"keypoololdest" : 1370645633,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."
}
Change BitBar logo next time! What? does this guy know what he's doing? don't bother to change the checkpoints? and put a trojan in the client? man, the world is big, and we find all kinds cheaters, lol |
|
|
|
|
this is a good coin, fast and stable
|
|
|
|
'Premined 1,000 coins for bounties' would be a huge Lol  lol |
|
|
|
|
RLCDEoYUgFSmrYyDdHWKm3Y8mzdu229PzL
thanks
|
|
|
|
|
this one seems dead, but I don't get why some dead ones like AMC, HYC went to exchange, what a joke!
|
|
|
|
|
RLCDEoYUgFSmrYyDdHWKm3Y8mzdu229PzL
|
|
|
|
Funny coin to mine! At least the gui of the qt client is somewhat different, refreshing  yes that mining logo has added some color, looks good |
|
|
|
|
Show Posts
